跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

storage-s3-resiliency-expertise

S3 resiliency, security, and data protection review. Assesses one or many S3 buckets across nine dimensions — versioning, replication, object lock, encryption, block public access, bucket policy, ownership controls, server access logging, and static website hosting — using read-only control-plane API calls, then produces a rated report with prioritized findings and remediation guidance. Single-bucket and multi-bucket (fleet) reviews are routed automatically by input count. Use when a user asks to review, audit, or assess an S3 bucket's resiliency, security, data protection, recovery posture, disaster recovery readiness, or audit posture, or asks about any of those nine features. Triggers on phrasings like "S3 resiliency review", "is my bucket safe", "audit S3 bucket security", "review these buckets: A, B, C", or "check versioning/replication/encryption/public access". Do NOT use for cost optimization, performance tuning, or EFS, FSx, AWS Backup, or Storage Gateway.

hokang · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aws/tools-for-devops-agent --skill storage-s3-resiliency-expertise

技能说明


name: storage-s3-resiliency-expertise description: > S3 resiliency, security, and data protection review. Assesses one or many S3 buckets across nine dimensions — versioning, replication, object lock, encryption, block public access, bucket policy, ownership controls, server access logging, and static website hosting — using read-only control-plane API calls, then produces a rated report with prioritized findings and remediation guidance. Single-bucket and multi-bucket (fleet) reviews are routed automatically by input count.

Use when a user asks to review, audit, or assess an S3 bucket's resiliency, security, data protection, recovery posture, disaster recovery readiness, or audit posture, or asks about any of those nine features. Triggers on phrasings like "S3 resiliency review", "is my bucket safe", "audit S3 bucket security", "review these buckets: A, B, C", or "check versioning/replication/encryption/public access".

Do NOT use for cost optimization, performance tuning, or EFS, FSx, AWS Backup, or Storage Gateway. metadata: author: hokang version: "1.0.1" aws-devops-agent-skills.agent-types: "Chat tasks, Evaluation, Incident RCA" aws-devops-agent-skills.aws-services: "Amazon S3" aws-devops-agent-skills.technical-domains: "Storage"

S3 Resiliency Review

Perform 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.

When to Use

Activate this skill when the user asks to:

  • Review, audit, or assess an S3 bucket's resiliency, security, or data protection
  • Evaluate an S3 bucket's protection/recovery posture or disaster recovery readiness
  • Check any of: versioning, replication, object lock, encryption, block public access, bucket policy, ownership controls, server access logging, website hosting
  • Review a list of buckets ("review these buckets: A, B, C")

Do NOT activate for cost optimization, performance tuning, or EFS/FSx/AWS Backup/Storage Gateway.

Architecture

  • This skill (orchestrator/analyzer): input parsing, routing, finding logic application, report rendering.
  • Data collection: 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.
  • Finding logic: references/finding-logic.md — all severity rules and body templates.
  • Report format: references/report-format.md — report structure, dimensions table, pre-render validation.
  • Fleet orchestration: references/fleet-orchestration.md — batching, caching, manifest, diffing (loaded only for multi-bucket reviews).
  • Operational depth: references/s3-resiliency-best-practices.md — reasoning behind thresholds, replication risk model, encryption tradeoffs, ownership migration patterns, triage decision tree.

Input Parsing & Validation

Accepted input formats

  • Single bucket name: my-production-bucket
  • Comma-separated: bucket-a, bucket-b, bucket-c
  • Newline-separated (pasted list)
  • File reference: "review buckets in buckets.txt" (read file, one bucket per line)
  • S3 URI/ARN/URL wrappers (stripped automatically per rules below)

Wrapper recognition

Strip the bucket name from these patterns before collecting data:

  • s3://, s3a://, s3n:// — take the first path segment after the scheme
  • arn: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 subdomain
  • https://<bucket>.s3-website-<region>.amazonaws.com — take the subdomain
  • https://s3.amazonaws.com/<bucket>, https://s3.<region>.amazonaws.com/<bucket> — take the first path segment
  • Bare bucket name (no prefix) — use as-is

When a wrapper is extracted, surface it: "Reviewing bucket my-bucket (extracted from s3://my-bucket/path)."

Reject (abort without API call)

  • Empty string or whitespace only → "No bucket name was provided."
  • Single input contains / with no recognized wrapper prefix → "The input looks like a bucket name with a path. Did you mean to review bucket <first-segment>?"

Do NOT enforce S3 naming rules client-side

Legacy buckets can have characters strict validation would reject. HeadBucket is the source of truth.

Routing

After parsing, route based on bucket count. The user never chooses. Routing is automatic and silent.

CountPathBehavior
1Single-bucketFull report with all details
2-10Fleet (single pass)Summary matrix + full details for all
11-20Fleet (single pass)Summary matrix + details for Low-rated only
21+Fleet (batched)Batches of 10, manifest tracking, resume support

Single-Bucket Path

Execution flow

  1. Collect bucket configuration per references/data-collection.md.
  2. If region discovery fails (bucket does not exist or the role has no access) → abort: "Bucket <name> does not exist or the role does not have access."
  3. Evaluate pre-flight: check all status fields in the collected data.
    • If any AccessDenied → present permissions audit (see Pre-flight section)
    • If any ToolingFailure → present tooling notice (see Pre-flight section)
    • If no gaps → proceed
  4. Load references/finding-logic.md.
  5. Apply finding logic against the structured configuration data.
  6. Load references/report-format.md.
  7. Render the single-bucket report.
  8. Run the pre-render validation (13 checks).
  9. Deliver the report per the Final Delivery Contract below.

Pre-flight: Permissions audit

If any check returned AccessDenied, present:

⚠️ The role is missing read permissions for some configurations.

阅读完整来源 ↗