When Amazon Web Services misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- 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
Commands for diagnosis
aws sts get-caller-identity
aws s3 ls
aws eks update-kubeconfig --name prod --region eu-west-1Prevent the repeat
- 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
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.