← All insightsBest Practices

Amazon Web Services best practices for teams

Nir Geier, CodeWizard · 14 January 2026 · 3 min read · Intermediate

Amazon Web Services rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.

The 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

What good looks like

A least-privilege S3 read policy as Terraform.

hcl
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
}

Anti-patterns to retire

  • Long-lived access keys instead of SSO/OIDC roles
  • Over-broad IAM policies with wildcard actions and resources
  • Public S3 buckets and security groups open to 0.0.0.0/0

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.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult