AWS Core Services and Architecture Questions

Amazon Web Services' core service catalog and how the pieces compose into a working system: EC2, Lambda, S3, VPC, IAM, RDS, and the managed-service ecosystem. Covers service selection within AWS, common reference architectures, the AWS Well-Architected Framework pillars, and operational patterns specific to the platform. For provider-agnostic compute or storage trade-offs, see the cross-cloud entries.

HardTechnical
41 practiced

You detect a suspicious IAM assume-role event, for example a role assumed from an unusual region or IP. Walk through how you'd detect this, contain it (revoke or limit the session, tighten the trust policy), and make sure the automation that does this can't itself be abused.

HardTechnical
43 practiced

How would you design preventive and detective controls to avoid accidental mass-deletion of S3 objects or buckets, and what's your recovery plan if a mass delete happens anyway?

HardTechnical
44 practiced

A DynamoDB table is write-throttling even though provisioned capacity looks sufficient. Walk through your investigation: partition-key analysis, hot-partition detection, adaptive capacity, and the mitigations you'd apply (including whether to switch to on-demand).

EasyTechnical
47 practiced

What are EC2 placement groups (cluster, spread, partition) and when would you use each? What are the trade-offs and limitations?

MediumTechnical
40 practiced

You notice increased end-to-end request latency for a microservice. Walk through the diagnostic steps using CloudWatch metrics, ALB metrics, X-Ray, and logs: which would you check first, and what patterns tell you infrastructure versus application problem?

Unlock Full Question Bank

Get access to all AWS Core Services and Architecture interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.