s3-lifecycle-automator
Designs and implements automated S3 lifecycle policy deployment across single and multi-account environments. Covers tag-based lifecycle policy deployment via CloudFormation StackSets and Lambda, bucket inventory collection for lifecycle audit, automated storage class transitions (Standard to IA to Glacier to Deep Archive) based on object age patterns, versioning lifecycle rules (NoncurrentVersionTransition and NoncurrentVersionExpiration), Intelligent-Tiering opt-in automation, Storage Lens analysis for identifying buckets without lifecycle policies, S3 Batch Operations for retroactive storage-class tiering of existing objects, lifecycle policy validation enforcing minimum-days rules per tier (30 days for IA, 90 days for Glacier Instant Retrieval), multi- account lifecycle enforcement via StackSets, and EventBridge notifications on lifecycle policy changes. Emits AUTOMATION_DEPLOYED with a fully validated lifecycle configuration or REVIEW_REQUIRED with the specific validation gap. Use when building S3...
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-24
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- s3-lifecycle-automator
- license
- Apache-2.0
- metadata
- { "tags": "aws-s3, s3-lifecycle, storage-tiering, intelligent-tiering, storage-lens, batch-operations, automate", "phase": "4", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "Storage", "version": "0.1.0", "keywords": "S3 lifecycle, lifecycle policy, storage class transition, Standard to IA, Glacier, Deep Archive, Intelligent-Tiering, NoncurrentVersionTransition, NoncurrentVersionExpiration, S3 Batch Operations, Storage Lens, CloudFormation StackSets, lifecycle validation, min-days rules, multi-account lifecycle, tag-based lifecycle", "task_type": "automate", "complexity": "high", "entry_point": "false", "skill_class": "capability", "when_to_use": "Building S3 lifecycle automation, deploying tiering policies (Standard to IA to Glacier to Deep Archive), setting up versioning lifecycle rules (NoncurrentVersionTransition, NoncurrentVersionExpiration), enabling Intelligent-Tiering at scale, remediating Storage Lens gaps, running S3 Batch Operations for retroactive tiering, validating lifecycle min-days rules, or deploying multi-account lifecycle via StackSets.", "requires_llm": "true", "verdict_shape": "AUTOMATION_DEPLOYED | REVIEW_REQUIRED", "lifecycle_status": "active", "invocation_schema": "Input: either (a) an S3 lifecycle requirement (\"transition objects to IA after 30 days, Glacier after 90 days\", \"expire non-current versions after 60 days\"), OR (b) a Storage Lens report identifying buckets without lifecycle policies. Output: deterministic LIFECYCLE block per bucket — POLICY/TRANSITIONS/VERSIONING/VALIDATION/ENFORCEMENT/ VERDICT — where VERDICT is AUTOMATION_DEPLOYED (policy validated and ready) or REVIEW_REQUIRED (specific gap cited).", "supports_pipeline": "true", "activation_triggers": "automate S3 lifecycle policy, deploy lifecycle StackSets, put-bucket-lifecycle-configuration, Standard to IA to Glacier transition, NoncurrentVersionTransition, Intelligent-Tiering opt-in, S3 Batch Operations tiering, Storage Lens lifecycle gap, lifecycle min-days validation, multi-account lifecycle enforcement" }
- description
- Designs and implements automated S3 lifecycle policy deployment across single and multi-account environments. Covers tag-based lifecycle policy deployment via CloudFormation StackSets and Lambda, bucket inventory collection for lifecycle audit, automated storage class transitions (Standard to IA to Glacier to Deep Archive) based on object age patterns, versioning lifecycle rules (NoncurrentVersionTransition and NoncurrentVersionExpiration), Intelligent-Tiering opt-in automation, Storage Lens analysis for identifying buckets without lifecycle policies, S3 Batch Operations for retroactive storage-class tiering of existing objects, lifecycle policy validation enforcing minimum-days rules per tier (30 days for IA, 90 days for Glacier Instant Retrieval), multi- account lifecycle enforcement via StackSets, and EventBridge notifications on lifecycle policy changes. Emits AUTOMATION_DEPLOYED with a fully validated lifecycle configuration or REVIEW_REQUIRED with the specific validation gap. Use when building S3...
- compatibility
- Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline workflow design. Live deployment uses aws s3api put-bucket-lifecycle-configuration, get-bucket-lifecycle- configuration, put-bucket-intelligent-tiering-configuration, aws s3control create-job, get-storage-lens-configuration, and aws cloudformation create-stack-set, create-stack-instances — AWS CLI v2, SSO or key-based credentials.
02 资源文件 19
- 参考文档eval/test-cases.yaml6.0 KB
- 参考文档evals/baselines/intelligent-tiering-optin.md688 B
- 参考文档evals/baselines/min-days-validation-fail.md715 B
- 参考文档evals/baselines/standard-tier-transition.md879 B
- 参考文档evals/baselines/storage-lens-gap.md772 B
- 参考文档evals/baselines/versioning-lifecycle.md817 B
- 参考文档evals/eval_config.yaml1.7 KB
- 参考文档evals/evals.json4.1 KB
- 参考文档evals/prompts/intelligent-tiering-optin.md674 B
- 参考文档evals/prompts/min-days-validation-fail.md568 B
- 参考文档evals/prompts/standard-tier-transition.md661 B
- 参考文档evals/prompts/storage-lens-gap.md741 B
- 参考文档evals/prompts/versioning-lifecycle.md650 B
- 参考文档examples/end-to-end.md6.7 KB
- 参考文档references/advanced-patterns.md6.8 KB
- 参考文档references/storage-class-transition-rules.md6.5 KB
- 参考文档references/storage-lens-and-batch-operations.md8.2 KB
- 参考文档references/worked-examples.md1.0 KB
- 参考文档skill.usf.yaml4.5 KB
03 SKILL.md 正文
S3 Lifecycle Automator
Mindset
One-line takeaway: S3 lifecycle automation is a four-stage pipeline — inventory (identify buckets and object-age patterns) → design (lifecycle rules with correct transition days per tier) → validate (enforce min-days: 30 for IA, 90 for Glacier IR) → deploy (put-bucket-lifecycle-configuration or StackSets). A gap in ANY stage produces silent cost leakage.
- Design without validation is fragile: S3 silently rejects rules that violate min-days constraints. A rule transitioning to IA at 15 days is accepted by the API but never executes.
- Lifecycle min-days per tier is enforced. Standard to Standard-IA requires 30 days. Standard-IA to Glacier Instant Retrieval requires 90 days total object age. These are hard constraints.
- Versioning lifecycle is SEPARATE from current-version rules.
NoncurrentVersionTransitionandNoncurrentVersionExpirationoperate on non-current versions only. A policy that only transitions current versions leaves all deleted-object versions in Standard forever.
Quick navigation
| You want to... | Go to |
|---|---|
| Design Standard→IA→Glacier→DeepArchive policy | Step 2 + Appendix A |
| Validate min-days rules | Step 3 + Step 9 |
| Add versioning lifecycle rules | Step 4 |
| Enable Intelligent-Tiering | Step 5 |
| Deploy via StackSets (multi-account) | Step 6 |
| Find buckets without lifecycle via Storage Lens | Step 7 |
| Retroactive tiering via Batch Operations | Step 8 |
| Add EventBridge notifications on changes | Step 10 |
| Avoid common pitfall patterns | Anti-Patterns |
Critical rules at a glance (do NOT bury these)
-
Lifecycle min-days per tier is a HARD constraint. Minimum for Standard-IA is 30 days. For Glacier Instant Retrieval, 90 days total object age. For Deep Archive, 180 days total. A rule with
Days: 15for IA is silently accepted but NEVER executes. -
Versioning lifecycle rules are SEPARATE from current-version rules.
NoncurrentVersionTransitionandNoncurrentVersionExpirationoperate exclusively on non-current versions. Without them, non-current versions accumulate in Standard indefinitely. -
put-bucket-lifecycle-configurationREPLACES the entire policy. No append mode. Alwaysget-bucket-lifecycle-configurationfirst, merge, then PUT. -
Intelligent-Tiering has no transition-day minimums. Auto-moves objects between access tiers based on access patterns. Key advantage for buckets with unpredictable access.
-
Storage Lens identifies buckets without lifecycle policies at scale. The
LifecycleEnabledmetric shows which buckets lack configuration. Use as the inventory input for multi-bucket deployment.
Pre-flight: data requirements
| Input | Source | Why |
|---|---|---|
| Bucket name(s) | aws s3api list-buckets |
Target for lifecycle |
| Current lifecycle | aws s3api get-bucket-lifecycle-configuration |
Don't overwrite blindly |
| Versioning status | aws s3api get-bucket-versioning |
Determines NoncurrentVersion rules |
| Object age distribution | Storage Lens or S3 Inventory | Drives transition day selection |
| Storage Lens report | aws s3control get-storage-lens-configuration |
Identifies gaps |
| Account list (multi-account) | aws organizations list-accounts |
For StackSets |
| StackSet status | aws cloudformation list-stack-instances |
Verify rollout |
If the input is malformed, emit:
LIFECYCLE: <reference>
BUCKET: <bucket-name>
VERDICT: ERROR
REASON: Cannot design lifecycle policy — bucket name and transition schedule are required.
GAP: Re-supply bucket name, versioning status, and desired transition days per storage class.
Process — Lifecycle design (apply in order)
Step 0: Expert knowledge — non-obvious S3 lifecycle behaviors
→ Moved to references/advanced-patterns.md — non-obvious lifecycle behaviors deep dive.
Step 1: Classify the lifecycle requirement
| Requirement | Pattern | Transition schedule |
|---|---|---|
| Log archival | Standard→IA→Glacier→DeepArchive | 30d→90d→180d→365d |
| Backup retention | Standard→IA→Glacier IR | 30d→90d |
| Temporary uploads | Standard→Expire | 30d expire |
| Versioned data | Current: Standard→IA; Noncurrent: IA→Expire | 30d current, 60d noncurrent |
| Unknown access pattern | Intelligent-Tiering opt-in | Auto-tiering |
| Compliance archive | Standard→DeepArchive | 180d |
If the access pattern is unknown, default to Intelligent-Tiering.
Step 2: Design the lifecycle policy
aws s3api put-bucket-lifecycle-configuration \
--bucket my-logs-bucket \
--lifecycle-configuration '{
"Rules": [
{
"ID": "log-archival-policy",
"Status": "Enabled",
"Filter": {"Prefix": "logs/"},
"Transitions": [
{"Days": 30, "StorageClass": "STANDARD_IA"},
{"Days": 90, "StorageClass": "GLACIER_IR"},
{"Days": 180, "StorageClass": "GLACIER"},
{"Days": 365, "StorageClass": "DEEP_ARCHIVE"}
]
}
]
}'
Tag-based lifecycle rule:
aws s3api put-bucket-lifecycle-configuration \
--bucket my-data-bucket \
--lifecycle-configuration '{
"Rules": [{
"ID": "archive-tagged-objects",
"Status": "Enabled",
"Filter": {"Tag": {"Key": "ArchiveClass", "Value": "glacier"}},
"Transitions": [{"Days": 1, "StorageClass": "GLACIER"}]
}]
}'
Step 3: Validate min-days rules
Before deploying, validate every transition against enforced minimums:
| From | To | Min days (total object age) | Notes |
|---|---|---|---|
| STANDARD | STANDARD_IA | 30 | Hard minimum |
| STANDARD_IA | GLACIER_IR | 90 | Must be >= 90 total |
| STANDARD_IA | GLACIER | 91 (1 day after IA) | 30 (IA) + 61 |
| STANDARD | GLACIER (direct) | 1 | Can skip IA |
| Any | DEEP_ARCHIVE | 180 | Hard minimum |
| STANDARD | ONEZONE_IA | 30 | Same as STANDARD_IA |
| STANDARD | INTELLIGENT_TIERING | 0 | No minimum |
If ANY transition violates the minimum, emit:
LIFECYCLE: <reference>
BUCKET: <bucket-name>
RULE: <rule-id>
TRANSITION: STANDARD → STANDARD_IA
CONFIGURED_DAYS: 15
MINIMUM_DAYS: 30
VERDICT: REVIEW_REQUIRED
GAP: Transition to STANDARD_IA requires minimum 30 days. Configured 15 days will be silently accepted but NEVER execute.
Step 4: Add versioning lifecycle rules
aws s3api put-bucket-lifecycle-configuration \
--bucket my-versioned-bucket \
--lifecycle-configuration '{
"Rules": [
{
"ID": "versioned-lifecycle-policy",
"Status": "Enabled",
"Filter": {},
"Transitions": [
{"Days": 30, "StorageClass": "STANDARD_IA"},
{"Days": 90, "StorageClass": "GLACIER_IR"}
],
"NoncurrentVersionTransitions": [
{"NoncurrentDays": 30, "StorageClass": "STANDARD_IA"},
{"NoncurrentDays": 90, "StorageClass": "GLACIER"}
],
"NoncurrentVersionExpiration": {"NoncurrentDays": 120},
"AbortIncompleteMultipartUpload": {"DaysAfterInitiation": 7},
"ExpiredObjectDeleteMarker": true
}
]
}'
| Field | What it does |
|---|---|
NoncurrentVersionTransitions |
Transition non-current versions to cheaper storage |
NoncurrentVersionExpiration |
Permanently delete non-current versions after N days |
AbortIncompleteMultipartUpload |
Abort uploads incomplete within N days |
ExpiredObjectDeleteMarker |
Remove delete marker when it's the only version |
Step 5: Enable Intelligent-Tiering
# Opt-in via lifecycle rule (Days: 0 = immediate transition to IT)
aws s3api put-bucket-lifecycle-configuration \
--bucket my-data-bucket \
--lifecycle-configuration '{
"Rules": [{
"ID": "intelligent-tiering-all-objects",
"Status": "Enabled",
"Filter": {},
"Transitions": [{"Days": 0, "StorageClass": "INTELLIGENT_TIERING"}]
}]
}'
# Configure archive tiers (optional)
aws s3api put-bucket-intelligent-tiering-configuration \
--bucket my-data-bucket \
--id ArchiveConfig \
--intelligent-tiering-configuration '{
"Id": "ArchiveConfig",
"Status": "Enabled",
"Tierings": [
{"AccessTier": "ARCHIVE_ACCESS", "Days": 90},
{"AccessTier": "DEEP_ARCHIVE_ACCESS", "Days": 180}
]
}'
| IT tier | Auto-transition trigger | Retrieval |
|---|---|---|
| Frequent Access | Accessed within 30 days | Milliseconds |
| Infrequent Access | Not accessed 31+ days | Milliseconds |
| Archive Instant | Not accessed 90+ days | Milliseconds |
| Archive | Configurable (default 90) | Minutes to hours |
| Deep Archive | Configurable (default 180) | Up to 12 hours |
Step 6: Multi-account deployment via StackSets
→ Advanced pattern moved to references/advanced-patterns.md — multi-account StackSets deployment.
Step 7: Identify lifecycle gaps via Storage Lens
→ Moved to references/storage-lens-and-batch-operations.md.
Step 8: Retroactive tiering via S3 Batch Operations
→ Moved to references/storage-lens-and-batch-operations.md.
Step 9: Pre-deployment validation function
MIN_DAYS = {
('STANDARD', 'STANDARD_IA'): 30,
('STANDARD', 'ONEZONE_IA'): 30,
('STANDARD_IA', 'GLACIER_IR'): 90,
('STANDARD_IA', 'GLACIER'): 91,
('STANDARD', 'GLACIER'): 1,
('STANDARD', 'GLACIER_IR'): 90,
('GLACIER', 'DEEP_ARCHIVE'): 180,
('STANDARD', 'DEEP_ARCHIVE'): 180,
}
def validate_lifecycle(config):
errors = []
for rule in config.get('Rules', []):
if rule.get('Status') != 'Enabled':
continue
prev_class = 'STANDARD'
for t in rule.get('Transitions', []):
key = (prev_class, t['StorageClass'])
min_required = MIN_DAYS.get(key, 0)
if t['Days'] < min_required:
errors.append(f"Rule '{rule['ID']}': {prev_class}->{t['StorageClass']} "
f"configured {t['Days']} days, minimum is {min_required}.")
prev_class = t['StorageClass']
return errors
Step 10: EventBridge notifications on lifecycle changes
aws events put-rule \
--name s3-lifecycle-change \
--event-pattern '{
"source": ["aws.s3"],
"detail-type": ["AWS API Call via CloudTrail"],
"detail": {
"eventName": ["PutBucketLifecycleConfiguration", "DeleteBucketLifecycle"],
"eventSource": ["s3.amazonaws.com"]
}
}'
aws events put-targets \
--rule s3-lifecycle-change \
--targets '[{"Id":"lifecycle-monitor","Arn":"arn:aws:lambda:us-east-1:111111111111:function:s3-lifecycle-monitor"}]'
Output format
LIFECYCLE: <reference>
BUCKET: <bucket-name>
POLICY:
- Rule ID: <rule-id>
- Status: Enabled
- Filter: <prefix, tag, or all>
TRANSITIONS:
- Standard → Standard-IA: <days> days (min 30)
- Standard-IA → Glacier IR: <days> days (min 90)
VERSIONING:
- NoncurrentVersionTransition: <days> → <storage class>
- NoncurrentVersionExpiration: <days>
VALIDATION:
- Min-days check: PASS | FAIL
- Overlap check: PASS | FAIL
ENFORCEMENT:
- Deployment: direct-CLI | StackSet | Lambda-tag-based
- Accounts: <list or "single">
- EventBridge: <rule ARN or "NOT WIRED">
VERDICT: AUTOMATION_DEPLOYED | REVIEW_REQUIRED
GAP: <if REVIEW_REQUIRED, the specific missing piece>
TEMPLATE: <CLI snippet for the lifecycle configuration>
Worked example — AUTOMATION_DEPLOYED, log archival with versioning
LIFECYCLE: log-archival-baseline
BUCKET: app-access-logs
POLICY:
- Rule ID: log-archival-policy
- Status: Enabled
- Filter: Prefix "logs/"
TRANSITIONS:
- Standard → Standard-IA: 30 days (min 30) — PASS
- Standard-IA → Glacier IR: 90 days (min 90) — PASS
- Glacier IR → Deep Archive: 365 days (min 180) — PASS
VERSIONING:
- NoncurrentVersionTransition: 30 days → STANDARD_IA
- NoncurrentVersionExpiration: 120 days
- AbortIncompleteMultipartUpload: 7 days
VALIDATION:
- Min-days check: PASS
- Overlap check: PASS
ENFORCEMENT:
- Deployment: direct-CLI
- Accounts: single (111111111111)
VERDICT: AUTOMATION_DEPLOYED
GAP: None
TEMPLATE:
aws s3api put-bucket-lifecycle-configuration --bucket app-access-logs --lifecycle-configuration '{"Rules":[{"ID":"log-archival-policy","Status":"Enabled","Filter":{"Prefix":"logs/"},"Transitions":[{"Days":30,"StorageClass":"STANDARD_IA"},{"Days":90,"StorageClass":"GLACIER_IR"},{"Days":365,"StorageClass":"DEEP_ARCHIVE"}],"NoncurrentVersionTransitions":[{"NoncurrentDays":30,"StorageClass":"STANDARD_IA"}],"NoncurrentVersionExpiration":{"NoncurrentDays":120},"AbortIncompleteMultipartUpload":{"DaysAfterInitiation":7}}]}'
Worked example — REVIEW_REQUIRED, invalid min-days
→ Secondary example moved to references/worked-examples.md; the AUTOMATION_DEPLOYED example above is primary.
Anti-Patterns — NEVER do these things
-
NEVER deploy lifecycle rules with transition days below the enforced minimum without validation. The API accepts invalid rules silently. Objects remain in the original storage class and costs never decrease.
-
NEVER call
put-bucket-lifecycle-configurationwithout first callingget-bucket-lifecycle-configuration. PUT is a full replacement. A call with one new rule silently deletes all existing rules. -
NEVER omit NoncurrentVersionExpiration on versioned buckets. Without it, every deleted-object version accumulates in Standard indefinitely. This is the single most common cause of "S3 costs keep growing despite lifecycle policies."
-
NEVER confuse Glacier Instant Retrieval (millisecond latency, 90-day min) with Glacier Flexible Retrieval (minutes-hours latency, 1-day min after IA). Choosing wrong produces excessive retrieval costs or inaccessible data.
-
NEVER deploy lifecycle policies to production without testing on a non-production bucket first. A misconfigured expiration rule deletes objects permanently.
-
NEVER use overlapping lifecycle rules with conflicting transitions. Design rules with non-overlapping filters.
-
NEVER omit
AbortIncompleteMultipartUploadon buckets that receive multipart uploads. Orphaned parts are billed at Standard and are NOT visible in the standard object listing. -
NEVER deploy StackSets without verifying the administration role has
s3:PutBucketLifecycleConfigurationin each target account. -
NEVER assume Intelligent-Tiering is always cheaper. It charges a monitoring fee ($0.0025 per 1,000 objects). For small objects with predictable access, explicit transitions may be cheaper.
-
NEVER set
ExpiredObjectDeleteMarker: truewithout understanding the consequence. It removes the delete marker when it's the only version, making the object name available for reuse. -
NEVER forget to validate after deployment.
get-bucket-lifecycle- configurationshows the policy but does NOT confirm rules are executing. Monitor Storage LensStorageClassdistribution over time. -
NEVER use S3 Batch Operations without a test run on a small manifest first.
S3SetStorageClasschanges are irreversible. -
NEVER omit the Batch Operations report. Without
Report.Enabled: true, there is no audit trail of which objects were tiered.
Pre-flight safety checks (run before applying any lifecycle CLI)
-
MANDATORY CONFIRMATION GATE. Before any state-changing operation, emit:
CONFIRM: About to <action> for bucket <bucket>. Proceed? (yes/no) -
Back up current configuration before modifying:
aws s3api get-bucket-lifecycle-configuration --bucket <bucket> > /tmp/<bucket>-lifecycle-backup-$(date +%s).json -
Before deploying expiration rules, verify the filter prefix targets only intended objects. An empty prefix with
Expirationdeletes ALL. -
Before StackSets deployment, validate the template:
aws cloudformation validate-template --template-body file://lifecycle-stackset.yaml -
For Batch Operations, start with 10 objects. Verify storage class changes before running the full manifest.
Appendix A — Storage class reference
→ Storage class table moved to references/storage-class-transition-rules.md.
Appendix B — Decision tree
Is the access pattern predictable?
├─ Yes → Retrieval latency requirement?
│ ├─ Milliseconds → Standard → IA (30d) → Glacier IR (90d)
│ └─ Minutes/hours → Standard → IA (30d) → Glacier (91d) → Deep Archive (180d)
└─ No → Enable Intelligent-Tiering (auto-tiering, no day configs)
Versioning enabled?
├─ Yes → Add NoncurrentVersionTransition + Expiration + AbortMultipart
└─ No → Current-version transitions + Expiration only
Multi-account?
├─ Yes → Deploy via CloudFormation StackSets
└─ No → Direct CLI per bucket
Existing objects need immediate tiering?
├─ Yes → S3 Batch Operations (S3SetStorageClass)
└─ No → Lifecycle rules handle going forward
Recent AWS features (2024-2026)
→ Moved to references/advanced-patterns.md.
Expert heuristic: the silent lifecycle failure
→ Moved to references/advanced-patterns.md — the silent lifecycle failure.
References (load on demand)
- references/advanced-patterns.md — Step 0 expert knowledge, StackSets multi-account pattern, silent lifecycle failure, recent AWS features.
- references/worked-examples.md — secondary worked example (REVIEW_REQUIRED, invalid min-days).
- references/storage-class-transition-rules.md — pre-existing; extended with Appendix A storage class reference.
- references/storage-lens-and-batch-operations.md — pre-existing; extended with Steps 7-8 (Storage Lens gaps, Batch Operations tiering).
Domain
AWS CloudOps / Storage Automation — S3 Lifecycle and Intelligent-Tiering.
AWS documentation
- S3 Lifecycle Configuration — https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html
- S3 Intelligent-Tiering — https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html#sc-glacier-tiering
- S3 Batch Operations — https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-ops.html
- S3 Storage Lens — https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage_lens.html
- Lifecycle Transition Considerations — https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html
04 同仓库更多 Skills
xray-tracing-deployer
Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL / method / service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry / ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS / EKS / Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.
wellarchitected-workload-auditor
Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.
wellarchitected-review-operator
Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer / get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.
wafv2-web-acl-deployer
Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB/API Gateway/CloudFront, or configuring CAPTCHA/Challenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.
wafv2-web-acl-auditor
Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow/bypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.
waf-rule-deployer
Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.