[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AC2NMXFX5J7R2QVSC4P3Q9":3,"skill-same:01M7AC2NMXFX5J7R2QVSC4P3Q9":151},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7AC2NMXFX5J7R2QVSC4P3Q9","s3-transfer-acceleration-operator",null,"Operates S3 Transfer Acceleration workflows — enable\u002Fdisable acceleration per bucket (put-bucket-accelerate-configuration), cost analysis by source region ($0.004-0.025\u002FGB depending on edge location), speed comparison tool (CloudFront edge vs direct S3 endpoint), multipart upload with acceleration endpoints (\u003Cbucket>.s3-accelerate.amazonaws.com), checksum verification (CRC32C, SHA-256) on accelerated uploads, S3 multipart copy between accelerated buckets, Direct Connect comparison, and diagnostic loops (get-bucket-accelerate-configuration, CloudWatch BytesUploaded). Runs deterministic pre-checks (bucket exists, not a directory bucket, caller has s3:PutAccelerateConfiguration, region supports acceleration, cost acknowledgment) behind a CONFIRM gate and emits a READY, BLOCKED, or COMPLETED verdict. Use when enabling\u002Fdisabling acceleration, comparing transfer speeds, planning multipart uploads over acceleration, or diagnosing slow transfers.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: s3-transfer-acceleration-operator\ndescription: Operates S3 Transfer Acceleration workflows — enable\u002Fdisable acceleration per bucket (put-bucket-accelerate-configuration), cost analysis by source region ($0.004-0.025\u002FGB depending on edge location), speed comparison tool (CloudFront edge vs direct S3 endpoint), multipart upload with acceleration endpoints (\u003Cbucket>.s3-accelerate.amazonaws.com), checksum verification (CRC32C, SHA-256) on accelerated uploads, S3 multipart copy between accelerated buckets, Direct Connect comparison, and diagnostic loops (get-bucket-accelerate-configuration, CloudWatch BytesUploaded). Runs deterministic pre-checks (bucket exists, not a directory bucket, caller has s3:PutAccelerateConfiguration, region supports acceleration, cost acknowledgment) behind a CONFIRM gate and emits a READY, BLOCKED, or COMPLETED verdict. Use when enabling\u002Fdisabling acceleration, comparing transfer speeds, planning multipart uploads over acceleration, or diagnosing slow transfers.\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline plan classification. Live-account operations use aws s3api put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, s3api create-multipart-upload \u002F upload-part \u002F complete-multipart-upload (with accelerate endpoint), aws s3 ls --endpoint-url, CloudWatch GetMetricStatistics (AWS CLI v2, SSO or key-based credentials).\nmetadata:\n  domain: aws-cloudops\n  complexity: medium\n  requires_llm: 'true'\n  phase: '4'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Storage\n  task_type: operate\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY | BLOCKED | COMPLETED\n  when_to_use: Enabling or disabling S3 Transfer Acceleration on a bucket, comparing transfer speed between accelerated and direct S3 endpoints, planning a multipart upload over the accelerate endpoint, verifying checksums on accelerated uploads, performing a multipart copy between accelerated buckets, comparing Transfer Acceleration vs Direct Connect for large data transfers, or diagnosing why accelerated transfers are slower than expected.\n  activation_triggers: enable S3 Transfer Acceleration, disable S3 Transfer Acceleration, accelerate endpoint, s3-accelerate.amazonaws.com, put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, S3 speed comparison, accelerated multipart upload, S3 checksum verification, CRC32C upload, S3 multipart copy accelerated, Transfer Acceleration cost, Direct Connect vs Transfer Acceleration, slow S3 transfer, S3 edge network upload\n  invocation_schema: 'Input: either (a) a bucket configuration (get-bucket-accelerate-configuration, get-bucket-location, head-bucket output) plus the intended operation (enable-acceleration, disable-acceleration, speed-comparison, plan-multipart-upload, compare-direct-connect, diagnose-transfer), OR (b) a bucket-name + operation for live- account execution. Output: deterministic OPERATION \u002F VERDICT \u002F PRE_CHECKS \u002F STEPS \u002F POST_VERIFY \u002F COST \u002F NOTES block per operation, where VERDICT is one of READY, BLOCKED, COMPLETED.'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: S3 Transfer Acceleration, accelerate endpoint, s3-accelerate.amazonaws.com, multipart upload, checksum verification, CRC32, CRC32C, SHA-256, Direct Connect, edge network, put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, BytesUploaded, speed comparison, cost per GB, multipart copy, bucket configuration\n  tags: aws, s3, storage, transfer-acceleration, upload, networking, operate\n---\n\n# S3 Transfer Acceleration Operator\n\n## What this skill does\n\nExecutes S3 Transfer Acceleration operations correctly and\ncost-effectively. Runs deterministic pre-checks before any\nstate-changing CLI (bucket exists, not a directory bucket, caller has\n`s3:PutAccelerateConfiguration`, region supports acceleration), then\nexecutes `put-bucket-accelerate-configuration` behind a CONFIRM gate,\nand verifies the result via `get-bucket-accelerate-configuration`.\nEvery enable-acceleration produces a cost analysis (source region to\nS3 region at $0.004-0.025\u002FGB), a speed comparison recommendation\n(accelerated endpoint vs direct endpoint), and a multipart upload plan\nwith checksum verification. Disabling acceleration includes\nverification that no in-flight multipart uploads depend on the\naccelerate endpoint.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **§ Quick reference** | Verdict thresholds (BLOCKED\u002FREADY\u002FCOMPLETED) + pre-check priority | Before any operation |\n| **§ Mindset** | Why acceleration routes through edge, the cost-by-region model, the Direct Connect crossover | Understanding the cost\u002Fspeed model |\n| **§ Pre-flight** | Bucket metadata gate — exists, not directory bucket, region, caller IAM | Before executing any CLI |\n| **§ Process** | Per-operation planning: enable, disable, speed-comparison, plan-multipart, compare-DC, diagnose | When choosing which operation to run |\n| **§ Output format** | STRICT output contract — OPERATION\u002FVERDICT\u002FPRE_CHECKS\u002FSTEPS\u002FPOST_VERIFY\u002FCOST template | Formatting the response |\n| **§ Anti-Patterns** | NEVER list — top mistakes that waste money or corrupt transfers | Review before risky operations |\n| **§ Pre-flight safety** | Capture pre-state, verify no in-flight uploads, cost capture | Defense-in-depth |\n\n## Quick reference — verdict thresholds\n\n| Verdict | Trigger condition | Action |\n|---|---|---|\n| `BLOCKED` | One or more pre-checks failed (bucket is a directory bucket, region does not support acceleration, caller lacks `s3:PutAccelerateConfiguration`, bucket does not exist, cost threshold exceeded without acknowledgment) | List failures, do NOT execute |\n| `READY` | All pre-checks passed; awaiting CONFIRM gate | Emit exact CLI sequence, wait for operator yes |\n| `COMPLETED` | Acceleration enable\u002Fdisable finished and post-verification passed (`get-bucket-accelerate-configuration` matches intent, accelerate endpoint reachable, CloudWatch metrics confirm traffic) | Emit verification results, cost summary, monitoring plan |\n\n**Priority order for pre-checks (apply in this sequence, all must pass\nfor READY):**\n\n1. **Bucket reachability** — bucket exists (`head-bucket` does not\n   return `404` or `403`).\n2. **Not a directory bucket** — S3 Express One Zone directory buckets\n   do NOT support Transfer Acceleration. Check bucket naming\n   (`\u003Cname>--xaz-\u003Caz-id>`) and `get-bucket-location`.\n3. **Region supports acceleration** — most AWS commercial regions\n   support Transfer Acceleration. AWS GovCloud, China, and some\n   opt-in regions may have limited support. Verify via\n   `get-bucket-accelerate-configuration` (returns\n   `Status: Suspended` if acceleration is not available in the\n   region).\n4. **Caller IAM permission** — the calling identity must have\n   `s3:PutAccelerateConfiguration` on the bucket for enable\u002Fdisable\n   operations, and `s3:GetAccelerateConfiguration` for verification.\n5. **Cost acknowledgment** — Transfer Acceleration charges\n   $0.004-0.025\u002FGB depending on the source edge location. Surface\n   the estimated cost based on the planned transfer volume.\n6. **No conflicting bucket policies** — bucket policies that deny\n   `s3:PutAccelerateConfiguration` or restrict endpoint access must\n   be resolved before enabling.\n7. **In-flight multipart upload check (disable only)** — before\n   disabling, verify no in-flight multipart uploads are using the\n   accelerate endpoint via `list-multipart-uploads`.\n\n**Cost\u002Ftime baselines (2026):**\n\n- Transfer Acceleration pricing by source edge location:\n  - Asia Pacific (excluding Australia): $0.025\u002FGB\n  - South America: $0.025\u002FGB\n  - Australia \u002F New Zealand: $0.025\u002FGB\n  - Europe: $0.004\u002FGB\n  - North America: $0.004\u002FGB (if source is in NA)\n  - Africa: $0.025\u002FGB\n  - Middle East: $0.025\u002FGB\n- Acceleration is billed on DATA IN (uploads to S3 via the\n  accelerate endpoint). Downloads via accelerate are also billed.\n- Direct S3 upload (no acceleration): free (standard S3 PUT request\n  costs only: $0.005 per 1,000 PUT requests).\n- Typical speed improvement: 2-10x for long-distance transfers\n  (Asia to US, South America to EU). Minimal or no improvement for\n  short-distance transfers (same continent).\n- Multipart upload overhead: each part is a separate PUT request.\n  10,000 parts at 8MB each = 10,000 PUT requests ($0.05 at\n  $0.005\u002F1,000 requests) + acceleration data-in fee.\n- Direct Connect: flat port hourly rate ($0.30\u002Fhour for 1 Gbps)\n  plus $0.02\u002FGB data transfer out. Economical for sustained\n  high-volume transfers (>50 TB\u002Fmonth from a fixed location).\n\n## Mindset\n\n**One-line takeaway:** Transfer Acceleration routes uploads through\nthe nearest CloudFront edge location over an optimized AWS backbone\npath — it excels for long-distance, high-latency transfers but costs\n$0.004-0.025\u002FGB and is pointless for same-region traffic. Driven by\nthree S3 realities:\n\n- **Acceleration is a routing optimization, not a bandwidth boost.**\n  S3 Transfer Acceleration uses the CloudFront edge network to find\n  the fastest path to the destination S3 bucket. The edge location\n  receives the upload, then forwards it to S3 over the AWS backbone\n  (optimized routing, larger TCP windows, fewer hops). For\n  long-distance transfers (Asia to US, South America to EU), this\n  can reduce transfer time by 2-10x. For same-region transfers\n  (EU to EU, US to US), the improvement is negligible — and you pay\n  the $\u002FGB acceleration fee for nothing.\n\n- **Cost scales with data volume, not speed.** You pay per GB\n  transferred through the accelerate endpoint. A 1 TB upload from\n  Asia to a US bucket costs $25.00 ($0.025\u002FGB x 1,024 GB). A 100 TB\n  migration costs $2,500. Always run the speed comparison tool first\n  to confirm acceleration provides a meaningful speedup before\n  committing to the cost. For sustained high-volume transfers from a\n  fixed location, Direct Connect is usually cheaper.\n\n- **Multipart upload is the performance multiplier.** Acceleration\n  reduces per-connection latency. Multipart upload increases\n  throughput by parallelizing across multiple connections. Together,\n  they maximize transfer speed: each part is uploaded over an\n  accelerated connection, and multiple parts run in parallel. Always\n  use multipart upload for files > 100 MB when acceleration is\n  enabled. The accelerate endpoint\n  (`\u003Cbucket>.s3-accelerate.amazonaws.com`) accepts standard multipart\n  upload API calls.\n\n## Pre-flight: bucket metadata gate\n\nRun before classification. Misclassifying these produces wrong plans.\n\n**Pagination:** `list-multipart-uploads` paginates at 1,000\u002Fpage —\ndrain `--page-size` \u002F `--starting-token` to completion.\n\n**Live-account pre-flight (skip if offline plan audit):**\n1. `aws s3api head-bucket --bucket \u003Cname>` — confirm bucket exists\n   and is accessible (200 OK).\n2. `aws s3api get-bucket-location --bucket \u003Cname>` — capture the\n   bucket region. Verify it is a supported commercial region.\n3. `aws s3api get-bucket-accelerate-configuration --bucket \u003Cname>`\n   — capture `Status` (`Enabled`, `Suspended`, or null).\n4. `aws s3api get-bucket-logging --bucket \u003Cname>` — verify logging\n   is configured for audit trail (advisory).\n5. `aws s3api list-multipart-uploads --bucket \u003Cname>` — capture\n   in-flight multipart uploads (critical for disable-acceleration).\n6. `aws cloudwatch get-metric-statistics --namespace AWS\u002FS3\n   --metric-name BytesUploaded --dimensions Name=BucketName,\n   Value=\u003Cname> --start-time \u003C24h-ago> --end-time \u003Cnow>\n   --period 3600 --statistics Sum` — capture recent upload volume\n   for cost estimation.\n\n**Malformed input:** if the input is invalid or missing required\nfields, emit `VERDICT: ERROR` with `REASON: Bucket configuration\nis not valid or is missing required fields — cannot plan.` and\n`REMEDIATION: Re-fetch with aws s3api head-bucket --bucket \u003Cname>\n--output json and re-plan.`\n\n| Bucket attribute | Effect on operation |\n|---|---|\n| Directory bucket (`--xaz-` suffix) | BLOCKED — S3 Express One Zone does not support Transfer Acceleration. |\n| Bucket in GovCloud \u002F China region | BLOCKED — Transfer Acceleration not available in isolated regions. |\n| `Status: Enabled` | Already accelerated. For enable: no-op or advisory. For disable: plan the disable. |\n| `Status: Suspended` | Acceleration was enabled then suspended. Re-enable to resume. |\n| In-flight multipart uploads (disable only) | BLOCKED — disabling acceleration while multipart uploads are in-flight via the accelerate endpoint will cause upload failures. |\n| Bucket policy denies `s3:PutAccelerateConfiguration` | BLOCKED — update the bucket policy first. |\n| Virtual-hosted-style incompatible | Advisory — the accelerate endpoint uses `\u003Cbucket>.s3-accelerate.amazonaws.com`. Ensure the client supports virtual-hosted-style addressing. |\n| Bucket name with underscores | BLOCKED — underscores are not DNS-compatible; the accelerate endpoint requires DNS-compatible bucket names. |\n\n## Process — operation planning (apply in order)\n\n### Step 0: Expert heuristic — non-obvious S3 acceleration behaviors\n\nNon-obvious acceleration behaviors — accelerate endpoint DNS vs standard endpoint, directory buckets, per-GB (not per-request) pricing, non-destructive speed test, checksum end-to-end protection, mid-upload disable failures, Direct Connect crossover, dual-stack IPv6, Object Lambda, KMS — live in [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad that reference before planning enable\u002Fdisable, speed-comparison, or diagnose operations.\n\n### Step 1: Pre-check gate — BLOCKED if any check fails\n\nRun ALL pre-checks for the chosen operation. If ANY fails, the verdict\nis BLOCKED with the failed checks in PRE_CHECKS. Do NOT execute.\n\n**For ALL operations:**\n1. Bucket exists (`head-bucket` returns 200).\n2. Bucket is accessible (caller has `s3:GetAccelerateConfiguration`).\n\n**For enable-acceleration:**\n3. Bucket is NOT a directory bucket (no `--xaz-` suffix, not S3\n   Express One Zone).\n4. Bucket region supports acceleration (commercial region, not\n   GovCloud or China).\n5. Calling identity has `s3:PutAccelerateConfiguration` on the bucket.\n6. Bucket name is DNS-compatible (lowercase letters, numbers, hyphens;\n   no underscores, no uppercase).\n7. (Advisory) Cost acknowledgment: surface estimated $\u002FGB based on\n   source region.\n\n**For disable-acceleration:**\n3. No in-flight multipart uploads using the accelerate endpoint\n   (`list-multipart-uploads` returns empty, or all uploads use the\n   standard endpoint).\n4. Calling identity has `s3:PutAccelerateConfiguration`.\n5. (Advisory) Confirm no SDK clients are configured with\n   `use_accelerate_endpoint: true` — they will fail after disable.\n\n**For speed-comparison (read-only, non-destructive):**\n3. Acceleration is enabled OR the operator plans to test before\n   enabling. The speed comparison tool works on buckets with\n   acceleration enabled.\n4. Test files are small (\u003C 1 MB) and do not affect production data.\n\n**For plan-multipart-upload (read-only planning):**\n3. Object size is known and > 100 MB (multipart is recommended for\n   larger objects).\n4. Acceleration is enabled on the target bucket (or planned to be\n   enabled).\n5. Checksum algorithm is specified (CRC32C recommended for\n   performance, SHA-256 for compatibility).\n\n**For compare-direct-connect (read-only analysis):**\n3. Source location (data center or region) is known.\n4. Transfer volume (GB\u002Fmonth) is estimated.\n5. Direct Connect port speed (1 Gbps or 10 Gbps) is identified.\n\n**For diagnose-transfer (read-only):**\n3. Read `get-bucket-accelerate-configuration`, CloudWatch metrics,\n   and the failure-mode table to identify why acceleration is slow\n   or not working.\n\nThe full symptom \u002F root cause \u002F fix table — same-region slowness, UnsupportedArgument on directory buckets, PermanentRedirect, upload-part failure after disable, checksum mismatch, AccessDenied, IPv6 dual-stack, KMS throttling — lives in [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nConsult it during diagnose-transfer before emitting a verdict.\n\n### Step 2: READY — emit operation plan\n\nIf all pre-checks pass, emit `VERDICT: READY` with the exact CLI\nsequence and the CONFIRM gate. The plan includes:\n\n- The exact AWS CLI command with all flags populated.\n- The expected cost (per-GB rate x estimated volume).\n- The accelerate endpoint to use in the SDK\u002Fclient configuration.\n- The expected side-effects (accelerate endpoint becomes available,\n  standard endpoint unchanged).\n- The CONFIRM gate prompt.\n- The verification step (`get-bucket-accelerate-configuration` +\n  endpoint reachability test).\n\n### Step 3: Execute behind CONFIRM gate\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing CLI\n  (`put-bucket-accelerate-configuration`), emit:\n  `CONFIRM: About to \u003Cenable\u002Fdisable> Transfer Acceleration on bucket\n  \u003Cname> (region \u003Cregion>). \u003CCost\u002Fspeed impact>. Proceed? (yes\u002Fno)`.\n  Do NOT execute until the operator confirms.\n- Capture pre-state for rollback:\n  `aws s3api get-bucket-accelerate-configuration --bucket \u003Cname>\n  --output json > \u002Ftmp\u002F\u003Cname>-accel-pre-$(date +%s).json`.\n- Execute the CLI. `put-bucket-accelerate-configuration` is\n  synchronous — it returns once the configuration is applied.\n  Propagation to the DNS (accelerate endpoint resolving) can take\n  20-30 minutes for the first enable.\n- For multipart uploads: execute the `create-multipart-upload` →\n  `upload-part` (x N) → `complete-multipart-upload` sequence with\n  the accelerate endpoint configured.\n\n### Step 4: Post-verification — COMPLETED\n\nAfter the CLI completes, run post-verification. ALL checks must pass\nfor `COMPLETED`.\n\n1. `get-bucket-accelerate-configuration --bucket \u003Cname>` — confirm\n   `Status: Enabled` (or `Suspended` for disable).\n2. Endpoint reachability:\n   `aws s3 ls s3:\u002F\u002F\u003Cname>\u002F --endpoint-url https:\u002F\u002F\u003Cname>.s3-accelerate.amazonaws.com`\n   — confirm the accelerate endpoint resolves and responds.\n3. CloudWatch `BytesUploaded` metric — confirm traffic is flowing\n   through the accelerate endpoint (spike in BytesUploaded\n   correlated with the upload time).\n4. (For multipart uploads) Verify checksum: compare the object's\n   `x-amz-checksum-crc32c` with the locally computed checksum.\n5. Cost verification: confirm the CloudWatch BytesUploaded matches\n   the expected volume and the estimated acceleration cost.\n\nIf ANY verification fails, emit `VERDICT: ERROR` with the failure\ndetails — do not claim COMPLETED.\n\n## Output format (STRICT output contract — per operation)\n\n```text\nOPERATION: \u003Cenable-acceleration | disable-acceleration | speed-comparison | plan-multipart-upload | compare-direct-connect | diagnose-transfer>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Cbucket-name> (region \u003Cregion>, account \u003Caccount>)\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. \u003CCLI command with flags populated>\n  2. \u003Cwait \u002F monitoring command>\n  3. \u003Cnext step>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nCOST: \u003C$X.XX per GB from \u003Csource-region> | $0.00 for direct>\nNOTES: \u003Cspeed comparison, multipart recommendation, monitoring>\n```\n\n### Worked example — enable-acceleration\n\n```text\nOPERATION: enable-acceleration\nVERDICT: READY\nTARGET: prod-data-lake (region us-east-1, account 111111111111)\nPRE_CHECKS:\n  - [PASS] Bucket exists (head-bucket: 200 OK)\n  - [PASS] Not a directory bucket (standard bucket)\n  - [PASS] Region us-east-1 supports acceleration\n  - [PASS] Calling role has s3:PutAccelerateConfiguration\n  - [PASS] Bucket name is DNS-compatible (lowercase, hyphens)\n  - [INFO] Current Status: Suspended (not yet enabled)\n  - [INFO] Estimated uploaders: Asia Pacific (Tokyo, Singapore,\n    Sydney) and South America (Sao Paulo)\nSTEPS:\n  1. CONFIRM: About to enable Transfer Acceleration on bucket\n     prod-data-lake (us-east-1). Uploaders in Asia Pacific will\n     pay $0.025\u002FGB; uploaders in North America $0.004\u002FGB; Europe\n     $0.004\u002FGB. The accelerate endpoint\n     (prod-data-lake.s3-accelerate.amazonaws.com) will become\n     available within 20-30 minutes. Proceed? (yes\u002Fno)\n  2. aws s3api put-bucket-accelerate-configuration \\\n       --bucket prod-data-lake \\\n       --accelerate-configuration Status=Enabled\n  3. Verify:\n     aws s3api get-bucket-accelerate-configuration \\\n       --bucket prod-data-lake\nPOST_VERIFY:\n  - (pending execution)\nCOST: $0.025\u002FGB (Asia Pacific uploaders), $0.004\u002FGB (EU\u002FNA uploaders)\nNOTES:\n  - The accelerate endpoint DNS (prod-data-lake.s3-accelerate\n    .amazonaws.com) may take 20-30 minutes to propagate after\n    enabling. Test with a small upload before production use.\n  - Configure SDK clients with use_accelerate_endpoint: true or use\n    the endpoint URL directly.\n  - Use multipart upload for files > 100 MB to maximize throughput\n    with acceleration.\n  - Run the speed comparison tool first for each uploader region to\n    confirm acceleration provides a meaningful speedup.\n```\n\nAdditional worked examples — disable-acceleration (with in-flight check), plan-multipart-upload with acceleration, and directory-bucket BLOCKED — live in [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad that reference when formatting a verdict block for those operations.\n\n## Anti-Patterns — NEVER (top mistakes)\n\n- NEVER use the standard S3 endpoint after enabling acceleration.\n  The accelerate endpoint (`\u003Cbucket>.s3-accelerate.amazonaws.com`)\n  is the only way to route through the edge network. Using\n  `\u003Cbucket>.s3.\u003Cregion>.amazonaws.com` bypasses acceleration — you\n  pay for the feature but get no speed benefit. Configure the SDK\n  with `use_accelerate_endpoint: true`.\n\n- NEVER disable acceleration while multipart uploads are in-flight\n  via the accelerate endpoint. The in-flight `upload-part` calls\n  will fail with `PermanentRedirect` or `NoSuchUpload`. Always\n  check `list-multipart-uploads` and complete or abort all active\n  uploads before disabling.\n\n- NEVER enable acceleration for same-region transfers. If the\n  uploader and the bucket are in the same region (e.g., EU to EU,\n  US-East to US-West), the edge network adds latency and cost with\n  no speed benefit. Transfer Acceleration is designed for\n  long-distance, high-latency transfers. Run the speed comparison\n  tool first.\n\n- NEVER forget to specify checksums on accelerated multipart\n  uploads. Accelerated uploads traverse the edge network and\n  backbone — while TCP provides integrity per-hop, end-to-end\n  checksum verification (CRC32C) ensures the object was not\n  corrupted in transit. For multipart uploads, each part gets its\n  own checksum; the final object checksum is aggregated.\n\n- NEVER assume acceleration is cheaper than Direct Connect for\n  sustained high-volume transfers. At 50 TB\u002Fmonth from Asia to US,\n  acceleration costs $1,280\u002Fmonth ($0.025\u002FGB). A 1 Gbps Direct\n  Connect port costs ~$220\u002Fmonth + $1,024 (50 TB x $0.0204\u002FGB) =\n  ~$1,244\u002Fmonth. At 100+ TB\u002Fmonth, Direct Connect is significantly\n  cheaper.\n\n- NEVER use the accelerate endpoint for downloads unless you\n  explicitly need the speed. Acceleration fees apply to both data IN\n  and data OUT. For read-heavy workloads (many downloads), use\n  CloudFront instead — it caches at the edge and reduces origin\n  fetches.\n\n- NEVER attempt to enable acceleration on a bucket with underscores\n  in the name. The accelerate endpoint requires DNS-compatible\n  bucket names (lowercase letters, numbers, hyphens only). Underscores\n  cause DNS resolution failures. Rename the bucket or use a standard\n  endpoint.\n\n- NEVER assume `Status: Enabled` means the endpoint is immediately\n  ready. DNS propagation for the accelerate endpoint can take 20-30\n  minutes after the first enable. Test with a small upload before\n  starting production transfers.\n\n- NEVER skip the speed comparison tool for new acceleration use\n  cases. The tool uploads and downloads small test files through\n  both endpoints and reports the speed difference. If the speedup is\n  less than 1.5x, acceleration is not worth the cost for that source\n  region.\n\n- NEVER use acceleration with S3 Object Lambda. Object Lambda Access\n  Points do not work with the accelerate endpoint. If the bucket has\n  Object Lambda transformations, uploads via the accelerate endpoint\n  bypass the transformation.\n\n## Pre-flight safety checks (run before any remediation CLI)\n\nThe full pre-flight safety checklist — confirm gate, pre-state capture, in-flight multipart check, DNS compatibility, cost acceptance, multipart preference — lives in [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nRun these before any remediation CLI.\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features 2024-2026 — S3 Express One Zone, CRC32C multipart checksums, accelerated multipart copy, dual-stack IPv6, Direct Connect S3 endpoints, Batch Operations with acceleration, per-endpoint CloudWatch metrics — live in [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad when a plan depends on recent service behavior.\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked examples: disable-acceleration (in-flight check), plan-multipart-upload with acceleration, directory-bucket BLOCKED\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — transfer failure-mode table (symptom \u002F root cause \u002F fix) for diagnose-transfer\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — pre-flight safety checks and pre-state capture commands\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert heuristics and recent AWS features (2024-2026)\n- [references\u002Fcost-and-speed-comparison.md](references\u002Fcost-and-speed-comparison.md) — acceleration pricing by edge location, speed comparison, Direct Connect crossover\n- [references\u002Fmultipart-upload-and-checksum.md](references\u002Fmultipart-upload-and-checksum.md) — part-size selection, multipart lifecycle, checksum verification\n\n## Domain\n\nAWS CloudOps \u002F S3 Transfer Acceleration, Multipart Upload Optimization & Cross-Region Transfer Strategy.\n\n## AWS documentation\n\n- **S3 User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002F\n- **Transfer Acceleration** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Ftransfer-acceleration.html\n- **Transfer Acceleration speed comparison** — https:\u002F\u002Fs3-accelerate-speedtest.s3-accelerate.amazonaws.com\u002Fen\u002Faccelerate-speed-comparsion.html\n- **Multipart upload** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fmpuoverview.html\n- **S3 checksums** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fchecking-object-integrity.html\n- **S3 Express One Zone** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fs3-express-one-zone.html\n- **S3 pricing** — https:\u002F\u002Faws.amazon.com\u002Fs3\u002Fpricing\u002F\n- **Direct Connect pricing** — https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002Fpricing\u002F\n- **S3 CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fs3api\u002F\n","# S3 Transfer Acceleration Operator\n\n## What this skill does\n\nExecutes S3 Transfer Acceleration operations correctly and\ncost-effectively. Runs deterministic pre-checks before any\nstate-changing CLI (bucket exists, not a directory bucket, caller has\n`s3:PutAccelerateConfiguration`, region supports acceleration), then\nexecutes `put-bucket-accelerate-configuration` behind a CONFIRM gate,\nand verifies the result via `get-bucket-accelerate-configuration`.\nEvery enable-acceleration produces a cost analysis (source region to\nS3 region at $0.004-0.025\u002FGB), a speed comparison recommendation\n(accelerated endpoint vs direct endpoint), and a multipart upload plan\nwith checksum verification. Disabling acceleration includes\nverification that no in-flight multipart uploads depend on the\naccelerate endpoint.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **§ Quick reference** | Verdict thresholds (BLOCKED\u002FREADY\u002FCOMPLETED) + pre-check priority | Before any operation |\n| **§ Mindset** | Why acceleration routes through edge, the cost-by-region model, the Direct Connect crossover | Understanding the cost\u002Fspeed model |\n| **§ Pre-flight** | Bucket metadata gate — exists, not directory bucket, region, caller IAM | Before executing any CLI |\n| **§ Process** | Per-operation planning: enable, disable, speed-comparison, plan-multipart, compare-DC, diagnose | When choosing which operation to run |\n| **§ Output format** | STRICT output contract — OPERATION\u002FVERDICT\u002FPRE_CHECKS\u002FSTEPS\u002FPOST_VERIFY\u002FCOST template | Formatting the response |\n| **§ Anti-Patterns** | NEVER list — top mistakes that waste money or corrupt transfers | Review before risky operations |\n| **§ Pre-flight safety** | Capture pre-state, verify no in-flight uploads, cost capture | Defense-in-depth |\n\n## Quick reference — verdict thresholds\n\n| Verdict | Trigger condition | Action |\n|---|---|---|\n| `BLOCKED` | One or more pre-checks failed (bucket is a directory bucket, region does not support acceleration, caller lacks `s3:PutAccelerateConfiguration`, bucket does not exist, cost threshold exceeded without acknowledgment) | List failures, do NOT execute |\n| `READY` | All pre-checks passed; awaiting CONFIRM gate | Emit exact CLI sequence, wait for operator yes |\n| `COMPLETED` | Acceleration enable\u002Fdisable finished and post-verification passed (`get-bucket-accelerate-configuration` matches intent, accelerate endpoint reachable, CloudWatch metrics confirm traffic) | Emit verification results, cost summary, monitoring plan |\n\n**Priority order for pre-checks (apply in this sequence, all must pass\nfor READY):**\n\n1. **Bucket reachability** — bucket exists (`head-bucket` does not\n   return `404` or `403`).\n2. **Not a directory bucket** — S3 Express One Zone directory buckets\n   do NOT support Transfer Acceleration. Check bucket naming\n   (`\u003Cname>--xaz-\u003Caz-id>`) and `get-bucket-location`.\n3. **Region supports acceleration** — most AWS commercial regions\n   support Transfer Acceleration. AWS GovCloud, China, and some\n   opt-in regions may have limited support. Verify via\n   `get-bucket-accelerate-configuration` (returns\n   `Status: Suspended` if acceleration is not available in the\n   region).\n4. **Caller IAM permission** — the calling identity must have\n   `s3:PutAccelerateConfiguration` on the bucket for enable\u002Fdisable\n   operations, and `s3:GetAccelerateConfiguration` for verification.\n5. **Cost acknowledgment** — Transfer Acceleration charges\n   $0.004-0.025\u002FGB depending on the source edge location. Surface\n   the estimated cost based on the planned transfer volume.\n6. **No conflicting bucket policies** — bucket policies that deny\n   `s3:PutAccelerateConfiguration` or restrict endpoint access must\n   be resolved before enabling.\n7. **In-flight multipart upload check (disable only)** — before\n   disabling, verify no in-flight multipart uploads are using the\n   accelerate endpoint via `list-multipart-uploads`.\n\n**Cost\u002Ftime baselines (2026):**\n\n- Transfer Acceleration pricing by source edge location:\n  - Asia Pacific (excluding Australia): $0.025\u002FGB\n  - South America: $0.025\u002FGB\n  - Australia \u002F New Zealand: $0.025\u002FGB\n  - Europe: $0.004\u002FGB\n  - North America: $0.004\u002FGB (if source is in NA)\n  - Africa: $0.025\u002FGB\n  - Middle East: $0.025\u002FGB\n- Acceleration is billed on DATA IN (uploads to S3 via the\n  accelerate endpoint). Downloads via accelerate are also billed.\n- Direct S3 upload (no acceleration): free (standard S3 PUT request\n  costs only: $0.005 per 1,000 PUT requests).\n- Typical speed improvement: 2-10x for long-distance transfers\n  (Asia to US, South America to EU). Minimal or no improvement for\n  short-distance transfers (same continent).\n- Multipart upload overhead: each part is a separate PUT request.\n  10,000 parts at 8MB each = 10,000 PUT requests ($0.05 at\n  $0.005\u002F1,000 requests) + acceleration data-in fee.\n- Direct Connect: flat port hourly rate ($0.30\u002Fhour for 1 Gbps)\n  plus $0.02\u002FGB data transfer out. Economical for sustained\n  high-volume transfers (>50 TB\u002Fmonth from a fixed location).\n\n## Mindset\n\n**One-line takeaway:** Transfer Acceleration routes uploads through\nthe nearest CloudFront edge location over an optimized AWS backbone\npath — it excels for long-distance, high-latency transfers but costs\n$0.004-0.025\u002FGB and is pointless for same-region traffic. Driven by\nthree S3 realities:\n\n- **Acceleration is a routing optimization, not a bandwidth boost.**\n  S3 Transfer Acceleration uses the CloudFront edge network to find\n  the fastest path to the destination S3 bucket. The edge location\n  receives the upload, then forwards it to S3 over the AWS backbone\n  (optimized routing, larger TCP windows, fewer hops). For\n  long-distance transfers (Asia to US, South America to EU), this\n  can reduce transfer time by 2-10x. For same-region transfers\n  (EU to EU, US to US), the improvement is negligible — and you pay\n  the $\u002FGB acceleration fee for nothing.\n\n- **Cost scales with data volume, not speed.** You pay per GB\n  transferred through the accelerate endpoint. A 1 TB upload from\n  Asia to a US bucket costs $25.00 ($0.025\u002FGB x 1,024 GB). A 100 TB\n  migration costs $2,500. Always run the speed comparison tool first\n  to confirm acceleration provides a meaningful speedup before\n  committing to the cost. For sustained high-volume transfers from a\n  fixed location, Direct Connect is usually cheaper.\n\n- **Multipart upload is the performance multiplier.** Acceleration\n  reduces per-connection latency. Multipart upload increases\n  throughput by parallelizing across multiple connections. Together,\n  they maximize transfer speed: each part is uploaded over an\n  accelerated connection, and multiple parts run in parallel. Always\n  use multipart upload for files > 100 MB when acceleration is\n  enabled. The accelerate endpoint\n  (`\u003Cbucket>.s3-accelerate.amazonaws.com`) accepts standard multipart\n  upload API calls.\n\n## Pre-flight: bucket metadata gate\n\nRun before classification. Misclassifying these produces wrong plans.\n\n**Pagination:** `list-multipart-uploads` paginates at 1,000\u002Fpage —\ndrain `--page-size` \u002F `--starting-token` to completion.\n\n**Live-account pre-flight (skip if offline plan audit):**\n1. `aws s3api head-bucket --bucket \u003Cname>` — confirm bucket exists\n   and is accessible (200 OK).\n2. `aws s3api get-bucket-location --bucket \u003Cname>` — capture the\n   bucket region. Verify it is a supported commercial region.\n3. `aws s3api get-bucket-accelerate-configuration --bucket \u003Cname>`\n   — capture `Status` (`Enabled`, `Suspended`, or null).\n4. `aws s3api get-bucket-logging --bucket \u003Cname>` — verify logging\n   is configured for audit trail (advisory).\n5. `aws s3api list-multipart-uploads --bucket \u003Cname>` — capture\n   in-flight multipart uploads (critical for disable-acceleration).\n6. `aws cloudwatch get-metric-statistics --namespace AWS\u002FS3\n   --metric-name BytesUploaded --dimensions Name=BucketName,\n   Value=\u003Cname> --start-time \u003C24h-ago> --end-time \u003Cnow>\n   --period 3600 --statistics Sum` — capture recent upload volume\n   for cost estimation.\n\n**Malformed input:** if the input is invalid or missing required\nfields, emit `VERDICT: ERROR` with `REASON: Bucket configuration\nis not valid or is missing required fields — cannot plan.` and\n`REMEDIATION: Re-fetch with aws s3api head-bucket --bucket \u003Cname>\n--output json and re-plan.`\n\n| Bucket attribute | Effect on operation |\n|---|---|\n| Directory bucket (`--xaz-` suffix) | BLOCKED — S3 Express One Zone does not support Transfer Acceleration. |\n| Bucket in GovCloud \u002F China region | BLOCKED — Transfer Acceleration not available in isolated regions. |\n| `Status: Enabled` | Already accelerated. For enable: no-op or advisory. For disable: plan the disable. |\n| `Status: Suspended` | Acceleration was enabled then suspended. Re-enable to resume. |\n| In-flight multipart uploads (disable only) | BLOCKED — disabling acceleration while multipart uploads are in-flight via the accelerate endpoint will cause upload failures. |\n| Bucket policy denies `s3:PutAccelerateConfiguration` | BLOCKED — update the bucket policy first. |\n| Virtual-hosted-style incompatible | Advisory — the accelerate endpoint uses `\u003Cbucket>.s3-accelerate.amazonaws.com`. Ensure the client supports virtual-hosted-style addressing. |\n| Bucket name with underscores | BLOCKED — underscores are not DNS-compatible; the accelerate endpoint requires DNS-compatible bucket names. |\n\n## Process — operation planning (apply in order)\n\n### Step 0: Expert heuristic — non-obvious S3 acceleration behaviors\n\nNon-obvious acceleration behaviors — accelerate endpoint DNS vs standard endpoint, directory buckets, per-GB (not per-request) pricing, non-destructive speed test, checksum end-to-end protection, mid-upload disable failures, Direct Connect crossover, dual-stack IPv6, Object Lambda, KMS — live in [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad that reference before planning enable\u002Fdisable, speed-comparison, or diagnose operations.\n\n### Step 1: Pre-check gate — BLOCKED if any check fails\n\nRun ALL pre-checks for the chosen operation. If ANY fails, the verdict\nis BLOCKED with the failed checks in PRE_CHECKS. Do NOT execute.\n\n**For ALL operations:**\n1. Bucket exists (`head-bucket` returns 200).\n2. Bucket is accessible (caller has `s3:GetAccelerateConfiguration`).\n\n**For enable-acceleration:**\n3. Bucket is NOT a directory bucket (no `--xaz-` suffix, not S3\n   Express One Zone).\n4. Bucket region supports acceleration (commercial region, not\n   GovCloud or China).\n5. Calling identity has `s3:PutAccelerateConfiguration` on the bucket.\n6. Bucket name is DNS-compatible (lowercase letters, numbers, hyphens;\n   no underscores, no uppercase).\n7. (Advisory) Cost acknowledgment: surface estimated $\u002FGB based on\n   source region.\n\n**For disable-acceleration:**\n3. No in-flight multipart uploads using the accelerate endpoint\n   (`list-multipart-uploads` returns empty, or all uploads use the\n   standard endpoint).\n4. Calling identity has `s3:PutAccelerateConfiguration`.\n5. (Advisory) Confirm no SDK clients are configured with\n   `use_accelerate_endpoint: true` — they will fail after disable.\n\n**For speed-comparison (read-only, non-destructive):**\n3. Acceleration is enabled OR the operator plans to test before\n   enabling. The speed comparison tool works on buckets with\n   acceleration enabled.\n4. Test files are small (\u003C 1 MB) and do not affect production data.\n\n**For plan-multipart-upload (read-only planning):**\n3. Object size is known and > 100 MB (multipart is recommended for\n   larger objects).\n4. Acceleration is enabled on the target bucket (or planned to be\n   enabled).\n5. Checksum algorithm is specified (CRC32C recommended for\n   performance, SHA-256 for compatibility).\n\n**For compare-direct-connect (read-only analysis):**\n3. Source location (data center or region) is known.\n4. Transfer volume (GB\u002Fmonth) is estimated.\n5. Direct Connect port speed (1 Gbps or 10 Gbps) is identified.\n\n**For diagnose-transfer (read-only):**\n3. Read `get-bucket-accelerate-configuration`, CloudWatch metrics,\n   and the failure-mode table to identify why acceleration is slow\n   or not working.\n\nThe full symptom \u002F root cause \u002F fix table — same-region slowness, UnsupportedArgument on directory buckets, PermanentRedirect, upload-part failure after disable, checksum mismatch, AccessDenied, IPv6 dual-stack, KMS throttling — lives in [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nConsult it during diagnose-transfer before emitting a verdict.\n\n### Step 2: READY — emit operation plan\n\nIf all pre-checks pass, emit `VERDICT: READY` with the exact CLI\nsequence and the CONFIRM gate. The plan includes:\n\n- The exact AWS CLI command with all flags populated.\n- The expected cost (per-GB rate x estimated volume).\n- The accelerate endpoint to use in the SDK\u002Fclient configuration.\n- The expected side-effects (accelerate endpoint becomes available,\n  standard endpoint unchanged).\n- The CONFIRM gate prompt.\n- The verification step (`get-bucket-accelerate-configuration` +\n  endpoint reachability test).\n\n### Step 3: Execute behind CONFIRM gate\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing CLI\n  (`put-bucket-accelerate-configuration`), emit:\n  `CONFIRM: About to \u003Cenable\u002Fdisable> Transfer Acceleration on bucket\n  \u003Cname> (region \u003Cregion>). \u003CCost\u002Fspeed impact>. Proceed? (yes\u002Fno)`.\n  Do NOT execute until the operator confirms.\n- Capture pre-state for rollback:\n  `aws s3api get-bucket-accelerate-configuration --bucket \u003Cname>\n  --output json > \u002Ftmp\u002F\u003Cname>-accel-pre-$(date +%s).json`.\n- Execute the CLI. `put-bucket-accelerate-configuration` is\n  synchronous — it returns once the configuration is applied.\n  Propagation to the DNS (accelerate endpoint resolving) can take\n  20-30 minutes for the first enable.\n- For multipart uploads: execute the `create-multipart-upload` →\n  `upload-part` (x N) → `complete-multipart-upload` sequence with\n  the accelerate endpoint configured.\n\n### Step 4: Post-verification — COMPLETED\n\nAfter the CLI completes, run post-verification. ALL checks must pass\nfor `COMPLETED`.\n\n1. `get-bucket-accelerate-configuration --bucket \u003Cname>` — confirm\n   `Status: Enabled` (or `Suspended` for disable).\n2. Endpoint reachability:\n   `aws s3 ls s3:\u002F\u002F\u003Cname>\u002F --endpoint-url https:\u002F\u002F\u003Cname>.s3-accelerate.amazonaws.com`\n   — confirm the accelerate endpoint resolves and responds.\n3. CloudWatch `BytesUploaded` metric — confirm traffic is flowing\n   through the accelerate endpoint (spike in BytesUploaded\n   correlated with the upload time).\n4. (For multipart uploads) Verify checksum: compare the object's\n   `x-amz-checksum-crc32c` with the locally computed checksum.\n5. Cost verification: confirm the CloudWatch BytesUploaded matches\n   the expected volume and the estimated acceleration cost.\n\nIf ANY verification fails, emit `VERDICT: ERROR` with the failure\ndetails — do not claim COMPLETED.\n\n## Output format (STRICT output contract — per operation)\n\n```text\nOPERATION: \u003Cenable-acceleration | disable-acceleration | speed-comparison | plan-multipart-upload | compare-direct-connect | diagnose-transfer>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Cbucket-name> (region \u003Cregion>, account \u003Caccount>)\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. \u003CCLI command with flags populated>\n  2. \u003Cwait \u002F monitoring command>\n  3. \u003Cnext step>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nCOST: \u003C$X.XX per GB from \u003Csource-region> | $0.00 for direct>\nNOTES: \u003Cspeed comparison, multipart recommendation, monitoring>\n```\n\n### Worked example — enable-acceleration\n\n```text\nOPERATION: enable-acceleration\nVERDICT: READY\nTARGET: prod-data-lake (region us-east-1, account 111111111111)\nPRE_CHECKS:\n  - [PASS] Bucket exists (head-bucket: 200 OK)\n  - [PASS] Not a directory bucket (standard bucket)\n  - [PASS] Region us-east-1 supports acceleration\n  - [PASS] Calling role has s3:PutAccelerateConfiguration\n  - [PASS] Bucket name is DNS-compatible (lowercase, hyphens)\n  - [INFO] Current Status: Suspended (not yet enabled)\n  - [INFO] Estimated uploaders: Asia Pacific (Tokyo, Singapore,\n    Sydney) and South America (Sao Paulo)\nSTEPS:\n  1. CONFIRM: About to enable Transfer Acceleration on bucket\n     prod-data-lake (us-east-1). Uploaders in Asia Pacific will\n     pay $0.025\u002FGB; uploaders in North America $0.004\u002FGB; Europe\n     $0.004\u002FGB. The accelerate endpoint\n     (prod-data-lake.s3-accelerate.amazonaws.com) will become\n     available within 20-30 minutes. Proceed? (yes\u002Fno)\n  2. aws s3api put-bucket-accelerate-configuration \\\n       --bucket prod-data-lake \\\n       --accelerate-configuration Status=Enabled\n  3. Verify:\n     aws s3api get-bucket-accelerate-configuration \\\n       --bucket prod-data-lake\nPOST_VERIFY:\n  - (pending execution)\nCOST: $0.025\u002FGB (Asia Pacific uploaders), $0.004\u002FGB (EU\u002FNA uploaders)\nNOTES:\n  - The accelerate endpoint DNS (prod-data-lake.s3-accelerate\n    .amazonaws.com) may take 20-30 minutes to propagate after\n    enabling. Test with a small upload before production use.\n  - Configure SDK clients with use_accelerate_endpoint: true or use\n    the endpoint URL directly.\n  - Use multipart upload for files > 100 MB to maximize throughput\n    with acceleration.\n  - Run the speed comparison tool first for each uploader region to\n    confirm acceleration provides a meaningful speedup.\n```\n\nAdditional worked examples — disable-acceleration (with in-flight check), plan-multipart-upload with acceleration, and directory-bucket BLOCKED — live in [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad that reference when formatting a verdict block for those operations.\n\n## Anti-Patterns — NEVER (top mistakes)\n\n- NEVER use the standard S3 endpoint after enabling acceleration.\n  The accelerate endpoint (`\u003Cbucket>.s3-accelerate.amazonaws.com`)\n  is the only way to route through the edge network. Using\n  `\u003Cbucket>.s3.\u003Cregion>.amazonaws.com` bypasses acceleration — you\n  pay for the feature but get no speed benefit. Configure the SDK\n  with `use_accelerate_endpoint: true`.\n\n- NEVER disable acceleration while multipart uploads are in-flight\n  via the accelerate endpoint. The in-flight `upload-part` calls\n  will fail with `PermanentRedirect` or `NoSuchUpload`. Always\n  check `list-multipart-uploads` and complete or abort all active\n  uploads before disabling.\n\n- NEVER enable acceleration for same-region transfers. If the\n  uploader and the bucket are in the same region (e.g., EU to EU,\n  US-East to US-West), the edge network adds latency and cost with\n  no speed benefit. Transfer Acceleration is designed for\n  long-distance, high-latency transfers. Run the speed comparison\n  tool first.\n\n- NEVER forget to specify checksums on accelerated multipart\n  uploads. Accelerated uploads traverse the edge network and\n  backbone — while TCP provides integrity per-hop, end-to-end\n  checksum verification (CRC32C) ensures the object was not\n  corrupted in transit. For multipart uploads, each part gets its\n  own checksum; the final object checksum is aggregated.\n\n- NEVER assume acceleration is cheaper than Direct Connect for\n  sustained high-volume transfers. At 50 TB\u002Fmonth from Asia to US,\n  acceleration costs $1,280\u002Fmonth ($0.025\u002FGB). A 1 Gbps Direct\n  Connect port costs ~$220\u002Fmonth + $1,024 (50 TB x $0.0204\u002FGB) =\n  ~$1,244\u002Fmonth. At 100+ TB\u002Fmonth, Direct Connect is significantly\n  cheaper.\n\n- NEVER use the accelerate endpoint for downloads unless you\n  explicitly need the speed. Acceleration fees apply to both data IN\n  and data OUT. For read-heavy workloads (many downloads), use\n  CloudFront instead — it caches at the edge and reduces origin\n  fetches.\n\n- NEVER attempt to enable acceleration on a bucket with underscores\n  in the name. The accelerate endpoint requires DNS-compatible\n  bucket names (lowercase letters, numbers, hyphens only). Underscores\n  cause DNS resolution failures. Rename the bucket or use a standard\n  endpoint.\n\n- NEVER assume `Status: Enabled` means the endpoint is immediately\n  ready. DNS propagation for the accelerate endpoint can take 20-30\n  minutes after the first enable. Test with a small upload before\n  starting production transfers.\n\n- NEVER skip the speed comparison tool for new acceleration use\n  cases. The tool uploads and downloads small test files through\n  both endpoints and reports the speed difference. If the speedup is\n  less than 1.5x, acceleration is not worth the cost for that source\n  region.\n\n- NEVER use acceleration with S3 Object Lambda. Object Lambda Access\n  Points do not work with the accelerate endpoint. If the bucket has\n  Object Lambda transformations, uploads via the accelerate endpoint\n  bypass the transformation.\n\n## Pre-flight safety checks (run before any remediation CLI)\n\nThe full pre-flight safety checklist — confirm gate, pre-state capture, in-flight multipart check, DNS compatibility, cost acceptance, multipart preference — lives in [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nRun these before any remediation CLI.\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features 2024-2026 — S3 Express One Zone, CRC32C multipart checksums, accelerated multipart copy, dual-stack IPv6, Direct Connect S3 endpoints, Batch Operations with acceleration, per-endpoint CloudWatch metrics — live in [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad when a plan depends on recent service behavior.\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked examples: disable-acceleration (in-flight check), plan-multipart-upload with acceleration, directory-bucket BLOCKED\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — transfer failure-mode table (symptom \u002F root cause \u002F fix) for diagnose-transfer\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — pre-flight safety checks and pre-state capture commands\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert heuristics and recent AWS features (2024-2026)\n- [references\u002Fcost-and-speed-comparison.md](references\u002Fcost-and-speed-comparison.md) — acceleration pricing by edge location, speed comparison, Direct Connect crossover\n- [references\u002Fmultipart-upload-and-checksum.md](references\u002Fmultipart-upload-and-checksum.md) — part-size selection, multipart lifecycle, checksum verification\n\n## Domain\n\nAWS CloudOps \u002F S3 Transfer Acceleration, Multipart Upload Optimization & Cross-Region Transfer Strategy.\n\n## AWS documentation\n\n- **S3 User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002F\n- **Transfer Acceleration** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Ftransfer-acceleration.html\n- **Transfer Acceleration speed comparison** — https:\u002F\u002Fs3-accelerate-speedtest.s3-accelerate.amazonaws.com\u002Fen\u002Faccelerate-speed-comparsion.html\n- **Multipart upload** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fmpuoverview.html\n- **S3 checksums** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fchecking-object-integrity.html\n- **S3 Express One Zone** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonS3\u002Flatest\u002Fuserguide\u002Fs3-express-one-zone.html\n- **S3 pricing** — https:\u002F\u002Faws.amazon.com\u002Fs3\u002Fpricing\u002F\n- **Direct Connect pricing** — https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002Fpricing\u002F\n- **S3 CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fs3api\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":42},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"requires_llm":37,"verdict_shape":38,"lifecycle_status":39,"invocation_schema":40,"supports_pipeline":37,"activation_triggers":41},"aws, s3, storage, transfer-acceleration, upload, networking, operate","4","Jacky Chan — AWS Community Builder","aws-cloudops","Storage","0.1.0","S3 Transfer Acceleration, accelerate endpoint, s3-accelerate.amazonaws.com, multipart upload, checksum verification, CRC32, CRC32C, SHA-256, Direct Connect, edge network, put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, BytesUploaded, speed comparison, cost per GB, multipart copy, bucket configuration","operate","medium","false","capability","Enabling or disabling S3 Transfer Acceleration on a bucket, comparing transfer speed between accelerated and direct S3 endpoints, planning a multipart upload over the accelerate endpoint, verifying checksums on accelerated uploads, performing a multipart copy between accelerated buckets, comparing Transfer Acceleration vs Direct Connect for large data transfers, or diagnosing why accelerated transfers are slower than expected.","true","READY | BLOCKED | COMPLETED","active","Input: either (a) a bucket configuration (get-bucket-accelerate-configuration, get-bucket-location, head-bucket output) plus the intended operation (enable-acceleration, disable-acceleration, speed-comparison, plan-multipart-upload, compare-direct-connect, diagnose-transfer), OR (b) a bucket-name + operation for live- account execution. Output: deterministic OPERATION \u002F VERDICT \u002F PRE_CHECKS \u002F STEPS \u002F POST_VERIFY \u002F COST \u002F NOTES block per operation, where VERDICT is one of READY, BLOCKED, COMPLETED.","enable S3 Transfer Acceleration, disable S3 Transfer Acceleration, accelerate endpoint, s3-accelerate.amazonaws.com, put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, S3 speed comparison, accelerated multipart upload, S3 checksum verification, CRC32C upload, S3 multipart copy accelerated, Transfer Acceleration cost, Direct Connect vs Transfer Acceleration, slow S3 transfer, S3 edge network upload","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline plan classification. Live-account operations use aws s3api put-bucket-accelerate-configuration, get-bucket-accelerate-configuration, s3api create-multipart-upload \u002F upload-part \u002F complete-multipart-upload (with accelerate endpoint), aws s3 ls --endpoint-url, CloudWatch GetMetricStatistics (AWS CLI v2, SSO or key-based credentials).","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fs3-transfer-acceleration-operator",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill s3-transfer-acceleration-operator",{"tool":57,"command":58},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill s3-transfer-acceleration-operator",{"tool":60,"command":61},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill s3-transfer-acceleration-operator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",7218,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Feval\u002Ftest-cases.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Fbaselines\u002Fcost-analysis-bulk-transfer-ready.md",579,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fbaselines\u002Fcost-analysis-bulk-transfer-ready.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Fbaselines\u002Fdisable-acceleration-inflight-blocked.md",439,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fbaselines\u002Fdisable-acceleration-inflight-blocked.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"evals\u002Fbaselines\u002Fenable-acceleration-directory-bucket-blocked.md",462,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fbaselines\u002Fenable-acceleration-directory-bucket-blocked.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"evals\u002Fbaselines\u002Fenable-acceleration-standard-bucket-ready.md",491,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fbaselines\u002Fenable-acceleration-standard-bucket-ready.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fbaselines\u002Fspeed-comparison-acceleration-completed.md",441,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fbaselines\u002Fspeed-comparison-acceleration-completed.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"evals\u002Feval_config.yaml",1961,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Feval_config.yaml",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"evals\u002Fevals.json",4424,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fevals.json",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"evals\u002Fprompts\u002Fcost-analysis-bulk-transfer-ready.md",778,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fprompts\u002Fcost-analysis-bulk-transfer-ready.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"evals\u002Fprompts\u002Fdisable-acceleration-inflight-blocked.md",854,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fprompts\u002Fdisable-acceleration-inflight-blocked.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"evals\u002Fprompts\u002Fenable-acceleration-directory-bucket-blocked.md",696,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fprompts\u002Fenable-acceleration-directory-bucket-blocked.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"evals\u002Fprompts\u002Fenable-acceleration-standard-bucket-ready.md",757,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fprompts\u002Fenable-acceleration-standard-bucket-ready.md",{"path":116,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":117,"sourceHtmlUrl":118},"evals\u002Fprompts\u002Fspeed-comparison-acceleration-completed.md",985,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fevals\u002Fprompts\u002Fspeed-comparison-acceleration-completed.md",{"path":120,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":121,"sourceHtmlUrl":122},"examples\u002FREADME.md",6370,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fexamples\u002FREADME.md",{"path":124,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fadvanced-patterns.md",6393,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Fadvanced-patterns.md",{"path":128,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fcost-and-speed-comparison.md",5988,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Fcost-and-speed-comparison.md",{"path":132,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fdiagnostic-commands.md",1553,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Fdiagnostic-commands.md",{"path":136,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Ferror-handling.md",2340,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Ferror-handling.md",{"path":140,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fmultipart-upload-and-checksum.md",7275,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Fmultipart-upload-and-checksum.md",{"path":144,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fworked-examples.md",4861,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Freferences\u002Fworked-examples.md",{"path":148,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":149,"sourceHtmlUrl":150},"skill.usf.yaml",4729,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fs3-transfer-acceleration-operator\u002Fskill.usf.yaml",[152,159,166,173,180,187],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","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 \u002F method \u002F 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 \u002F 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 \u002F EKS \u002F 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","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 \u002F 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","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\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","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\u002Fbypass 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]