<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tech Mahato on Medium]]></title>
        <description><![CDATA[Stories by Tech Mahato on Medium]]></description>
        <link>https://medium.com/@techmahato?source=rss-df39eee9f69e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yZLlu0KYo2lN4rNoxfaCpg.png</url>
            <title>Stories by Tech Mahato on Medium</title>
            <link>https://medium.com/@techmahato?source=rss-df39eee9f69e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:01:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@techmahato/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Amazon EKS Disaster Recovery: AWS Backup, Terraform, Cross-Region DR, and Real-World Restore…]]></title>
            <link>https://medium.com/@techmahato/amazon-eks-disaster-recovery-aws-backup-terraform-cross-region-dr-and-real-world-restore-23fa590f2138?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/23fa590f2138</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 02:26:06 GMT</pubDate>
            <atom:updated>2026-10-15T02:26:06.146Z</atom:updated>
            <content:encoded><![CDATA[<h3>Amazon EKS Disaster Recovery: AWS Backup, Terraform, Cross-Region DR, and Real-World Restore Failures</h3><p>What happens when your Amazon EKS cluster fails and your backups don’t restore as expected? Discover how to build production-grade EKS disaster recovery using AWS Backup and Terraform, with immutable backups, cross-Region replication, Vault Lock, automated alerts, and real-world restore failures. Learn practical troubleshooting techniques and test your recovery strategy before disaster strikes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kj1t7m1-cV8v-36K9xWhtQ.png" /></figure><p>Since November 2025, AWS Backup protects an Amazon EKS cluster natively. One job captures the Kubernetes state and the EBS, EFS and S3 volumes behind your PVCs as a composite recovery point. It’s agent-free, but that doesn’t make it hands-off. In my tests, restores into the existing cluster finished in 4–5 minutes. “Create a new cluster” restores failed in both of my attempts: in the same Region after 1 h 17 min, and cross-Region, where no cluster came up at all. An add-on removed through the EKS console didn’t come back, and a single crashlooping metrics-server was enough to fail a backup. This article builds the setup I’d run in production with Terraform: vaults with Vault Lock, separate backup and restore roles, a cross-Region copy and alerting in both Regions. It adds a preflight script and a scripted restore drill that proves the data comes back.</p><h3>The problem</h3><p>“We have backups” usually means an EBS snapshot policy and a Git repository of manifests. That falls apart on the first real incident:</p><ul><li><strong>Snapshots without state:</strong> a volume snapshot without the PVC, StorageClass, Secrets and ServiceAccounts that bind it to a workload is a disk you have to re-wire by hand, at 3 a.m.</li><li><strong>Git isn’t the cluster:</strong> Git holds the <em>desired</em> state you remembered to commit. It doesn’t hold the Secrets created by operators, the CRs your controllers generated, or the kubectl edit someone made last week.</li><li><strong>Untested restores:</strong> a backup that has never been restored is a hypothesis, not a recovery plan.</li></ul><p>The classic answer was Velero: an in-cluster controller, its own IAM, a bucket, snapshot plugins and upgrades you own. AWS Backup now does the same job as a managed, agent-free service, with the vault controls (encryption, immutability, cross-account and cross-Region copies) your audit team already understands. The question this article answers is how to run it so that a restore <em>works</em> when you need it.</p><h3>What AWS Backup actually captures</h3><p>An EKS backup job creates one <strong>composite recovery point</strong> (the parent) and a <strong>nested recovery point</strong> for each component (the children):</p><ul><li><strong>Kubernetes cluster state</strong>: Manifests: Secrets, ConfigMaps, StatefulSets, DaemonSets, ReplicaSets, PVCs, CRDs, Roles, RoleBindings, …. <em>Always a full copy, encrypted with the vault’s KMS key.</em></li><li><strong>Cluster configuration</strong>: Cluster name, IAM role, VPC config, networking, logging, encryption, add-ons, access entries, managed node groups, Fargate profiles, Pod Identity associations. <em>Used when AWS Backup </em>creates<em> a cluster during restore.</em></li><li><strong>Persistent storage</strong>: EBS, EFS and S3 attached through PVCs and <strong>CSI drivers</strong>. <em>Incremental where the storage supports it.</em></li><li><strong>Not included</strong>: Container images (ECR, Docker Hub), VPCs and subnets, nodes, auto-generated pods, events, leases, jobs. <em>Your IaC and registry replication own these.</em></li><li><strong>Not supported</strong>: In-tree or CSI-<em>migrated</em> volumes, ACK-managed volumes, FSx via CSI, S3 <em>prefix</em> mounts, EFS non-root sub-path mounts, cross-account EFS, EKS on Outposts. <em>A child job fails, or the volume is skipped.</em></li></ul><figure><img alt="Architecture: backup, cross-Region copy and restore flows" src="https://cdn-images-1.medium.com/max/1024/1*fyzCGIjIz2qzYDJHia4DFQ.png" /></figure><h3>Architecture</h3><figure><img alt="Architecture: backup, cross-Region copy and restore flows" src="https://cdn-images-1.medium.com/max/1024/1*W9egIzYL_HCim9qKckFhcg.png" /></figure><ol><li>When a job runs, AWS Backup assumes the <strong>backup role</strong> and creates an EKS <strong>access entry</strong> for itself. This is why the cluster’s authentication mode must be API or API_AND_CONFIG_MAP. Its managed policy includes eks:CreateAccessEntry and eks:AssociateAccessPolicy for this purpose.</li><li>Persistent volumes are snapshotted through their native mechanisms (EBS snapshots, EFS and S3 backups).</li><li>Everything lands as one composite recovery point in the primary vault, encrypted with its CMK.</li><li>The plan’s copy_action copies the composite to a vault in the DR Region right after the backup completes, while it&#39;s still in warm storage. Timing matters, as you&#39;ll see in Decision 3.</li><li>Restores run with a separate <strong>restore role</strong>, into a cluster that already exists.</li></ol><h3>Design decisions</h3><h4>Decision 1: restore into a pre-provisioned cluster, not “Create a new cluster”</h4><p>The restore wizard offers <em>Source cluster</em>, <em>Choose an existing cluster</em> and <em>Create a new cluster</em>. These are my results from Nov 2025 on poc-project-cluster (EKS 1.34, two EBS PVCs, one EFS file system, one S3 bucket):</p><ul><li><strong>Full cluster-state restore into the source cluster (×4)</strong> — Result: <strong>Completed in 4–5 min</strong> each</li><li><strong>“Create a new cluster”, same Region</strong> — Result: <strong>Failed after 1 h 17 min</strong>: the cluster and node group were created, but not all add-ons came up</li><li><strong>“Create a new cluster”, another Region</strong> — Result: <strong>Failed</strong>: no cluster came up</li><li><strong>EFS child restored to a new file system, same Region</strong> — Result: Completed in about 1 min, data intact</li><li><strong>EFS recovery point copied us-east-1 → ap-south-1, restored to a new file system there</strong> — Result: Completed, all data present</li><li><strong>S3 bucket backed up and restored to a different bucket, same Region</strong> — Result: Completed</li></ul><figure><img alt="Restore jobs: four restores to the source cluster at 4–5 minutes, one new-cluster restore failed after 1h17m" src="https://cdn-images-1.medium.com/max/1024/1*MvoiFDmNjimtKO-hgJHUXw.png" /><figcaption>Measured restore jobs from the author’s account. Four restores into poc-project-cluster took 4–5 minutes. The restore that created restore-cluster failed after 1 h 17 min. An EFS-only restore took 1 minute.</figcaption></figure><p>The documentation explains why new-cluster restores are fragile:</p><ul><li>Security groups (for ALB, Pod Identity and node groups) must be <strong>pre-created</strong> in the target account and Region.</li><li>Every IAM role the source referenced (cluster role, node roles, Pod Identity and IRSA roles) must <strong>already exist</strong> there.</li><li><strong>Every</strong> node group and Fargate profile from backup time must be supplied, with matching IDs.</li><li>A launch template that hard-codes the source cluster’s endpoint must be replaced.</li><li>AWS Backup offers “a limited set of options” for new clusters, and AWS recommends creating the cluster yourself for full control.</li></ul><p><strong>So the target cluster should come from the same Terraform that built the source</strong> (same add-ons, CSI drivers, StorageClasses and node pools), and AWS Backup restores the <em>Kubernetes state and data</em> into it. This also matches what the backup does well. Infrastructure belongs in IaC; workload state belongs in the vault.</p><p><em>Choose “Create a new cluster” when</em> you have no IaC for the cluster and accept a slower, less predictable RTO. Rehearse it first, using the metadata in the restore section.</p><h4>Decision 2: separate backup and restore roles</h4><p>The console flow (Fig. 4) attaches all four managed policies to one role. The restore policy is far more powerful. Its November 2025 EKS additions include eks:CreateCluster, eks:CreateNodegroup, ec2:RunInstances and iam:PassRole. A role that runs every night shouldn&#39;t hold those permissions. Two roles let you review the restore role&#39;s access separately, and the Terraform sends a notification for <strong>every</strong> restore job, so nobody uses the restore role unnoticed.</p><figure><img alt="Single console-created role with all four AWS Backup managed policies" src="https://cdn-images-1.medium.com/max/1024/1*-F5-5bmvJyYPxEgspezIpA.png" /><figcaption>The console-created aws-backup-role with both backup and restore policies. The Terraform below splits them.</figcaption></figure><h4>Decision 3: warm storage only, and copy at backup time</h4><p>My first plan moved recovery points to cold storage after 1 day (Fig. 5). That caused two problems:</p><ul><li>The EKS cluster-state child can’t transition to cold at all. Only children whose storage supports cold storage move. Cold storage also has a 90-day minimum retention.</li><li>When I later tried to copy a cold recovery point to another Region, AWS Backup refused with <em>“Resource is not supported, reason: Storage tier is COLD”</em>. Same-Region restore still worked.</li></ul><figure><img alt="Lifecycle settings moving backups to cold storage after 1 day" src="https://cdn-images-1.medium.com/max/1024/1*XEL1-q-yCmFMBh0GNH-BBw.png" /><figcaption>Fig. 5. The lifecycle setting to avoid for EKS: cold storage after 1 day.</figcaption></figure><p>The plan below keeps daily points warm for 35 days and copies each one to the DR vault as part of the same rule. For long-term retention, add a separate monthly rule with cold storage for the EBS and EFS children only, and accept that those can’t be copied once they’re cold.</p><h4>Decision 4: Vault Lock in governance mode, then compliance</h4><p>Vault Lock rejects backup and copy jobs whose retention falls outside [min, max], and it protects recovery points from early deletion. <strong>Governance mode</strong> (no changeable_for_days) can still be managed by sufficiently privileged IAM users, which is the right place to start. <strong>Compliance mode</strong> becomes immutable, even for the account root, once its grace time (minimum 3 days) ends. Move to it only after the retention numbers have survived a quarter of real use.</p><h4>Decision 5: Pod Identity for anything that must move</h4><p>Restoring to another cluster doesn’t rewrite IRSA. ServiceAccount annotations and role trust policies still point at the <strong>source</strong> cluster’s OIDC provider, so pods in the restored cluster fail to assume their roles. AWS’s restore guide recommends EKS Pod Identity for workloads that need cross-cluster portability, because its trust policy doesn’t reference a cluster-specific OIDC issuer. One caveat: Pod Identity <em>associations</em> belong to the cluster configuration. When you restore into an existing DR cluster (Path B), create them in that cluster’s IaC. Don’t rely on the restore to create them.</p><h3>Prerequisites and assumptions</h3><ul><li><strong>EKS cluster</strong> — Requirement: Authentication mode API or API_AND_CONFIG_MAP · Why: AWS Backup authenticates through an access entry</li><li><strong>Storage</strong> — Requirement: PVs provisioned by <strong>CSI drivers</strong> (ebs.csi.aws.com, efs.csi.aws.com, S3 Mountpoint) · Why: In-tree and CSI-migrated volumes aren&#39;t supported</li><li><strong>S3 PVs</strong> — Requirement: Bucket versioning enabled · Why: Required for S3 backups and restore</li><li><strong>Restore target</strong> — Requirement: A cluster built from the same IaC, with the same CSI add-ons and StorageClasses · Why: Decision 1; StorageClasses and CSI drivers must exist before restore</li><li><strong>Tools</strong> — Requirement: Terraform ≥ 1.6 (AWS provider ~&gt; 6.0), AWS CLI v2, kubectl, jq · Why: Validated with provider 6.20.0</li></ul><p>Region us-east-1 (primary) and ap-south-1 (DR). Account 111122223333 and all IDs are illustrative. The screenshots come from the author&#39;s account, with the account ID redacted.</p><pre>export AWS_REGION=us-east-1<br>export CLUSTER=&lt;REPLACE_ME&gt;<br>export ALERT_EMAIL=&lt;REPLACE_ME&gt;@example.com<br>export REPO=&quot;$PWD/code&quot;<br>aws eks update-kubeconfig --name &quot;$CLUSTER&quot; --region &quot;$AWS_REGION&quot;</pre><h3>Implementation</h3><h4>Repository layout</h4><pre>code/<br>├── terraform/   versions.tf variables.tf kms.tf vaults.tf iam.tf plan.tf alerts.tf outputs.tf<br>├── scripts/     preflight.sh configure-vault-notifications.sh backup-now.sh restore-eks.sh<br>│                restore-drill.sh delete-recovery-point.sh<br>└── k8s/         backup-drill.yaml   # canary workload for restore drills</pre><h4>Step 0: Preflight the cluster</h4><p>Two of my failures would have been caught by a preflight check: the crashlooping metrics-server, and add-ons that were managed outside IaC. scripts/preflight.sh checks the following:</p><ul><li>the authentication mode;</li><li>that the CSI add-ons are installed;</li><li>that every aggregated APIService is Available. A dead metrics-server takes metrics.k8s.io down, and the AWS docs list it among the object types skipped on HTTP 503;</li><li>that no in-tree EBS PVs or in-tree StorageClasses are in use;</li><li>that no pods are crashlooping.</li></ul><pre>CLUSTER=&quot;$CLUSTER&quot; AWS_REGION=&quot;$AWS_REGION&quot; &quot;$REPO/scripts/preflight.sh&quot;</pre><pre>OK    authentication mode: API_AND_CONFIG_MAP<br>OK    add-on aws-ebs-csi-driver installed<br>OK    add-on aws-efs-csi-driver installed<br>FAIL  unavailable APIServices: v1beta1.metrics.k8s.io<br>OK    no in-tree EBS PVs<br>WARN  unhealthy pods (check before relying on the backup): kube-system/metrics-server-6d4c8d8f7b-x2kq9</pre><p><em>(Illustrative output, reproducing the condition that failed my backup.)</em></p><p>If the mode is CONFIG_MAP, switch it. The change is one-way, CONFIG_MAP → API_AND_CONFIG_MAP → API:</p><pre>aws eks update-cluster-config --name &quot;$CLUSTER&quot; --region &quot;$AWS_REGION&quot; \<br>  --access-config authenticationMode=API_AND_CONFIG_MAP</pre><figure><img alt="EKS console Access tab showing authentication mode EKS API and ConfigMap" src="https://cdn-images-1.medium.com/max/1024/1*rVl9vS52zEiAy0pzJGq7hg.png" /><figcaption>Fig. 6. The prerequisite in the EKS console: Access → Authentication mode = EKS API and ConfigMap.</figcaption></figure><h4>Step 1: Opt in to EKS (and the storage types) for the Region</h4><p>Opt-in is an account-and-Region-wide setting that affects every backup plan in the account, so I don’t let a workload’s Terraform own it. Turn it on with the CLI and verify:</p><pre>aws backup update-region-settings --region &quot;$AWS_REGION&quot; \<br>  --resource-type-opt-in-preference EKS=true,EBS=true,EFS=true,S3=true<br>aws backup describe-region-settings --region &quot;$AWS_REGION&quot; \<br>  --query &#39;ResourceTypeOptInPreference.{EKS:EKS,EBS:EBS,EFS:EFS,S3:S3}&#39;</pre><figure><img alt="AWS Backup Service opt-in page with EBS, EC2, EFS and EKS enabled" src="https://cdn-images-1.medium.com/max/1024/1*MOiNPQYGvbsC2M5WJp8dmQ.png" /><figcaption>Fig. 7. Settings → Service opt-in. EKS appears as “EKS — new”. The S3 opt-in notes that buckets need versioning.</figcaption></figure><h4>Step 2: Vaults, keys and Vault Lock (Terraform)</h4><pre># file: terraform/vaults.tf (abridged)<br>resource &quot;aws_backup_vault&quot; &quot;primary&quot; {<br>  name        = &quot;${var.name_prefix}-vault&quot;<br>  kms_key_arn = aws_kms_key.vault.arn<br>}</pre><pre>resource &quot;aws_backup_vault&quot; &quot;dr&quot; {<br>  region      = var.dr_region            # AWS provider v6: per-resource Region, no provider alias needed<br>  name        = &quot;${var.name_prefix}-vault-dr&quot;<br>  kms_key_arn = aws_kms_key.vault_dr.arn<br>}</pre><pre>resource &quot;aws_backup_vault_lock_configuration&quot; &quot;primary&quot; {<br>  backup_vault_name  = aws_backup_vault.primary.name<br>  min_retention_days = var.vault_lock_min_days   # 7<br>  max_retention_days = var.vault_lock_max_days   # 365<br>  # no changeable_for_days =&gt; governance mode<br>}</pre><p>Each Region gets its own customer managed key with rotation enabled (kms.tf). The cluster-state child is encrypted with the vault&#39;s key. EBS and EFS children keep their own storage encryption.</p><figure><img alt="Create vault page: backup vault type and encryption key" src="https://cdn-images-1.medium.com/max/1024/1*aQGHTL7900IlSSltpO5ZQw.png" /><figcaption>Fig. 8. The console equivalent. Choose a customer managed key rather than leaving encryption to the default.</figcaption></figure><h4>Step 3: Roles, plan and selection (Terraform)</h4><pre># file: terraform/iam.tf (abridged)<br>data &quot;aws_iam_policy_document&quot; &quot;backup_trust&quot; {<br>  statement {<br>    actions = [&quot;sts:AssumeRole&quot;]<br>    principals {<br>      type        = &quot;Service&quot;<br>      identifiers = [&quot;backup.amazonaws.com&quot;]<br>    }<br>    condition {                         # confused-deputy guard<br>      test     = &quot;StringEquals&quot;<br>      variable = &quot;aws:SourceAccount&quot;<br>      values   = [data.aws_caller_identity.current.account_id]<br>    }<br>  }<br>}<br># backup role:  AWSBackupServiceRolePolicyForBackup (+ ForS3Backup if PVs use S3)<br># restore role: AWSBackupServiceRolePolicyForRestores (+ ForS3Restore)</pre><pre># file: terraform/plan.tf<br>resource &quot;aws_backup_plan&quot; &quot;eks&quot; {<br>  name = &quot;${var.name_prefix}-plan&quot;<br>  rule {<br>    rule_name                    = &quot;daily-with-dr-copy&quot;<br>    target_vault_name            = aws_backup_vault.primary.name<br>    schedule                     = var.schedule            # cron(30 22 * * ? *)<br>    schedule_expression_timezone = var.schedule_timezone   # Asia/Kolkata<br>    start_window                 = 60<br>    completion_window            = 360   # composite jobs wait for every PV snapshot<br>    lifecycle { delete_after = var.retention_days }        # 35, warm only<br>    copy_action {<br>      destination_vault_arn = aws_backup_vault.dr.arn<br>      lifecycle { delete_after = var.retention_days }<br>    }<br>    recovery_point_tags = { Cluster = var.cluster_name }<br>  }<br>}</pre><pre>resource &quot;aws_backup_selection&quot; &quot;eks&quot; {<br>  name         = &quot;${var.cluster_name}-selection&quot;<br>  plan_id      = aws_backup_plan.eks.id<br>  iam_role_arn = aws_iam_role.backup.arn<br>  resources    = [data.aws_eks_cluster.this.arn]<br>  lifecycle {<br>    precondition {<br>      condition     = contains([&quot;API&quot;, &quot;API_AND_CONFIG_MAP&quot;], data.aws_eks_cluster.this.access_config[0].authentication_mode)<br>      error_message = &quot;AWS Backup needs EKS access entries: set the cluster authentication mode to API or API_AND_CONFIG_MAP first.&quot;<br>    }<br>    precondition {<br>      condition     = var.vault_lock_min_days &lt;= var.retention_days &amp;&amp; var.retention_days &lt;= var.vault_lock_max_days<br>      error_message = &quot;retention_days must sit between vault_lock_min_days and vault_lock_max_days, or jobs will fail.&quot;<br>    }<br>  }<br>}</pre><p>The two precondition blocks turn the two most common silent failures into terraform plan errors:</p><ul><li>a cluster still in CONFIG_MAP mode;</li><li>a retention period that Vault Lock would reject at job time.</li></ul><p>schedule_expression_timezone keeps the 22:30 IST window from drifting, so you don&#39;t have to translate it to UTC by hand.</p><p>The console screens for the same objects, for orientation:</p><figure><img alt="Create backup plan: Build a new plan, plan name and tags" src="https://cdn-images-1.medium.com/max/1024/1*wk95wMCjXantNUZw_IIoqQ.png" /><figcaption>Fig. 9. Create backup plan → Build a new plan.</figcaption></figure><figure><img alt="Backup rule: vault, daily frequency, 22:30 start, start within 1 hour" src="https://cdn-images-1.medium.com/max/1024/1*8gRIrA2pM1drc7R1gJPxbA.png" /><figcaption>Fig. 10. The rule: target vault, daily frequency and backup window. Terraform sets the same values.</figcaption></figure><figure><img alt="Copy to destination: choose a Region" src="https://cdn-images-1.medium.com/max/1024/1*ifP-kBBAHUdDwDPYEmOfAg.png" /><figcaption>Fig. 11. “Copy to destination” is the console’s copy_action. Set it here so copies happen while the recovery point is warm.</figcaption></figure><figure><img alt="Assign resources: IAM role and resource selection" src="https://cdn-images-1.medium.com/max/1024/1*jOQBgSQwHUFmRjzc3RH7-g.png" /><figcaption>Fig. 12. Resource assignment, with the backup role chosen explicitly.</figcaption></figure><figure><img alt="Assign resources: resource type EKS with poc-project-cluster selected" src="https://cdn-images-1.medium.com/max/1024/1*vnF3b9326VD2zSuRviyWqg.png" /><figcaption>Fig. 13. Selecting the cluster by name. One EKS selection pulls in its CSI-backed volumes automatically, so you don’t add EBS volume IDs separately.</figcaption></figure><p>Apply:</p><pre>cd &quot;$REPO/terraform&quot;<br>sed -e &quot;s/^cluster_name .*/cluster_name = \&quot;$CLUSTER\&quot;/&quot; \<br>    -e &quot;s/^alert_email .*/alert_email  = \&quot;$ALERT_EMAIL\&quot;/&quot; \<br>    terraform.tfvars.example &gt; terraform.tfvars<br>terraform init &amp;&amp; terraform apply<br>cd &quot;$REPO&quot;</pre><pre># Values used by every later step:<br>export PRIMARY_VAULT=$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw primary_vault_name)<br>export DR_VAULT=$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw dr_vault_name)<br>export CLUSTER_ARN=$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw cluster_arn)<br>export BACKUP_ROLE_ARN=$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw backup_role_arn)<br>export RESTORE_ROLE_ARN=$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw restore_role_arn)</pre><p><strong>Verify:</strong></p><pre>aws backup get-backup-plan --region &quot;$AWS_REGION&quot; \<br>  --backup-plan-id &quot;$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw backup_plan_id)&quot; \<br>  --query &#39;BackupPlan.Rules[].{rule:RuleName,schedule:ScheduleExpression,tz:ScheduleExpressionTimezone,copy:CopyActions[0].DestinationBackupVaultArn}&#39;<br>aws backup describe-backup-vault --region &quot;$AWS_REGION&quot; --backup-vault-name &quot;$PRIMARY_VAULT&quot; \<br>  --query &#39;{Locked:Locked,Min:MinRetentionDays,Max:MaxRetentionDays}&#39;</pre><pre>[ { &quot;rule&quot;: &quot;daily-with-dr-copy&quot;, &quot;schedule&quot;: &quot;cron(30 22 * * ? *)&quot;, &quot;tz&quot;: &quot;Asia/Kolkata&quot;,<br>    &quot;copy&quot;: &quot;arn:aws:backup:ap-south-1:111122223333:backup-vault:eks-backup-vault-dr&quot; } ]<br>{ &quot;Locked&quot;: true, &quot;Min&quot;: 7, &quot;Max&quot;: 365 }</pre><p><em>(Expected shape. </em><em>Locked is </em><em>true once a lock configuration exists, in either mode.)</em></p><h4>Step 4: Alerts that catch “Completed with issues”</h4><p>The job state stays COMPLETED even when individual Kubernetes objects failed, so job-level alarms miss it. AWS Backup publishes <strong>object-level</strong> vault events for EKS: EKS_BACKUP_OBJECT_FAILED, EKS_RESTORE_OBJECT_FAILED and EKS_RESTORE_OBJECT_SKIPPED. Terraform creates the SNS topic and an EventBridge rule for FAILED/ABORTED/EXPIRED jobs (including PARTIAL) and a second rule that reports <strong>every restore job</strong>. Both exist in the primary <em>and</em> the DR Region, because restores from the DR vault emit their events in ap-south-1. The vault event lists are set by a script:</p><pre>&quot;$REPO/scripts/configure-vault-notifications.sh&quot; &quot;$PRIMARY_VAULT&quot; \<br>  &quot;$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw alerts_topic_arn)&quot;<br>AWS_REGION=ap-south-1 &quot;$REPO/scripts/configure-vault-notifications.sh&quot; &quot;$DR_VAULT&quot; \<br>  &quot;$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw dr_alerts_topic_arn)&quot;</pre><blockquote><strong>Pitfall:</strong> don’t encrypt these topics with the AWS managed key alias/aws/sns. EventBridge and AWS Backup need kms:GenerateDataKey* and kms:Decrypt in the key policy, and you can&#39;t edit an AWS managed key&#39;s policy. The topic accepts the subscription and then drops every alert without telling you. alerts.tf creates a customer managed key per Region that grants both services.</blockquote><blockquote><strong>Why a script and not </strong><strong>aws_backup_vault_notifications?</strong> In AWS provider 6.20.0, that resource&#39;s validation rejects the EKS_* event names (I hit this during terraform validate). The API call also replaces the vault&#39;s whole event list, so a Terraform resource and the script would overwrite each other. Move this back into Terraform once your provider version accepts the EKS events.</blockquote><p>Confirm <strong>both</strong> SNS email subscriptions (one per Region), or nothing arrives.</p><h4>Step 5: Run an on-demand backup and read the result properly</h4><pre>RP=$(&quot;$REPO/scripts/backup-now.sh&quot; &quot;$CLUSTER_ARN&quot; &quot;$PRIMARY_VAULT&quot; &quot;$BACKUP_ROLE_ARN&quot;)<br>echo &quot;$RP&quot;     # arn:aws:backup:us-east-1:111122223333:recovery-point:composite:eks/&lt;cluster&gt;-&lt;timestamp&gt;</pre><p>The script waits for the composite job and reports progress on stderr. It shows the StatusMessage, which is where &quot;Completed with issues&quot; details appear, and lists the child jobs with --by-parent-job-id. It prints only the composite recovery point ARN on stdout, so you can capture it, and it exits non-zero unless the state is COMPLETED:</p><figure><img alt="Backup jobs: parent job for poc-project-cluster with child jobs for two EBS PVCs, EFS and cluster state" src="https://cdn-images-1.medium.com/max/1024/1*uSoh2oaWJgMK_5Ny0ew_YA.png" /><figcaption>Fig. 14. One parent job (poc-project-cluster) with a child job per component: two dynamic EBS PVCs, the EFS file system and the cluster state.</figcaption></figure><figure><img alt="Protected resources: two EBS volumes, one EFS file system and the EKS cluster" src="https://cdn-images-1.medium.com/max/1024/1*ZUPVUmZCStVMfLzuhrPlVw.png" /><figcaption>Fig. 15. Protected resources after the first job: the EKS selection discovered both EBS volumes and the EFS file system on its own.</figcaption></figure><h3>Restore: three paths, ranked by how often you’ll need them</h3><figure><img alt="Restore backup: composite recovery point summary" src="https://cdn-images-1.medium.com/max/1024/1*m9HGN_DeK1Tgfd4YvSkLlw.png" /><figcaption>Fig. 16. Choosing a composite recovery point restores all of its children. Choosing a nested recovery point restores only that component.</figcaption></figure><p>All restores are <strong>non-destructive</strong>: objects that already exist in the target are <em>skipped</em>, never overwritten. The target’s Kubernetes version isn’t changed. That has two consequences:</p><ul><li><strong>Restoring into the source cluster only fills gaps.</strong> It brings back what was <em>deleted</em>, not what was <em>changed</em>. To roll back a bad change to an existing object, delete the object first or restore into another namespace or cluster.</li><li><strong>Add-ons weren’t re-created on an existing cluster.</strong> I deleted the metrics-server add-on through the EKS console, restored the cluster-state child into the same cluster, and the job <strong>succeeded without bringing the add-on back</strong>. Objects deleted with kubectl <em>were</em> restored. <em>(This is my observation. The restore guide describes existing-cluster restores as restoring Kubernetes resources and persistent volumes, and doesn&#39;t say whether EKS-level configuration such as add-ons is re-applied.)</em> Keep add-ons in IaC.</li></ul><h4>Path A: namespace restore (the everyday one)</h4><p>Use this when someone deleted a namespace, or a bad deploy took one out. You can restore up to <strong>five</strong> namespaces per job, and cluster-scoped resources such as CRDs and StorageClasses come with them. The example restores monitoring, the namespace from my own test (Fig. 17).</p><figure><img alt="Restore settings: select cluster namespaces, monitoring selected, destination source cluster" src="https://cdn-images-1.medium.com/max/1024/1*Wxatxx-VZANo7YYMFGuhbg.png" /><figcaption>Fig. 17. Namespace restore in the console: monitoring into the source cluster.</figcaption></figure><p>Each EBS child needs an Availability Zone <strong>in which a node is running</strong>, or the volume can’t attach:</p><figure><img alt="Fig. 18. The console blocks the restore until every EBS child has an AZ. The script passes the AZ through nestedRestoreJobs." src="https://cdn-images-1.medium.com/max/1024/1*SWyKHZ0HUEAfFBRXILKiaw.png" /><figcaption>Fig. 18. The console blocks the restore until every EBS child has an AZ. The script passes the AZ through nestedRestoreJobs.</figcaption></figure><p>The scripted equivalent, using the <strong>restore role</strong>. scripts/restore-eks.sh does a namespace restore when you pass namespaces, and a full restore when you don&#39;t:</p><pre>latest_composite() {   # newest completed parent (composite) point; nested cluster-state points are also type EKS<br>  aws backup list-recovery-points-by-backup-vault --region &quot;$1&quot; --backup-vault-name &quot;$2&quot; --by-resource-type EKS \<br>    --query &quot;sort_by(RecoveryPoints[?IsParent==\`true\` &amp;&amp; Status==&#39;COMPLETED&#39;], &amp;CreationDate)[-1].RecoveryPointArn&quot; \<br>    --output text<br>}<br>RP=$(latest_composite &quot;$AWS_REGION&quot; &quot;$PRIMARY_VAULT&quot;)</pre><pre>VAULT_NAME=&quot;$PRIMARY_VAULT&quot; &quot;$REPO/scripts/restore-eks.sh&quot; &quot;$RP&quot; &quot;$CLUSTER&quot; &quot;$RESTORE_ROLE_ARN&quot; us-east-1a monitoring</pre><p>The script builds this metadata, with the AZ map generated from the EBS children of the recovery point:</p><pre>{&quot;clusterName&quot;:&quot;&lt;target&gt;&quot;,&quot;newCluster&quot;:&quot;false&quot;,&quot;namespaceLevelRestore&quot;:&quot;true&quot;,<br> &quot;namespaces&quot;:&quot;[\&quot;monitoring\&quot;]&quot;,<br> &quot;nestedRestoreJobs&quot;:&quot;{\&quot;arn:aws:ec2:us-east-1::snapshot/snap-…\&quot;:\&quot;{\\\&quot;AvailabilityZone\\\&quot;:\\\&quot;us-east-1a\\\&quot;}\&quot;}&quot;}</pre><blockquote><strong>Note:</strong> The restore guide’s metadata reference spells the key nestedRestoreJobs, while one of its CLI examples uses nestedrestorejobs. I use the reference spelling. If your first drill ignores the AZ, try the other spelling and tell me which one worked.</blockquote><figure><img alt="Select restore role and tags: Choose an IAM role" src="https://cdn-images-1.medium.com/max/1024/1*IjQKNtZ0_VjRNhM-j14qrQ.png" /><figcaption>Fig. 19. Always choose the restore role explicitly.</figcaption></figure><h4>Path B: full cluster state into an existing cluster (DR)</h4><p>This is the DR path. Restore the newest composite from the <strong>DR vault</strong> into the cluster your Terraform built in ap-south-1. Omitting namespaces makes the script do a full restore, and it still maps every EBS child to an AZ with nodes. First make sure the copy of the backup you want has actually landed. Copy jobs run <em>after</em> the backup and are listed in the source Region:</p><pre>aws backup list-copy-jobs --region &quot;$AWS_REGION&quot; \<br>  --by-destination-vault-arn &quot;$(terraform -chdir=&quot;$REPO/terraform&quot; output -raw dr_vault_arn)&quot; \<br>  --query &#39;CopyJobs[].{state:State,source:SourceRecoveryPointArn,created:CreationDate}&#39; --output table<br># or wait for it unattended (COPY_JOB_ID from the table above):<br>until [ &quot;$(aws backup describe-copy-job --region &quot;$AWS_REGION&quot; --copy-job-id &quot;$COPY_JOB_ID&quot; \<br>          --query CopyJob.State --output text)&quot; = COMPLETED ]; do sleep 60; done</pre><pre>export DR_CLUSTER=&lt;REPLACE_ME&gt;          # built from the same IaC, with CSI add-ons and Pod Identity associations<br>DR_RP=$(latest_composite ap-south-1 &quot;$DR_VAULT&quot;)<br>aws eks update-kubeconfig --name &quot;$DR_CLUSTER&quot; --region ap-south-1<br>AWS_REGION=ap-south-1 VAULT_NAME=&quot;$DR_VAULT&quot; \<br>  &quot;$REPO/scripts/restore-eks.sh&quot; &quot;$DR_RP&quot; &quot;$DR_CLUSTER&quot; &quot;$RESTORE_ROLE_ARN&quot; ap-south-1a</pre><figure><img alt="Configure EKS cluster: restore full EKS cluster, destination options, advanced restore order" src="https://cdn-images-1.medium.com/max/1024/1*0j7cijvBfpNcQaKhkh6oGw.png" /><figcaption>Fig. 20. Full restore. “Advanced restore settings” exposes kubernetesRestoreOrder if your CRs depend on other objects.</figcaption></figure><p>Before a cross-Region restore, check these:</p><ul><li><strong>Images:</strong> they must be pullable in the DR Region. Replicate ECR repositories.</li><li><strong>Pod roles:</strong> for IRSA workloads, update the trust policies to the DR cluster’s OIDC issuer, or use Pod Identity.</li><li><strong>Storage:</strong> EFS file systems restore to a random prefix with <strong>no access points or mount targets</strong>. Create those, then point the PV at them.</li><li><strong>Ingress:</strong> load balancers and DNS are recreated by your controllers, not restored. Plan the DNS cut-over.</li></ul><h4>Path C: let AWS Backup create the cluster (last resort)</h4><p>Use this only if there’s no IaC. Pass &quot;newCluster&quot;:&quot;true&quot; plus clusterRole, clusterVpcConfig (subnets and security groups are required), <strong>every</strong> node group with its original nodeGroupId, every Fargate profile and the Pod Identity roles. The restore waits 15 minutes after the cluster turns ACTIVE before it creates anything else, so budget well over an hour for RTO. Rehearse it before you depend on it. Mine failed.</p><h3>Restore drill: prove it, monthly</h3><p>AWS Backup’s managed restore testing doesn’t support EKS today, so the drill is scripted in scripts/restore-drill.sh. It deploys a canary that writes a marker file and 1 MiB of random data to a gp3 CSI volume once and logs their checksums. Then it takes a <strong>fresh</strong> backup, deletes the namespace, restores it and compares the checksums. If the backup doesn&#39;t complete, it stops before deleting anything.</p><pre>kubectl config use-context &quot;$(kubectl config get-contexts -o name | grep &quot;:cluster/$CLUSTER$&quot;)&quot;   # primary cluster<br>&quot;$REPO/scripts/restore-drill.sh&quot; &quot;$CLUSTER&quot; &quot;$CLUSTER_ARN&quot; &quot;$PRIMARY_VAULT&quot; \<br>  &quot;$BACKUP_ROLE_ARN&quot; &quot;$RESTORE_ROLE_ARN&quot; us-east-1a</pre><pre>statefulset rolling update complete 1 pods at revision canary-5c9…<br>recovery point: arn:aws:backup:us-east-1:111122223333:recovery-point:composite:eks/&lt;cluster&gt;-…<br>namespace &quot;backup-drill&quot; deleted<br>… COMPLETED<br>RESTORE VERIFIED: data identical; restore + rollout took 312s</pre><p><em>(Expected shape, not captured from a live run.)</em></p><p>The drill passes only if both checksum files are non-empty and identical. That proves the PVC, the StorageClass binding and the volume data came back, not just the manifests. Every restore also sends emails through the restore-activity rule, which proves the alerting path. Record the reported duration each month as your measured namespace RTO.</p><h3>Troubleshooting</h3><ul><li><strong>Backup </strong>Failed<strong> or <em>Completed with issues</em> while a </strong><strong>metrics-server pod is crashlooping</strong> — Likely cause: Aggregated API metrics.k8s.io returns 503 during discovery · Confirm: kubectl get apiservices | grep False; job StatusMessage · Fix: Fix or remove the broken APIService before the window; run preflight.sh</li><li><strong>Job fails immediately; no access entry for AWS Backup</strong> — Likely cause: Cluster in CONFIG_MAP mode · Confirm: aws eks describe-cluster --query cluster.accessConfig · Fix: Switch to API_AND_CONFIG_MAP (one-way)</li><li><strong>A PV missing from the composite, or a failed child job</strong> — Likely cause: In-tree/CSI-migrated PV, FSx, EFS sub-path mount, S3 prefix mount · Confirm: kubectl get pv -o yaml (provisioner, csi.driver) · Fix: Migrate the data to a CSI StorageClass</li><li><strong>Backup or copy job fails right away after enabling Vault Lock</strong> — Likely cause: Lifecycle retention outside [min,max] · Confirm: Job StatusMessage · Fix: Align retention_days (the Terraform precondition catches this)</li><li><strong>Copy fails: *Storage tier is COLD</strong> — Likely cause: Recovery point already transitioned · Confirm: describe-recovery-point --query StorageClass · Fix: Copy at backup time (copy_action); keep copied points warm</li><li><strong>Restore </strong><strong>COMPLETED but objects missing</strong> — Likely cause: Objects already existed (skipped) or failed · Confirm: SNS EKS_RESTORE_OBJECT_SKIPPED / _FAILED · Fix: Delete the conflicting objects or restore elsewhere</li><li><strong>Restored pod </strong><strong>Pending, volume won&#39;t attach</strong> — Likely cause: EBS AZ has no node · Confirm: kubectl describe pod; node AZ labels · Fix: Restore with an AZ that has nodes</li><li><strong>EFS PVC never binds after restore</strong> — Likely cause: Restored file system has no access point or mount targets · Confirm: EFS console · Fix: Create both, then update the PV</li><li><strong>Pods </strong><strong>AccessDenied after cross-cluster restore</strong> — Likely cause: IRSA still trusts the source OIDC issuer · Confirm: Role trust policy · Fix: Update trust, or move to Pod Identity</li><li><strong>New-cluster restore runs for an hour and fails</strong> — Likely cause: Missing pre-created SGs/roles, node group mismatch, hard-coded launch template endpoint · Confirm: Restore job StatusMessage; EKS events · Fix: Use Path B with an IaC-built target</li><li><strong>Add-on still missing after a successful restore</strong> — Likely cause: Add-ons weren’t recreated on an existing cluster (my test) · Confirm: aws eks list-addons · Fix: Manage add-ons in IaC</li><li><strong>No alert emails, although jobs failed</strong> — Likely cause: Subscription unconfirmed, or the topic uses alias/aws/sns · Confirm: SNS subscription status; EventBridge FailedInvocations metric · Fix: Confirm the subscription; use a CMK that grants events and backup</li></ul><h3>Security considerations</h3><ul><li><strong>The vault is the crown jewel.</strong> It holds every Secret in the cluster, so the vault’s KMS key policy and IAM decide who can read your production Secrets. Restrict backup:StartRestoreJob and iam:PassRole on the restore role to a small break-glass group.</li><li><strong>Ransomware and insider deletion:</strong> Vault Lock enforces the minimum retention. The DR copy lives in a separate Region with a separate key. For the strongest isolation, copy to a vault in a <strong>separate account</strong>, or to a logically air-gapped vault (supported for EKS, except in me-south-1 and me-central-1).</li><li><strong>Confused deputy:</strong> both role trust policies are pinned with aws:SourceAccount.</li><li><strong>Least privilege:</strong> the backup role can’t create clusters or launch instances. Every restore job, in either Region, sends a notification, so an unplanned restore (a common data-exfiltration path) can’t go unnoticed.</li><li><strong>Access entries:</strong> AWS Backup creates its own access entry. Review cluster access entries periodically, and don’t delete AWS Backup’s entry as “unknown”.</li></ul><h3>Reliability: RPO and RTO you can actually claim</h3><figure><img alt="Table: Scenario, RPO, RTO (measured or documented). Namespace deleted | Cluster lost, same Region, IaC target | Region lost | No IaC, “create new cluster”" src="https://cdn-images-1.medium.com/max/1024/1*qcZn0Nh8Bh9raMoDWCqYTA.png" /><figcaption>Fig. 21. RPO and RTO per scenario (measured or documented).</figcaption></figure><p>The backup is crash-consistent at the volume level. For databases running on PVs, take application-consistent dumps as well, or quiesce them before the window.</p><h3>Cost</h3><p>Pricing comes from the worked examples on the AWS Backup pricing page (us-east-1, checked 14 Oct 2026). Two EKS-specific charges have <strong>no published amount I could retrieve</strong>: storage for the cluster-state child, and the “one-time backup creation fee charged per namespace backed up”. Treat the total below as a <strong>floor</strong>, and check both rates before you budget. The DR rows reuse us-east-1 rates as an approximation, because ap-south-1 prices differ.</p><p>Worked example, at steady state (after the 35-day retention fills): 60 GiB of used EBS data changing about 3% a day, 20 GiB of EFS changing about 2% a day, daily backups, 35-day retention in both vaults.</p><figure><img alt="Table: Item, Calculation, Monthly. EBS snapshots, primary | EFS backups, primary | Same again in the DR vault (approximate rate) | Cross-Region transfer of daily changes | KMS keys | EKS cluster-state storage | EKS per-namespace creation fee | Floor (excluding the two EKS charges)" src="https://cdn-images-1.medium.com/max/1024/1*zYRkuwcKKfYUVURAAq9hPA.png" /><figcaption>Fig. 22. Worked monthly cost at steady state (floor; two EKS charges unpublished).</figcaption></figure><p>The first month is lower for storage, because retention hasn’t filled yet, and higher for transfer, because the first copy is a full one (about 114 GiB of EBS and 32 GiB of EFS, roughly $3.56). Cost is driven by volume change rate × retention, and doubled by the DR copy. The per-namespace fee scales with namespace count × backup frequency, which is a reason not to make every rule hourly.</p><p><strong>Quotas and throttling:</strong> AWS Backup’s service quotas apply to EKS backups, including concurrent jobs and recovery points per vault. A large cluster produces one child job per persistent volume, so give completion_window enough room (360 minutes here). Stagger plans if several clusters share one window.</p><h3>Alternatives and trade-offs</h3><figure><img alt="Table: Option, Strengths, Weaknesses, Choose it when. AWS Backup for EKS (this article) | Velero | GitOps rebuild + data-only backups (EBS/EFS policies)" src="https://cdn-images-1.medium.com/max/1024/1*Q7DDCDpL4BPzEKdZV2pdCA.png" /><figcaption>Fig. 23. AWS Backup for EKS vs Velero vs GitOps rebuild.</figcaption></figure><h3>Cleanup and rollback</h3><pre>kubectl delete namespace backup-drill --ignore-not-found</pre><pre># Vault Lock blocks deleting recovery points until their lifecycle ends, even for root.<br># In governance mode an administrator can remove the lock first (compliance mode: you wait).<br>aws backup delete-backup-vault-lock-configuration --region &quot;$AWS_REGION&quot; --backup-vault-name &quot;$PRIMARY_VAULT&quot;</pre><pre># Recovery points must go before their vaults: children first, then the composite.<br>for rp in $(aws backup list-recovery-points-by-backup-vault --region &quot;$AWS_REGION&quot; --backup-vault-name &quot;$PRIMARY_VAULT&quot; \<br>    --by-resource-type EKS --query &quot;RecoveryPoints[?IsParent==\`true\`].RecoveryPointArn&quot; --output text); do<br>  &quot;$REPO/scripts/delete-recovery-point.sh&quot; &quot;$PRIMARY_VAULT&quot; &quot;$rp&quot;      # asks for confirmation<br>done<br># Repeat both steps for &quot;$DR_VAULT&quot; with --region ap-south-1 / AWS_REGION=ap-south-1.</pre><pre>cd &quot;$REPO/terraform&quot;<br>terraform state rm &#39;aws_backup_vault_lock_configuration.primary&#39; &#39;aws_backup_vault_lock_configuration.dr&#39;  # locks already removed above<br>terraform destroy</pre><blockquote><strong>Warning:</strong> • terraform destroy <strong>can&#39;t delete a vault that still contains recovery points</strong>, and a locked vault&#39;s recovery points can&#39;t be deleted before their lifecycle (35 days here) ends. A governance-mode lock can be removed by an administrator, as above. A compliance-mode vault can&#39;t be cleaned up early. You wait. • Removing the lock in production defeats its purpose. Do it only in sandboxes, and audit who holds that permission. • <strong>Restores create real resources</strong> that are billed and that Terraform doesn&#39;t track: EBS volumes from restored PVCs, new EFS file systems with their random prefixes, and S3 buckets. Delete them after a drill. Delete the PVCs with a Delete reclaim policy, and remove the EFS file systems and buckets by hand. • KMS keys enter a 30-day pending-deletion window. <strong>Never</strong> delete a key that encrypts recovery points you still need.</blockquote><p>Rolling back a plan change is a plain terraform apply of the previous commit. Existing recovery points keep their original lifecycle.</p><h3>Production-readiness checklist</h3><ul><li>☐ Cluster authentication mode is API or API_AND_CONFIG_MAP; preflight runs before the window (or as a CI check)</li><li>☐ All PVs use CSI StorageClasses; no in-tree provisioners; S3 buckets versioned</li><li>☐ Add-ons, node groups and StorageClasses live in IaC (backup isn’t config management)</li><li>☐ Separate backup and restore roles; every restore job notifies (both Regions)</li><li>☐ CMK per vault; Vault Lock (governance → compliance after a quarter); DR copy at backup time; warm storage for copied points</li><li>☐ SNS on a customer managed key: job failures (incl. PARTIAL) <strong>and</strong> EKS_*_OBJECT_* events, in both Regions; email subscriptions confirmed</li><li>☐ Monthly scripted restore drill with checksum verification; RTO recorded</li><li>☐ DR cluster buildable from IaC in the DR Region; ECR replicated; Pod Identity for portable workloads</li><li>☐ Database PVs also have application-consistent backups</li></ul><h3>Key takeaways</h3><ul><li>AWS Backup for EKS backs up <strong>state plus volumes as one composite</strong>. Read child job status, not just the parent.</li><li>Restores <strong>never overwrite</strong>. Plan rollbacks around deletion, or around restoring into a different target.</li><li>Restore into a cluster <strong>your IaC built</strong>. “Create a new cluster” was the slowest and least reliable path in my tests.</li><li>“Completed with issues” is invisible without <strong>object-level notifications</strong>. Wire them up on day one.</li><li>Copy to DR <strong>at backup time</strong>. Cold recovery points can’t be copied cross-Region.</li></ul><h3>What was validated</h3><ul><li><strong>Terraform:</strong> tofu validate and fmt -check (OpenTofu 1.10.7, AWS provider 6.20.0) and tflint: pass. The provider rejected the EKS vault event names, which is why they&#39;re configured by a script (Step 4).</li><li><strong>Checkov:</strong> 6 findings, all on the standard root statement of the two KMS key policies (vault and SNS keys), accepted.</li><li><strong>Kubernetes and scripts:</strong> kubeconform -strict, yamllint and shellcheck pass. The restore metadata JSON (namespace and full) was generated offline and matches the documented format.</li><li><strong>Hands-on results:</strong> the screenshots, the restore timings and the results table in Decision 1 come from the author’s hands-on runs (Nov 2025), done through the console.</li><li><strong>Not run end-to-end on AWS in its final form:</strong> the Terraform and scripts in this article haven’t been run against AWS together. The preflight output is illustrative.</li></ul><h3>References</h3><ul><li><a href="https://aws.amazon.com/about-aws/whats-new/2025/11/aws-backup-supports-amazon-eks">AWS Backup now supports Amazon EKS (What’s New, 10 Nov 2025)</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/eks-backups.html">Amazon EKS backups, AWS Backup Developer Guide</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/restoring-eks.html">Restore an Amazon EKS cluster, AWS Backup Developer Guide</a></li><li><a href="https://docs.aws.amazon.com/eks/latest/userguide/integration-backup.html">Back up your EKS clusters with AWS Backup, EKS User Guide</a></li><li><a href="https://aws.amazon.com/blogs/aws/secure-eks-clusters-with-the-new-support-for-amazon-eks-in-aws-backup/">AWS News Blog: Secure EKS clusters with the new support for Amazon EKS in AWS Backup</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/security-iam-awsmanpol.html">AWS Backup managed policies (EKS permissions added 10 Nov 2025)</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/backup-feature-availability.html">Feature availability by resource</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html">AWS Backup Vault Lock</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/backup-notifications.html">Backup vault notifications (incl. EKS object events)</a></li><li><a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/eventbridge.html">AWS Backup events in EventBridge</a></li><li><a href="https://aws.amazon.com/backup/pricing/">AWS Backup pricing</a></li><li><a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html">EKS Pod Identity</a></li></ul><p><em>If this saved you a failed restore, follow me for production-focused AWS, EKS and DevOps write-ups. I’m Arbind Kr. Mahato (Tech Mahato): Cloud &amp; DevOps engineer, AWS Community Builder, AWS Certified Solution Architect, CKA, CKAD &amp; CKS.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23fa590f2138" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[❌ Why Most DevOps Engineers Struggle in Production (And the Learning Order That Fixes Everything)]]></title>
            <link>https://medium.com/@techmahato/why-most-devops-engineers-struggle-in-production-and-the-learning-order-that-fixes-everything-09af4b3bf15d?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/09af4b3bf15d</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 03:57:13 GMT</pubDate>
            <atom:updated>2025-12-13T03:57:13.229Z</atom:updated>
            <content:encoded><![CDATA[<p>Most DevOps engineers fail in production not due to lack of tools — but due to skipped fundamentals. Learn the exact DevOps learning roadmap that prevents burnout, outages, and career stagnation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lA7120ms-borrC9owBxHmQ.png" /></figure><h3>🎯 Outcome of This Blog</h3><p>After reading this blog, you will:</p><ul><li>Understand <strong>why DevOps engineers struggle in real production environments</strong></li><li>Learn the <strong>correct DevOps learning sequence</strong> used by strong engineers</li><li>Avoid costly mistakes caused by skipping fundamentals</li><li>Build <strong>long-term career stability</strong>, not tool-based shortcuts</li><li>Gain clarity on how to <strong>master Kubernetes the right way</strong> and monetize your skills</li></ul><h3>🚨 The Hard Truth About DevOps No One Tells You</h3><p>If you’re working in DevOps — or planning to move into it — this article can <strong>save you months (or years) of frustration</strong>.</p><p>Here’s the uncomfortable truth most engineers realize too late:</p><blockquote><strong><em>Modern DevOps tools are incredibly powerful.<br>But without strong fundamentals, they become fragile shortcuts.</em></strong></blockquote><p>I’ve seen this pattern repeatedly across startups, enterprises, and production systems:</p><ul><li>Engineers know Kubernetes, Terraform, CI/CD</li><li>But panic during incidents</li><li>Break systems while scaling</li><li>Struggle with debugging</li><li>Fear production deployments</li></ul><p><strong>The problem isn’t talent.<br>The problem is learning things in the wrong order.</strong></p><h3>🔍 Why DevOps Engineers Fail in Production</h3><p>Most DevOps struggles come from <strong>skipping foundations</strong> and jumping straight to shiny tools.</p><p>When fundamentals are weak:</p><ul><li>Kubernetes feels “magical” until it breaks</li><li>Automation amplifies mistakes</li><li>Scaling multiplies failures</li><li>Costs spiral out of control</li></ul><p><strong>Strong DevOps engineers aren’t tool experts first.<br>They are fundamentals experts first.</strong></p><h3>🧱 The DevOps Learning Sequence Most Engineers Wish They Followed</h3><p>Let’s break this down clearly.</p><h4>1️⃣ Foundations First (Non-Negotiable)</h4><h4>✅ Learn Linux before Kubernetes</h4><p>Containers don’t float in the air.<br> They run on <strong>Linux processes, namespaces, cgroups, and filesystems</strong>.</p><p>If Linux is weak, Kubernetes will always feel confusing.</p><h4>✅ Learn Networking before VPCs</h4><p>Before AWS VPC diagrams, you must understand:</p><ul><li>Subnets</li><li>Routing</li><li>NAT</li><li>Firewalls</li><li>TCP/IP basics</li></ul><p>Cloud networking is <strong>not new networking</strong> — it’s networking with APIs.</p><h4>2️⃣ Platform Before Orchestration</h4><h4>✅ Learn Containers before EKS or AKS</h4><p>Kubernetes orchestrates containers.<br> It does <strong>not</strong> replace container fundamentals.</p><p>If you don’t understand:</p><ul><li>Dockerfiles</li><li>Image layers</li><li>Networking between containers</li><li>Volumes</li></ul><p>Kubernetes will feel overwhelming.</p><h4>✅ Learn IAM before multi-account strategies</h4><p>Security should always come <strong>before scale</strong>.</p><p>If IAM concepts are unclear, multi-account setups become dangerous, not powerful.</p><h4>3️⃣ Infrastructure Before Automation</h4><h4>✅ Learn EC2 basics before Auto Scaling Groups</h4><p>Scaling a broken system doesn’t fix it.<br> It just creates <strong>more broken systems</strong> — faster.</p><h4>✅ Learn DNS before Ingress Controllers</h4><p>All traffic starts with <strong>name resolution</strong>.<br> Ingress, ALB, NLB, Service Mesh — everything depends on DNS.</p><h4>✅ Learn Load Balancing before Service Mesh</h4><p>Service Mesh is advanced.<br> Don’t add complexity until you’ve <strong>earned it</strong>.</p><h4>4️⃣ Operations Before Abstractions</h4><h4>✅ Learn CI basics before full CD pipelines</h4><p>Automation without understanding leads to chaos.</p><p>You must know:</p><ul><li>What you’re automating</li><li>Why failures happen</li><li>How to roll back safely</li></ul><h4>✅ Learn Stateful Apps before StatefulSets</h4><p>Kubernetes objects don’t remove data complexity.<br> Databases still break. Disks still fail.</p><h4>✅ Learn Resource Requests &amp; Limits before Karpenter</h4><p>Cost optimization starts with <strong>right sizing</strong>, not autoscaling magic.</p><h4>✅ Learn Pod Lifecycle before Operators</h4><p>Controllers only make sense when you understand <strong>how Pods live, die, and restart</strong>.</p><h4>💡 The Core Lesson Most Engineers Miss</h4><blockquote><strong><em>Strong DevOps engineers are built on fundamentals — not buzzwords.</em></strong></blockquote><p>Tools will change:</p><ul><li>Docker → containerd</li><li>EKS → something else</li><li>Terraform → newer IaC tools</li></ul><p>But <strong>Linux, networking, security, and systems thinking compound for decades</strong>.</p><h3>📈 Why This Matters for Your Career</h3><p>Engineers who follow the right learning order:</p><ul><li>Debug faster</li><li>Handle production incidents calmly</li><li>Design scalable architectures</li><li>Earn trust from teams and leadership</li><li>Command higher salaries</li></ul><p>Those who skip it:</p><ul><li>Depend on trial-and-error</li><li>Fear outages</li><li>Burn out faster</li></ul><h3>🚀 Want to Master Kubernetes and Monetize Your Skills?</h3><p>If you’re serious about <strong>mastering Kubernetes the right way</strong> — and not just using it —</p><p>I’ve designed a practical program to help you:</p><h4>🎓 Master Kubernetes &amp; Generate 4 Sources of Income</h4><p>Inside the course, you’ll learn:</p><ul><li>Kubernetes fundamentals → production mastery</li><li>Real-world architecture &amp; troubleshooting</li><li>How to teach, consult, freelance, and create products</li><li>How to turn Kubernetes skills into <strong>multiple income streams</strong></li></ul><p>👉 <strong>Click the link below to learn more and enroll</strong><br> <strong>“Master Kubernetes &amp; Generate 4 Source of Income”</strong></p><h3>🧠 Content Summary</h3><ul><li>DevOps struggles are caused by <strong>skipped fundamentals</strong>, not lack of tools</li><li>Learning order matters more than tool count</li><li>Linux, networking, containers, and security come first</li><li>Kubernetes and automation work best <strong>after</strong> fundamentals</li><li>Strong foundations = long-term DevOps success</li></ul><h3>💬 Let’s Hear From You</h3><p>Would you change this learning order — or do you strongly agree with it?</p><p>👇 <strong>Drop your experience in the comments</strong><br> 👏 <strong>Clap if this resonated</strong><br> 🔔 <strong>Subscribe / Follow for more real-world DevOps insights</strong><br> 🔁 <strong>Share this with someone struggling in DevOps</strong></p><p>Let’s help engineers build <strong>careers that last — not shortcuts that break</strong>.</p><p>Cheers,<br> <strong>Arbind</strong><br> <em>Senior Cloud &amp; DevOps Engineer</em></p><p>#DevOps #CloudEngineering #Kubernetes #AWS #CareerGrowth</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09af4b3bf15d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ 3-Month Cloud & DevOps Live Training in Hindi — Kickstart Your IT Career!]]></title>
            <link>https://medium.com/@techmahato/3-month-cloud-devops-live-training-in-hindi-kickstart-your-it-career-354fea8bd28a?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/354fea8bd28a</guid>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Sat, 01 Nov 2025 14:56:11 GMT</pubDate>
            <atom:updated>2025-11-01T14:56:11.624Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚀 3-Month Cloud &amp; DevOps Live Training in Hindi — Kickstart Your IT Career!</h3><p>If you are just complete college or you are working and looking for job change then Cloud and DevOps is the best for you because it is high in demand and Trending skill for 2025.</p><p>Are you a <strong>fresh graduate</strong> or a <strong>working professional</strong> looking to switch to a <strong>high-paying IT job</strong>? <strong>Cloud &amp; DevOps</strong> is one of the <strong>most in-demand and trending skills for 2025</strong>! This <strong>free live training in Hindi</strong> will help you master <strong>industry-relevant tools</strong> and gain hands-on experience to secure a <strong>job in Cloud &amp; DevOps</strong>.</p><p>💡 <strong>Don’t miss this opportunity!</strong> Learn from experts and fast-track your IT career. <strong>Read the full blog to get started!</strong> 🚀</p><h3>Why Choose Cloud &amp; DevOps in 2025? 🚀</h3><p>The <strong>IT industry is evolving rapidly</strong>, and <strong>Cloud &amp; DevOps</strong> have become the backbone of modern technology. Whether you are a <strong>fresh graduate</strong> or a <strong>working professional</strong> looking for a <strong>career change</strong>, mastering Cloud &amp; DevOps can open doors to <strong>high-paying jobs</strong> and <strong>endless career opportunities</strong>.</p><h4>1️⃣ High Demand &amp; Job Opportunities</h4><p>📈 <strong>Every company is moving to the cloud</strong> and adopting <strong>DevOps practices</strong> to improve efficiency. Top companies like <strong>Amazon, Google, Microsoft, and startups</strong> are hiring <strong>Cloud &amp; DevOps Engineers</strong> in bulk.</p><h4>2️⃣ Lucrative Salary Packages 💰</h4><p>💵 <strong>Cloud &amp; DevOps engineers earn ₹10–30 LPA in India</strong> and <strong>$100K+ globally</strong>. With the right skills, you can land <strong>a high-paying job faster</strong> than traditional IT roles.</p><h4>3️⃣ Future-Proof Career 🔥</h4><p>🚀 <strong>Cloud computing and automation are the future</strong>. As businesses continue to migrate to the cloud, skilled DevOps professionals will remain in <strong>high demand for years to come</strong>.</p><h4>4️⃣ Fast-Track Your IT Career 🎯</h4><p>⏳ Unlike traditional IT jobs, you don’t need <strong>years of experience</strong> to enter Cloud &amp; DevOps. With the right <strong>roadmap, hands-on training, and projects</strong>, you can become job-ready in just <strong>90 days</strong>!</p><h4>5️⃣ Work Flexibility &amp; Remote Opportunities 🌍</h4><p>💻 Cloud &amp; DevOps roles offer <strong>remote work flexibility</strong>, allowing you to <strong>work from anywhere</strong> and explore global opportunities.</p><h3>Why Is This Training Free? 🤔</h3><p>When I started my journey in <strong>Cloud &amp; DevOps</strong>, I spent <strong>a lot of money</strong> on various courses, but I didn’t get the right <strong>guidance or results</strong>. Everything changed when I found a <strong>mentor</strong> who provided me with a <strong>clear roadmap</strong> — that’s when I landed my <strong>first job</strong>.</p><p>At that moment, I promised myself: <strong>Once I succeed in this field, I will help others learn these skills for free.</strong> That’s why I have created this <strong>90-Day Cloud &amp; DevOps Course</strong> to mentor you, teach you in a structured way, and help you get a <strong>high-paying job</strong>.</p><p>However, to <strong>ensure only serious learners join</strong>, I am charging a <strong>small token registration fee of ₹1,000</strong>, which will be <strong>fully refunded</strong> once you complete the course.</p><p>💡 <strong>Why This Matters?</strong><br> 🚀 Many institutes charge <strong>lakhs of rupees</strong> for Cloud &amp; DevOps training, making it <strong>unaffordable</strong> for many students. I believe <strong>everyone deserves a chance</strong> to learn these high-demand skills, so I created this course to <strong>train and guide you towards a successful career</strong>.</p><p>🔥 <strong>This is your opportunity to learn Cloud &amp; DevOps for FREE!</strong> Join now and take the first step towards your dream IT job! 🚀</p><h3>Why Is There a Registration Fee of ₹1000?</h3><p>As a working Cloud &amp; DevOps Engineer with limited free time, I want to channel my passion and expertise into providing quality training. I’ve observed that some participants aren’t serious, and disruptive behavior can hinder the learning environment. To ensure a focused, high-quality experience for <strong>dedicated learners</strong>, I’ve introduced a small registration fee of ₹1000.</p><p>This fee guarantees that only committed individuals join the course. In return, you’ll receive hands-on training through <strong>10 real-world Cloud &amp; DevOps projects</strong>. You’ll have the opportunity to showcase your work on GitHub, making your profile stand out for high-paying IT job interviews. Complete the projects, and you’ll not only master essential skills but also receive a certificate — and your ₹1000 fee will be fully refunded.</p><p>This token fee is all about fostering a serious learning community focused on career growth in the Cloud &amp; DevOps industry.</p><p>Register Now</p><p>90-Day Rodmap for AWS Cloud Engineer</p><p>First 3 Month I will be focus on AWS Cloud Engineer Job and In this Course I will Cover AWS Certified Cloud Practicener and AWS Certified Solution Architect Associate.</p><p>I have breakdown this course into 12 Week and I will Cover 100+ project on AWS Cloud that will make master on AWS Clud and give you live project experience.</p><p>Week 1: AWS Cloud Practicener with Hands-On Labs</p><p>Week 2: Linux and Networking with Hands-On Labs</p><p>Week 3: Git and GitHub with Hands-On Labs</p><p>Week 4: Microservice, Docker Container &amp; Docker Hub with Hands-On Lab</p><p>Week 5: Kubernetes (WS EKS) and Helm with Hands-On Labs</p><p>Week 6: CI/CD Jenkins with Hands-On Lab</p><p>Week 7: Promethius &amp; Grafan with Hands-On Labs</p><p>Week 8: Terraform on AWS Service with Hands-On Labs</p><p>Week 9: Terraform on Kubernetes (AWS EKS) Hands-On Labs</p><p>Week 10: 3 DevOps Project Project Hands-On</p><p>Week 11: Create Linkedin Profile and Follow Like Minded People</p><p>Week 12: Create Resume and Share LinkedIn Friends</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=354fea8bd28a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When AWS US-East-1 Went Down — How to Make Sure Your Infra Doesn’t]]></title>
            <link>https://medium.com/@techmahato/when-aws-us-east-1-went-down-how-to-make-sure-your-infra-doesnt-10abc2d43ba9?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/10abc2d43ba9</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[tech-mahato]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 04:14:39 GMT</pubDate>
            <atom:updated>2025-10-22T04:14:39.109Z</atom:updated>
            <content:encoded><![CDATA[<h3>When AWS US-East-1 Went Down — How to Make Sure <em>Your Infra Doesn’t</em></h3><p><strong>On October 20, 2025, a DNS failure in AWS’s US-East-1 region</strong> triggered a cascade of disruptions, impacting <strong>DynamoDB, EC2, Lambda, and countless enterprise applications </strong>— from fintech platforms to global SaaS solutions. This outage, which affected major services like <strong>Snapchat, Alexa, and payment APIs</strong>, was a stark reminder: even the most robust cloud provider can falter. For enterprises running mission-critical workloads on AWS, this event underscores the urgent need for ironclad <strong>disaster recovery (DR) strategies</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ua4fXLkrs6GHpkC-n5SXwQ.png" /><figcaption>AWS US-East-1 Went Down</figcaption></figure><p>As a DevOps engineer, I’ve seen firsthand how a single point of failure can ripple across global operations. The US-East-1 outage wasn’t just a technical hiccup; it was a <strong>wake-up call for enterprises</strong> to prioritize resilience over reliance. Below, I outline <strong>three actionable DR solutions</strong> to ensure your AWS infrastructure can withstand similar disruptions, keeping your business online, your customers happy, and your revenue secure.</p><h3>The US-East-1 Outage: What Exactly Happened?</h3><p>Before diving into solutions, let’s recap the incident. On October 20, 2025, a DNS resolution failure in AWS’s US-East-1 (Northern Virginia) region disrupted the DynamoDB API endpoint. This caused widespread errors across dependent services like EC2, Lambda, API Gateway, and Route 53. By 6:30 AM ET, AWS mitigated the DNS issue, but some services, including EC2 instance launches and Lambda event processing, faced lingering latency and throttling.</p><p><strong>Let’s simplify it:</strong></p><ol><li><strong>The Trigger:</strong> A DNS issue prevented AWS services from talking to each other.</li><li><strong>The Domino Effect:</strong> DynamoDB went down — and since many core AWS services rely on it, everything from EC2 instance launches to Lambda invocations began failing.</li><li><strong>The Spread:</strong> Dependent applications (across gaming, fintech, and even healthcare) experienced massive slowdowns or outages.</li><li><strong>The Fix:</strong> AWS mitigated the DNS issue after a few hours, but several services continued to recover slowly as backlogs cleared.</li></ol><p>The impact was global. Enterprises relying on US-East-1 saw their applications — ranging from e-commerce platforms to real-time analytics — grind to a halt. This event exposed a critical truth: US-East-1 is a backbone for many AWS services, and a single-region dependency can cripple even the most sophisticated setups.</p><p>The takeaway? Enterprises must architect for failure. Below are three comprehensive DR solutions to make your AWS infrastructure resilient, ensuring uptime and trust even when the cloud stumbles.</p><h3>Lets Focus on Solution as DevOps &amp; Cloud Engineers</h3><h3><strong>Solution 1: Implement Multi-Region Architecture for Seamless Failover</strong></h3><h4>Why It Matters</h4><p>The US-East-1 outage highlighted the risk of single-region architectures. Many enterprises centralize workloads in US-East-1 due to its maturity and service availability, but this creates a single point of failure. A multi-region setup distributes workloads across geographically distinct AWS regions, ensuring your application stays online during regional disruptions.</p><h4>How to Implement</h4><ol><li><strong>Distribute Critical Workloads</strong>: Deploy your application across at least two AWS regions (e.g., US-East-1 and US-West-2 or EU-West-1). Use AWS Global Accelerator to route traffic to the healthiest region based on latency and availability.</li><li><strong>Replicate Data Across Regions</strong>: For databases like DynamoDB, enable <strong>DynamoDB Global Tables</strong> to replicate data across regions with low-latency synchronization. For RDS, configure cross-region read replicas with automated failover using Route 53 health checks.</li><li><strong>Leverage Route 53 for DNS Failover</strong>: Configure Route 53 with health checks and failover policies to redirect traffic to a secondary region if the primary region fails. Use latency-based routing to optimize performance.</li><li><strong>Automate Infrastructure Deployment</strong>: Use Infrastructure as Code (IaC) tools like Terraform or AWS CloudFormation to replicate environments across regions consistently. This reduces setup time during failover.</li></ol><h4>Enterprise Benefits</h4><ul><li><strong>Uptime Assurance</strong>: Multi-region setups ensure your application remains accessible, even during a regional outage.</li><li><strong>Customer Trust</strong>: Seamless failover minimizes disruptions, preserving user experience and brand reputation.</li><li><strong>Compliance</strong>: Multi-region architectures support regulatory requirements for high availability and data redundancy.</li></ul><h4>Pro Tip</h4><p>Test your multi-region setup regularly using AWS Fault Injection Simulator to validate failover performance. Ensure latency between regions doesn’t impact critical workloads by monitoring with CloudWatch.</p><h3>Solution 2: Automate Chaos Testing and Incident Response Playbooks</h3><h4>Why It Matters</h4><p>The US-East-1 outage showed that reactive firefighting leads to panic, not progress. Enterprises need proactive strategies to identify weaknesses and respond swiftly. Automated chaos testing and well-defined incident response playbooks transform outages from chaos to controlled recovery.</p><h4>How to Implement</h4><ol><li><strong>Conduct Chaos Testing</strong>: Use AWS Fault Injection Simulator to simulate regional failures, DNS issues, or service throttles. For example, simulate a DynamoDB outage in US-East-1 to test your application’s fallback to a secondary region.</li><li><strong>Build Comprehensive Playbooks</strong>: Create detailed incident response playbooks for common failure scenarios (e.g., DNS failure, EC2 launch errors, or database throttling). Include:</li></ol><ul><li>Step-by-step recovery actions (e.g., flushing DNS caches, scaling alternative resources).</li><li>Roles and responsibilities for incident response teams.</li><li>Communication templates for stakeholders and customers.</li></ul><ol><li><strong>Automate Recovery Actions</strong>: Use AWS Systems Manager Automation to execute predefined recovery steps, such as restarting failed services or redirecting traffic. Integrate with AWS Lambda for custom automation workflows.</li><li><strong>Test Playbooks Quarterly</strong>: Schedule regular drills to ensure your team can execute playbooks under pressure. Document lessons learned to refine processes.</li></ol><h4>Enterprise Benefits</h4><ul><li><strong>Faster Recovery</strong>: Automated testing and playbooks reduce mean time to recovery (MTTR), minimizing downtime costs.</li><li><strong>Team Confidence</strong>: Well-rehearsed processes empower teams to handle incidents calmly and efficiently.</li><li><strong>Stakeholder Trust</strong>: Clear communication during outages builds trust with customers and leadership.</li></ul><h4>Pro Tip</h4><p>Integrate chaos testing results with AWS CloudTrail and CloudWatch Logs Insights to analyze failure patterns and optimize your DR strategy.</p><h3>Solution 3: Strengthen DNS Redundancy and Monitoring</h3><h4>Why It Matters</h4><p>The root cause of the US-East-1 outage was a DNS resolution failure, which crippled DynamoDB and downstream services. Enterprises must prioritize redundant DNS configurations and robust monitoring to detect and mitigate issues before they escalate.</p><h4>How to Implement</h4><ol><li><strong>Configure Redundant DNS</strong>: Use Route 53 with health checks to monitor endpoint availability. Set up failover DNS records to redirect traffic to a secondary region or provider if the primary DNS fails. Consider a secondary DNS provider (e.g., Cloudflare) for added resilience.</li><li><strong>Flush DNS Caches Proactively</strong>: During the outage, AWS recommended flushing DNS caches to resolve DynamoDB endpoint issues. Automate cache flushing using scripts triggered by Route 53 health check failures.</li><li><strong>Enhance Monitoring</strong>: Deploy comprehensive monitoring with AWS CloudWatch for real-time metrics on service health, latency, and error rates. Complement with third-party tools like Datadog or New Relic for cross-region visibility and advanced alerting.</li><li><strong>Set Up Proactive Alerts</strong>: Configure CloudWatch Alarms to notify your team of anomalies, such as increased API error rates or EC2 launch failures. Use SNS or PagerDuty to escalate alerts to on-call engineers.</li></ol><h4>Enterprise Benefits</h4><ul><li><strong>Early Detection</strong>: Robust monitoring catches issues before they impact users, reducing downtime.</li><li><strong>Resilient DNS</strong>: Redundant DNS configurations prevent single points of failure, ensuring service availability.</li><li><strong>Cost Savings</strong>: Proactive alerts and automation reduce the financial impact of prolonged outages.</li></ul><h4>Pro Tip</h4><p>Use Route 53 Application Recovery Controller to simplify failover management and ensure consistent DNS updates across regions.</p><h4>Key Takeaways for Enterprises</h4><p>The US-East-1 outage was a humbling reminder that no cloud is infallible. Enterprises running on AWS must shift from assuming uptime to designing for failure. By implementing multi-region architectures, automating chaos testing, and strengthening DNS redundancy and monitoring, you can ensure your infrastructure withstands disruptions. These solutions aren’t just technical — they’re strategic imperatives to protect revenue, reputation, and customer trust.</p><h4>Immediate Actions</h4><ul><li><strong>Review Your Architecture</strong>: Audit your AWS setup for single-region dependencies. Prioritize multi-region deployment for critical workloads.</li><li><strong>Test Your DR Plan</strong>: Schedule a chaos testing session within the next 30 days to validate resilience.</li><li><strong>Monitor the AWS Health Dashboard</strong>: Stay updated on recovery efforts (https://lnkd.in/gddJABiK) and apply recommended fixes, like flushing DNS caches for DynamoDB.</li></ul><h4>The Road Ahead</h4><p>The cloud powers enterprise innovation, but resilience is what keeps it running. The US-East-1 outage is a chance to learn, adapt, and build smarter. As DevOps professionals, let’s commit to architectures that don’t just scale — they survive.</p><blockquote><strong>What steps is your enterprise taking to strengthen AWS resilience? Share your thoughts or DM me to discuss DR strategies!</strong></blockquote><h4>Final Thoughts</h4><p><strong>Cloud outages like this one are rare, but they <em>do</em> happen — and today’s events were a blunt reminder of that.</strong> The AWS US-East-1 outage showed that even the most advanced cloud can have a bad day, and the impact can be massive. For those of us building on the cloud, it’s a humbling lesson: <strong>the cloud is powerful, but not infallible</strong>.</p><p>The good news? We can learn and improve. Use this as motivation to <strong>audit your own infrastructure</strong>: Are you truly multi-region or just one failure away from downtime? Do you have a tested DR plan, or is it gathering dust? Now is the time to fix the roof <em>before</em> the next storm comes.</p><p>In summary: <strong>Stay calm. Stay redundant. Stay resilient.</strong> 💪☁️ When one cloud data center goes dark, let’s make sure our systems can shine through the gloom. <strong>Build smarter, not just bigger — and design for the inevitable rainy day</strong>. Your future self (and your customers) will thank you when disaster strikes the next time, and you’re already prepared.</p><blockquote><strong>If you found this blog helpful, drop your thoughts in the comments and give it a clap! Your support means a lot — it keeps me inspired to create more content that helps you grow and learn.</strong></blockquote><p>💪 #AWSEnterprise #DisasterRecovery #CloudArchitecture</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10abc2d43ba9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Ultimate Kubernetes Key Commands Cheat Sheet (With Examples) — For Beginners in 2025 ]]></title>
            <link>https://awstip.com/the-ultimate-kubernetes-key-commands-cheat-sheet-with-examples-for-beginners-in-2025-3a084fd64351?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a084fd64351</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes-command]]></category>
            <category><![CDATA[kubernetes-cheatsheet]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[tech-mahato]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Tue, 15 Jul 2025 04:10:46 GMT</pubDate>
            <atom:updated>2025-07-21T15:06:00.402Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Ultimate Kubernetes Key Commands Cheat Sheet (With Examples) — For Beginners in 2025 🚀</h3><p><strong>Author:</strong> <em>Tech Mahato — Kubernetes Expert | 10+ Years Experience | 10K+ Followers on Medium, LinkedIn &amp; YouTube</em><br><em>Follow me for DevOps, Cloud &amp; Kubernetes tutorials made simple.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YztPRxBQjT7fJpsnAddz0A.png" /><figcaption>The Ultimate Kubernetes Key Commands Cheat Sheet (With Examples)</figcaption></figure><h3>🔍 Why Learn Kubernetes Key Commands?</h3><p>If you’re diving into Kubernetes (K8s) in <strong>2025</strong>, mastering kubectl commands is non-negotiable. Whether you&#39;re:</p><p>👨‍💻 A developer deploying microservices<br> 🔧 A DevOps engineer managing infrastructure<br> 🧪 A student preparing for CKA, CKAD, or CKS exams</p><p>This beginner-friendly cheat sheet delivers <strong>actionable </strong><strong>kubectl commands</strong>, <strong>real-world examples</strong>, and <strong>pro tips</strong> to help you navigate Kubernetes like a pro. With SEO-structured formatting and visual clarity, it&#39;s your go-to K8s guide.</p><p>Let’s dive in! 🧭</p><h3>🧭 1. Cluster Management — Your Kubernetes Control Room</h3><p>These commands help you inspect the cluster’s health, nodes, and connectivity — <strong>your first checkpoint</strong> in troubleshooting or configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*DGGBqTl5VuZDQoVzvgiN3w.png" /></figure><h4>🧪 Example:</h4><pre>kubectl get nodes</pre><p><strong>Output:</strong></p><pre>NAME       STATUS   ROLES    AGE   VERSION<br>node-1     Ready    worker   10d   v1.28.2</pre><h3>🧱 2. Pod Management — Manage Your App Containers</h3><p>Pods are the <strong>smallest deployable units</strong> in Kubernetes. These commands help you interact, debug, and manage pod lifecycles.</p><h4>🔧 Key Commands:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*LDpkHCZDwEwlJodwG4-UyA.png" /></figure><h4>🧪 Example:</h4><pre>kubectl logs nginx-6d6b75cc7b-jk5vn</pre><h3>📊 3. Resource Monitoring — Track Usage and Performance</h3><p>Resource monitoring helps you analyze <strong>CPU</strong>, <strong>memory</strong>, and <strong>quota</strong> usage to identify bottlenecks or overuse.</p><h4>🔧 Key Commands:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*dDYU97QDQSwLgd5T_UVTzQ.png" /></figure><h4>🧪 Example:</h4><pre>kubectl top pods -n kube-system</pre><h3>🌐 4. Service Management — Make Your App Reachable</h3><p>Services expose your pods internally or externally. Think of them as <strong>entry points</strong> to your applications.</p><h3>🔧 Key Commands:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*BKva5u1G8LYvoy7hh216_Q.png" /></figure><h4>🧪 Example:</h4><pre>kubectl expose deployment nginx --type=NodePort --port=80</pre><h3>🔐 5. Configuration &amp; Secrets — Secure Your App Settings</h3><p>Use <strong>ConfigMaps</strong> for environment variables and <strong>Secrets</strong> for sensitive data (like DB passwords or API keys).</p><h4>🔧 Key Commands:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*AG45MQkZI4VS_Le-cv_4ow.png" /></figure><h3>🚀 6. Deployment Management — Scale, Rollout, Rollback</h3><p>Deployments let you <strong>automate</strong>, <strong>scale</strong>, and <strong>manage updates</strong> to your applications easily.</p><h4>🔧 Key Commands:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*VxdkVi3OlfZkpGXDLyv1Pw.png" /></figure><h3>🧭 7. Namespace Management — Isolate and Organize</h3><p>Namespaces help separate <strong>dev</strong>, <strong>test</strong>, and <strong>prod</strong> environments inside the same cluster.</p><h4>🔧 Key Commands:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*eVvPTCQKXyfDqqrL-HNW7Q.png" /></figure><h3>🧠 Pro Tips to Accelerate Your Kubernetes Journey</h3><p>✅ Use kubectl get all -n &lt;namespace&gt; to view everything in a namespace<br> ✅ Use kubectl explain &lt;resource&gt; to learn object syntax<br> ✅ Practice on your laptop using minikube or kind<br> ✅ Try UI tools: K9s, Lens, or Octant for a visual dashboard</p><h3>📌 Command Quick Reference</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*5zFEvNZct5YZG1gcYosGJQ.png" /></figure><h3>🔥 Bonus: Docker &amp; Kubernetes Zero to Hero</h3><p>📥 Do you want to become master in DevOps then master the kubernetes beacause it is a backbone of DevOps.</p><p>Learn Kubernetes &amp; Generate 3 source of income. Book Demo Class <a href="https://forms.gle/eMvDspHf56v61gL39">https://forms.gle/eMvDspHf56v61gL39</a></p><h3>✍️ Final Words</h3><p>Mastering kubectl commands is your <strong>first milestone</strong> toward becoming a confident Kubernetes engineer.<br> Whether you’re managing apps in production or preparing for certifications like <strong>CKA</strong>, these commands will save you time and boost efficiency.</p><h3>🔗 Let’s Connect!</h3><p>📌 <strong>Medium</strong>: <a href="https://medium.com/@techmahato">medium.com/@techmahato</a><br> 📌 <strong>LinkedIn</strong>: <a href="https://linkedin.com/in/techmahato">linkedin.com/in/techmahato</a><br> 📌 <strong>YouTube</strong>: <em>Tech Mahato: Kubernetes visual guides + live demos</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a084fd64351" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/the-ultimate-kubernetes-key-commands-cheat-sheet-with-examples-for-beginners-in-2025-3a084fd64351">The Ultimate Kubernetes Key Commands Cheat Sheet (With Examples) — For Beginners in 2025 🚀</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps Roadmap 2025: How to Become a DevOps Engineer (Step-by-Step Guide)]]></title>
            <link>https://medium.com/@techmahato/devops-roadmap-2025-how-to-become-a-devops-engineer-step-by-step-guide-a451d054f815?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a451d054f815</guid>
            <category><![CDATA[tech-mahato]]></category>
            <category><![CDATA[devops-courses]]></category>
            <category><![CDATA[devops-roadmap]]></category>
            <category><![CDATA[devops-training]]></category>
            <category><![CDATA[cloud-computing-training]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Sun, 23 Mar 2025 05:24:15 GMT</pubDate>
            <atom:updated>2025-03-23T05:24:15.311Z</atom:updated>
            <content:encoded><![CDATA[<p>Master your DevOps journey with our 2025 roadmap. Learn Linux, Git, Docker, Kubernetes, and more with easy steps to become a skilled DevOps Engineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FDqpPQC6-qa7E_ZLnXn1FQ.png" /><figcaption>Master your DevOps journey with our 2025 roadmap. Learn Linux, Git, Docker, Kubernetes, and more with easy steps to become a skilled DevOps Engineer.</figcaption></figure><h3>Introduction</h3><p>DevOps is one of the most in-demand fields in the IT industry today. Companies are looking for skilled DevOps engineers who can automate processes, manage infrastructure, and ensure smooth deployment of applications. If you’re wondering <strong>how to become a DevOps engineer in 2025</strong>, this guide will provide a clear roadmap with all the necessary tools and technologies.</p><p>By the end of this blog, you will understand:<br> ✅ What a DevOps engineer does<br> ✅ The essential skills and tools you need to learn<br> ✅ A step-by-step roadmap to becoming a DevOps engineer<br> ✅ The best resources to learn DevOps</p><h3>What Does a DevOps Engineer Do?</h3><p>A <strong>DevOps Engineer</strong> bridges the gap between development (Dev) and operations (Ops) teams. Their main responsibilities include:</p><p>✔ <strong>Application Deployment</strong> — Setting up servers, databases, and infrastructure.<br> ✔ <strong>Automation</strong> — Reducing manual work by writing scripts and using tools like Ansible, Terraform, and CI/CD pipelines.<br> ✔ <strong>Monitoring &amp; Troubleshooting</strong> — Ensuring applications run smoothly after deployment.</p><p>🔹 <strong>Why is DevOps Important?</strong></p><ul><li>Companies release software <strong>faster</strong> and with <strong>fewer errors</strong> using DevOps.</li><li>DevOps salaries are high — <strong>$130,000+ in the US</strong> and <strong>₹10L+ per year in India</strong>.</li></ul><h3>Step-by-Step DevOps Roadmap (Beginner to Expert)</h3><p>If you are new to DevOps, <strong>follow this learning path</strong> to build a strong foundation.</p><h3>📌 Step 1: Learn the Software Development Life Cycle (SDLC)</h3><p>Understanding how software moves from planning to deployment will help you know where DevOps fits.</p><p>🔹 What to Learn:<br> ✔ The stages of SDLC — Planning, Coding, Testing, Deployment<br> ✔ How DevOps improves software delivery speed</p><p>Free Learning Resource: <a href="https://www.youtube.com/live/z6AlFH-ufFo?si=h8Ih58pp2LgMsd1i">https://www.youtube.com/live/z6AlFH-ufFo?si=h8Ih58pp2LgMsd1i</a></p><h3>📌 Step 2: Learn Linux &amp; System Administration</h3><p>Most DevOps tools run on <strong>Linux</strong>, so knowing Linux is essential.</p><p>🔹 What to Learn:<br> ✔ <strong>Basic Shell Commands</strong> (ls, cd, cp, mv, grep)<br> ✔ <strong>File Permissions &amp; Ownership</strong> (chmod, chown)<br> ✔ <strong>User Management</strong> (adduser, passwd)<br> ✔ <strong>SSH (Secure Shell)</strong> — Connecting to remote servers<br> ✔ <strong>Package Management</strong> — (APT for Ubuntu, YUM for CentOS)</p><p>🛠 <strong>Hands-on Practice</strong> — Install a Linux OS (Ubuntu/CentOS) and try commands in the terminal.</p><p>Free Learning Resource: <a href="https://youtu.be/sWbUDq4S6Y8?si=R4dOEgmkVrEOE2vR">https://youtu.be/sWbUDq4S6Y8?si=R4dOEgmkVrEOE2vR</a></p><h3>📌 Step 3: Learn a Scripting Language (Bash, Python, or Go)</h3><p>Automation is a key DevOps skill. You must learn <strong>at least one scripting language</strong> to automate tasks.</p><p>🔹 Best Languages for DevOps:<br> ✔ <strong>Bash</strong> — Best for scripting on Linux<br> ✔ <strong>Python</strong> — Great for automation, APIs, and infrastructure management<br> ✔ <strong>Go</strong> — Used in Kubernetes and cloud automation</p><p>🛠 <strong>Hands-on Practice</strong> — Write a script to automate a simple task, such as cleaning up logs or scheduling backups.</p><p>Free Learning Resource: <a href="https://youtu.be/ix9cRaBkVe0?si=L9UCjP-PZGOPioLf">https://youtu.be/ix9cRaBkVe0?si=L9UCjP-PZGOPioLf</a></p><h3>📌 Step 4: Master Git &amp; Version Control</h3><p>Git is <strong>the backbone of DevOps workflows</strong>. Every DevOps engineer must know <strong>how to use Git and GitHub/GitLab</strong>.</p><p>🔹 What to Learn:<br> ✔ <strong>Git Basics</strong> — Clone, Commit, Push, Pull<br> ✔ <strong>Branching &amp; Merging</strong> — Creating and switching between branches<br> ✔ <strong>Pull Requests &amp; Merge Requests</strong> — Used in team collaboration</p><p>🛠 <strong>Hands-on Practice</strong> — Create a GitHub repository and push your first project.</p><p>Free Learning Resource: <a href="https://youtu.be/Jdc0i7RcBv8?si=ci4eUFZy4RD19etj">https://youtu.be/Jdc0i7RcBv8?si=ci4eUFZy4RD19etj</a></p><p>And <a href="https://youtu.be/Jdc0i7RcBv8?si=ci4eUFZy4RD19etj">https://youtu.be/Jdc0i7RcBv8?si=ci4eUFZy4RD19etj</a></p><h3>📌 Step 5: Learn Networking &amp; Security Basics</h3><p>DevOps engineers <strong>deploy and manage applications</strong>, so they need to understand networking concepts.</p><p>🔹 What to Learn:<br> ✔ <strong>IP Addressing</strong> — How computers communicate on networks<br> ✔ <strong>Ports &amp; Protocols</strong> — TCP, HTTP, HTTPS, DNS<br> ✔ <strong>Firewalls &amp; Security</strong> — Securing cloud applications</p><p>🛠 <strong>Hands-on Practice</strong> — Set up a basic firewall on a Linux server.</p><p>Free Learning Resource: <a href="https://youtu.be/IPvYjXCsTg8?si=EnX6jHTpYZ3hKzji">https://youtu.be/IPvYjXCsTg8?si=EnX6jHTpYZ3hKzji</a></p><h3>📌 Step 6: Learn Cloud Computing (AWS, Azure, or GCP)</h3><p>Most companies run applications in the <strong>cloud</strong>, so knowing <strong>at least one cloud platform</strong> is a must.</p><p>🔹 Best Cloud Providers for DevOps:<br> ✔ <strong>AWS</strong> — Most popular cloud provider<br> ✔ <strong>Azure</strong> — Used by many enterprises<br> ✔ <strong>GCP</strong> — Growing fast with Kubernetes support</p><p>🛠 <strong>Hands-on Practice</strong> — Create a free-tier AWS account and deploy a simple EC2 server.</p><p>Free Learning Resource: <a href="https://www.youtube.com/playlist?list=PL7foQG1Y7xk-kM32_Vkeh0tob8sb9cGbY">https://www.youtube.com/playlist?list=PL7foQG1Y7xk-kM32_Vkeh0tob8sb9cGbY</a></p><h3>📌 Step 7: Learn Infrastructure as Code (IaC) — Terraform &amp; Ansible</h3><p>IaC allows you to <strong>automate infrastructure setup using code</strong>, making deployments faster and error-free.</p><p>🔹 What to Learn:<br> ✔ <strong>Terraform</strong> — Create cloud resources with code<br> ✔ <strong>Ansible</strong> — Automate server configuration</p><p>🛠 <strong>Hands-on Practice</strong> — Use Terraform to create an EC2 instance on AWS</p><p>Free Learning Resource: <a href="https://youtu.be/SPcwo0Gq9T8?si=asDD_Z7tJ1QOfse-">https://youtu.be/SPcwo0Gq9T8?si=asDD_Z7tJ1QOfse-</a></p><p>Free Learning Resource: <a href="https://youtu.be/q8MX_ldXrt8?si=yeRgU9MmhL56VcAb">https://youtu.be/q8MX_ldXrt8?si=yeRgU9MmhL56VcAb</a></p><p>.</p><h3>📌 Step 8: Learn Docker &amp; Containerization</h3><p>Containers allow applications to <strong>run consistently across different environments</strong>.</p><p>🔹 What to Learn:<br> ✔ <strong>Docker Basics</strong> — Containers, Images, Dockerfile<br> ✔ <strong>Docker Compose</strong> — Running multiple containers together</p><p>🛠 <strong>Hands-on Practice</strong> — Create a Docker container for a simple web application.</p><p>Free Learning Resource: <a href="https://youtu.be/Wf2eSG3owoA?si=vi_9AhGPlaqa-Pp_">https://youtu.be/Wf2eSG3owoA?si=vi_9AhGPlaqa-Pp_</a></p><p>Docker Free Learning Resource: <a href="https://youtu.be/Jdc0i7RcBv8?si=17BjmSo78Rh1StJW">https://youtu.be/Jdc0i7RcBv8?si=17BjmSo78Rh1StJW</a></p><h3>📌 Step 9: Learn Kubernetes for Container Orchestration</h3><p>Kubernetes <strong>manages multiple containers</strong> efficiently and is used in almost every DevOps setup.</p><p>🔹 What to Learn:<br> ✔ <strong>Kubernetes Architecture</strong> — Nodes, Pods, Deployments<br> ✔ <strong>kubectl Commands</strong> — Managing Kubernetes clusters<br> ✔ <strong>Helm Charts</strong> — Automating Kubernetes deployments</p><p>🛠 <strong>Hands-on Practice</strong> — Deploy a containerized app on a local Kubernetes cluster using Minikube.</p><p>Free Learning Resource: <a href="https://youtu.be/JoHUi9KvnOA?si=OA4__f6ILz0sU_dN">https://youtu.be/JoHUi9KvnOA?si=OA4__f6ILz0sU_dN</a></p><h3>📌 Step 10: Learn CI/CD Pipelines (Jenkins, GitHub Actions, GitLab CI/CD)</h3><p>CI/CD automates testing and deployment, making software <strong>delivery faster and more reliable</strong>.</p><p>🔹 Best CI/CD Tools:<br> ✔ <strong>Jenkins</strong> — Most popular CI/CD tool<br> ✔ <strong>GitHub Actions</strong> — Integrated with GitHub<br> ✔ <strong>GitLab CI/CD</strong> — Built-in CI/CD for GitLab</p><p>🛠 <strong>Hands-on Practice</strong> — Create a simple CI/CD pipeline that builds and deploys an app.</p><p>Jenkins Free Learning Resource: <a href="https://www.youtube.com/live/QIhRgW7OhPY?si=6z5C5idfe2rYMIJd">https://www.youtube.com/live/QIhRgW7OhPY?si=6z5C5idfe2rYMIJd</a></p><p>GitHub Action Free Learning Resource: <a href="https://youtu.be/Tz7FsunBbfQ?si=CUVXZM88V9hhrrak">https://youtu.be/Tz7FsunBbfQ?si=CUVXZM88V9hhrrak</a></p><p>GitLab CI/CD Free Learning Resource: <a href="https://youtu.be/qP8kir2GUgo?si=KhdVJ7aoBKisP_Xh">https://youtu.be/qP8kir2GUgo?si=KhdVJ7aoBKisP_Xh</a></p><h3>📌 Step 11: Learn Monitoring &amp; Logging (Prometheus, Grafana, CloudWatch)</h3><p>Monitoring ensures applications run smoothly after deployment.</p><p>🔹 What to Learn:<br> ✔ <strong>Prometheus</strong> — Collects monitoring data<br> ✔ <strong>Grafana</strong> — Visualizes monitoring data<br> ✔ <strong>CloudWatch</strong> — AWS monitoring tool</p><p>🛠 <strong>Hands-on Practice</strong> — Set up Grafana to monitor a Kubernetes cluster.</p><p>CloudWatch Free Learning Resource: <a href="https://youtu.be/AF7NogcOTvk?si=bmwyk3mkJWImqK4J">https://youtu.be/AF7NogcOTvk?si=bmwyk3mkJWImqK4J</a></p><p>Prometheus &amp; Graphan Free Learning Resource: <a href="https://www.youtube.com/watch?v=cYAE0ZhT43c&amp;list=PLdpzxOOAlwvJUIfwmmVDoPYqXXUNbdBmb">https://www.youtube.com/watch?v=cYAE0ZhT43c&amp;list=PLdpzxOOAlwvJUIfwmmVDoPYqXXUNbdBmb</a></p><h3>Bonus: Advanced DevOps Topics</h3><p>Once you master the basics, explore these advanced DevOps topics:</p><p>✔ <strong>GitOps</strong> — Automate deployments using Git (Tools: Argo CD)<br> ✔ <strong>Service Mesh</strong> — Secure and manage microservices (Tool: Istio)</p><h3>Conclusion: Your Next Steps</h3><p>🚀 <strong>If You Want to GEt Job in Cloud &amp; DevOps then You have to Learn in a Structure Way and Focus in Hands-on Prace and DevOps Related Project Hands-On.</strong></p><p><strong>I have created a Personal Training Course “Cloud &amp; DevOps Mastery with AI”. In this Course I will Understand Your Educational and Professional Background and Customize a Learning Path and Provide You Customize Training to GEt a High Paying DevOps Job.</strong></p><p><strong>Book Free Demo Class: </strong><a href="https://forms.gle/cZHLcZM9KLokQmts7"><strong>https://forms.gle/cZHLcZM9KLokQmts7</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a451d054f815" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step-by-Step Guide to Creating a Production-Grade AWS EKS Cluster Using Terraform]]></title>
            <link>https://medium.com/@techmahato/step-by-step-guide-to-creating-a-production-grade-aws-eks-cluster-using-terraform-f8639156affb?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8639156affb</guid>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Fri, 21 Mar 2025 02:31:37 GMT</pubDate>
            <atom:updated>2026-06-15T18:31:10.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2hG5WPwT_Yd-ye0t" /></figure><h3>Step 001: Introduction</h3><p>In this blog post, we will walk you through the process of creating an AWS EKS (Elastic Kubernetes Service) cluster using Terraform. Think of EKS as a managed service that makes it much easier to run containerized applications using Kubernetes on AWS, without needing to manage the complex underlying infrastructure. With Terraform, you write simple code to describe your infrastructure, which makes it easier to deploy and manage consistently across different environments.</p><p>We are going to cover everything from setting up a secure bastion host (a dedicated server for managing your cluster) to configuring node groups, creating a container image repository with ECR, securing your connections with ACM certificates, and much more. The goal is to build a production-ready environment where even beginners can follow along, understand every step, and successfully deploy a robust Kubernetes cluster on AWS.</p><p>This guide breaks down the process into simple, manageable steps. Whether you’re new to Terraform or AWS EKS, you’ll find clear explanations, detailed instructions, and practical tips that ensure you won’t miss any important details. Let’s get started on building your cloud-native infrastructure!</p><h3>Step 002: What is AWS EKS and Why Should We Provision Our Microservice Container Infrastructure on AWS EKS?</h3><p><strong>AWS EKS (Elastic Kubernetes Service)</strong> is a managed Kubernetes service provided by Amazon Web Services (AWS). In simple terms, Kubernetes is a system for automating the deployment, scaling, and management of containerized applications, and AWS EKS takes care of running this complex system for you. Here’s why it’s a great choice for your microservice container infrastructure:</p><h3>What is AWS EKS?</h3><ul><li><strong>Managed Service:</strong> AWS EKS handles much of the heavy lifting of managing Kubernetes, such as upgrading the Kubernetes control plane, patching security vulnerabilities, and maintaining high availability.</li><li><strong>Scalability:</strong> EKS makes it easy to scale your applications up or down based on demand. This means your application can handle more traffic without needing manual intervention.</li><li><strong>Integration with AWS Ecosystem:</strong> EKS is built to work seamlessly with other AWS services like Elastic Container Registry (ECR), IAM for security, and CloudWatch for monitoring. This tight integration simplifies building a complete, secure, and robust cloud environment.</li><li><strong>Security:</strong> AWS takes care of securing the Kubernetes control plane. You also have the flexibility to enforce fine-grained access controls, ensuring that only authorized users and services interact with your infrastructure.</li></ul><h3>Why Provision Microservice Infrastructure on AWS EKS?</h3><ul><li><strong>Ease of Management:</strong> Managing Kubernetes on your own can be complex and time-consuming. With AWS EKS, much of the complexity is managed for you, allowing you to focus on developing and deploying your microservices.</li><li><strong>Reliability and High Availability:</strong> AWS EKS runs Kubernetes across multiple availability zones, ensuring that your applications remain available even if one zone experiences issues.</li><li><strong>Cost Efficiency:</strong> EKS allows you to optimize costs by using different types of instances (including cost-effective spot instances) and scaling your services dynamically based on usage.</li><li><strong>Enhanced Security:</strong> With built-in integrations for IAM, VPC, and AWS security services, EKS provides a secure environment for your microservices. This helps protect your data and applications from unauthorized access.</li><li><strong>Improved Developer Productivity:</strong> By leveraging a managed service, your team can spend more time writing code and less time managing infrastructure. This improves overall productivity and accelerates the development cycle.</li></ul><h3>Step 003: What is Terraform and What is a Terraform Module?</h3><h3>What is Terraform?</h3><ul><li><strong>Infrastructure as Code (IaC):</strong> Terraform is a tool that allows you to define your infrastructure (servers, databases, networks, etc.) using code. This means you can version control, share, and reuse your infrastructure configuration, similar to how you manage application code.</li><li><strong>Automation:</strong> With Terraform, you can automate the creation, modification, and management of your cloud resources. This reduces the risk of human error and saves time compared to manually configuring services via a web console.</li><li><strong>Provider Agnostic:</strong> Terraform works with various cloud providers like AWS, Azure, Google Cloud, and even on-premises environments. This makes it a versatile tool for managing infrastructure across different platforms.</li></ul><h3>What is a Terraform Module?</h3><ul><li><strong>Definition:</strong> A Terraform module is essentially a container for multiple resources that are used together. It bundles related configuration files and abstracts complexity, allowing you to reuse and share common setups.</li><li><strong>Reusability:</strong> Modules help you avoid repetition by letting you define common configurations once and then reuse them in different parts of your project or across different projects.</li><li><strong>Simplification:</strong> By encapsulating resources into modules, you can simplify complex setups. Instead of dealing with many interrelated configuration files, you use modules to package them into logical units, making the infrastructure easier to manage.</li><li><strong>Customization:</strong> Modules are designed to be flexible. You can pass in variables to customize behavior without modifying the module’s internal code, ensuring consistency while allowing for environment-specific configurations.</li></ul><h3>Step 004: What are the Standard Terraform File Structure for AWS EKS Cluster?</h3><p>When organizing your Terraform project, it’s important to structure your files for clarity and modularity. Below is a simple, structured overview of the standard file layout for an AWS EKS cluster setup:</p><p># tree<br>└── terraform-eks-cluster-setup-best-practice<br> ├── EKS.png<br> ├── README.md<br> ├── acm.tf<br> ├── data.tf<br> ├── ecr.tf<br> ├── eks.tf<br> ├── locals.tf<br> ├── output.tf<br> ├── provider.tf<br> ├── terraform.tfvars<br> └── variables.tf</p><h3>Step 005: Prerequisites</h3><p>Before starting, make sure you have all the necessary tools installed and configured. Here’s a detailed breakdown of what you need and why:</p><ol><li><strong>Bastion Host</strong></li></ol><ul><li><strong>Purpose:</strong> Acts as a secure gateway to manage your EKS cluster.</li><li><strong>Recommendation:</strong> Use an Ubuntu server (e.g., Ubuntu 22.04 LTS) to serve as your bastion host.</li></ul><ol><li><strong>Terraform</strong></li></ol><ul><li><strong>Purpose:</strong> Terraform is used to write, plan, and create your infrastructure using code.</li><li><strong>Installation:</strong> Follow the official Terraform installation guide to get started.</li></ul><ol><li><strong>AWS CLI</strong></li></ol><ul><li><strong>Purpose:</strong> The AWS Command Line Interface (CLI) allows you to interact with AWS services directly from your terminal.</li><li><strong>Installation and Configuration:</strong> Install the AWS CLI and configure it with your credentials by following the<a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html"> AWS CLI installation guide</a>.</li></ul><ol><li><strong>IAM Access Key &amp; Secret Key</strong></li></ol><ul><li><strong>Purpose:</strong> These credentials are necessary for Terraform and AWS CLI to interact with your AWS account.</li><li><strong>Requirement:</strong> Ensure the keys have admin permissions to allow full control over the resources being created.</li></ul><ol><li><strong>kubectl</strong></li></ol><ul><li><strong>Purpose:</strong> kubectl is the command-line tool for managing Kubernetes clusters, including your EKS cluster.</li><li><strong>Installation:</strong> Follow the kubectl installation guide to set up this tool.</li></ul><ol><li><strong>eksctl</strong></li></ol><ul><li><strong>Purpose:</strong> eksctl is a CLI tool specifically designed to simplify the creation and management of EKS clusters.</li><li><strong>Installation:</strong> Although optional, it’s recommended to install eksctl to streamline EKS cluster management.</li></ul><h3>Step 006: Create a Bastion Server to Manage Your EKS Cluster</h3><p>A bastion server is a secure gateway that provides controlled access to your private resources, such as your EKS cluster. In this step, you’ll set up a bastion server using Ubuntu 22.04 LTS. Follow the detailed instructions below:</p><ol><li>Create Key pair: bastion-host-kp</li><li>Create Security Group in Default VPC and Allow ssh, http, https</li><li>Launch Instance</li><li>Instance Name: Bastion-Host-Server</li><li>AMI: Ubuntu 22.04 LTS</li><li>VPC: Default</li><li>Volum: 20 GP, GP3</li><li>Access Server Using SSH command</li><li>$ ssh -i path/to/your-key.pem ubuntu@&lt;bastion-server-public-ip&gt;</li></ol><h3>Step 007: Install and Configure AWS CLI on Bastion-Host-Server</h3><ol><li>Create IAM User</li><li>Create Access Key and Secret Key for IAM User</li><li>Install AWS CLI version 2: You can use below script to install</li></ol><p><a href="https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/install_awscli2_ubuntu.sh">https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/install_awscli2_ubuntu.sh</a></p><ol><li>Configure Access &amp; and Secret Key</li><li>Validate</li></ol><h3>Step 008: Install Terraform, eksctl, kubectl, and Helm</h3><ol><li><strong>Terraform:<br></strong> Install Terraform to define and manage your infrastructure as code. Follow the official guide for installation.</li></ol><p>Script: <a href="https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/install_terraform_ubuntu.sh">https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/install_terraform_ubuntu.sh</a></p><ol><li><strong>eksctl:<br></strong> Install eksctl, a CLI tool to simplify creating and managing EKS clusters.</li><li><strong>kubectl:<br></strong> Install kubectl, the command-line tool for interacting with your Kubernetes (EKS) cluster.</li><li><strong>Helm:<br></strong> Install Helm to manage Kubernetes applications using Helm charts.</li></ol><p>Script for eksctl, kubectl, helm: <a href="https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/eksctl-kubectl-helm.sh">https://github.com/techmahato-com/Automation-Script/blob/1b38ec23acfe60e8ae27262805e4539d9a4adf82/eksctl-kubectl-helm.sh</a></p><h3>Step 009: Clone the Repository on Your Bastion Host or Local Machine</h3><ol><li><strong>Clone the Repository:<br></strong> Run the following command to clone the repository that contains the Terraform configuration for your EKS cluster:</li></ol><p>git clone <a href="https://github.com/techmahato-com/terraform-eks-cluster-setup-best-practice.git">https://github.com/techmahato-com/terraform-eks-cluster-setup-best-practice.git</a></p><ol><li><strong>Navigate to the Repository Directory:<br></strong> Change to the repository folder using:</li></ol><p>cd terraform-eks-cluster-setup-best-practice</p><ol><li><strong>Verify the Files:<br></strong> List the directory contents to ensure all files have been cloned correctly:</li></ol><p>ls</p><p>This repository contains all the necessary Terraform files and documentation for setting up your production-ready AWS EKS cluster.</p><p># tree<br>└── terraform-eks-cluster-setup-best-practice<br> ├── EKS.png<br> ├── README.md<br> ├── acm.tf<br> ├── data.tf<br> ├── ecr.tf<br> ├── eks.tf<br> ├── locals.tf<br> ├── output.tf<br> ├── provider.tf<br> ├── terraform.tfvars<br> └── variables.tf</p><h3>Step 010: Understanding Each Terraform File and Where to Modify as Needed</h3><p>When setting up an AWS EKS cluster using Terraform, different Terraform files are used to manage various configurations. Below is a detailed explanation of each file and where you may need to make changes based on your requirements.</p><h4>.1 provider.tf</h4><ul><li>This file specifies the Terraform provider, which in this case is <strong>AWS</strong>.</li><li>It defines the AWS region and authentication method (access keys or IAM role).</li><li><strong>Changes Needed:</strong> Update the AWS region if you want to deploy the cluster in a different location.</li></ul><h4>.2 variables.tf</h4><ul><li>This file defines <strong>input variables</strong> to make configurations reusable and modular.</li><li>Variables include values like the AWS region, VPC ID, instance type, and EKS cluster name.</li><li><strong>Changes Needed:</strong> Modify variables according to your infrastructure needs, such as instance sizes or networking settings.</li></ul><h4>.3 terraform.tfvars</h4><ul><li>This file assigns actual values to the variables defined in variables.tf.</li><li>It helps in keeping configurations <strong>separate from the main code</strong>, making it easy to customize.</li><li><strong>Changes Needed:</strong> Update this file with specific values that match your AWS setup, such as cluster name, region, and node instance types.</li></ul><h4>.4 locals.tf</h4><ul><li>This file contains <strong>local variables</strong> that simplify complex expressions and avoid repetitive values.</li><li>It helps in making the Terraform code <strong>cleaner and easier to manage</strong>.</li><li><strong>Changes Needed:</strong> If you want to define reusable constants or computed values, modify this file accordingly.</li></ul><h4>.5 data.tf</h4><ul><li>This file <strong>fetches existing AWS resources</strong> using Terraform data sources.</li><li>Examples include retrieving an existing <strong>VPC, subnets, or IAM roles</strong> instead of creating new ones.</li><li><strong>Changes Needed:</strong> If you want to use a specific VPC, subnet, or IAM role, update this file to fetch those resources.</li></ul><h4>.6 acm.tf (Optional)</h4><ul><li>This file provisions <strong>AWS Certificate Manager (ACM)</strong> certificates for enabling <strong>HTTPS</strong> on your services.</li><li>If you are deploying applications that require <strong>SSL/TLS encryption</strong>, ACM helps secure the domain.</li><li><strong>Changes Needed:</strong> If your project requires HTTPS, update this file with your domain details. Otherwise, you can ignore or remove it.</li></ul><h4>.7 ecr.tf</h4><ul><li>This file creates <strong>AWS Elastic Container Registry (ECR)</strong>, which is used to <strong>store Docker container images</strong>.</li><li>ECR is useful if you are deploying microservices that require <strong>private container storage</strong>.</li><li><strong>Changes Needed:</strong> Modify this file if you need a different ECR repository name or want to enable image scanning.</li></ul><h4>.8 eks.tf</h4><ul><li>This is the <strong>most important file</strong> as it defines and deploys the <strong>Amazon EKS cluster</strong>.</li><li>It includes configurations for the <strong>control plane, worker nodes, networking, and IAM roles</strong>.</li><li><strong>Changes Needed:</strong> If you need to customize <strong>node sizes, scaling settings, or networking configurations</strong>, update this file.</li></ul><h4>.9 output.tf</h4><ul><li>This file defines <strong>Terraform output values</strong>, making it easy to retrieve key information about the EKS cluster after deployment.</li><li>Examples include the <strong>EKS cluster name, endpoint URL, and authentication token</strong>.</li><li><strong>Changes Needed:</strong> If you need additional outputs (e.g., VPC ID or security group ID), update this file.</li></ul><h4>.10 .terraform.lock.hcl (Auto-Generated)</h4><ul><li>This is an <strong>auto-generated lock file</strong> that ensures <strong>consistent provider versions</strong> across different environments.</li><li>It prevents unexpected updates by locking Terraform provider versions.</li><li><strong>Changes Needed:</strong> You don’t need to modify this file. It is automatically created when you initialize Terraform.</li></ul><h4>Final Notes</h4><ul><li><strong>Where to Change?</strong></li><li>Update terraform.tfvars and variables.tf for custom configurations.</li><li>Modify eks.tf, ecr.tf, and acm.tf if you want to adjust cluster settings, container registry, or security.</li><li><strong>Best Practice:</strong> Keep <strong>variable values separate</strong> in terraform.tfvars to maintain flexibility.</li></ul><h3>Step 011: Configuring Terraform Backend with S3 for State Storage</h3><p>Terraform keeps track of infrastructure using a <strong>state file (terraform.tfstate)</strong>. Storing this file <strong>remotely in AWS S3</strong> ensures better security, collaboration, and recovery.</p><p>Follow these steps to set up <strong>S3 as the Terraform backend</strong> with <strong>state locking</strong> using <strong>DynamoDB</strong>.</p><h4>Step 1: Create an S3 Bucket for Terraform State Storage</h4><p>Terraform stores the state file in an <strong>S3 bucket</strong>.</p><p>🔹 Run this command to create an S3 bucket:</p><p>aws s3api create-bucket — bucket tm-devsecops-backend-codedevops — region ap-south-1 — create-bucket-configuration LocationConstraint=ap-south-1</p><p><strong>Explanation:</strong></p><ul><li>Replace <strong>tm-devsecops-backend-codedevops</strong> with your unique bucket name</li><li>Change <strong>ap-south-1</strong> to your preferred AWS region</li></ul><h4>Step 2: Enable Versioning on the S3 Bucket</h4><p>Versioning <strong>protects the state file</strong> by allowing rollbacks.</p><p>🔹 Enable versioning using this command:</p><p>aws s3api put-bucket-versioning — bucket tm-devsecops-backend-codedevops — versioning-configuration Status=Enabled</p><p><strong>Why?</strong></p><ul><li>Helps recover old state versions if changes cause issues</li></ul><h4>Step 3: Create a DynamoDB Table for State Locking</h4><p>State locking prevents <strong>conflicts</strong> when multiple users apply Terraform changes.</p><p>🔹 Run this command to create a <strong>DynamoDB table</strong>:</p><p>aws dynamodb create-table \<br> — table-name terraform-state-lock \<br> — attribute-definitions AttributeName=LockID,AttributeType=S \<br> — key-schema AttributeName=LockID,KeyType=HASH \<br> — billing-mode PAY_PER_REQUEST \<br> — region ap-south-1</p><p><strong>Why?</strong></p><ul><li>Avoids corruption of Terraform state when multiple users modify infrastructure</li></ul><h4>Step 4: Configure Terraform to Use S3 Backend</h4><p>Now, add the <strong>backend configuration</strong> in provider.tf:</p><p>terraform {<br> backend “s3” {<br> bucket = “tm-devsecops-backend-codedevops” # 🔹 Replace with your S3 bucket name<br> key = “secops-dev.tfstate” # 🔹 State file path in S3<br> region = “ap-south-1” # 🔹 AWS region<br> dynamodb_table = “terraform-state-lock” # 🔹 Enables state locking<br> encrypt = true # 🔹 Encrypts the state file<br> }<br>}</p><p><strong>Why?</strong></p><ul><li>Stores the state file securely in <strong>S3</strong></li><li>Enables <strong>state locking</strong> with <strong>DynamoDB</strong></li><li>Ensures <strong>encryption</strong> for security</li></ul><h4>Step 5: Verify the State File in S3</h4><p>Check if the <strong>state file</strong> was successfully stored in S3:</p><p>aws s3 ls s3://tm-devsecops-backend-codedevops/</p><p><strong>Expected Output:<br></strong> You should see a file named <strong>secops-dev.tfstate</strong> inside the bucket.</p><h4>Why Store Terraform State in S3?</h4><p>✔ <strong>Centralized State Management</strong> — Avoids storing state files locally<br> ✔ <strong>Collaboration</strong> — Multiple team members can work together<br> ✔ <strong>Versioning</strong> — Rollback to previous state versions<br> ✔ <strong>State Locking</strong> — Prevents conflicts in multi-user environments<br> ✔ <strong>Security</strong> — Encrypts the Terraform state file</p><h3>Step 012: Applying Terraform Commands to Create an EKS Cluster</h3><p>After configuring Terraform and storing the state in <strong>AWS S3</strong>, the next step is to <strong>initialize</strong>, <strong>validate</strong>, and <strong>apply</strong> Terraform to create an <strong>Amazon EKS (Elastic Kubernetes Service) cluster</strong>.</p><h4>Step 1: Initialize Terraform (terraform init)</h4><p><strong>Why is Initialization Required?</strong></p><ul><li>Terraform <strong>downloads necessary providers</strong> (like AWS)</li><li>It <strong>configures the backend</strong> (S3 &amp; DynamoDB)</li><li>Ensures Terraform <strong>can manage infrastructure</strong></li></ul><p><strong>🔹 Run the following command:</strong></p><p>terraform init</p><p><strong>Expected Output:</strong></p><ul><li>Terraform will download necessary plugins</li><li>It will confirm backend configuration</li><li>No errors should appear</li></ul><p><strong>If successful, you will see a message:</strong></p><p>Terraform has been successfully initialized!</p><h4>Step 2: Validate the Terraform Configuration (terraform validate)</h4><p><strong>Why Validate?</strong></p><ul><li>Ensures <strong>Terraform scripts</strong> (.tf files) have <strong>no syntax errors</strong></li><li>Checks <strong>proper configurations</strong> before applying changes</li><li>Saves time by avoiding errors at the apply stage</li></ul><p><strong>🔹 Run the following command:</strong></p><p>terraform validate</p><p><strong>Expected Output:</strong></p><p>If there are no issues, you’ll see:</p><p>Success! The configuration is valid.</p><p><strong>If errors exist:</strong></p><ul><li>Terraform will highlight them</li><li>Fix the issues and rerun terraform validate</li></ul><h4>🛠 Step 3: Apply Terraform Configuration (terraform apply)</h4><p><strong>Why Apply?</strong></p><ul><li><strong>Creates the AWS infrastructure</strong> as defined in Terraform files</li><li>Provisions <strong>EKS Cluster, VPC, IAM roles, and other AWS resources</strong></li><li>Saves the infrastructure state in <strong>S3</strong></li></ul><p><strong>🔹 Run the following command:</strong></p><p>terraform apply -auto-approve</p><p><strong>Explanation:</strong></p><ul><li><strong>terraform apply</strong> → Starts the deployment</li><li><strong>-auto-approve</strong> → Skips confirmation prompt</li></ul><p><strong>If successful, you will see:</strong></p><p>Apply complete! Resources: X added, 0 changed, 0 destroyed.</p><p><strong>It may take 10–15 minutes for EKS cluster creation.</strong></p><h4>Step 4: Verify the EKS Cluster</h4><p><strong>Why Verify?</strong></p><ul><li>Ensures the EKS Cluster is successfully created</li><li>Confirms that resources exist in AWS</li></ul><p><strong>🔹 Run the following command to check the EKS Cluster:</strong></p><p>aws eks list-clusters — region ap-south-1</p><p><strong>Expected Output:</strong></p><p>{<br> “clusters”: [<br> “my-eks-cluster”<br> ]<br>}</p><p><strong>If the cluster name appears, deployment was successful!</strong></p><h4>What Happens After Terraform Apply?</h4><p>✔ <strong>An EKS cluster is created</strong> in AWS<br> ✔ Terraform <strong>stores the state file in S3<br></strong> ✔ You can now <strong>deploy workloads</strong> on Kubernetes</p><p><strong>Congratulations!</strong> You have successfully initialized, validated, and applied Terraform to create your EKS Cluster. Let me know if you need any clarifications! 🔥</p><h3>Step 014: Allow EKS Cluster Security Group Access from the Bastion Server</h3><p>After deploying the EKS cluster, your Bastion Server needs proper network access to communicate with the EKS cluster. This is done by allowing inbound traffic from the Bastion Server to the EKS Cluster’s Security Group.</p><ol><li>Go to Cluster &gt;&gt; Networking &gt;&gt; Additional Security Group &gt;&gt; HTTPS allow to Bastion-Host-Server SG.</li></ol><h3>Step 015: Update AWS EKS Config File on Bastion Host</h3><h4>1. Verify AWS CLI &amp; kubectl Installation</h4><p>Check if AWS CLI and kubectl are installed:</p><p>aws — version<br>kubectl version — client</p><h4>2. Update kubeconfig to Access EKS</h4><p>Run the following command to configure kubectl for your EKS cluster:</p><p>aws eks update-kubeconfig — region &lt;aws-region&gt; — name &lt;eks-cluster-name&gt;</p><p><strong>Example:</strong></p><p>aws eks update-kubeconfig — region ap-south-1 — name my-eks-cluster</p><h4>3. Verify Cluster Connection</h4><p>Check if your EKS cluster is accessible:</p><p>kubectl get nodes</p><p><strong>Expected Output:</strong></p><p>NAME STATUS ROLES AGE VERSION<br>ip-192–168–10–21.ec2.internal Ready &lt;none&gt; 10m v1.29.0</p><p>If nodes are in <strong>Ready</strong> state, the setup is correct.</p><h4>4. Check Kubernetes Context</h4><p>Verify that you are using the correct cluster:</p><p>kubectl config current-context</p><p>List all available contexts:</p><p>kubectl config get-contexts</p><h3>Step 016: Validate EKS Cluster from AWS Console</h3><ol><li><strong>Login to AWS Console</strong> → Navigate to <strong>EKS Dashboard</strong>.</li><li><strong>Check Cluster Status</strong> → Ensure the cluster is <strong>Active</strong>.</li><li><strong>Verify Worker Nodes</strong> → Go to <strong>Compute &gt; Node Groups</strong>, check if nodes are <strong>Active</strong>.</li><li><strong>Review Networking &amp; Security</strong> → Confirm VPC, subnets, and security groups are correct.</li><li><strong>Validate IAM Roles</strong> → Check IAM role permissions for the cluster</li><li><strong>(Optional) Verify Load Balancer</strong> → If deployed, check <strong>EC2 &gt; Load Balancers</strong>.</li></ol><h3>🎉 Congratulations! 🎉</h3><p>You have successfully set up your <strong>AWS EKS Cluster</strong> using Terraform! 🚀</p><p>This is a major milestone in your DevOps journey. Now, you can deploy and manage containerized applications efficiently on Kubernetes.</p><p>Keep exploring, fine-tuning, and scaling your infrastructure. The cloud is yours to conquer!</p><h4>Happy Learning! 🎯Show You Love by Clap 👏 Comment &amp; Follow</h4><h3>Step 017: Delete EKS Cluster and Resources</h3><p>After completing your practice, it’s important to delete the AWS EKS cluster and its associated resources to <strong>avoid unnecessary costs</strong> and keep your AWS environment clean. Unused resources can lead to unexpected charges, so it’s best to remove them when they are no longer needed.</p><p>Steps to Delete EKS Cluster and Resources:</p><p>1. <strong>Navigate to the Terraform Directory:<br></strong> Move to the folder where your Terraform configuration files are stored.</p><p>cd terraform-eks-cluster-setup-best-practice</p><p><strong>2. Destroy the Infrastructure Using Terraform:<br></strong> Run the following command to delete all resources managed by Terraform:</p><p>terraform destroy -auto-approve</p><ul><li>This will remove the <strong>EKS cluster, worker nodes, IAM roles, VPC, security groups, and other AWS resources.</strong></li></ul><p><strong>3. Verify Deletion in AWS Console:</strong></p><ul><li>Go to the <strong>AWS Console</strong> and check:<br> ✅ <strong>EKS Dashboard</strong> — Ensure the cluster is removed.<br> ✅ <strong>VPC</strong> — Confirm associated networking components are deleted.<br> ✅ <strong>IAM</strong> — Verify roles and policies created for EKS are gone.<br> ✅ <strong>ECR</strong> — Delete any container images if not managed by Terraform.</li></ul><p><strong>4. (Optional) Delete Terraform State from S3 (If Using Remote Backend):<br></strong> If you stored the Terraform state file in an <strong>S3 bucket</strong>, remove it manually:</p><p>aws s3 rm s3://tm-devsecops-backend-codedevops/secops-dev.tfstate</p><p><strong>5. (Optional) Clean Up Local Terraform Files:<br></strong> Remove local state files and cached Terraform data:</p><p>rm -rf .terraform terraform.tfstate terraform.tfstate.backup</p><h4>Cluster and Resources Successfully Deleted!</h4><p>You have now <strong>freed up AWS resources and prevented unnecessary billing.</strong></p><p>Please comment you question and clap this article to I can get motivation to upload more this kind of article and content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8639156affb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[90-Day Roadmap to Get Job as Cloud & DevOps Engineer in 2025]]></title>
            <link>https://medium.com/@techmahato/90-day-roadmap-to-get-job-as-cloud-devops-engineer-in-2025-4f7c4f0d76e4?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f7c4f0d76e4</guid>
            <category><![CDATA[devops-tutorial]]></category>
            <category><![CDATA[devops2025]]></category>
            <category><![CDATA[devops-roadmap]]></category>
            <category><![CDATA[devops-courses]]></category>
            <category><![CDATA[tech-mahato]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Sun, 16 Mar 2025 06:58:22 GMT</pubDate>
            <atom:updated>2025-03-16T07:00:37.314Z</atom:updated>
            <content:encoded><![CDATA[<p>Looking to land a high-paying IT job or switch careers? You’re in the right place! With over a decade of experience in the IT industry, I’ve helped thousands of professionals upgrade their skills and secure top-paying roles. In this blog, I’ll share proven strategies and techniques to fast-track your success. Read till the end to boost your career!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNGOoguT0Aqp9rXjLIhEpg.png" /></figure><h3>About Tech Mahato</h3><p>Hi, I’m Arbind Mahato, the founder of Tech Mahato. I started my IT career in 2011 after completing my college education, and today, I work as a Cloud &amp; DevOps Engineer. My passion lies in sharing my knowledge and real-world experience with you.</p><p>I create hands-on tutorials and educational content on AWS Cloud and DevOps in <strong>Hindi</strong>, making complex topics easy to understand. If you’re looking to <strong>master AWS and DevOps tools</strong> with practical learning, subscribe to my <strong>YouTube channel</strong> and join my <strong>newsletter</strong> to stay updated with the latest content! 🚀</p><h3>About the 90-Day Cloud &amp; DevOps Roadmap 2025</h3><p>In 2025, the internet is flooded with learning resources, making it overwhelming to find the right path. Without a <strong>clear, structured, and proven roadmap</strong>, beginners often waste time learning outdated or unnecessary tools.</p><p>To help you <strong>save time, gain the right skills, and secure a high-paying job</strong>, I’ve created this <strong>step-by-step Cloud &amp; DevOps roadmap</strong> based on current industry demands. This guide focuses only on <strong>essential and in-demand tools</strong>, ensuring you build job-ready expertise.</p><p>I highly recommend reading the <strong>entire roadmap</strong> and implementing each step <strong>without skipping any tools</strong>. Let’s get started on your Cloud &amp; DevOps journey! 🚀</p><h3>WWWH Secret Formula for Becoming a High-Paying DevOps Engineer in 2025</h3><p>Before diving into any skill, you need a <strong>proven formula</strong> to learn efficiently and achieve the best results in the shortest time. This isn’t a <strong>shortcut</strong>, but a <strong>sure-cut method</strong> to mastering DevOps faster and maximizing your career growth.</p><h4>The WWWH Framework for Success</h4><p>✅ <strong>W — What:</strong> Define your goal clearly. My goal is to secure a <strong>high-paying DevOps job in 2025</strong>.</p><p>✅ <strong>W — Why:</strong> In 2025, <strong>DevOps skills are in high demand</strong>, with plenty of job openings but a shortage of skilled professionals. This makes it an excellent opportunity to enter the <strong>IT industry</strong> and command a <strong>higher salary</strong>.</p><p>✅ <strong>W — When:</strong> With the <strong>right resources and a structured roadmap</strong>, it takes around <strong>90 days</strong> to learn Cloud &amp; DevOps skills and become job-ready.</p><p>✅ <strong>H — How:</strong> To land a <strong>Cloud &amp; DevOps job</strong>, you must focus on <strong>industry-relevant skills</strong> and hands-on learning. That’s why I’ve broken down the required tools into a <strong>90-day learning plan</strong>, combining <strong>structured mentorship and real-world projects</strong> for maximum impact.</p><p>In the next sections, I’ll walk you through the <strong>step-by-step roadmap</strong> to help you master DevOps and achieve your career goals in 2025. Let’s get started! 🚀</p><h3>Phase 1: Master the Foundations (Day 1–30)</h3><h4>Week 1: Linux Fundamentals</h4><p>✅ <strong>Why?</strong> Most cloud and DevOps systems run on Linux. ✅ <strong>What to Learn?</strong></p><ul><li>Basic commands: ls, cd, grep, chmod</li><li>User management: adduser, passwd</li><li>File permissions &amp; process management ✅ <strong>Resources:</strong></li><li><a href="https://linuxjourney.com/">Linux Journey</a></li><li>YouTube: <strong>“Linux for Beginners”</strong></li></ul><h4>Week 2: Networking Basics</h4><p>✅ <strong>Why?</strong> Strong networking knowledge is essential for cloud and DevOps roles. ✅ <strong>What to Learn?</strong></p><ul><li>IP addressing, DNS, DHCP</li><li>Load balancers, NAT, Firewalls</li><li>Tools: netstat, curl, ping ✅ <strong>Resources:</strong></li><li>YouTube: <strong>“Networking Basics Full Course” by NetworkChuck</strong></li></ul><h4>Week 3: Version Control with Git</h4><p>✅ <strong>Why?</strong> Git is essential for collaboration in DevOps. ✅ <strong>What to Learn?</strong></p><ul><li>Basic Git commands: git clone, git commit, git push</li><li>Branching, merging, resolving conflicts ✅ <strong>Resources:</strong></li><li><a href="https://www.freecodecamp.org/">FreeCodeCamp’s Git Tutorial</a></li><li>Hands-on practice on <strong>GitHub</strong></li></ul><h4>Week 4: Cloud Basics (AWS)</h4><p>✅ <strong>Why?</strong> Cloud platforms are the backbone of modern IT infrastructure. ✅ <strong>What to Learn?</strong></p><ul><li>AWS Services: <strong>EC2, S3, IAM, VPC</strong></li><li>Launch &amp; manage virtual machines ✅ <strong>Resources:</strong></li><li>AWS Free Tier for hands-on practice</li><li>AWS Tutorials by <strong>TechMahato</strong></li></ul><h3>Phase 2: DevOps Essentials (Day 31–60)</h3><h4>Week 5: Docker (Containerization)</h4><p>✅ <strong>Why?</strong> Containers make applications portable and scalable. ✅ <strong>What to Learn?</strong></p><ul><li>Docker basics: Images, Containers, Dockerfile</li><li>Essential commands: docker run, docker build, docker-compose ✅ <strong>Resources:</strong></li><li>Docker’s Official Docs</li><li>YouTube: <strong>“Docker Tutorial for Beginners” by Amigoscode</strong></li></ul><h4>Week 6: Kubernetes (K8s) Basics</h4><p>✅ <strong>Why?</strong> Kubernetes is the industry standard for container orchestration. ✅ <strong>What to Learn?</strong></p><ul><li>Deploy a Pod</li><li>Key concepts: Services, ReplicaSets, ConfigMaps, Ingress ✅ <strong>Resources:</strong></li><li>Kubernetes Official Tutorials</li><li>YouTube: <strong>“Kubernetes Simplified” by TechWorld with Nana</strong></li></ul><h4>Week 7: CI/CD with Jenkins</h4><p>✅ <strong>Why?</strong> Automating software delivery is a key DevOps skill. ✅ <strong>What to Learn?</strong></p><ul><li>Install &amp; configure Jenkins</li><li>Build a simple CI/CD pipeline ✅ <strong>Resources:</strong></li><li>Jenkins Official Docs</li><li>Udemy: <strong>“Jenkins Basics”</strong></li></ul><h4>Week 8: Infrastructure as Code (IaC) with Terraform</h4><p>✅ <strong>Why?</strong> Automates cloud infrastructure creation. ✅ <strong>What to Learn?</strong></p><ul><li>Basics: Resources, Variables, Modules</li><li>Writing scripts to deploy AWS infrastructure ✅ <strong>Resources:</strong></li><li>HashiCorp Learn Terraform</li></ul><h3>Phase 3: Advanced Tools &amp; Real-World Projects (Day 61–90)</h3><h4>Week 9: Monitoring with Prometheus &amp; Grafana</h4><p>✅ <strong>Why?</strong> Monitoring ensures system reliability. ✅ <strong>What to Learn?</strong></p><ul><li>Install and configure Prometheus &amp; Grafana</li><li>Set up dashboards for CPU &amp; memory monitoring ✅ <strong>Resources:</strong></li><li>YouTube: <strong>“Prometheus &amp; Grafana Full Course”</strong></li></ul><h4>Week 10: Security &amp; Logging</h4><p>✅ <strong>Why?</strong> DevOps engineers must ensure system security. ✅ <strong>What to Learn?</strong></p><ul><li>AWS CloudTrail &amp; IAM Policies</li><li>ELK Stack (Elasticsearch, Logstash, Kibana) basics ✅ <strong>Resources:</strong></li><li>AWS Docs: IAM &amp; CloudTrail</li><li>Udemy: ELK Stack Tutorials</li></ul><h4>Week 11: Real-World Projects</h4><p>✅ <strong>Projects to Build:</strong></p><ul><li>Deploy a <strong>multi-tier web app</strong> on AWS using Kubernetes</li><li>Set up a <strong>CI/CD pipeline</strong> with Jenkins for automated deployments</li><li>Automate infrastructure deployment with <strong>Terraform</strong></li></ul><h4>Week 12: Certifications &amp; Job Interviews</h4><p>✅ <strong>Certifications to Target:</strong></p><ul><li>AWS Certified Solutions Architect — Associate</li><li>Certified Kubernetes Administrator (CKA) ✅ <strong>Interview Prep Topics:</strong></li><li>Kubernetes Architecture</li><li>CI/CD Pipeline Design</li><li>Docker vs. Kubernetes vs. Terraform</li></ul><h4>Pro Tips for Success</h4><p>✅ <strong>Hands-on Practice Daily</strong> — Theory alone won’t get you hired. ✅ <strong>Join Tech Communities</strong> — Engage in <strong>LinkedIn &amp; Facebook Groups</strong>. ✅ <strong>Use Free Learning Resources</strong> — YouTube, blogs, and free cloud credits. ✅ <strong>Focus on Projects</strong> — Employers value practical experience over certificates.</p><h4>Final Thoughts</h4><p>Cloud &amp; DevOps engineering is one of the <strong>hottest career paths</strong> in 2025. If you dedicate yourself to this <strong>90-day roadmap</strong>, you’ll be <strong>job-ready with hands-on expertise</strong>. Follow this structured learning plan, apply your skills in real-world projects, and prepare for job interviews.</p><p>Start today, and take charge of your future!</p><h3>Good News for You :)</h3><h4>🚀 Master Kubernetes &amp; DevOps with AI — Unlock 4 Income Streams!</h4><p>I’ve designed <strong>two powerful courses</strong> to help you break into <strong>high-paying Cloud &amp; DevOps roles!</strong></p><p>🎯 <strong>100-Day Cloud &amp; DevOps Mastery with AI</strong> — Perfect for <strong>freshers &amp; career switchers</strong></p><p>✅ <strong>100-Day Kubernetes Mastery with AI</strong> — Learn Kubernetes with <strong>10 real-world projects</strong></p><p>🔥 <strong>Get job-ready &amp; start earning!</strong> <strong>Book your FREE demo now:</strong><br>📌 Kubernetes Mastery 👉 <a href="https://forms.gle/tqxT7YwERaF8tPEc7">Enroll Now</a><br>📌 Cloud &amp; DevOps Mastery 👉 <a href="https://forms.gle/Cxxhn8hkXG3STRi69">Enroll Now</a></p><h4>Show you Love: If you find this blog is helpfull please 👏 and comment below.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f7c4f0d76e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Became an AWS Certified DevOps Professional in 2025: My Personal Roadmap, Study Tips &…]]></title>
            <link>https://medium.com/@techmahato/how-i-became-an-aws-certified-devops-professional-in-2025-my-personal-roadmap-study-tips-243e77a217af?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/243e77a217af</guid>
            <category><![CDATA[tech-mahato]]></category>
            <category><![CDATA[devops-roadmap]]></category>
            <category><![CDATA[devops-certification]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[dop-co2]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Sat, 15 Mar 2025 05:37:47 GMT</pubDate>
            <atom:updated>2025-03-15T05:37:47.111Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Became an AWS Certified DevOps Professional in 2025: My Personal Roadmap, Study Tips &amp; Journey</h3><p>After lots of effor and dedication with dicipline finaly I pass the AWS Certified DevOps Pro exame 2025. I am feeling proud to share with you my journey to become an AWS Certified DevOps Professional in 2025.Discover my step-by-step roadmap, proven study tips, and hands-on experiences that helped me master AWS cloud automation, continuous integration, and secure deployments. Let my story guide you on your path to DevOps success and a rewarding cloud career.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1YxXHVQWuVL-Cuthv49fg.png" /><figcaption>How I Became an AWS Certified DevOps Professional in 2025: My Personal Roadmap, Study Tips &amp; Journey</figcaption></figure><p>About Me: Hi I’m Arbind Kr. Mahato, working as Sr. Cloud engineer at IT company, and I am having one YouTube Channel “Tech Mahato” where I am sharing my knowledge and experience with you.</p><p>Let me share with you my Certitifaction Journey</p><p>2025: AWS Certified DevOps Professional</p><p>2024: Certified Kubernetes Application Devloper</p><p>2024: CertifiedKubernetes Administrator.</p><p>2023: AWS Certified Solution Architect Professional</p><p>2022: AWS Certified Solution Architect Associate</p><p>2014: RedHat Certified OpenStack Administrator</p><p>2013: RedHat Certified Engineer</p><p>2013: Redhat Certified System Administrator</p><h3>Introduction</h3><p>Passing the <strong>AWS Certified DevOps Engineer — Professional (DOP-C02)</strong> exam was a turning point in my cloud career. This isn’t just another credential — it’s a journey that deepened my understanding of cloud technologies and honed my skills in building secure, scalable, and automated systems.</p><p>In this blog, I’m excited to share my personal story and the step-by-step strategies that helped me pass the exam on my first try. Over the course of 30-day challenge, I immersed myself in an 90-hour advanced AWS DevOps skills, filled with video lessons, hands-on labs, and practice exams. That dedication paid off when I received my <strong>AWS Certified DevOps Engineer — Professional badge in 2025</strong>.</p><p>I’ll walk you through my study plan, the resources I found invaluable, and practical tips drawn from real-world experiences — even if you’re just starting out in AWS. Whether you’re preparing for the new DOP-C02 exam or looking to boost your cloud expertise, this guide is designed to help you succeed.</p><p>Join me on this journey, and let’s transform your approach to learning AWS together.</p><h3><strong>What is the AWS Certified DevOps Engineer — Professional Certification?</strong></h3><p>It is a credential that proves you can design, deploy, and manage scalable, secure, and automated applications on AWS.</p><p>This certification is aimed at experienced DevOps professionals and cloud engineers who have a deep understanding of modern DevOps practices and AWS services.</p><p><strong>Achieving this certification demonstrates that you can:</strong></p><ul><li><strong>Design and Build CI/CD Pipelines:</strong> Develop continuous integration and continuous delivery pipelines to streamline application deployment and updates.</li><li><strong>Automate Infrastructure Management:</strong> Utilize Infrastructure as Code (IaC) tools like <strong><em>AWS CloudFormation</em></strong> or Terraform to provision and manage cloud resources efficiently.</li><li><strong>Enhance Security and Compliance:</strong> Implement robust security measures, automate security controls, and ensure compliance with industry standards.</li><li><strong>Monitor and Optimize AWS Environments:</strong> Use AWS monitoring tools to track system performance, troubleshoot issues, and optimize resources for maximum efficiency.</li><li><strong>Ensure High Availability and Fault Tolerance:</strong> Design systems that are resilient and can recover quickly from failures, ensuring continuous operation in dynamic environments.</li><li><strong>Implement Advanced Automation and Orchestration:</strong> Leverage automation tools and orchestration platforms to streamline complex workflows and reduce manual intervention.</li><li><strong>Develop and Maintain Microservices Architectures:</strong> Design distributed, modular applications that allow for rapid development, scalability, and easier maintenance.</li><li><strong>Integrate and Manage Containerized Workloads:</strong> Deploy and manage containerized applications using Docker, Kubernetes, AWS ECS, and EKS to enhance portability and scalability.</li><li><strong>Optimize Cost and Resource Utilization:</strong> Apply best practices for cost management and efficient resource use on AWS, ensuring optimal performance with minimal waste.</li><li><strong>Troubleshoot Complex Environments:</strong> Quickly diagnose and resolve issues in multifaceted, distributed systems using deep technical expertise and analytical skills.</li><li><strong>Drive Continuous Improvement:</strong> Foster a culture of innovation and continuous improvement by refining processes and adopting cutting-edge solutions.</li><li><strong>Collaborate Across Teams:</strong> Effectively work with development and operations teams to create seamless, integrated workflows that boost productivity.</li><li><strong>Adopt Modern DevOps Practices:</strong> Stay current with the latest trends and tools in the DevOps world to ensure your skills remain relevant and cutting-edge.</li></ul><h3>Who Should Take This Exam?</h3><p>The AWS Certified DevOps Engineer — Professional exam is ideal for experienced professionals who want to validate their advanced skills in cloud automation and DevOps on the AWS platform. This exam is designed for:</p><ul><li><strong>DevOps Engineers:</strong> Those who build, deploy, and manage automated CI/CD pipelines and have hands-on experience with AWS services.</li><li><strong>Cloud Engineers and Solutions Architects:</strong> Professionals looking to design scalable, resilient, and secure applications on AWS.</li><li><strong>System Administrators:</strong> Individuals who manage AWS environments and want to demonstrate their expertise in continuous integration, infrastructure as code, and automated deployments.</li><li><strong>IT Professionals:</strong> Anyone with practical AWS experience, especially if you’ve earned associate-level certifications (like AWS Certified Developer or AWS Certified SysOps Administrator), and are ready to take your skills to a professional level.</li></ul><h3>Why This Certification Matters</h3><p>Earning the AWS Certified DevOps Engineer — Professional certification is a game-changer for your career. It demonstrates that you have advanced skills in building, deploying, and managing automated, scalable, and secure AWS solutions. Here’s why it matters:</p><ul><li><strong>Proves Advanced Expertise:</strong><br>It validates your ability to design and manage complex AWS systems, setting you apart as a true expert in cloud automation and DevOps.</li><li><strong>Boosts Career Opportunities:</strong><br>Employers highly value this credential, opening doors to higher-level roles and better compensation in the competitive cloud computing market.</li><li><strong>Enhances Professional Credibility:</strong><br>With this certification, you gain recognition from peers and industry leaders, establishing yourself as a trusted professional in the field.</li><li><strong>Stays Current with Industry Trends:</strong><br>The certification ensures you are up-to-date with the latest AWS services, best practices, and emerging technologies, which is crucial in today’s fast-evolving IT landscape.</li><li><strong>Empowers You to Drive Innovation:</strong><br>With proven expertise in CI/CD, Infrastructure as Code, and automated deployments, you’re better equipped to implement efficient, resilient solutions that drive business success.</li></ul><h3><strong>Prerequisites for the AWS Certified DevOps Engineer — Professional Certification</strong></h3><p>Before diving into this advanced certification, it’s important to have a strong foundation in AWS and DevOps practices. Here’s what you should have:</p><ul><li><strong>Hands-On AWS Experience:</strong><br>Ideally, at least two years of practical experience working with AWS services in a production environment.</li><li><strong>Familiarity with DevOps Concepts:</strong><br>A solid understanding of continuous integration (CI), continuous delivery (CD), and automation techniques.</li><li><strong>Experience with Infrastructure as Code (IaC):</strong><br>Knowledge of tools like AWS CloudFormation or Terraform to automate resource provisioning.</li><li><strong>Prior AWS Certifications (Recommended):</strong><br>It’s beneficial to have one or more associate-level certifications, such as AWS Certified Developer — Associate or AWS Certified SysOps Administrator — Associate, to ensure you have a strong base in AWS services.</li><li><strong>Technical Skills:</strong><br>Proficiency in at least one scripting language (Python, Bash, etc.) and a good grasp of Linux fundamentals, version control (like Git), and configuration management.</li></ul><h3>Career Opportunities After Earning the AWS Certified DevOps Engineer — Professional Certification</h3><p>Achieving this certification can open many doors in the cloud and DevOps fields. Here are some career paths and opportunities you can explore:</p><ul><li><strong>Cloud DevOps Engineer:</strong><br>Focus on building, deploying, and managing cloud infrastructure using automation, CI/CD pipelines, and AWS services.</li><li><strong>Senior DevOps Engineer/Architect:</strong><br>Take on leadership roles in designing and implementing scalable, secure, and resilient cloud solutions across complex environments.</li><li><strong>Cloud Infrastructure Engineer:</strong><br>Specialize in automating and maintaining robust cloud systems, ensuring high availability and performance.</li><li><strong>DevOps Consultant:</strong><br>Work with various organizations to optimize their cloud strategies, improve deployment processes, and streamline operations through automation.</li><li><strong>Cloud Solutions Architect:</strong><br>Design end-to-end cloud architectures that integrate DevOps best practices, infrastructure as code, and continuous monitoring.</li><li><strong>IT Manager/Team Lead:</strong><br>Oversee cloud operations and DevOps teams, driving innovation and ensuring efficient system management.</li></ul><h3><strong>How Much Time Does It Take to Prepare for This Certification?</strong></h3><p>The time needed to prepare for the AWS Certified DevOps Engineer — Professional exam varies based on your background and experience. Here’s a general guideline:</p><ul><li><strong>For Experienced AWS and DevOps Professionals:</strong><br>If you already work with AWS and have hands-on experience in DevOps practices, you might be ready in about <strong>2 to 3 months</strong> of focused study (roughly 10–15 hours per week).</li><li><strong>For Those New to AWS or DevOps:</strong><br>If you’re just starting out or transitioning from a non-cloud background, you may need <strong>4 to 6 months</strong> to build a solid foundation before taking on the advanced topics.</li></ul><h3><strong>Exam Overview (Detailed)</strong></h3><p>The AWS Certified DevOps Engineer — Professional exam is a professional-level test designed to validate your ability to design, deploy, and manage complex AWS environments using advanced DevOps practices. Here’s a detailed breakdown of what to expect:</p><ul><li><strong>Number of Questions:</strong><br>The exam consists of <strong>75 questions</strong> that cover a wide range of topics. These questions are designed to assess your in-depth knowledge of AWS services and your ability to apply DevOps principles in real-world scenarios.</li><li><strong>Time Limit:</strong><br>You will have <strong>180 minutes</strong> (3 hours) to complete the exam. Some candidates have reported receiving a bit more time — up to 190 minutes — which can give you extra minutes to review your answers carefully.</li><li><strong>Exam Format:</strong><br>The test includes both <strong>multiple-choice</strong> and <strong>multiple-response</strong> questions. This format challenges you to select the best answer(s) from a list of options, requiring careful analysis and a deep understanding of the material.</li><li><strong>Passing Score:</strong><br>AWS uses a <strong>scaled scoring system</strong>, so the passing score varies depending on the difficulty of the exam questions. Your final score reflects not only the number of correct answers but also the weight assigned to each question.</li><li><strong>Exam Cost:</strong><br>The cost to take the exam is <strong>$300 USD</strong>, which is a standard fee for professional-level AWS certifications.</li><li><strong>Delivery Method:</strong><br>The exam is administered through <strong>Pearson VUE</strong>. You have the flexibility to take it either <strong>online via secure remote proctoring</strong> or at an authorized <strong>testing center</strong>. This allows you to choose the option that best fits your schedule and testing preferences.</li></ul><p>Reference Link:</p><h3>Understanding the Exam Domains</h3><p>The AWS Certified DevOps Engineer — Professional exam is divided into <strong>six key domains</strong>. Each domain focuses on critical areas of AWS and DevOps practices that you must master to build, deploy, and manage secure, scalable, and automated systems. Here’s a detailed look at each domain:</p><h4>1. SDLC Automation (20%)</h4><p>This domain evaluates your ability to automate the Software Development Life Cycle (SDLC). Key areas include:</p><ul><li><strong>Continuous Integration &amp; Delivery (CI/CD):</strong><br>Designing and managing automated pipelines that build, test, and deploy applications.</li><li><strong>Pipeline Orchestration:</strong><br>Implementing strategies like blue-green or canary deployments using AWS services such as CodePipeline, CodeBuild, CodeDeploy, and CodeCommit.</li><li><strong>Automation Best Practices:</strong><br>Ensuring quality and efficiency by integrating automated testing and deployment processes.</li></ul><p><em>Why It Matters:</em><br>Mastering SDLC automation helps speed up software delivery, reduce manual errors, and improve the overall quality of applications.</p><h4>2. Configuration Management &amp; Infrastructure as Code (IaC) (17%)</h4><p>This domain focuses on using code to manage and provision your cloud infrastructure. Key topics include:</p><ul><li><strong>Infrastructure as Code (IaC):</strong><br>Using tools like AWS CloudFormation or Terraform to automate resource provisioning and configuration.</li><li><strong>Configuration Management:</strong><br>Ensuring consistency and version control for environments, reducing errors during deployment.</li><li><strong>Automation of Resource Setup:</strong><br>Simplifying complex deployments by codifying infrastructure and automating routine tasks.</li></ul><p><em>Why It Matters:</em><br>IaC enables you to deploy and manage environments reliably and efficiently, ensuring scalable and repeatable processes.</p><h4>3. Resilient Cloud Solutions (15%)</h4><p>This domain tests your skills in designing systems that can handle failures and recover quickly. Focus areas include:</p><ul><li><strong>High Availability &amp; Fault Tolerance:</strong><br>Creating architectures that remain operational even during system failures.</li><li><strong>Scalability:</strong><br>Implementing auto-scaling, load balancing, and multi-AZ deployments to manage varying workloads.</li><li><strong>Disaster Recovery:</strong><br>Developing backup and restore strategies that minimize downtime during unexpected events.</li></ul><p><em>Why It Matters:</em><br>Building resilient systems ensures business continuity and minimizes disruptions, even in challenging scenarios.</p><h4>4. Monitoring &amp; Logging (15%)</h4><p>In this domain, you demonstrate your ability to monitor the performance and health of AWS environments. It covers:</p><ul><li><strong>Amazon CloudWatch:</strong><br>Setting up metrics, alarms, and dashboards to track system performance.</li><li><strong>Logging Practices:</strong><br>Using tools like AWS CloudTrail and CloudWatch Logs to capture, store, and analyze logs for troubleshooting.</li><li><strong>Real-Time Monitoring:</strong><br>Implementing proactive monitoring to detect and respond to issues quickly.</li></ul><p><em>Why It Matters:</em><br>Effective monitoring and logging help maintain system reliability by enabling quick detection and resolution of issues.</p><h4>5. Incident &amp; Event Response (14%)</h4><p>This domain assesses your readiness to handle operational issues and unexpected events. Key aspects include:</p><ul><li><strong>Incident Detection:</strong><br>Using AWS services to identify and alert on anomalies and security events.</li><li><strong>Automated Remediation:</strong><br>Implementing automated responses to mitigate incidents and reduce downtime.</li><li><strong>Response Strategies:</strong><br>Developing incident response plans that outline clear steps for troubleshooting and recovery.</li></ul><p><em>Why It Matters:</em><br>Quick and effective incident response minimizes the impact of issues, ensuring continuous service and operational resilience.</p><h4>6. Security &amp; Compliance (19%)</h4><p>Security is a top priority in AWS environments. This domain focuses on protecting systems and data through:</p><ul><li><strong>Identity and Access Management (IAM):</strong><br>Implementing strict access controls and policies to safeguard resources.</li><li><strong>Data Encryption &amp; Compliance:</strong><br>Ensuring data security both in transit and at rest, while adhering to regulatory requirements.</li><li><strong>Security Automation:</strong><br>Leveraging AWS Security Hub, Config, and GuardDuty to automate threat detection and compliance validation.</li></ul><p><em>Why It Matters:</em><br>Strong security and compliance measures are essential to protect sensitive information and maintain trust in your cloud solutions.</p><p>Reference Link:</p><h3><strong>30-Day Study Plan for a Busy Cloud Engineer</strong></h3><p>As a full-time cloud engineer, I had limited time to study. Determined to prepare for the AWS DevOps Professional exam in just 30 days, I set aside 3 hours every day for focused learning. I studied from 8 pm to 11 pm after finishing work, and if I ever missed a session, I made sure to catch up the next morning.</p><p>Even though I work with DevOps tools daily, I wanted a structured learning approach to validate and expand my skills. I purchased a 45-hour Udemy course to fill the gaps in my knowledge. To save time, I used ChatGPT to quickly grasp key concepts instead of watching every video in full. I also leveraged a notebook LLM to summarize lengthy YouTube videos into short, clear takeaways.</p><p>I supplemented my studies by using an exam dump from Udemy, with ChatGPT assisting me in answering questions during practice. After scoring over 80% on mock tests, I noticed that many questions were repeated, so I decided to cancel that course. Then, I turned to Exam Topics to identify common exam questions, which boosted my confidence.</p><h3><strong>Steps to Book Your AWS Exam with a 50% Discount</strong></h3><ol><li><strong>Get Your 50% Exam Voucher:</strong></li></ol><ul><li>If you’ve already taken a foundation or associate-level exam, you should receive a 50% discount voucher for your next exam.</li><li>If this is your first exam, participate in the AWS Exam Readiness Workshop. This workshop can help you earn a discount voucher.</li></ul><ol><li><strong>Create Your AWS Certification Account:</strong></li></ol><ul><li>Sign up or log in to your AWS Certification account to manage your exam vouchers and registration.</li></ul><ol><li><strong>Schedule Your Exam Through Pearson VUE:</strong></li></ol><ul><li>Choose a date and time that fits your schedule using the Pearson VUE portal on the AWS Certification website.</li></ul><ol><li><strong>Complete Your Registration:</strong></li></ol><ul><li>Before finalizing your booking, make sure the 50% discount has been applied to your exam fee.</li><li>Complete the payment process with the reduced fee.</li><li>You will then receive a confirmation email with all your exam details.</li></ul><h3><strong>Available Exam Modes Available for AWS Certification Exam</strong></h3><p>There are two ways to take the exam: in-person at an exam center or online. I chose the online option because the nearest exam center was 30 km from my home, and I preferred the convenience of taking the exam from my own space.</p><h3>Tips: I follow Before the Exam.</h3><p>Before taking the exam, I follow these simple steps to ensure a smooth experience:</p><ol><li><strong>Uninstall Interfering Software:</strong><br>Remove antivirus programs (like Bitdefender) and any screen recording tools that might conflict with the exam’s security requirements.</li><li><strong>Run the Pearson VUE System Test:</strong><br>Install and run the Pearson VUE system test tool. This tool checks your computer for any software that could be against exam policies.<br><a href="https://www.pearsonvue.com/us/en/test-takers/onvue-online-proctoring.html">Learn more here</a>.</li><li><strong>Ensure Stable Internet:</strong><br>Make sure you have a good, reliable internet connection to avoid disruptions during your online exam.</li></ol><h3><strong>Tips I follow During the Exam</strong></h3><ul><li><strong>Clear Your Desk:</strong><br>Keep your desk empty — only your laptop, its charger, and a transparent water bottle should be present. This ensures there are no distractions and meets exam guidelines.</li><li><strong>Have Valid ID Ready:</strong><br>Make sure you have a valid ID card for identity verification at the start of the exam.</li><li><strong>Check In Early:</strong><br>Log in and complete the check-in process at least 30 minutes before your exam starts. This extra time allows for any system checks and helps you settle in calmly before the exam begins.</li></ul><h3><strong>After the Exam: How to Check Your Results</strong></h3><ul><li><strong>Result Notification:</strong><br>Within 24 hours after completing the exam, you will receive your results via the registered email. Additionally, you can check your results directly on the AWS Certification console dashboard, where your score will appear before the email arrives.</li><li><strong>Passing Standards:</strong><br>The passing scores for AWS exams remain consistent:</li><li><strong>Foundational-Level:</strong> Scaled score of 700</li><li><strong>Associate-Level:</strong> Scaled score of 720</li><li><strong>Professional-Level and Specialty:</strong> Scaled score of 750</li></ul><h3><strong>Retaking an Exam: What You Need to Know</strong></h3><ul><li><strong>Failure and Retakes:</strong><br>If you fail the exam, you must wait 14 calendar days before attempting it again. There is no limit to the number of attempts, but you’ll need to pay the full registration fee for each try.</li><li><strong>Post-Pass Policy:</strong><br>Once you pass an exam, you cannot retake the same exam for two years.</li><li><strong>New Exam Versions:</strong><br>If AWS updates the exam with a new guide and a new series code, you become eligible to take the new version, even if you’ve passed the previous one.</li><li><strong>Beta Exam Policy:</strong><br>For beta versions of the exam, you can only take it once. If you need to retake it, you’ll have to wait until the exam is generally available.</li></ul><h3><strong>Exam Certificate Validity</strong></h3><p>AWS certifications are valid for <strong>three years</strong>. After this period, you must recertify to maintain your status as an AWS certified professional. Recertification ensures you stay updated on the latest AWS services, best practices, and emerging trends in cloud computing. This process helps ensure that your skills remain relevant and that you continue to provide high-quality solutions in a rapidly evolving technology landscape.</p><h3>Top 5 Preparation Sources I have Used to Learn</h3><ol><li><strong>Exam Guides:</strong><br>Study the official AWS exam guides for an overview of topics and domains.</li></ol><ul><li><a href="https://d1.awsstatic.com/training-and-certification/ramp-up_guides/Ramp-Up_Guide_DevOps.pdf">AWS DevOps Ramp-Up Guide</a></li><li><a href="https://d1.awsstatic.com/training-and-certification/docs-devops-pro/AWS-Certified-DevOps-Engineer-Professional_Exam-Guide.pdf">AWS DevOps Engineer — Professional Exam Guide</a></li></ul><ol><li><strong>Sample Questions &amp; Exam Dumps:</strong><br>Practice with sample questions using free platforms like Exam Topic. I even used ChatGPT to create a script to display questions and answers quickly. (Note: Some Udemy dumps had incorrect answers, so I avoided relying on them.)</li><li><strong>AWS Official Documentation &amp; Whitepapers:</strong><br>Deep dive into AWS documentation and whitepapers to understand services and best practices.</li><li><strong>AWS DevOps Blog:</strong><br>Follow the AWS DevOps Blog on AWS and Medium for real-world examples and clear explanations.</li><li><strong>AWS FAQs:</strong><br>Read the FAQs for various AWS services to get a straightforward understanding of key features.</li></ol><h3>Key Topics and AWS Services to Master for the AWS DevOps Professional Exam</h3><p>To excel in the AWS DevOps Professional exam, it’s crucial to understand both the core concepts and the AWS services that bring them to life. Here’s a combined guide covering the essential topics and the main AWS tools you need to know:</p><h4>1. CI/CD &amp; SDLC Automation</h4><ul><li><strong>Core Concepts:</strong><br>Automate the software development lifecycle by building continuous integration and continuous delivery pipelines. Understand strategies like Blue-Green and Canary deployments.</li><li><strong>Key AWS Tools:</strong><br>AWS CodePipeline, CodeBuild, CodeDeploy, and CodeCommit.</li><li><strong>Other Tools:</strong><br>GitHub Actions and Jenkins can also be used to automate deployments.</li></ul><h4>2. Infrastructure as Code (IaC)</h4><ul><li><strong>Core Concepts:</strong><br>Learn to automate the setup and management of infrastructure using code. Focus on best practices, managing state files, and detecting configuration drift.</li><li><strong>Key Tools:</strong><br>AWS CloudFormation and Terraform.</li></ul><h4>3. Monitoring &amp; Logging</h4><ul><li><strong>Core Concepts:</strong><br>Monitor system performance and troubleshoot issues by setting up metrics, alarms, and logging.</li><li><strong>Key AWS Tools:</strong><br>AWS CloudWatch for logs, metrics, and alarms; AWS X-Ray for tracing distributed applications; AWS OpenSearch and Kinesis for centralized log management.</li></ul><h4>4. Security &amp; Compliance</h4><ul><li><strong>Core Concepts:</strong><br>Secure your AWS environment by implementing robust access controls, encryption, and compliance measures.</li><li><strong>Key AWS Tools:</strong><br>AWS IAM for roles and policies, AWS KMS for encryption, AWS Secrets Manager for managing sensitive information, and security services like AWS Security Hub, GuardDuty, and Config.</li></ul><h4>5. Additional AWS Services to Know</h4><ul><li><strong>DevOps Tools:</strong><br>AWS CodeArtifact enhances your CI/CD pipelines.</li><li><strong>Storage &amp; Compute:</strong><br>Amazon S3, AWS Lambda, Amazon ECS, Fargate, and EC2 Image Builder.</li><li><strong>Infrastructure Management:</strong><br>AWS Systems Manager, AWS Config, and AWS Organizations help manage your AWS environment.</li><li><strong>Networking &amp; Security:</strong><br>Amazon VPC, Route 53, AWS Control Tower, and Service Control Policies (SCPs) are essential for building secure and scalable architectures.</li><li><strong>Advanced Monitoring:</strong><br>AWS EventBridge further integrates monitoring with your automation workflows.</li></ul><h3>Final Tips to Pass the Exam: The Ninja Technique and <strong>Exam Strategy:</strong></h3><ul><li><strong>Flag Difficult Questions:</strong><br>Out of 75 questions, I flagged 25 that I found challenging. This allowed me to quickly revisit them later without losing time.</li><li><strong>Multiple-Choice Focus:</strong><br>I noticed that the hardest questions were those with 3 out of 5 or 6 options. I marked these and focused on identifying the best answer.</li><li><strong>Use the ABBA Method:</strong><br>“Always Be Back Answering” — I answered the easy questions first and then returned to the tougher ones later.</li><li><strong>Time Management:</strong><br>With 45 minutes left, I reviewed all the flagged questions, ensuring I caught any mistakes before submitting the exam.</li><li><strong>Keyword Strategy:</strong><br>I carefully read each question to spot keywords that hint at the right answer, which helped me quickly narrow down the options.</li><li><strong>Prioritize Cost-Effective Solutions:</strong><br>I focused on answers that were both cost-effective and easy to implement, aligning with real-world AWS best practices.</li></ul><h3>Time Management Tips for Preparation and Exam Day</h3><h4>During Study &amp; Preparation</h4><ul><li><strong>Set a Daily Goal:</strong><br>Allocate a specific number of hours each day for study. For example, aim for 1–2 hours of focused learning.</li><li><strong>Create a Study Schedule:</strong><br>Break down topics into daily tasks. Use a calendar or planner to assign topics to specific days, ensuring you cover all exam domains.</li><li><strong>Use Timers:</strong><br>Work in focused intervals (e.g., 25–30 minutes) with short breaks in between (like the Pomodoro Technique). This keeps you refreshed and improves concentration.</li><li><strong>Prioritize Weak Areas:</strong><br>Identify topics you struggle with and allocate extra time for them. Regularly review and adjust your schedule based on your progress.</li><li><strong>Practice Under Timed Conditions:</strong><br>Regularly take practice tests or quizzes with a timer to simulate exam conditions and improve your speed.</li><li><strong>Eliminate Distractions:</strong><br>Create a dedicated, quiet study space. Turn off notifications and limit interruptions to maintain focus.</li></ul><h4>During the Exam</h4><ul><li><strong>Skim Through the Exam:</strong><br>Quickly review all questions at the start to gauge difficulty and mark the ones you want to answer later.</li><li><strong>Answer Easy Questions First:</strong><br>Secure quick points by answering the questions you find easiest, then return to the tougher ones.</li><li><strong>Flag Challenging Questions:</strong><br>Mark difficult questions for review. Don’t spend too much time on any single question — move on and come back if time permits.</li><li><strong>Keep an Eye on the Clock:</strong><br>Regularly check the time to ensure you’re pacing yourself. Aim to complete sections within the allocated time.</li><li><strong>Use the ABBA Method:</strong><br>“Always Be Back Answering” — finish all easier questions first, then return to the flagged ones.</li></ul><h3>Ultimate Cheat Sheet for AWS Certified DevOps Engineer — Professional Certification</h3><p>This cheat sheet is your go-to reference to quickly review the key topics, tools, and exam strategies needed to ace the AWS DevOps Professional exam.</p><h4>1. Exam Domains &amp; Weightages</h4><ul><li><strong>SDLC Automation (20%)</strong></li><li><strong>Focus:</strong> CI/CD pipelines, automated testing, and deployment strategies.</li><li><strong>Key Tools:</strong> AWS CodePipeline, CodeBuild, CodeDeploy, CodeCommit; GitHub Actions; Jenkins.</li><li><strong>Deployment Strategies:</strong> Blue-green and canary deployments.</li><li><strong>Configuration Management &amp; Infrastructure as Code (IaC) (17%)</strong></li><li><strong>Focus:</strong> Automating infrastructure setup, managing state, and detecting drift.</li><li><strong>Key Tools:</strong> AWS CloudFormation, Terraform, AWS CDK.</li><li><strong>Resilient Cloud Solutions (15%)</strong></li><li><strong>Focus:</strong> High availability, fault tolerance, auto-scaling, and disaster recovery.</li><li><strong>Key Tools:</strong> Auto Scaling Groups, ELB, Multi-AZ deployments, AWS StackSets, Warm Pools.</li><li><strong>Monitoring &amp; Logging (15%)</strong></li><li><strong>Focus:</strong> Tracking system performance, troubleshooting, and centralized logging.</li><li><strong>Key Tools:</strong> AWS CloudWatch (logs, metrics, alarms), CloudTrail, AWS X-Ray, EventBridge, OpenSearch, Kinesis.</li><li><strong>Incident &amp; Event Response (14%)</strong></li><li><strong>Focus:</strong> Detecting incidents, automated remediation, and handling events.</li><li><strong>Key Tools:</strong> AWS Config, Systems Manager, Lambda, custom metrics.</li><li><strong>Security &amp; Compliance (19%)</strong></li><li><strong>Focus:</strong> Securing the environment, managing access, and ensuring compliance.</li><li><strong>Key Tools:</strong> IAM, AWS KMS, AWS Secrets Manager, Security Hub, GuardDuty, SCPs.</li></ul><h4>2. Key Tools &amp; Services</h4><ul><li><strong>DevOps &amp; CI/CD:</strong></li><li>CodePipeline, CodeBuild, CodeDeploy, CodeCommit</li><li>GitHub Actions, Jenkins</li><li><strong>Infrastructure as Code (IaC):</strong></li><li>CloudFormation, Terraform, CDK</li><li><strong>Monitoring &amp; Logging:</strong></li><li>CloudWatch, CloudTrail, AWS X-Ray, EventBridge</li><li>OpenSearch, Kinesis</li><li><strong>Security &amp; Compliance:</strong></li><li>IAM, KMS, Secrets Manager</li><li>Security Hub, GuardDuty, AWS Config, SCPs</li><li><strong>Resiliency &amp; Scalability:</strong></li><li>Auto Scaling, ELB, Multi-AZ, Warm Pools, StackSets</li></ul><h4>3. Exam Strategies &amp; Tips</h4><ul><li><strong>Read Carefully:</strong><br>Identify keywords in questions to guide your answer.</li><li><strong>Time Management:</strong><br>Answer easier questions first and flag the tougher ones for review. Use the ABBA method (Always Be Back Answering).</li><li><strong>Practice Hands-On:</strong><br>Real-world experience with AWS services is key. Utilize labs, practice exams, and hands-on projects.</li><li><strong>Cost-Effective &amp; Scalable Solutions:</strong><br>Focus on answers that are both efficient and easy to implement in a real-world scenario.</li><li><strong>Review &amp; Mock Exams:</strong><br>Regularly take full-length practice exams under timed conditions. Review flagged questions to improve your score.</li></ul><h4>4. Additional Tips</h4><ul><li><strong>System Check:</strong><br>Run the Pearson VUE system test before your exam to ensure all software and connectivity are in order.</li><li><strong>Exam Day Setup:</strong><br>Have a clear desk (only your laptop, charger, and a transparent water bottle) and valid ID. Log in 30 minutes early for check-in.</li><li><strong>Utilize Resources:</strong><br>Study from the AWS official documentation, whitepapers, AWS DevOps blogs, and FAQs. Leverage Udemy courses and online communities for additional practice and insights.</li><li><strong>Exam Vouchers:</strong><br>If you’ve passed a previous AWS exam, check your certification account for a 50% discount voucher.</li></ul><h3>Special Benefit: AWS Community Builders Program</h3><p>Being part of the AWS Community Builders Program has been a pivotal part of my certification journey. Through this program, I received a free exam voucher from AWS, which significantly reduced my exam expenses and made the certification process more accessible. This exclusive benefit not only eased the financial burden but also motivated me to pursue advanced AWS skills.</p><p>For anyone actively involved in the AWS community, the AWS Community Builders Program offers incredible opportunities. It provides access to valuable resources, expert insights, and networking with like-minded professionals. Moreover, the program’s perks, such as free exam vouchers, can help accelerate your career by making it easier to achieve AWS certifications. Embrace the chance to join this vibrant community and take advantage of the unique benefits it offers for your professional growth in the cloud industry.</p><h3>Good News for You :)</h3><h3>🚀 Master Kubernetes &amp; DevOps with AI — Unlock 4 Income Streams!</h3><p>I’ve designed <strong>two powerful courses</strong> to help you break into <strong>high-paying Cloud &amp; DevOps roles!</strong></p><p>🎯 <strong>100-Day Cloud &amp; DevOps Mastery with AI</strong> — Perfect for <strong>freshers &amp; career switchers</strong></p><p>✅ <strong>100-Day Kubernetes Mastery with AI</strong> — Learn Kubernetes with <strong>10 real-world projects</strong></p><p>🔥 <strong>Get job-ready &amp; start earning!</strong> <strong>Book your FREE demo now:</strong><br>📌 Kubernetes Mastery 👉 <a href="https://forms.gle/tqxT7YwERaF8tPEc7">Enroll Now</a><br>📌 Cloud &amp; DevOps Mastery 👉 <a href="https://forms.gle/Cxxhn8hkXG3STRi69">Enroll Now</a></p><p>If you find this blog is helpfull please 👏 and comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=243e77a217af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Job Search Sites in Indiia for Experienced and Fresher DevOps Engineer in 2025]]></title>
            <link>https://medium.com/@techmahato/best-job-search-sites-in-indiia-for-experienced-and-fresher-devops-engineer-in-2025-ec8cb00b41ce?source=rss-df39eee9f69e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec8cb00b41ce</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[devops-jobs]]></category>
            <category><![CDATA[top-10-job-website]]></category>
            <category><![CDATA[cloud-job]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[Tech Mahato]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 02:59:45 GMT</pubDate>
            <atom:updated>2025-03-11T02:59:45.792Z</atom:updated>
            <content:encoded><![CDATA[<p>The job market for tech professionals, especially those in DevOps and cloud computing, is highly competitive and fast-moving. As a 37-year-old Senior Cloud Engineer based in Kolkata with three years of hands-on experience in cloud and DevOps, I understand the challenges of finding the right opportunity. Whether you’re proficient in Linux and Windows administration, AWS Cloud services (including ECS, EKS, and Code Pipeline), or modern tools like Docker, Kubernetes, Jenkins, and GitOps with ArgoCD, the key is to be where the opportunities are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXHLkYmI9IdzASf6_3O7nw.png" /><figcaption>Top 10 Website Freshers/ Experienced Cloud &amp; DevOps Job</figcaption></figure><p>In this detailed guide, I’ve compiled a list of the top 10 job search websites that can significantly boost your chances of landing that perfect DevOps Engineer role in India.</p><h3>1. Naukri.com</h3><p><strong>Why It Stands Out:</strong><br> Naukri.com is one of India’s largest and most established job portals. It caters to a wide range of industries, but its IT and tech sections are particularly robust. The platform offers:</p><ul><li>Advanced search filters to narrow down jobs by location, experience, and role.</li><li>Regularly updated listings that include both permanent and contract positions.</li><li>Resume building tools and profile enhancements that can help you stand out to recruiters.</li></ul><p><strong>How It Can Help You:</strong><br> By leveraging Naukri.com’s comprehensive database, you can quickly identify opportunities that match your DevOps skills and experience. The site also provides insights into company reviews and salary benchmarks, enabling you to make informed decisions about your applications.</p><h3>2. LinkedIn</h3><p><strong>Why It Stands Out:</strong><br> LinkedIn is not just a professional networking site; it’s also a powerful job search engine. With millions of users worldwide, it offers:</p><ul><li>A vast network of recruiters and professionals in the cloud and DevOps space.</li><li>Personalized job recommendations based on your profile and activity.</li><li>The ability to join groups and participate in discussions, which can further your industry knowledge and visibility.</li></ul><p><strong>How It Can Help You:</strong><br> Create a strong, updated profile that highlights your skills in AWS, Docker, Kubernetes, and other areas. Engage with industry professionals and join relevant groups to increase your exposure to job opportunities and insider information about openings.</p><h3>3. Indeed India</h3><p><strong>Why It Stands Out:</strong><br> Indeed is known for its simplicity and powerful search capabilities. Key features include:</p><ul><li>A user-friendly interface with advanced filters for location, salary, experience level, and job type.</li><li>Aggregated listings from various sources, ensuring a broad spectrum of opportunities.</li><li>Company reviews and ratings that help you understand the work environment before applying.</li></ul><p><strong>How It Can Help You:</strong><br> For DevOps roles, Indeed can be an excellent resource to compare job descriptions and requirements across different companies. You can set up email alerts for new postings that match your criteria, ensuring you never miss an opportunity.</p><h3>4. Glassdoor</h3><p><strong>Why It Stands Out:</strong><br> Glassdoor offers a unique combination of job listings and company insights. The platform features:</p><ul><li>Detailed company reviews and ratings submitted by employees.</li><li>Salary insights and interview reviews, providing transparency about the recruitment process.</li><li>A straightforward application process that allows you to track your submissions.</li></ul><p><strong>How It Can Help You:</strong><br> By researching companies on Glassdoor, you can gain valuable insights into their work culture and compensation packages. This information is particularly useful when applying for competitive DevOps positions, allowing you to target employers that value your skill set.</p><h3>5. Monster India</h3><p><strong>Why It Stands Out:</strong><br> Monster India has been a staple in the Indian job market for years. Its strengths include:</p><ul><li>A broad database of job listings across various sectors, including IT and cloud computing.</li><li>Career advice, resume tips, and interview preparation resources.</li><li>Regularly updated listings that feature both established companies and emerging startups.</li></ul><p><strong>How It Can Help You:</strong><br> Monster India’s resources can help you not only find the right job but also refine your application materials. The platform’s career advice sections are particularly useful for understanding market trends in the DevOps and cloud space.</p><h3>6. TimesJobs</h3><p><strong>Why It Stands Out:</strong><br> TimesJobs is a well-known portal in India, particularly popular among tech professionals. It offers:</p><ul><li>A user-friendly search experience with detailed filtering options.</li><li>Insights into companies and industry trends.</li><li>A mix of opportunities from traditional companies to innovative startups.</li></ul><p><strong>How It Can Help You:</strong><br> TimesJobs’ dedicated tech section means you can focus solely on roles that align with your expertise in cloud technologies and DevOps. The site also provides alerts and updates on new job postings, ensuring you’re always in the loop.</p><h3>7. Shine.com</h3><p><strong>Why It Stands Out:</strong><br> Shine.com is another prominent job portal in India that combines modern technology with personalized services. Its features include:</p><ul><li>A sleek, intuitive interface that makes job searching seamless.</li><li>Tools for resume creation and enhancement.</li><li>Detailed job postings that help you assess your fit for a role.</li></ul><p><strong>How It Can Help You:</strong><br> For professionals in the cloud and DevOps sectors, Shine.com’s comprehensive listings and user-friendly design make it easy to filter out the noise and focus on relevant job opportunities.</p><h3>8. AngelList India</h3><p><strong>Why It Stands Out:</strong><br> AngelList India is the go-to platform for those interested in startups and emerging tech companies. It provides:</p><ul><li>Direct access to startup job listings and funding details.</li><li>An emphasis on innovative roles that often require up-to-date technical skills.</li><li>Opportunities to work in dynamic environments where your DevOps expertise can drive growth.</li></ul><p><strong>How It Can Help You:</strong><br> If you’re looking for a role in a fast-paced, startup environment, AngelList India is ideal. Your experience with AWS, Docker, Kubernetes, and GitOps can be especially valuable in these settings, where agility and innovation are key.</p><h3>9. CutShort</h3><p><strong>Why It Stands Out:</strong><br> CutShort is tailored specifically for tech roles. Its strengths include:</p><ul><li>A focus on connecting experienced professionals with companies that value technical expertise.</li><li>A simplified application process that emphasizes skills and experience over lengthy resumes.</li><li>Direct communication channels with recruiters and hiring managers.</li></ul><p><strong>How It Can Help You:</strong><br> CutShort is perfect for someone with specialized skills in cloud and DevOps. The platform streamlines the application process and allows you to directly interact with potential employers, increasing your chances of landing an interview.</p><h3>10. Hirist.com</h3><p><strong>Why It Stands Out:</strong><br> Hirist.com is designed for tech professionals, offering:</p><ul><li>Specialized listings for roles in cloud computing, DevOps, and software development.</li><li>A focus on mid to senior-level positions, which is ideal for experienced professionals.</li><li>Detailed job descriptions that help you gauge whether a role aligns with your expertise.</li></ul><p><strong>How It Can Help You:</strong><br> For seasoned engineers like yourself, Hirist.com provides a curated list of opportunities where advanced skills in AWS, Kubernetes, and Jenkins are in high demand. The platform’s niche focus means you’re more likely to find positions that fit your career stage and technical background.</p><h3><strong>Bonus:</strong></h3><h4>1. General Job Portals (India &amp; Global)</h4><ol><li>LinkedIn Jobs — <a href="https://www.linkedin.com/jobs">linkedin.com/jobs</a></li><li>Naukri.com — <a href="https://www.naukri.com/">naukri.com</a></li><li>Indeed India — <a href="https://www.indeed.co.in/">indeed.co.in</a></li><li>Freshersworld — <a href="https://www.freshersworld.com/">freshersworld.com</a></li><li>Shine — <a href="https://www.shine.com/">shine.com</a></li><li>Monster India — <a href="https://www.monsterindia.com/">monsterindia.com</a></li><li>TimesJobs — <a href="https://www.timesjobs.com/">timesjobs.com</a></li><li>Glassdoor — <a href="https://www.glassdoor.co.in/">glassdoor.co.in</a></li><li>CutShort — <a href="https://cutshort.io/">cutshort.io</a></li><li>Instahyre — <a href="https://www.instahyre.com/">instahyre.com</a></li><li>GraduatesFirst — <a href="https://graduatesfirst.com/">graduatesfirst.com</a></li><li>Apna — <a href="https://apna.co/">apna.co</a></li><li>HireMee — <a href="https://www.hiremee.co.in/">hiremee.co.in</a></li><li>FreshersLive — <a href="https://www.fresherslive.com/">fresherslive.com</a></li><li>CareerBuilder India — <a href="https://www.careerbuilder.co.in/">careerbuilder.co.in</a></li></ol><h4>2. Tech-Specific Job Boards</h4><ol><li>HackerEarth Jobs — <a href="https://www.hackerearth.com/jobs">hackerearth.com/jobs</a></li><li>AngelList/Wellfound — <a href="https://wellfound.com/">wellfound.com</a> (for startups)</li><li>Stack Overflow Jobs — <a href="https://stackoverflow.com/jobs">stackoverflow.com/jobs</a></li><li>GitHub Jobs — <a href="https://jobs.github.com/">jobs.github.com</a></li><li>DevOps.com Jobs — <a href="https://devops.com/jobs">devops.com/jobs</a></li><li>AWS Careers — <a href="https://aws.amazon.com/careers">aws.amazon.com/careers</a></li><li>Google Careers — <a href="https://careers.google.com/">careers.google.com</a></li><li>Microsoft Careers — <a href="https://careers.microsoft.com/">careers.microsoft.com</a></li><li>Kubernetes Jobs — <a href="https://kubernetes.careers/">kubernetes.careers</a></li><li>Docker Jobs — <a href="https://www.docker.com/careers">docker.com/careers</a></li><li>HashiCorp Careers — <a href="https://www.hashicorp.com/careers">hashicorp.com/careers</a></li><li>Red Hat Jobs — <a href="https://www.redhat.com/jobs">redhat.com/jobs</a></li><li>Cloudflare Careers — <a href="https://www.cloudflare.com/careers">cloudflare.com/careers</a></li><li>Cisco Careers — <a href="https://jobs.cisco.com/">jobs.cisco.com</a></li><li>IBM Careers — <a href="https://www.ibm.com/careers">ibm.com/careers</a></li></ol><h4>3. Company Career Pages (India)</h4><ol><li>TCS Careers — <a href="https://www.tcs.com/careers">tcs.com/careers</a></li><li>Infosys Careers — <a href="https://www.infosys.com/careers">infosys.com/careers</a></li><li>Wipro Careers — <a href="https://careers.wipro.com/">careers.wipro.com</a></li><li>Accenture India — <a href="https://www.accenture.com/in-en/careers">accenture.com/in-en/careers</a></li><li>Cognizant Careers — <a href="https://www.cognizant.com/careers">cognizant.com/careers</a></li><li>Capgemini India — <a href="https://www.capgemini.com/in-en/careers">capgemini.com/in-en/careers</a></li><li>Tech Mahindra — <a href="https://www.techmahindra.com/careers">techmahindra.com/careers</a></li><li>LTI (L&amp;T Infotech) — <a href="https://www.lntinfotech.com/careers">lntinfotech.com/careers</a></li><li>Mindtree Careers — <a href="https://www.mindtree.com/careers">mindtree.com/careers</a></li><li>Zoho Careers — <a href="https://www.zoho.com/careers">zoho.com/careers</a></li><li>Flipkart Careers — <a href="https://www.flipkartcareers.com/">flipkartcareers.com</a></li><li>Amazon India — <a href="https://www.amazon.jobs/">amazon.jobs</a></li><li>Paytm Careers — <a href="https://paytm.com/careers">paytm.com/careers</a></li><li>Ola Careers — <a href="https://ola.skillate.com/">ola.skillate.com</a></li><li>Byju’s Careers — <a href="https://byjus.com/careers">byjus.com/careers</a></li></ol><h4>4. Freelance &amp; Gig Platforms</h4><ol><li>Upwork — <a href="https://www.upwork.com/">upwork.com</a></li><li>Fiverr — <a href="https://www.fiverr.com/">fiverr.com</a></li><li>Toptal — <a href="https://www.toptal.com/">toptal.com</a></li><li>Freelancer — <a href="https://www.freelancer.in/">freelancer.in</a></li><li>Gigster — <a href="https://gigster.com/">gigster.com</a></li></ol><h4>5. Remote-First Job Boards</h4><ol><li>Remote OK — <a href="https://remoteok.com/">remoteok.com</a></li><li>We Work Remotely — <a href="https://weworkremotely.com/">weworkremotely.com</a></li><li>FlexJobs — <a href="https://www.flexjobs.com/">flexjobs.com</a></li><li>Working Nomads — <a href="https://www.workingnomads.com/">workingnomads.com</a></li><li>Himalayas — <a href="https://himalayas.app/">himalayas.app</a></li><li>Jobspresso — <a href="https://jobspresso.co/">jobspresso.co</a></li><li>JustRemote — <a href="https://justremote.co/">justremote.co</a></li><li>Remotive — <a href="https://remotive.com/">remotive.com</a></li><li>Pangian — <a href="https://pangian.com/">pangian.com</a></li><li>Outsourcely — <a href="https://www.outsourcely.com/">outsourcely.com</a></li></ol><h4>6. Learning Platforms with Job Boards</h4><ol><li>Coursera Jobs — <a href="https://www.coursera.org/jobs">coursera.org/jobs</a></li><li>Udacity Careers — <a href="https://www.udacity.com/careers">udacity.com/careers</a></li><li>Simplilearn Jobs — <a href="https://www.simplilearn.com/jobs">simplilearn.com/jobs</a></li><li>Edureka Careers — <a href="https://www.edureka.co/careers">edureka.co/careers</a></li><li>Cloud Academy Jobs — <a href="https://cloudacademy.com/jobs">cloudacademy.com/jobs</a></li></ol><h4>7. Networking &amp; Community Platforms</h4><ol><li>Meetup — <a href="https://www.meetup.com/">meetup.com</a> (Join DevOps/Cloud groups)</li><li>DevOps Institute — <a href="https://devopsinstitute.com/">devopsinstitute.com</a></li><li>CNCF (Cloud Native Computing Foundation) — <a href="https://www.cncf.io/community">cncf.io/community</a></li><li>AWS Community Builders — <a href="https://aws.amazon.com/developer/community">aws.amazon.com/developer/community</a></li><li>Docker Community — <a href="https://www.docker.com/community">docker.com/community</a></li><li>Kubernetes Slack — <a href="https://slack.k8s.io/">slack.k8s.io</a></li><li>GitHub Community — <a href="https://github.community/">github.community</a></li><li>Hashnode — <a href="https://hashnode.com/">hashnode.com</a> (Tech blogging + jobs)</li><li>Dev.to — <a href="https://dev.to/">dev.to</a> (Networking + job posts)</li><li>Reddit — <a href="https://www.reddit.com/r/devopsjobs">reddit.com/r/devopsjobs</a></li></ol><h4>8. Government &amp; Public Sector Portals (India)</h4><ol><li>National Career Service (NCS) — <a href="https://www.ncs.gov.in/">ncs.gov.in</a></li><li>Sarkari Naukri — <a href="https://www.sarkarinaukri.com/">sarkarinaukri.com</a></li><li>NIC Careers — <a href="https://www.nic.in/careers">nic.in/careers</a></li><li>UIDAI Careers — <a href="https://uidai.gov.in/careers">uidai.gov.in/careers</a></li><li>ISRO Careers — <a href="https://www.isro.gov.in/careers">isro.gov.in/careers</a></li></ol><h4>9. Recruitment Agencies</h4><ol><li>Michael Page — <a href="https://www.michaelpage.co.in/">michaelpage.co.in</a></li><li>Randstad India — <a href="https://www.randstad.in/">randstad.in</a></li><li>ABC Consultants — <a href="https://abcconsultants.in/">abcconsultants.in</a></li><li>TeamLease — <a href="https://www.teamlease.com/">teamlease.com</a></li><li>Adecco India — <a href="https://www.adecco.co.in/">adecco.co.in</a></li></ol><h4>10. Global Platforms (Open to Indian Candidates)</h4><ol><li>Dice — <a href="https://www.dice.com/">dice.com</a></li><li>Hired — <a href="https://hired.com/">hired.com</a></li><li>Vettery — <a href="https://www.vetter.com/">vettery.com</a></li><li>Y Combinator Jobs — <a href="https://www.ycombinator.com/jobs">ycombinator.com/jobs</a></li><li>Otta — <a href="https://otta.com/">otta.com</a></li><li>Wellfound (formerly AngelList Talent) — <a href="https://wellfound.com/">wellfound.com</a></li><li>Triplebyte — <a href="https://triplebyte.com/">triplebyte.com</a></li><li>Underdog.io — <a href="https://underdog.io/">underdog.io</a></li><li>Gun.io — <a href="https://gun.io/">gun.io</a></li><li>Jobbatical — <a href="https://jobbatical.com/">jobbatical.com</a></li></ol><h4>Bonus: Certification Platforms with Job Support</h4><ol><li>AWS Training &amp; Certification — <a href="https://aws.training/">aws.training</a></li><li>Microsoft Learn — <a href="https://learn.microsoft.com/">learn.microsoft.com</a></li><li>Google Cloud Training — <a href="https://cloud.google.com/training">cloud.google.com/training</a></li><li>Linux Foundation Jobs — <a href="https://www.linuxfoundation.org/careers">linuxfoundation.org/careers</a></li><li>Kubernetes Certification Jobs — <a href="https://training.linuxfoundation.org/">training.linuxfoundation.org</a></li></ol><h4>Tips for Freshers</h4><ol><li><strong>Certifications Matter:</strong> Get entry-level certs like:</li></ol><ul><li>AWS Certified Cloud Practitioner</li><li>Microsoft Azure Fundamentals (AZ-900)</li><li>Google Associate Cloud Engineer</li><li>Certified Kubernetes Administrator (CKA)</li></ul><ol><li><strong>Build Projects:</strong> Create GitHub repos for Terraform/Ansible scripts, CI/CD pipelines, or cloud deployments.</li><li><strong>Leverage Internships:</strong> Apply for internships on Internshala (<a href="https://internshala.com/">internshala.com</a>).</li><li><strong>Tailor Your Resume:</strong> Highlight labs, certifications, and personal projects.</li></ol><h3>Final Thoughts</h3><p>Finding the right job as a DevOps Engineer in India requires being proactive and utilizing multiple channels to maximize your reach. These top 10 websites offer diverse opportunities — from established corporate roles to innovative startup positions — each with unique features to support your job search. By optimizing your profile, tailoring your resume, and actively engaging on these platforms, you can significantly boost your chances of securing interviews and landing the role that best matches your skills and career aspirations.</p><p>Happy job hunting, and here’s to your next great opportunity in the dynamic world of cloud and DevOps!</p><p><em>If you found this guide helpful, feel free to share your own experiences or additional tips in the comments below. Let’s help each other navigate the evolving tech landscape!</em></p><h3>Good News for You :)</h3><h4>🚀 <strong>Master Kubernetes &amp; DevOps with AI — Unlock 4 Income Streams!</strong></h4><p>I’ve designed <strong>two powerful courses</strong> to help you break into <strong>high-paying Cloud &amp; DevOps roles!</strong></p><p>✅ <strong>100-Day Kubernetes Mastery with AI</strong> — Learn Kubernetes with <strong>10 real-world projects</strong><br> 🎯 <strong>100-Day Cloud &amp; DevOps Mastery with AI</strong> — Perfect for <strong>freshers &amp; career switchers</strong></p><p>🔥 <strong>Get job-ready &amp; start earning!</strong> <strong>Book your FREE demo now:</strong><br> 📌 Kubernetes Mastery 👉 <a href="https://forms.gle/tqxT7YwERaF8tPEc7">Enroll Now</a><br> 📌 Cloud &amp; DevOps Mastery 👉 <a href="https://forms.gle/Cxxhn8hkXG3STRi69">Enroll Now</a></p><h4>Show Your Love:</h4><p>If you find this blog is helpfull please 👏 and comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec8cb00b41ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>