CloudConsole

S3 bucket security audit: public access, versioning, encryption and logging

A tool in the CloudConsole app for iPhone and Android · read-only · free for one account

Short answer

A bucket is public when its policy or ACL grants public access and Block Public Access isn’t on, at the bucket or the account. CloudConsole’s S3 bucket audit reads every bucket in its own region and shows, for each, Block Public Access, whether the policy makes it public, versioning, default encryption, lifecycle rules and server access logging, with counts at the top, filters, and the S3 screen’s own fixes.

S3 bucket audit: one public bucket, one not blocked, three without versioning, and the account-level Block Public Access off
S3 bucket audit
The Tools list: Cost by resource, Waste finder, VPC IP usage, Find an IP, Open by ARN, Schedules, Service quotas and the S3 and IAM audits
Services → Tools

What it checks

Open Services → Tools → S3 bucket audit. First the account: whether account-level Block Public Access is on. Turning it on protects every bucket at once, so the audit says so plainly when it’s off. Then each bucket, read in its own region:

CheckWhat it shows
ExposurePublic (the bucket policy makes it public and nothing restricts it), Not blocked (no Block Public Access at bucket or account, so one policy or ACL change would make it public) or Blocked.
VersioningVersioned, versioning suspended, or never turned on. Without it, an overwrite or delete is permanent.
Default encryptionSSE-S3 or SSE-KMS. New objects have been encrypted with SSE-S3 by default since January 2023, so this mostly tells you whether a bucket uses your own KMS key.
Lifecycle rulesHow many. A bucket with none keeps every object, every old version and every incomplete multipart upload until someone deletes them.
Access loggingWhere server access logs go, or “No access logs”.

The counts at the top (public, not blocked, no versioning, and how many buckets lack lifecycle rules or logging) are also filters, so “show me only the exposed ones” is one tap. Each bucket opens on the S3 screen.

Two fixes are offered where they apply, and they are the S3 screen’s own actions: Block all public access on a bucket and Turn on versioning. Both are Pro changes with your confirmation. Before blocking, check the bucket isn’t meant to be public, such as a static website without CloudFront in front of it.

What it doesn’t do: read objects, evaluate object ACLs one by one, or judge whether a policy is too broad for principals inside AWS. For those, use IAM Access Analyzer and the bucket policy itself.

How it works, and what it can read

Buckets are read six at a time, each in its own region; a bucket that can’t be read is listed with the reason, and the rest still show.

What it readsIAM actions
Buckets and their regionss3:ListAllMyBuckets, s3:GetBucketLocation
Public accesss3:GetBucketPublicAccessBlock, s3:GetBucketPolicyStatus, s3:GetAccountPublicAccessBlock
Configurations3:GetBucketVersioning, s3:GetEncryptionConfiguration, s3:GetLifecycleConfiguration, s3:GetBucketLogging
Fixes (Pro, changes)s3:PutBucketPublicAccessBlock, s3:PutBucketVersioning

ViewOnlyAccess leaves out most bucket settings; ReadOnlyAccess has them all.

All of these reads are in the AWS managed ReadOnlyAccess policy. ViewOnlyAccess leaves some out; Recommended permissions lists the extras. If one call is denied, the rest of the tool still works and says which permission is missing.

Nothing leaves your phone. The app signs each request with your own credentials, which stay in the iOS Keychain or Android Keystore, and sends it straight to AWS. There is no CloudConcur server in between, so we never see your resources or the results.

Free to look, Pro to fix. Every check only reads, so it works on the free plan (one account) and in the built-in demo. Where the tool offers a fix, it is the app’s usual action: it needs Pro, goes through the confirmation you set for that account and is recorded in the activity log on your phone.

Do it without the app

Check the account setting, then loop over buckets. Whether a policy makes a bucket public:

aws s3control get-public-access-block --account-id 111122223333

for b in $(aws s3api list-buckets --query 'Buckets[].Name' --output text); do
  echo "$b $(aws s3api get-bucket-policy-status --bucket "$b" --query PolicyStatus.IsPublic --output text 2>/dev/null)"
done

The rest of the audit, per bucket (each returns an error when the setting doesn’t exist, which is itself the finding):

aws s3api get-public-access-block --bucket amzn-s3-demo-bucket
aws s3api get-bucket-versioning --bucket amzn-s3-demo-bucket
aws s3api get-bucket-encryption --bucket amzn-s3-demo-bucket
aws s3api get-bucket-lifecycle-configuration --bucket amzn-s3-demo-bucket
aws s3api get-bucket-logging --bucket amzn-s3-demo-bucket

Buckets in other regions may need --region. For an organization-wide, continuous view, AWS Security Hub and AWS Config have managed checks for public buckets and versioning; IAM Access Analyzer reports buckets shared outside your account.

Related free tool on this site:

Questions

What is the difference between “public” and “not blocked”?

Public means the bucket policy grants public access right now. Not blocked means it doesn’t, but Block Public Access is off at both bucket and account level, so nothing would stop a future policy or ACL from making it public.

Should every bucket have versioning?

Buckets holding data you can’t recreate, yes. Versioning keeps every overwritten and deleted object, so pair it with a lifecycle rule that expires noncurrent versions or the bucket grows forever.

Does it read my objects?

No. It reads bucket settings only. Object contents and object ACLs are never read.

Try it on your own account

CloudConsole is on the App Store for iPhone and Google Play for Android. Every tool also works in the built-in demo, if you’d rather look around before connecting an account.

Details: Tools for your AWS account in the help centre.