<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on DevOps Engineer &amp; CloudAdmin</title><link>https://ruadmin.root.sx/tags/aws/</link><description>Recent content in Aws on DevOps Engineer &amp; CloudAdmin</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><atom:link href="https://ruadmin.root.sx/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS → Another Cloud Migration</title><link>https://ruadmin.root.sx/posts/clouds/migration-from-aws/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ruadmin.root.sx/posts/clouds/migration-from-aws/</guid><description>&lt;h2 id="cloud-infrastructure-migration-from-aws-to-a-cost-optimized-private-cloud"&gt;Cloud Infrastructure Migration from AWS to a Cost-Optimized Private Cloud&lt;/h2&gt;
&lt;hr&gt;
&lt;h4 id="client"&gt;Client&lt;/h4&gt;
&lt;p&gt;Confidential&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="challenge"&gt;Challenge&lt;/h4&gt;
&lt;p&gt;The client needed to migrate their entire AWS infrastructure to an alternative cloud provider to reduce costs and eliminate vendor lock-in. The key requirements were minimal downtime, zero functionality loss, and a reliable rollback strategy.&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="solution"&gt;Solution&lt;/h4&gt;
&lt;h6 id="1-audit--planning"&gt;1. Audit &amp;amp; Planning&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Full inventory of AWS resources (EC2, RDS, S3, VPC)&lt;/li&gt;
&lt;li&gt;Service mapping: AWS → target cloud equivalents&lt;/li&gt;
&lt;li&gt;Phased migration plan with clear milestones&lt;/li&gt;
&lt;li&gt;Rollback strategy for each stage&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="2-infrastructure-preparation"&gt;2. Infrastructure Preparation&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Terraform for IaC on the target platform&lt;/li&gt;
&lt;li&gt;VPC, subnets, and security groups configuration&lt;/li&gt;
&lt;li&gt;Managed PostgreSQL and Redis deployment&lt;/li&gt;
&lt;li&gt;Object Storage setup (S3-compatible)&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="3-data-migration"&gt;3. Data Migration&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Database replication via DMS&lt;/li&gt;
&lt;li&gt;S3 → Object Storage sync&lt;/li&gt;
&lt;li&gt;Docker image transfer to private Container Registry&lt;/li&gt;
&lt;li&gt;Full validation on staging environment&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="4-production-cutover"&gt;4. Production Cutover&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;DNS failover for gradual traffic switching&lt;/li&gt;
&lt;li&gt;Real-time metrics monitoring during cutover&lt;/li&gt;
&lt;li&gt;AWS kept on standby for emergency rollback&lt;/li&gt;
&lt;li&gt;Final cutover completed in 2 hours&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h4 id="technologies"&gt;Technologies&lt;/h4&gt;
&lt;div class="row"&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/aws.svg" alt="AWS"&gt;&lt;div&gt;AWS&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/terraform-original.svg" alt="Terraform"&gt;&lt;div&gt;Terraform&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/prometheus-original.svg" alt="Prometheus"&gt;&lt;div&gt;Prometheus&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/grafana-original.svg" alt="Grafana"&gt;&lt;div&gt;Grafana&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/gitlab-original.svg" alt="GitLab CI"&gt;&lt;div&gt;GitLab CI&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;hr&gt;
&lt;h4 id="results"&gt;Results&lt;/h4&gt;
&lt;p&gt;✅ &lt;strong&gt;Cost reduction:&lt;/strong&gt; 40% savings (from $15k to $9k/month)&lt;br&gt;
✅ &lt;strong&gt;Downtime:&lt;/strong&gt; only 2 hours vs. 8 hours planned&lt;br&gt;
✅ &lt;strong&gt;Vendor independence:&lt;/strong&gt; full exit from AWS with no functionality loss&lt;br&gt;
✅ &lt;strong&gt;Performance:&lt;/strong&gt; maintained at the same level post-migration&lt;br&gt;
✅ &lt;strong&gt;Compliance:&lt;/strong&gt; data residency and security requirements met&lt;/p&gt;</description></item><item><title>Geo-Distributed Blockchain Node Cluster in Kubernetes</title><link>https://ruadmin.root.sx/posts/clouds/blockchain-k8s-cluster/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ruadmin.root.sx/posts/clouds/blockchain-k8s-cluster/</guid><description>&lt;h2 id="geo-distributed-blockchain-node-cluster-in-kubernetes"&gt;Geo-Distributed Blockchain Node Cluster in Kubernetes&lt;/h2&gt;
&lt;hr&gt;
&lt;h4 id="client"&gt;Client&lt;/h4&gt;
&lt;p&gt;Cryptocurrency platform (Web3 / DeFi)&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="challenge"&gt;Challenge&lt;/h4&gt;
&lt;p&gt;The client needed fault-tolerant infrastructure to run ETH and BSC full nodes across four regions (EU, US, AP, LatAm) with minimal latency for end users, DDoS and RPC spam protection, secure HSM-based transaction signing, and centralized observability. Cold node sync takes 2–3 weeks — a fast-bootstrap solution was required.&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="solution"&gt;Solution&lt;/h4&gt;
&lt;h6 id="1-infrastructure--iac-terraform--eks"&gt;1. Infrastructure &amp;amp; IaC (Terraform + EKS)&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Terraform modules: VPC, subnets, security groups for 4 regions (Frankfurt, Virginia, Singapore, São Paulo)&lt;/li&gt;
&lt;li&gt;Managed Kubernetes (EKS 1.29+) per region with dedicated node pools: full nodes, archive nodes, signing service&lt;/li&gt;
&lt;li&gt;NVMe StorageClass (gp3) via CSI driver for high-performance chaindata storage&lt;/li&gt;
&lt;li&gt;Helm charts for geth / bsc-node with per-region custom values&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="2-gitops-flux-cd-multi-cluster"&gt;2. GitOps: Flux CD Multi-Cluster&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Flux CD v2 with &lt;code&gt;Kustomization&lt;/code&gt; per region — single source of truth for all clusters&lt;/li&gt;
&lt;li&gt;Secrets management: HashiCorp Vault + External Secrets Operator (ESO)&lt;/li&gt;
&lt;li&gt;All infrastructure changes applied via git push — no direct cluster access required&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="3-load-balancing--anti-spam"&gt;3. Load Balancing &amp;amp; Anti-Spam&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;HAProxy 2.8: sticky sessions, health checks via &lt;code&gt;eth_syncing&lt;/code&gt; — traffic routed only to fully synced nodes&lt;/li&gt;
&lt;li&gt;Nginx Ingress: rate limiting, IP reputation filtering (Lua-based, fail2ban-style)&lt;/li&gt;
&lt;li&gt;Cloudflare Workers: geo-routing + L7 DDoS protection&lt;/li&gt;
&lt;li&gt;Custom Go sidecar: health endpoint returns &lt;code&gt;ready&lt;/code&gt; only when node is fully synced&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="4-hsm-integration-for-transaction-signing"&gt;4. HSM Integration for Transaction Signing&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;AWS CloudHSM (prod) / YubiHSM2 (staging) for private key storage&lt;/li&gt;
&lt;li&gt;Go microservice with PKCS#11 abstraction — swap HSM vendor without rewriting code&lt;/li&gt;
&lt;li&gt;Isolated K8s namespace + NetworkPolicy: no egress except to HSM endpoint&lt;/li&gt;
&lt;li&gt;gRPC API for backend: sign tx, get pubkey&lt;/li&gt;
&lt;li&gt;Full audit log of all signing operations → Loki&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="5-monitoring--alerting"&gt;5. Monitoring &amp;amp; Alerting&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Custom Prometheus exporter (Go): &lt;code&gt;eth_blockNumber&lt;/code&gt;, &lt;code&gt;eth_syncing&lt;/code&gt;, peer count per node&lt;/li&gt;
&lt;li&gt;Grafana dashboards: sync lag, block height per region, RPC latency, SLO 99.9%&lt;/li&gt;
&lt;li&gt;Alertmanager → PagerDuty: alerts on block lag &amp;gt; N blocks, node down, peer count below threshold&lt;/li&gt;
&lt;li&gt;Loki + Promtail: structured logs from all nodes with region/pod correlation&lt;/li&gt;
&lt;/ul&gt;
&lt;h6 id="6-operations--disaster-recovery"&gt;6. Operations &amp;amp; Disaster Recovery&lt;/h6&gt;
&lt;ul&gt;
&lt;li&gt;Snapshot bootstrap: chaindata from S3 via rclone — node ready in hours instead of weeks&lt;/li&gt;
&lt;li&gt;DR playbook: step-by-step runbooks for regional recovery&lt;/li&gt;
&lt;li&gt;Chaos Engineering (Chaos Mesh): node kill, network partition, pod failure tests&lt;/li&gt;
&lt;li&gt;Architecture Decision Records (ADR) for all key design choices&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h4 id="technologies"&gt;Technologies&lt;/h4&gt;
&lt;div class="row"&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/kubernetes-plain.svg" alt="Kubernetes"&gt;&lt;div&gt;Kubernetes&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/terraform-original.svg" alt="Terraform"&gt;&lt;div&gt;Terraform&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/helm-original.svg" alt="Helm"&gt;&lt;div&gt;Helm&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/flux-cd.svg" alt="Flux CD"&gt;&lt;div&gt;Flux CD&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/prometheus-original.svg" alt="Prometheus"&gt;&lt;div&gt;Prometheus&lt;/div&gt;&lt;/div&gt;
&lt;div class="col-4 col-lg-2 pt-2" style="text-align: center;"&gt;&lt;img src="https://ruadmin.root.sx/icons/grafana-original.svg" alt="Grafana"&gt;&lt;div&gt;Grafana&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;hr&gt;
&lt;h4 id="results"&gt;Results&lt;/h4&gt;
&lt;p&gt;✅ &lt;strong&gt;Geo-routing:&lt;/strong&gt; latency reduced by routing users to the nearest region&lt;br&gt;
✅ &lt;strong&gt;Fast bootstrap:&lt;/strong&gt; node ready in hours via S3 snapshot instead of 2–3 weeks of sync&lt;br&gt;
✅ &lt;strong&gt;Anti-spam:&lt;/strong&gt; rate limiting + IP reputation — public RPC handles bot load without degradation&lt;br&gt;
✅ &lt;strong&gt;HSM:&lt;/strong&gt; private keys never leave the hardware module&lt;br&gt;
✅ &lt;strong&gt;GitOps:&lt;/strong&gt; every infrastructure change goes through git with a full audit trail&lt;br&gt;
✅ &lt;strong&gt;SLO 99.9%:&lt;/strong&gt; tracked in Grafana, PagerDuty alerts on any degradation&lt;/p&gt;</description></item><item><title>Self-Hosted Project Management with Plane</title><link>https://ruadmin.root.sx/posts/self-hosted/plane-so/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ruadmin.root.sx/posts/self-hosted/plane-so/</guid><description>&lt;h2 id="self-hosted-project-management-with-plane-so"&gt;Self-Hosted Project Management with Plane So&lt;/h2&gt;
&lt;hr&gt;
&lt;h4 id="client"&gt;Client&lt;/h4&gt;
&lt;p&gt;A company seeking its own project management tool hosted on their office infrastructure&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="challenge"&gt;Challenge&lt;/h4&gt;
&lt;p&gt;The client wanted an open-source alternative to Jira/Linear for project and task management, deployed on their own server within an existing Coolify environment. Requirements included: installing the latest version of Plane CE, ensuring proper operation behind Traefik reverse proxy, extracting the database as a separate Coolify service for convenient archiving, and setting up regular backups for all data.&lt;/p&gt;</description></item></channel></rss>