s3-transfer-acceleration-operator
Operates S3 Transfer Acceleration workflows — enable/disable acceleration per bucket (put-bucket-accelerate-configuration), cost analysis by source region ($0.004-0.025/GB depending on edge location), speed comparison tool (CloudFront edge vs direct S3 endpoint), multipart upload with acceleration endpoints (<bucket>.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/disabling acceleration, comparing transfer speeds, planning multipart uploads over acceleration, or diagnosing slow transfers.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-24
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- s3-transfer-acceleration-operator
- license
- Apache-2.0
- metadata
- { "tags": "aws, s3, storage, transfer-acceleration, upload, networking, operate", "phase": "4", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "Storage", "version": "0.1.0", "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", "task_type": "operate", "complexity": "medium", "entry_point": "false", "skill_class": "capability", "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.", "requires_llm": "true", "verdict_shape": "READY | BLOCKED | COMPLETED", "lifecycle_status": "active", "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 / VERDICT / PRE_CHECKS / STEPS / POST_VERIFY / COST / NOTES block per operation, where VERDICT is one of READY, BLOCKED, COMPLETED.", "supports_pipeline": "true", "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" }
- description
- Operates S3 Transfer Acceleration workflows — enable/disable acceleration per bucket (put-bucket-accelerate-configuration), cost analysis by source region ($0.004-0.025/GB depending on edge location), speed comparison tool (CloudFront edge vs direct S3 endpoint), multipart upload with acceleration endpoints (<bucket>.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/disabling acceleration, comparing transfer speeds, planning multipart uploads over acceleration, or diagnosing slow transfers.
- compatibility
- 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 / upload-part / complete-multipart-upload (with accelerate endpoint), aws s3 ls --endpoint-url, CloudWatch GetMetricStatistics (AWS CLI v2, SSO or key-based credentials).
02 资源文件 21
- 参考文档eval/test-cases.yaml7.0 KB
- 参考文档evals/baselines/cost-analysis-bulk-transfer-ready.md579 B
- 参考文档evals/baselines/disable-acceleration-inflight-blocked.md439 B
- 参考文档evals/baselines/enable-acceleration-directory-bucket-blocked.md462 B
- 参考文档evals/baselines/enable-acceleration-standard-bucket-ready.md491 B
- 参考文档evals/baselines/speed-comparison-acceleration-completed.md441 B
- 参考文档evals/eval_config.yaml1.9 KB
- 参考文档evals/evals.json4.3 KB
- 参考文档evals/prompts/cost-analysis-bulk-transfer-ready.md778 B
- 参考文档evals/prompts/disable-acceleration-inflight-blocked.md854 B
- 参考文档evals/prompts/enable-acceleration-directory-bucket-blocked.md696 B
- 参考文档evals/prompts/enable-acceleration-standard-bucket-ready.md757 B
- 参考文档evals/prompts/speed-comparison-acceleration-completed.md985 B
- 参考文档examples/README.md6.2 KB
- 参考文档references/advanced-patterns.md6.2 KB
- 参考文档references/cost-and-speed-comparison.md5.8 KB
- 参考文档references/diagnostic-commands.md1.5 KB
- 参考文档references/error-handling.md2.3 KB
- 参考文档references/multipart-upload-and-checksum.md7.1 KB
- 参考文档references/worked-examples.md4.7 KB
- 参考文档skill.usf.yaml4.6 KB
03 SKILL.md 正文
S3 Transfer Acceleration Operator
What this skill does
Executes S3 Transfer Acceleration operations correctly and
cost-effectively. Runs deterministic pre-checks before any
state-changing CLI (bucket exists, not a directory bucket, caller has
s3:PutAccelerateConfiguration, region supports acceleration), then
executes put-bucket-accelerate-configuration behind a CONFIRM gate,
and verifies the result via get-bucket-accelerate-configuration.
Every enable-acceleration produces a cost analysis (source region to
S3 region at $0.004-0.025/GB), a speed comparison recommendation
(accelerated endpoint vs direct endpoint), and a multipart upload plan
with checksum verification. Disabling acceleration includes
verification that no in-flight multipart uploads depend on the
accelerate endpoint.
Quick navigation
| Section | What it covers | When to read it |
|---|---|---|
| § Quick reference | Verdict thresholds (BLOCKED/READY/COMPLETED) + pre-check priority | Before any operation |
| § Mindset | Why acceleration routes through edge, the cost-by-region model, the Direct Connect crossover | Understanding the cost/speed model |
| § Pre-flight | Bucket metadata gate — exists, not directory bucket, region, caller IAM | Before executing any CLI |
| § Process | Per-operation planning: enable, disable, speed-comparison, plan-multipart, compare-DC, diagnose | When choosing which operation to run |
| § Output format | STRICT output contract — OPERATION/VERDICT/PRE_CHECKS/STEPS/POST_VERIFY/COST template | Formatting the response |
| § Anti-Patterns | NEVER list — top mistakes that waste money or corrupt transfers | Review before risky operations |
| § Pre-flight safety | Capture pre-state, verify no in-flight uploads, cost capture | Defense-in-depth |
Quick reference — verdict thresholds
| Verdict | Trigger condition | Action |
|---|---|---|
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 |
READY |
All pre-checks passed; awaiting CONFIRM gate | Emit exact CLI sequence, wait for operator yes |
COMPLETED |
Acceleration enable/disable 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 |
Priority order for pre-checks (apply in this sequence, all must pass for READY):
- Bucket reachability — bucket exists (
head-bucketdoes not return404or403). - Not a directory bucket — S3 Express One Zone directory buckets
do NOT support Transfer Acceleration. Check bucket naming
(
<name>--xaz-<az-id>) andget-bucket-location. - Region supports acceleration — most AWS commercial regions
support Transfer Acceleration. AWS GovCloud, China, and some
opt-in regions may have limited support. Verify via
get-bucket-accelerate-configuration(returnsStatus: Suspendedif acceleration is not available in the region). - Caller IAM permission — the calling identity must have
s3:PutAccelerateConfigurationon the bucket for enable/disable operations, ands3:GetAccelerateConfigurationfor verification. - Cost acknowledgment — Transfer Acceleration charges $0.004-0.025/GB depending on the source edge location. Surface the estimated cost based on the planned transfer volume.
- No conflicting bucket policies — bucket policies that deny
s3:PutAccelerateConfigurationor restrict endpoint access must be resolved before enabling. - In-flight multipart upload check (disable only) — before
disabling, verify no in-flight multipart uploads are using the
accelerate endpoint via
list-multipart-uploads.
Cost/time baselines (2026):
- Transfer Acceleration pricing by source edge location:
- Asia Pacific (excluding Australia): $0.025/GB
- South America: $0.025/GB
- Australia / New Zealand: $0.025/GB
- Europe: $0.004/GB
- North America: $0.004/GB (if source is in NA)
- Africa: $0.025/GB
- Middle East: $0.025/GB
- Acceleration is billed on DATA IN (uploads to S3 via the accelerate endpoint). Downloads via accelerate are also billed.
- Direct S3 upload (no acceleration): free (standard S3 PUT request costs only: $0.005 per 1,000 PUT requests).
- Typical speed improvement: 2-10x for long-distance transfers (Asia to US, South America to EU). Minimal or no improvement for short-distance transfers (same continent).
- Multipart upload overhead: each part is a separate PUT request. 10,000 parts at 8MB each = 10,000 PUT requests ($0.05 at $0.005/1,000 requests) + acceleration data-in fee.
- Direct Connect: flat port hourly rate ($0.30/hour for 1 Gbps) plus $0.02/GB data transfer out. Economical for sustained high-volume transfers (>50 TB/month from a fixed location).
Mindset
One-line takeaway: Transfer Acceleration routes uploads through the nearest CloudFront edge location over an optimized AWS backbone path — it excels for long-distance, high-latency transfers but costs $0.004-0.025/GB and is pointless for same-region traffic. Driven by three S3 realities:
-
Acceleration is a routing optimization, not a bandwidth boost. S3 Transfer Acceleration uses the CloudFront edge network to find the fastest path to the destination S3 bucket. The edge location receives the upload, then forwards it to S3 over the AWS backbone (optimized routing, larger TCP windows, fewer hops). For long-distance transfers (Asia to US, South America to EU), this can reduce transfer time by 2-10x. For same-region transfers (EU to EU, US to US), the improvement is negligible — and you pay the $/GB acceleration fee for nothing.
-
Cost scales with data volume, not speed. You pay per GB transferred through the accelerate endpoint. A 1 TB upload from Asia to a US bucket costs $25.00 ($0.025/GB x 1,024 GB). A 100 TB migration costs $2,500. Always run the speed comparison tool first to confirm acceleration provides a meaningful speedup before committing to the cost. For sustained high-volume transfers from a fixed location, Direct Connect is usually cheaper.
-
Multipart upload is the performance multiplier. Acceleration reduces per-connection latency. Multipart upload increases throughput by parallelizing across multiple connections. Together, they maximize transfer speed: each part is uploaded over an accelerated connection, and multiple parts run in parallel. Always use multipart upload for files > 100 MB when acceleration is enabled. The accelerate endpoint (
<bucket>.s3-accelerate.amazonaws.com) accepts standard multipart upload API calls.
Pre-flight: bucket metadata gate
Run before classification. Misclassifying these produces wrong plans.
Pagination: list-multipart-uploads paginates at 1,000/page —
drain --page-size / --starting-token to completion.
Live-account pre-flight (skip if offline plan audit):
aws s3api head-bucket --bucket <name>— confirm bucket exists and is accessible (200 OK).aws s3api get-bucket-location --bucket <name>— capture the bucket region. Verify it is a supported commercial region.aws s3api get-bucket-accelerate-configuration --bucket <name>— captureStatus(Enabled,Suspended, or null).aws s3api get-bucket-logging --bucket <name>— verify logging is configured for audit trail (advisory).aws s3api list-multipart-uploads --bucket <name>— capture in-flight multipart uploads (critical for disable-acceleration).aws cloudwatch get-metric-statistics --namespace AWS/S3 --metric-name BytesUploaded --dimensions Name=BucketName, Value=<name> --start-time <24h-ago> --end-time <now> --period 3600 --statistics Sum— capture recent upload volume for cost estimation.
Malformed input: if the input is invalid or missing required
fields, emit VERDICT: ERROR with REASON: Bucket configuration is not valid or is missing required fields — cannot plan. and
REMEDIATION: Re-fetch with aws s3api head-bucket --bucket <name> --output json and re-plan.
| Bucket attribute | Effect on operation |
|---|---|
Directory bucket (--xaz- suffix) |
BLOCKED — S3 Express One Zone does not support Transfer Acceleration. |
| Bucket in GovCloud / China region | BLOCKED — Transfer Acceleration not available in isolated regions. |
Status: Enabled |
Already accelerated. For enable: no-op or advisory. For disable: plan the disable. |
Status: Suspended |
Acceleration was enabled then suspended. Re-enable to resume. |
| In-flight multipart uploads (disable only) | BLOCKED — disabling acceleration while multipart uploads are in-flight via the accelerate endpoint will cause upload failures. |
Bucket policy denies s3:PutAccelerateConfiguration |
BLOCKED — update the bucket policy first. |
| Virtual-hosted-style incompatible | Advisory — the accelerate endpoint uses <bucket>.s3-accelerate.amazonaws.com. Ensure the client supports virtual-hosted-style addressing. |
| Bucket name with underscores | BLOCKED — underscores are not DNS-compatible; the accelerate endpoint requires DNS-compatible bucket names. |
Process — operation planning (apply in order)
Step 0: Expert heuristic — non-obvious S3 acceleration behaviors
Non-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/advanced-patterns.md. Load that reference before planning enable/disable, speed-comparison, or diagnose operations.
Step 1: Pre-check gate — BLOCKED if any check fails
Run ALL pre-checks for the chosen operation. If ANY fails, the verdict is BLOCKED with the failed checks in PRE_CHECKS. Do NOT execute.
For ALL operations:
- Bucket exists (
head-bucketreturns 200). - Bucket is accessible (caller has
s3:GetAccelerateConfiguration).
For enable-acceleration:
3. Bucket is NOT a directory bucket (no --xaz- suffix, not S3
Express One Zone).
4. Bucket region supports acceleration (commercial region, not
GovCloud or China).
5. Calling identity has s3:PutAccelerateConfiguration on the bucket.
6. Bucket name is DNS-compatible (lowercase letters, numbers, hyphens;
no underscores, no uppercase).
7. (Advisory) Cost acknowledgment: surface estimated $/GB based on
source region.
For disable-acceleration:
3. No in-flight multipart uploads using the accelerate endpoint
(list-multipart-uploads returns empty, or all uploads use the
standard endpoint).
4. Calling identity has s3:PutAccelerateConfiguration.
5. (Advisory) Confirm no SDK clients are configured with
use_accelerate_endpoint: true — they will fail after disable.
For speed-comparison (read-only, non-destructive): 3. Acceleration is enabled OR the operator plans to test before enabling. The speed comparison tool works on buckets with acceleration enabled. 4. Test files are small (< 1 MB) and do not affect production data.
For plan-multipart-upload (read-only planning): 3. Object size is known and > 100 MB (multipart is recommended for larger objects). 4. Acceleration is enabled on the target bucket (or planned to be enabled). 5. Checksum algorithm is specified (CRC32C recommended for performance, SHA-256 for compatibility).
For compare-direct-connect (read-only analysis): 3. Source location (data center or region) is known. 4. Transfer volume (GB/month) is estimated. 5. Direct Connect port speed (1 Gbps or 10 Gbps) is identified.
For diagnose-transfer (read-only):
3. Read get-bucket-accelerate-configuration, CloudWatch metrics,
and the failure-mode table to identify why acceleration is slow
or not working.
The full symptom / root cause / 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/error-handling.md. Consult it during diagnose-transfer before emitting a verdict.
Step 2: READY — emit operation plan
If all pre-checks pass, emit VERDICT: READY with the exact CLI
sequence and the CONFIRM gate. The plan includes:
- The exact AWS CLI command with all flags populated.
- The expected cost (per-GB rate x estimated volume).
- The accelerate endpoint to use in the SDK/client configuration.
- The expected side-effects (accelerate endpoint becomes available, standard endpoint unchanged).
- The CONFIRM gate prompt.
- The verification step (
get-bucket-accelerate-configuration+ endpoint reachability test).
Step 3: Execute behind CONFIRM gate
- MANDATORY CONFIRMATION GATE. Before any state-changing CLI
(
put-bucket-accelerate-configuration), emit:CONFIRM: About to <enable/disable> Transfer Acceleration on bucket <name> (region <region>). <Cost/speed impact>. Proceed? (yes/no). Do NOT execute until the operator confirms. - Capture pre-state for rollback:
aws s3api get-bucket-accelerate-configuration --bucket <name> --output json > /tmp/<name>-accel-pre-$(date +%s).json. - Execute the CLI.
put-bucket-accelerate-configurationis synchronous — it returns once the configuration is applied. Propagation to the DNS (accelerate endpoint resolving) can take 20-30 minutes for the first enable. - For multipart uploads: execute the
create-multipart-upload→upload-part(x N) →complete-multipart-uploadsequence with the accelerate endpoint configured.
Step 4: Post-verification — COMPLETED
After the CLI completes, run post-verification. ALL checks must pass
for COMPLETED.
get-bucket-accelerate-configuration --bucket <name>— confirmStatus: Enabled(orSuspendedfor disable).- Endpoint reachability:
aws s3 ls s3://<name>/ --endpoint-url https://<name>.s3-accelerate.amazonaws.com— confirm the accelerate endpoint resolves and responds. - CloudWatch
BytesUploadedmetric — confirm traffic is flowing through the accelerate endpoint (spike in BytesUploaded correlated with the upload time). - (For multipart uploads) Verify checksum: compare the object's
x-amz-checksum-crc32cwith the locally computed checksum. - Cost verification: confirm the CloudWatch BytesUploaded matches the expected volume and the estimated acceleration cost.
If ANY verification fails, emit VERDICT: ERROR with the failure
details — do not claim COMPLETED.
Output format (STRICT output contract — per operation)
OPERATION: <enable-acceleration | disable-acceleration | speed-comparison | plan-multipart-upload | compare-direct-connect | diagnose-transfer>
VERDICT: READY | BLOCKED | COMPLETED
TARGET: <bucket-name> (region <region>, account <account>)
PRE_CHECKS:
- [PASS] <check description>
- [FAIL] <check description> — <reason>
STEPS:
1. <CLI command with flags populated>
2. <wait / monitoring command>
3. <next step>
POST_VERIFY:
- [PASS] <verification description>
- [FAIL] <verification description> — <reason>
COST: <$X.XX per GB from <source-region> | $0.00 for direct>
NOTES: <speed comparison, multipart recommendation, monitoring>
Worked example — enable-acceleration
OPERATION: enable-acceleration
VERDICT: READY
TARGET: prod-data-lake (region us-east-1, account 111111111111)
PRE_CHECKS:
- [PASS] Bucket exists (head-bucket: 200 OK)
- [PASS] Not a directory bucket (standard bucket)
- [PASS] Region us-east-1 supports acceleration
- [PASS] Calling role has s3:PutAccelerateConfiguration
- [PASS] Bucket name is DNS-compatible (lowercase, hyphens)
- [INFO] Current Status: Suspended (not yet enabled)
- [INFO] Estimated uploaders: Asia Pacific (Tokyo, Singapore,
Sydney) and South America (Sao Paulo)
STEPS:
1. CONFIRM: About to enable Transfer Acceleration on bucket
prod-data-lake (us-east-1). Uploaders in Asia Pacific will
pay $0.025/GB; uploaders in North America $0.004/GB; Europe
$0.004/GB. The accelerate endpoint
(prod-data-lake.s3-accelerate.amazonaws.com) will become
available within 20-30 minutes. Proceed? (yes/no)
2. aws s3api put-bucket-accelerate-configuration \
--bucket prod-data-lake \
--accelerate-configuration Status=Enabled
3. Verify:
aws s3api get-bucket-accelerate-configuration \
--bucket prod-data-lake
POST_VERIFY:
- (pending execution)
COST: $0.025/GB (Asia Pacific uploaders), $0.004/GB (EU/NA uploaders)
NOTES:
- The accelerate endpoint DNS (prod-data-lake.s3-accelerate
.amazonaws.com) may take 20-30 minutes to propagate after
enabling. Test with a small upload before production use.
- Configure SDK clients with use_accelerate_endpoint: true or use
the endpoint URL directly.
- Use multipart upload for files > 100 MB to maximize throughput
with acceleration.
- Run the speed comparison tool first for each uploader region to
confirm acceleration provides a meaningful speedup.
Additional worked examples — disable-acceleration (with in-flight check), plan-multipart-upload with acceleration, and directory-bucket BLOCKED — live in references/worked-examples.md. Load that reference when formatting a verdict block for those operations.
Anti-Patterns — NEVER (top mistakes)
-
NEVER use the standard S3 endpoint after enabling acceleration. The accelerate endpoint (
<bucket>.s3-accelerate.amazonaws.com) is the only way to route through the edge network. Using<bucket>.s3.<region>.amazonaws.combypasses acceleration — you pay for the feature but get no speed benefit. Configure the SDK withuse_accelerate_endpoint: true. -
NEVER disable acceleration while multipart uploads are in-flight via the accelerate endpoint. The in-flight
upload-partcalls will fail withPermanentRedirectorNoSuchUpload. Always checklist-multipart-uploadsand complete or abort all active uploads before disabling. -
NEVER enable acceleration for same-region transfers. If the uploader and the bucket are in the same region (e.g., EU to EU, US-East to US-West), the edge network adds latency and cost with no speed benefit. Transfer Acceleration is designed for long-distance, high-latency transfers. Run the speed comparison tool first.
-
NEVER forget to specify checksums on accelerated multipart uploads. Accelerated uploads traverse the edge network and backbone — while TCP provides integrity per-hop, end-to-end checksum verification (CRC32C) ensures the object was not corrupted in transit. For multipart uploads, each part gets its own checksum; the final object checksum is aggregated.
-
NEVER assume acceleration is cheaper than Direct Connect for sustained high-volume transfers. At 50 TB/month from Asia to US, acceleration costs $1,280/month ($0.025/GB). A 1 Gbps Direct Connect port costs ~$220/month + $1,024 (50 TB x $0.0204/GB) = ~$1,244/month. At 100+ TB/month, Direct Connect is significantly cheaper.
-
NEVER use the accelerate endpoint for downloads unless you explicitly need the speed. Acceleration fees apply to both data IN and data OUT. For read-heavy workloads (many downloads), use CloudFront instead — it caches at the edge and reduces origin fetches.
-
NEVER attempt to enable acceleration on a bucket with underscores in the name. The accelerate endpoint requires DNS-compatible bucket names (lowercase letters, numbers, hyphens only). Underscores cause DNS resolution failures. Rename the bucket or use a standard endpoint.
-
NEVER assume
Status: Enabledmeans the endpoint is immediately ready. DNS propagation for the accelerate endpoint can take 20-30 minutes after the first enable. Test with a small upload before starting production transfers. -
NEVER skip the speed comparison tool for new acceleration use cases. The tool uploads and downloads small test files through both endpoints and reports the speed difference. If the speedup is less than 1.5x, acceleration is not worth the cost for that source region.
-
NEVER use acceleration with S3 Object Lambda. Object Lambda Access Points do not work with the accelerate endpoint. If the bucket has Object Lambda transformations, uploads via the accelerate endpoint bypass the transformation.
Pre-flight safety checks (run before any remediation CLI)
The full pre-flight safety checklist — confirm gate, pre-state capture, in-flight multipart check, DNS compatibility, cost acceptance, multipart preference — lives in references/diagnostic-commands.md. Run these before any remediation CLI.
Recent AWS features (2024-2026)
Recent 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/advanced-patterns.md. Load when a plan depends on recent service behavior.
References (load on demand)
- references/worked-examples.md — secondary worked examples: disable-acceleration (in-flight check), plan-multipart-upload with acceleration, directory-bucket BLOCKED
- references/error-handling.md — transfer failure-mode table (symptom / root cause / fix) for diagnose-transfer
- references/diagnostic-commands.md — pre-flight safety checks and pre-state capture commands
- references/advanced-patterns.md — Step-0 expert heuristics and recent AWS features (2024-2026)
- references/cost-and-speed-comparison.md — acceleration pricing by edge location, speed comparison, Direct Connect crossover
- references/multipart-upload-and-checksum.md — part-size selection, multipart lifecycle, checksum verification
Domain
AWS CloudOps / S3 Transfer Acceleration, Multipart Upload Optimization & Cross-Region Transfer Strategy.
AWS documentation
- S3 User Guide — https://docs.aws.amazon.com/AmazonS3/latest/userguide/
- Transfer Acceleration — https://docs.aws.amazon.com/AmazonS3/latest/userguide/transfer-acceleration.html
- Transfer Acceleration speed comparison — https://s3-accelerate-speedtest.s3-accelerate.amazonaws.com/en/accelerate-speed-comparsion.html
- Multipart upload — https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html
- S3 checksums — https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html
- S3 Express One Zone — https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html
- S3 pricing — https://aws.amazon.com/s3/pricing/
- Direct Connect pricing — https://aws.amazon.com/directconnect/pricing/
- S3 CLI Reference — https://docs.aws.amazon.com/cli/latest/reference/s3api/
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.