Why this topic matters in interviews
AWS DevOps interviews test whether you can build and operate secure, automated and highly available cloud platforms. Answers should include architecture, security, observability and failure handling.
15 interview questions to prepare
Use least privilege, roles, policies, permission boundaries, MFA, access reviews and avoid long-lived access keys.
A VPC is an isolated network boundary with subnets, route tables, gateways, security groups and network ACLs.
Security groups are stateful instance/ENI-level firewalls; NACLs are stateless subnet-level controls.
Use multiple AZs, load balancers, autoscaling, managed databases, backups and health checks.
Auto Scaling adjusts capacity based on policies, schedules or metrics to maintain availability and cost efficiency.
Check target health, backend port, security groups, app logs, timeouts, TLS and health check path.
Block public access, bucket policies, encryption, IAM restrictions, versioning, lifecycle and logging.
Use CloudWatch metrics/logs/alarms, X-Ray, CloudTrail, dashboards and service-specific metrics.
Use IAM/authentication, kubeconfig, manifests/Helm/GitOps, ingress/load balancer and observability.
Check instance state, security group, NACL, route table, public/private IP, key, OS firewall and SSH service.
CloudTrail records AWS API activity for audit, security investigation and change tracking.
Use remote state, locked backend, modules, provider versions, plan review and CI/CD approvals.
Define RPO/RTO, use snapshots, automated backups, cross-region/cross-account options and restore testing.
Right-size, autoscale, use Savings Plans/Reserved Instances, lifecycle policies, monitor unused resources and tag costs.
Combine security, automation, HA, observability, cost, compliance and incident response.