Skip to content

Add storage-s3-resiliency-expertise skill for S3 resiliency reviews - #39

Open
howard-m-k wants to merge 2 commits into
aws-samples:mainfrom
howard-m-k:feature/storage-s3-resiliency-expertise
Open

Add storage-s3-resiliency-expertise skill for S3 resiliency reviews#39
howard-m-k wants to merge 2 commits into
aws-samples:mainfrom
howard-m-k:feature/storage-s3-resiliency-expertise

Conversation

@howard-m-k

Copy link
Copy Markdown

Add storage-s3-resiliency-expertise skill

Adds a read-only S3 resiliency, security, and data-protection review skill. Given one or more bucket names, it evaluates nine dimensions — versioning, replication, object lock, bucket policy, block public access, default encryption, ownership controls, server access logging, and static website hosting — using control-plane read APIs, then produces a rated report with prioritized findings and remediation guidance. Single-bucket and multi-bucket (fleet) reviews are routed automatically by input count.

Testing

Validated in AWS DevOps Agent (Investigation + on-demand) across single-bucket, multi-bucket fleet, S3 URI/ARN wrapper inputs, and negative-control prompts. The skill activates consistently from natural-language prompts and delivers the full report via a Final Delivery Contract.

Safety

Read-only — no write/delete/create operations and never reads object data (GetObject). Non-production disclaimer included in the README.

Structure

SKILL.md + references/ + evals/ + README.md + CHANGELOG.md, per the Agent Skills specification. Frontmatter includes name, description, metadata.version, and metadata.author.

…Agent sections to README

Aligns the README with sibling skills (wiz-security-context, msk-operations)
by adding a dedicated Agent Types section (Chat tasks, Evaluation, Incident RCA)
and an Uploading to AWS DevOps Agent section covering GitHub import, zip upload,
and Asset API deployment paths.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant