| name | securing-s3-buckets |
| description | Create and secure S3 buckets following AWS best practices for access control, encryption, monitoring, and remediation of misconfigurations. Use when the user wants to secure a new bucket, audit an existing bucket, fix a security finding, configure encryption, or enable logging and monitoring. Do NOT use for general S3 data operations, S3 Tables setup, or discovering existing data assets.
|
| metadata | {"upstream":{"version":1},"category":"development","source":{"repository":"https://github.com/aws/agent-toolkit-for-aws","path":"skills/specialized-skills/storage-skills/securing-s3-buckets","license_path":"LICENSE","commit":"cbdc61a29707dc97989d5d11a2b53ad584781e78"}} |
Overview
Implements layered S3 security controls across five workflows: securing new buckets,
auditing existing configurations, remediating findings, configuring encryption, and
enabling monitoring. Follows AWS Well-Architected security best practices.
Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging, observability). Fall back to AWS CLI or shell otherwise.
Common Tasks
0. Verify Dependencies
Check for required tools before starting.
Constraints:
- You MUST inform the user if required tools are missing
- You SHOULD confirm credentials with
aws sts get-caller-identity
See references/iam-permissions.md for IAM permissions by workflow.
1. Classify the Request
| User intent | Workflow |
|---|
| Secure a new bucket | A: Secure New Bucket |
