Demos and production are different sports. This checklist covers what changes when Amazon Web Services has to be reliable, secure and observable under real load.
Security and reliability defaults
- Scan IaC (tfsec/Checkov) for open buckets and wide security groups
- Enforce MFA, rotate credentials, and enable org-wide guardrails (SCPs)
A production-minded config
A least-privilege S3 read policy as Terraform.
data "aws_iam_policy_document" "read_assets" {
statement {
actions = ["s3:GetObject"]
resources = ["arn:aws:s3:::acme-assets/*"]
}
}
resource "aws_iam_policy" "read_assets" {
name = "read-assets"
policy = data.aws_iam_policy_document.read_assets.json
}Operational best practices
- Use SSO for humans and OIDC roles for CI - no static keys
- Write least-privilege IAM and manage everything via IaC
- Turn on CloudTrail, GuardDuty and budget alerts
In production, boring and reproducible beats clever every time.
Want senior help putting Amazon Web Services to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.