Full Platform Operations, Security & Troubleshooting Guide
20 minAdvanced
This creates billable resources. Run it in a dev environment and destroy it when you finish. Set a budget alarm first.
What you are building#
What is Day-2 Platform Operations?#
Day-2 Platform Operations encompasses the ongoing operational lifecycle of software infrastructure following initial deployment: continuous monitoring, incident resolution, cluster maintenance, credential rotation, and disaster recovery.
Verify it worked#
Verify all platform namespaces:
Terminal
kubectl get pods -AClean up#
Run this even if you did not finish. Everything above is destroyable, and an account full of half-built experiments is how a surprise bill starts.
Destructive — This removes real resources. Check which environment you are in first.
Terminal
kubectl delete ingress --all -A # removes the ALB first
helm list -A # then any releases holding volumes
terraform destroy -auto-approve # then the cluster and network
# Finally sweep for anything Kubernetes created outside Terraform state:
aws elbv2 describe-load-balancers --query 'LoadBalancers[].LoadBalancerName'
aws ec2 describe-volumes --filters Name=status,Values=available --query 'Volumes[].VolumeId'
aws ec2 describe-nat-gateways --filter Name=state,Values=available --query 'NatGateways[].NatGatewayId'
aws eks list-clusters --query 'clusters'Cost of this lab: Billable — this exercises the whole platform. Expect an EKS control plane, nodes, a load balancer and a NAT Gateway to be running simultaneously: roughly $0.20–0.30/hour while the lab is up. Work through it in one sitting and destroy everything afterwards.