Last updated
Last updated
Many AWS resources can become public whether intentionally or not and these resources may contain sensitive data and/or credentials that may lead to a compromised environment
There are legitimate use cases for exposing resources publicly (such as providing customers with easy access) but due diligence should be performed to ensure sensitive data and credentials are not contained in these resources
Since all S3 buckets have a unique URL, they can automatically be discovered
works by brute-forcing bucket names and informing if the bucket is real or not based on HTTP status codes. If a bucket is discovered, it attempts to list its contents s3:ListBucket
EBS Snapshots are backups of EC2 instances
RDS Snapshots are backups of RDS Databases
SSM Documents allow for running commands and automation
These may contain sensitive information
is a useful tool for downloading snapshots for local inspection otherwise you can
Public resources like EBS and RDS snapshots or SSM Documents can lead to data and credential leaks.