Terminal
Terminal/Skill
Read-only review of S3 buckets across nine settings, including versioning, replication, encryption, public access and logging, with prioritized fixes.
By Amazon Web Services
Works with
npx skills add aws/tools-for-devops-agent --skill storage-s3-resiliency-expertisePerform a structured, read-only resiliency, security, and data protection review of Amazon S3 buckets. Automatically handles single-bucket and multi-bucket (fleet) reviews based on how many buckets are provided.
Activate this skill when the user asks to:
Do NOT activate for cost optimization, performance tuning, or EFS/FSx/AWS Backup/Storage Gateway.
references/data-collection.md — the read-only control-plane
API calls used to gather bucket configuration and the structured object they
produce. Data is acquired with the agent's native use_aws tool under the
assumed role in the target account. No credentials or profile are requested from
the user.references/finding-logic.md — all severity rules and body
templates.references/report-format.md — report structure, dimensions
table, pre-render validation.references/fleet-orchestration.md — batching, caching,
manifest, diffing (loaded only for multi-bucket reviews).references/s3-resiliency-best-practices.md — reasoning
behind thresholds, replication risk model, encryption tradeoffs, ownership
migration patterns, triage decision tree.my-production-bucketbucket-a, bucket-b, bucket-cStrip the bucket name from these patterns before collecting data:
s3://, s3a://, s3n:// — take the first path segment after the schemearn:aws:s3:::, arn:aws-cn:s3:::, arn:aws-us-gov:s3::: — take the segment after :::https://<bucket>.s3.amazonaws.com, https://<bucket>.s3.<region>.amazonaws.com — take the subdomainhttps://<bucket>.s3-website-<region>.amazonaws.com — take the subdomainhttps://s3.amazonaws.com/<bucket>, https://s3.<region>.amazonaws.com/<bucket> — take the first path segmentWhen a wrapper is extracted, surface it: "Reviewing bucket my-bucket (extracted from s3://my-bucket/path)."
/ with no recognized wrapper prefix → "The input looks like a bucket name with a path. Did you mean to review bucket <first-segment>?"Legacy buckets can have characters strict validation would reject. HeadBucket is the source of truth.
After parsing, route based on bucket count. The user never chooses. Routing is automatic and silent.
| Count | Path | Behavior |
|---|---|---|
| 1 | Single-bucket | Full report with all details |
| 2-10 | Fleet (single pass) | Summary matrix + full details for all |
| 11-20 | Fleet (single pass) | Summary matrix + details for Low-rated only |
| 21+ | Fleet (batched) | Batches of 10, manifest tracking, resume support |
references/data-collection.md.<name> does not exist or the role does not have access."status fields in the collected data.
AccessDenied → present permissions audit (see Pre-flight section)ToolingFailure → present tooling notice (see Pre-flight section)references/finding-logic.md.references/report-format.md.If any check returned AccessDenied, present:
⚠️ The role is missing read permissions for some configurations.
Check Status <check name>AccessDenied The minimum policy required includes the read actions for each check above.
How would you like to proceed?
- Stop here (recommended). Add the missing permissions and re-run.
- Continue with reduced accuracy. Report will note gaps; rating capped at Medium.
Wait for user response. Do NOT proceed by default.
If any check returned ToolingFailure, present:
⚠️ Tooling infrastructure failure — some checks could not reach the AWS API.
Check Status <check name>ToolingFailure How would you like to proceed?
- Stop here and retry later (recommended).
- Continue with partial data. Report will note gaps; rating capped at Medium.
Wait for user response. Do NOT proceed by default.
Load references/fleet-orchestration.md for full fleet behavior. Summary:
# S3 Fleet Resiliency Review — <N> Buckets
## Summary
- Buckets reviewed, accounts, date
- Resiliency distribution table (High/Medium/Low counts)
- Common gaps table (sorted by frequency)
## Dimensions Matrix
<all buckets, one row each, emoji per check>
## Bucket Details
<full single-bucket report for Low-rated buckets only (or all, for ≤10 buckets)>
## References
The complete S3 Resiliency Review report is the authoritative output of this skill.
After completing the review (single-bucket or fleet):
s3-resiliency-review-<bucket-name>-<YYYY-MM-DD>.md for a single bucket, or
s3-fleet-resiliency-review-<YYYY-MM-DD>.md for a fleet review. If the runtime
does not support persisted artifacts, skip artifact creation and rely on step 3.references/report-format.md (and references/fleet-orchestration.md for fleets).references/report-format.md. Never produce a
condensed, reframed, or "focused view" variant tailored to the question wording.GetObject). See the allowlist in references/data-collection.md.references/finding-logic.md and use the
body templates verbatim. Substitute only placeholder values.references/report-format.md before delivering the report.references/data-collection.md — Read-only control-plane API calls, error
classification, and the structured configuration object they produce.references/finding-logic.md — All finding rules, severity assignments, and body
templates for the 9 resiliency checks.references/report-format.md — Report structure, dimensions table, Resiliency
Rating criteria, pre-render validation, canonical AWS documentation URLs.references/fleet-orchestration.md — Fleet-specific: batching, caching, manifest,
diffing, summary matrix rendering. Load only for multi-bucket reviews.references/s3-resiliency-best-practices.md — Operational depth: reasoning behind
thresholds, replication risk model, encryption tradeoffs, ownership migration
patterns, triage decision tree.