Quick answer
Most AWS breaches come from misconfiguration, not flaws in AWS itself. Common weaknesses are over-permissive IAM roles and policies, leaked long-lived access keys, publicly exposed storage, unprotected instance metadata and missing logging.
On this page
How It Works
Under the shared responsibility model, AWS secures the cloud and customers secure what they build in it. Attackers look for access keys committed to code repositories, roles that allow privilege escalation, storage buckets readable by anyone, and applications vulnerable to SSRF that can reach instance metadata for credentials. Once inside, they move between accounts and services using IAM permissions.
Why It Matters
One leaked key or over-permissive role can expose entire environments, data stores and backups, and cloud attacks can be fast and fully automated.
How to Test for It
- Review IAM for wildcard permissions and privilege escalation paths.
- Search code and build systems for exposed access keys.
- Check storage, snapshots and databases for public access.
- Verify the hardened metadata service is required on compute instances.
- Confirm CloudTrail and alerting cover all regions and accounts.
How to Reduce the Risk
Use least-privilege IAM and short-lived credentials, block public access at the account level, require IMDSv2, enable CloudTrail and GuardDuty everywhere, separate workloads into accounts and test with authorised cloud penetration testing.
Regulatory and Framework Context
For Australian organisations, AWS hardening supports ASD cloud security guidance and Privacy Act obligations for data held in the cloud.
Latest intel on this topic
- Cloud keys leaked in Docker Hub images are stolen within secondsBleepingComputer · 17 November 2026
- SpyCloud’s 2027 Forecast: Attackers Will Exploit Trusted Access, From Hijacked Sessions to AI AgentsHackerNoon · 17 November 2026
- Apple reports outages affecting iCloud Mail, AppleCare and moreBleepingComputer · 17 November 2026
- Barracuda links cloud breach to ARTEX AI-powered cyberattackBleepingComputer · 16 November 2026
- TSMC employee data breach linked to cloud providerBleepingComputer · 15 November 2026
Updated hourly from the daily briefing.
Common questions
Do we need permission from AWS to pen test?
AWS allows customers to test many services without prior approval, within its published policy. Some activities remain prohibited.
What is the most common AWS misconfiguration?
Over-permissive identity and access management, followed by publicly exposed storage and leaked credentials.
For testers: finding write-ups
How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.
Change log
- 13 November 2026First published.