/configure-s3
Create and configure an S3 bucket with security best practices.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/configure-s3
Context preview
What this command does when you run it.
Create and configure an S3 bucket with security best practices.
Command definition
configure-s3.md/configure-s3 - Configure AWS S3 Bucket
Create and configure an S3 bucket with security best practices.
Steps
1. Ask the user for the bucket purpose: static hosting, file storage, backups, logs 2. Generate a globally unique bucket name following naming conventions 3. Configure bucket policy based on access requirements (private, public-read, CDN-only) 4. Enable server-side encryption (AES-256 or KMS) by default 5. Block all public access unless explicitly required for static hosting 6. Configure CORS rules if the bucket serves content to web applications 7. Set up lifecycle rules: transition to Glacier after 90 days, expire after 365 days 8. Enable versioning for data protection and accidental deletion recovery 9. Configure access logging to a separate logging bucket 10. Set up event notifications for object creation or deletion if needed 11. Generate the IaC definition (CloudFormation or CDK) for the bucket 12. Document bucket configuration: name, region, access policy, encryption, lifecycle
Rules
- Always block public access unless the user explicitly requires public hosting
- Enable encryption at rest for all buckets
- Use bucket policies over ACLs (ACLs are legacy)
- Enable versioning for any bucket containing user data or important files
- Configure lifecycle rules to manage storage costs
- Set up access logging for compliance and audit requirements
- Use regional bucket names to avoid global namespace conflicts
Read more
/configure-s3 - Configure AWS S3 Bucket
Create and configure an S3 bucket with security best practices.
Steps
1. Ask the user for the bucket purpose: static hosting, file storage, backups, logs 2. Generate a globally unique bucket name following naming conventions 3. Configure bucket policy based on access requirements (private, public-read, CDN-only) 4. Enable server-side encryption (AES-256 or KMS) by default 5. Block all public access unless explicitly required for static hosting 6. Configure CORS rules if the bucket serves content to web applications 7. Set up lifecycle rules: transition to Glacier after 90 days, expire after 365 days 8. Enable versioning for data protection and accidental deletion recovery 9. Configure access logging to a separate logging bucket 10. Set up event notifications for object creation or deletion if needed 11. Generate the IaC definition (CloudFormation or CDK) for the bucket 12. Document bucket configuration: name, region, access policy, encryption, lifecycle
Rules
- Always block public access unless the user explicitly requires public hosting
- Enable encryption at rest for all buckets
- Use bucket policies over ACLs (ACLs are legacy)
- Enable versioning for any bucket containing user data or important files
- Configure lifecycle rules to manage storage costs
- Set up access logging for compliance and audit requirements
- Use regional bucket names to avoid global namespace conflicts
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

