[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADVD60X4PCAPKSE58P9NDC":3,"skill-same:01M7ADVD60X4PCAPKSE58P9NDC":137},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer",null,"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.","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\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: xray-tracing-deployer\ndescription: '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.'\nlicense: Apache-2.0\ncompatibility: 'Requires an LLM agent runtime (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with xray, ec2, ecs, eks, lambda, iam, logs, and servicediscovery access. Works with Terraform aws_xray_* resources, CloudFormation AWS::XRay::* resources, and the AWS Distro for OpenTelemetry (ADOT) Collector.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Management\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, xray, distributed-tracing, cloudops, deploy, observability, sampling-rules, opentelemetry\n  dependencies: aws-orchestrator\n  keywords: aws, xray, x-ray, distributed-tracing, cloudops, deploy, provisioning, observability, daemon, sampling-rules, service-map, opentelemetry, adot, servicelens\n  when_to_use: Invoke when the user wants to enable X-Ray distributed tracing on a new application, add the X-Ray daemon to ECS \u002F EKS \u002F EC2 \u002F Lambda, create or validate custom sampling rules, instrument an SDK (Java, Python, Node.js, Go, .NET), set up CloudWatch ServiceLens, or migrate from X-Ray SDK to OpenTelemetry \u002F ADOT. Do NOT invoke for CloudWatch Logs metrics alone (use cloudwatch-alarm-auditor), for application performance monitoring without tracing (use cloudwatch-application-signals-deployer), or for pure log aggregation.\n---\n\n# X-Ray Tracing Deployer\n\nAn AWS CloudOps agent skill that deploys AWS X-Ray distributed tracing\nwith correct production defaults. Emits a READY_TO_DEPLOY checklist\nverifying every configuration item.\n\n## Quick navigation\n\n| Need | Section |\n|---|---|\n| What MUST be in the response | \"STRICT output contract\" |\n| Why the deployment order matters | \"Reasoning framework\" |\n| What to verify before deploying | \"Prerequisites\" |\n| The ordered deployment steps | \"Deployment procedure\" |\n| Common silent-failure pitfalls | \"NEVER\" |\n| Platform-specific defaults | \"Platform matrix\" |\n| 2024-2026 feature changes | \"Recent AWS features\" |\n| Deep daemon + sampling CLI | `references\u002Fdaemon-and-sampling-guide.md` |\n| SDK instrumentation, OTel, full NEVER | `references\u002Fsdk-instrumentation-guide.md` |\n\n## STRICT output contract\n\nWhen this skill is invoked with an X-Ray tracing deployment request, the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in \"Output\nformat\" using the literal all-caps labels `SERVICE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines.\n\n### Required output structure\n\n1. `SERVICE: \u003Capplication-name>` — the application being traced.\n2. `VERDICT: READY_TO_DEPLOY` OR `VERDICT: PREREQUISITES_MISSING`.\n3. `CHECKLIST:` followed by indented lines with status markers\n   (`[✓]`, `[✗]`, `[OPTIONAL]`, `[INPUT NEEDED]`).\n4. `VERIFICATION_COMMANDS:` followed by indented `aws xray ...` commands.\n\n### FORBIDDEN output patterns\n\n- **No prose preamble before `SERVICE:`** — first non-empty line MUST be\n  `SERVICE:`.\n- **No markdown variants of labels** — write `VERDICT:`, not `**VERDICT:**`,\n  `### Verdict`, or `` `VERDICT` ``.\n- **No swapping verdict tokens** — exactly `READY_TO_DEPLOY` or\n  `PREREQUISITES_MISSING`.\n- **No omitting `VERIFICATION_COMMANDS:`** — include even when\n  PREREQUISITES_MISSING.\n- **No extra sections after `VERIFICATION_COMMANDS:`** — the checklist\n  block is the entire response.\n- **No status marker drift** — use only `[✓]`, `[✗]`, `[OPTIONAL]`,\n  `[INPUT NEEDED]`.\n\n### Perfect example (copy the shape exactly)\n\n```text\nSERVICE: payments-api-prod\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓]      Platform — ECS Fargate, cluster payments-prod\n  [✓]      Daemon — aws-xray-daemon:4.1 sidecar (UDP 2000), task definition payments-xray-sidecar:3\n  [✓]      SDK instrumentation — Python 3.11, aws-xray-sdk 2.13, middleware on Flask app\n  [✓]      Sampling rule — default (reservoir 1\u002Fs, rate 5%), custom rule payments-checkout (reservoir 10\u002Fs, rate 100% on POST \u002Fcheckout)\n  [✓]      IAM execution role — payments-task-exec has xray:PutTraceSegments + xray:PutTelemetryRecords\n  [✓]      IAM task role — payments-task has xray:PutTraceSegments + xray:PutTelemetryRecords + xray:GetSamplingRules + xray:GetSamplingTargets\n  [✓]      Annotations — region, environment, customer_id (indexable)\n  [✓]      Metadata — request_body_size, response_status (not indexable, for correlation)\n  [✓]      Service map — generated from traces, 4 segments (ALB, payments-api, DynamoDB, SQS)\n  [✓]      CloudWatch ServiceLens — integrated, service map visible in CloudWatch console\n  [OPTIONAL] X-Ray group — payments-checkout-group (filter expression annotation.region = \"us-east-1\")\nVERIFICATION_COMMANDS:\n  aws xray get-sampling-rules\n  aws xray get-sampling-targets\n  aws ecs describe-task-definition --task-definition payments-xray-sidecar:3\n  aws ecs describe-services --cluster payments-prod --services payments-api-prod\n  aws xray get-service-graph --start-time 2026-08-10T00:00:00Z --end-time 2026-08-10T23:59:59Z\n```\n\n## Reasoning framework (why the deployment order matters)\n\n1. **IAM FIRST** — without `xray:PutTraceSegments` and\n   `xray:PutTelemetryRecords` on the application's runtime role, the SDK\n   generates traces but the daemon cannot upload them. Traces are silently\n   dropped. This is the #1 X-Ray deployment failure.\n2. **Daemon (or OTel Collector) SECOND** — the X-Ray SDK sends segment\n   documents to `127.0.0.1:2000` (UDP). If no daemon is listening, the\n   SDK silently drops the segment. No error, no log, no trace.\n3. **SDK instrumentation THIRD** — the SDK captures incoming requests\n   (HTTP framework middleware) and downstream calls (SDK patches). Without\n   SDK patches for downstream AWS calls, only the entry segment is\n   captured — no downstream dependencies appear in the service map.\n4. **Sampling rules FOURTH** — sampling rules control WHICH requests are\n   traced. Without a custom rule, the default rule (reservoir 1\u002Fs, rate\n   5%) is applied. For high-traffic endpoints, this is too low; for\n   critical endpoints (checkout, payment), set a custom rule with\n   100% sampling.\n5. **Groups + insights FIFTH** — groups are saved trace filters for\n   recurring queries. Insights auto-detect anomalies (latency spikes,\n   error rate increases). Apply AFTER traces are flowing.\n6. **ServiceLens SIXTH** — ServiceLens integrates X-Ray traces with\n   CloudWatch metrics and logs. It is enabled at the account level, no\n   per-service config needed.\n\n## Prerequisites (verify before deployment)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| **IAM role with X-Ray permissions** | App runtime role needs `xray:PutTraceSegments`, `xray:PutTelemetryRecords`, `xray:GetSamplingRules`, `xray:GetSamplingTargets`. Without these, traces are silently dropped. | `aws iam list-attached-role-policies --role-name \u003Crole>` + `aws iam list-role-policies --role-name \u003Crole>` |\n| **X-Ray daemon \u002F OTel Collector** | Must be running and listening on UDP 2000 (X-Ray daemon) or gRPC 4317 (OTel Collector). Without it, the SDK drops segments. | `aws ecs describe-task-definition` (ECS) \u002F `kubectl get daemonset` (EKS) \u002F `systemctl status xray` (EC2) |\n| **SDK installed + middleware enabled** | The SDK must be a dependency AND the middleware\u002Fpatcher must be active. Installing the package without enabling the middleware captures nothing. | Check `requirements.txt` \u002F `package.json` \u002F `pom.xml` for `aws-xray-sdk` or `opentelemetry-*` |\n| **AWS region with X-Ray endpoint** | X-Ray is regional. The daemon resolves the regional endpoint. Ensure the region supports X-Ray. | `aws xray get-sampling-rules --region \u003Cregion>` |\n| **VPC endpoints (if private)** | If the app runs in a private VPC without NAT Gateway, an X-Ray VPC interface endpoint is needed. | `aws ec2 describe-vpc-endpoints --filter Name=service-name,Values=com.amazonaws.\u003Cregion>.xray` |\n| **ECS task definition (if ECS)** | The daemon must be a sidecar container in the SAME task definition as the app. | `aws ecs describe-task-definition --task-definition \u003Cfamily>` |\n| **EKS DaemonSet (if EKS)** | The daemon runs as a DaemonSet (one pod per node). The app pod's traffic to the daemon is via the node IP. | `kubectl get daemonset -n kube-system aws-xray-daemon` |\n| **Lambda layer \u002F Powertools (if Lambda)** | Lambda does NOT need the daemon — the runtime injects it. Use the X-Ray Lambda layer or Powertools for tracing. | `aws lambda get-function-configuration --function-name \u003Cname> --query 'Layers'` |\n| **KMS key (if encryption)** | X-Ray encrypts at rest with AWS-owned KMS by default. CMK needs grant on the X-Ray service role. | `aws xray get-encryption-config` |\n\n## Deployment procedure (apply in order)\n\n### Step 1: IAM permissions (application runtime role)\n\nThe application's runtime role (ECS task role, EC2 instance profile,\nLambda execution role, EKS pod IRSA role) needs X-Ray permissions.\n\n```bash\naws iam attach-role-policy \\\n  --role-name \u003Capp-role> \\\n  --policy-arn arn:aws:iam::aws:policy\u002FAWSXRayDaemonWriteAccess\n```\n\n`AWSXRayDaemonWriteAccess` grants:\n- `xray:PutTraceSegments`\n- `xray:PutTelemetryRecords`\n- `xray:GetSamplingRules`\n- `xray:GetSamplingTargets`\n- `xray:GetEncryptionConfig`\n\nIt does NOT grant read access to traces (`BatchGetTraces`,\n`GetServiceGraph`). Those are for operators \u002F CI roles, not the app.\n\nFor custom inline policy:\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [{\n    \"Effect\": \"Allow\",\n    \"Action\": [\n      \"xray:PutTraceSegments\",\n      \"xray:PutTelemetryRecords\",\n      \"xray:GetSamplingRules\",\n      \"xray:GetSamplingTargets\",\n      \"xray:GetEncryptionConfig\"\n    ],\n    \"Resource\": \"*\"\n  }]\n}\n```\n\n**NEVER forget `xray:GetSamplingRules` and `xray:GetSamplingTargets`.**\nWithout these, the SDK cannot fetch sampling rules and falls back to\nlocal default sampling (1\u002Fs, fixed). The central sampling rules you\nconfigure in the console are NEVER applied.\n\n### Step 2: X-Ray daemon deployment (by platform)\n\n#### EC2 (systemd)\n\nEC2 systemd install (daemon download, unit file, enable): [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for EC2 deployments.\n\n#### ECS Fargate (sidecar container)\n\nECS Fargate sidecar container definition (JSON) and localhost UDP 2000 rationale: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for ECS Fargate deployments.\n\n#### ECS EC2 (daemon as a service, NOT sidecar)\n\nOn ECS EC2, you can run the daemon as a separate ECS service (one daemon\ntask per instance) or a sidecar. The daemon-as-a-service pattern saves\nmemory but requires the app to send traces to the HOST IP on port 2000\n(NOT localhost). Set the `AWS_XRAY_DAEMON_ADDRESS` env var to\n`\u003Chost-ip>:2000`.\n\n#### EKS \u002F Kubernetes (DaemonSet)\n\nEKS DaemonSet manifest and node-IP downward-API injection: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for EKS deployments.\n\n#### Lambda (built-in — no daemon needed)\n\nLambda enable-tracing and Powertools layer CLI: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for Lambda deployments.\n\n### Step 3: SDK instrumentation (by language)\n\nFull code examples in `references\u002Fsdk-instrumentation-guide.md`.\n\n| Language | Package | Middleware |\n|---|---|---|\n| **Python** | `aws-xray-sdk` | `XRayMiddleware(app)` for Flask\u002FDjango, `@xray_recorder.capture()` for functions |\n| **Node.js** | `aws-xray-sdk-core` | `aws-xray-sdk.express.openSegment(\u003Cname>)` for Express, `AWSXRay.captureAWS()` for AWS SDK |\n| **Java** | `aws-xray-recorder-sdk-core` | `@XRayEnabled` on JAX-RS resources, `AWSXRay.beginSegment()` for custom |\n| **Go** | `github.com\u002Faws\u002Faws-xray-sdk-go` | `xray.Handler(nil, http.HandlerFunc(handler))` for HTTP |\n| **.NET** | `AWSXRayRecorder` | `app.UseXRay(\"\u003Cname>\")` for ASP.NET Core |\n\n**Critical SDK patterns:**\n\n1. **Patch AWS SDK** — without `AWSXRay.captureAWS(AWS)` (Node.js) or\n   `aws_xray_sdk.core.patch_all()` (Python), downstream AWS calls do NOT\n   generate subsegments. The service map shows only the entry point.\n2. **Patch HTTP clients** — patch `requests` (Python), `http`\u002F`https`\n   (Node.js) to trace outbound HTTP calls to non-AWS APIs.\n3. **Annotations vs metadata** — annotations are indexable (use for\n   `customer_id`, `region`, `environment`). Metadata is NOT indexable\n   (use for request\u002Fresponse bodies, debug info).\n\n### Step 4: Sampling rules\n\n```bash\n# Default rule (always present, applied to all services without a custom match)\naws xray create-sampling-rule --cli-input-json '{\n  \"SamplingRule\": {\n    \"RuleName\": \"Default\",\n    \"RuleARN\": \"\",\n    \"ResourceARN\": \"*\",\n    \"Priority\": 10000,\n    \"FixedRate\": 0.05,\n    \"ReservoirSize\": 1,\n    \"ServiceName\": \"*\",\n    \"ServiceType\": \"*\",\n    \"Host\": \"*\",\n    \"HTTPMethod\": \"*\",\n    \"URLPath\": \"*\",\n    \"Version\": 1,\n    \"Attributes\": {}\n  }\n}'\n\n# Custom rule — 100% sampling for checkout endpoint\naws xray create-sampling-rule --cli-input-json '{\n  \"SamplingRule\": {\n    \"RuleName\": \"payments-checkout-100\",\n    \"ResourceARN\": \"*\",\n    \"Priority\": 100,\n    \"FixedRate\": 1.0,\n    \"ReservoirSize\": 10,\n    \"ServiceName\": \"payments-api\",\n    \"ServiceType\": \"*\",\n    \"Host\": \"*\",\n    \"HTTPMethod\": \"POST\",\n    \"URLPath\": \"\u002Fcheckout\u002F*\",\n    \"Version\": 1,\n    \"Attributes\": {}\n  }\n}'\n```\n\n**Sampling rule semantics:**\n- **Priority** — lower number = higher priority. Rules are evaluated in\n  priority order. The FIRST match wins.\n- **ReservoirSize** — guaranteed traces per second BEFORE the rate\n  applies. The reservoir ensures at least N traces\u002Fs even at low traffic.\n- **FixedRate** — fraction of requests ABOVE the reservoir to sample.\n  `1.0` = 100%, `0.05` = 5%.\n- **Matching** — a rule matches if ALL of `ServiceName`, `ServiceType`,\n  `Host`, `HTTPMethod`, `URLPath`, and `Attributes` match. `*` is\n  wildcard.\n\n**NEVER set FixedRate=1.0 on the Default rule for a high-traffic service.**\nThis generates massive trace volume, X-Ray costs scale with trace count,\nand the service map becomes noisy. Use a custom rule scoped to specific\nendpoints.\n\n### Step 5: Annotations and metadata\n\n```python\nfrom aws_xray_sdk.core import xray_recorder\n\n# Annotation — indexable, use for filtering in X-Ray console\nxray_recorder.put_annotation(\"customer_id\", \"cust-12345\")\nxray_recorder.put_annotation(\"region\", \"us-east-1\")\n\n# Metadata — NOT indexable, for debug context\nxray_recorder.put_metadata(\"request_body_size\", 1024)\nxray_recorder.put_metadata(\"feature_flags\", {\"new_checkout\": True})\n```\n\nAnnotations are indexed and searchable in the X-Ray console. Metadata\nis visible on individual traces but NOT searchable. Use annotations for\nfields you will filter on; use metadata for everything else.\n\n### Step 6: Groups and insights\n\n```bash\n# Group — saved filter expression\naws xray create-group \\\n  --group-name \"payments-checkout-group\" \\\n  --filter-expression 'annotation.region = \"us-east-1\" AND service(\"payments-api\") { fault = true }'\n\n# Insights — auto-detect anomalies (enabled by default, no config needed)\naws xray get-insight --insight-id \u003Cid>\n```\n\nGroups are saved filter expressions for recurring queries. Insights\nauto-detect latency spikes, error rate increases, and anomalous behavior.\nInsights are enabled by default — no config needed.\n\n### Step 7: CloudWatch ServiceLens\n\nServiceLens integrates X-Ray traces with CloudWatch metrics and logs. It\nis enabled at the account level — no per-service config needed. To\nverify:\n\n```bash\naws cloudwatch describe-alarms-for-metric \\\n  --namespace AWS\u002FXRay \\\n  --metric-name FaultRate\n```\n\nThe ServiceLens service map is visible in the CloudWatch console under\n\"ServiceLens\" > \"Service Map\".\n\n### Step 8: Verification\n\n```bash\naws xray get-sampling-rules\naws xray get-sampling-targets\naws xray get-service-graph --start-time \u003CISO> --end-time \u003CISO>\naws xray get-trace-summaries --start-time \u003CISO> --end-time \u003CISO>\naws xray get-groups\naws xray get-insight-summaries --start-time \u003CISO> --end-time \u003CISO>\n```\n\n## Latest X-Ray features (2024-2026)\n\n2024-2026 feature delta (Powertools v2, ADOT Collector, attribute-based sampling, Insights anomaly detection, cross-account ServiceLens, CMK, daemon 4.x maintenance mode, W3C): [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when choosing components.\n\n## Platform matrix\n\n| Platform | Daemon | SDK address | IAM role | Notes |\n|---|---|---|---|---|\n| **EC2** | systemd service | `127.0.0.1:2000` | Instance profile | Daemon runs as a background process |\n| **ECS Fargate** | Sidecar container | `127.0.0.1:2000` | Task role | Same task definition (awsvpc shared network) |\n| **ECS EC2** | Sidecar or daemon-service | `127.0.0.1:2000` or `\u003Chost-ip>:2000` | Task role | Daemon-service saves memory; sidecar is simpler |\n| **EKS** | DaemonSet | `\u003Cnode-ip>:2000` (downward API) | Pod IRSA role | DaemonSet = one daemon per node |\n| **Lambda** | Built-in (no daemon) | N\u002FA | Execution role | Enable `TracingConfig Mode=Active` |\n| **App Runner** | N\u002FA (managed) | N\u002FA | Instance role | Enable observability config with `Vendor=AWSXRay` |\n| **Elastic Beanstalk** | Instance or sidecar | `127.0.0.1:2000` | Instance profile | EB config has an X-Ray option |\n\n## NEVER (top 5 — full list of 14 in references)\n\n- NEVER deploy the X-Ray SDK without `xray:GetSamplingRules` and\n  `xray:GetSamplingTargets` on the application's runtime role. The SDK\n  fetches central sampling rules from the X-Ray API. Without these\n  permissions, the SDK falls back to local default (1\u002Fs, fixed) and the\n  rules you configure in the console are NEVER applied. #1 silent-failure.\n- NEVER run the X-Ray daemon \u002F OTel Collector without\n  `xray:PutTraceSegments` and `xray:PutTelemetryRecords`. The SDK\n  generates segments and sends them to the daemon, but the daemon\n  uploads them. Without upload permissions, traces are silently dropped.\n- NEVER set `FixedRate=1.0` on the Default sampling rule for high-traffic\n  services. This generates massive trace volume. X-Ray charges per trace\n  ingested. Use a custom rule scoped to specific endpoints.\n- NEVER forget to patch the AWS SDK (`AWSXRay.captureAWS()` \u002F\n  `aws_xray_sdk.core.patch_all()`). Without the patch, downstream AWS\n  calls (DynamoDB, S3, SQS) do NOT generate subsegments. The service map\n  shows only the entry point — no dependencies.\n- NEVER deploy the daemon as a separate ECS service on Fargate and point\n  the app to it via DNS. Fargate tasks cannot reach each other on\n  localhost. The daemon MUST be a sidecar in the same task definition.\n\n## Expert heuristic — choosing X-Ray SDK vs ADOT, sampling, and annotations\n\nSDK-vs-ADOT choice, reservoir\u002Frate tuning, annotation discipline, trace-context propagation, and cost control: [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when making design decisions.\n\n## Pre-flight safety checks (run before any deployment CLI)\n\n- **Confirm IAM role has all 5 X-Ray actions** (PutTraceSegments,\n  PutTelemetryRecords, GetSamplingRules, GetSamplingTargets,\n  GetEncryptionConfig). Use `AWSXRayDaemonWriteAccess` managed policy.\n- **Confirm daemon \u002F OTel Collector is running** and listening on UDP\n  2000 (X-Ray) or gRPC 4317 (OTel).\n- **Confirm SDK package is installed** and the middleware\u002Fpatcher is\n  active in the code.\n- **Confirm AWS SDK is patched** for downstream call tracing.\n- **Confirm trace context propagation** across all service boundaries.\n- **Confirm sampling rules** (check the Default rule and any custom\n  rules).\n- **Confirm X-Ray encryption config** (AWS-owned key vs CMK).\n- **For existing services, capture current sampling config for rollback.**\n\nFull CLI sequences for all checks in `references\u002Fdaemon-and-sampling-guide.md`.\n\n## Output format — MANDATORY literal labels\n\nWhen invoked with a tracing deployment request, your ENTIRE response MUST\nbe the checklist block below. The labels are **case-sensitive all-caps\nkeywords**. Do NOT write a preamble. Start with `SERVICE:` and stop after\nthe `VERIFICATION_COMMANDS:` block.\n\n```text\nSERVICE: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓]      Platform — \u003Cec2|ecs|eks|lambda|app-runner>, \u003Ccluster\u002Ffunction\u002Fdetail>\n  [✓]      Daemon — \u003Cdaemon-image:version> \u003Cdeployment-mode> (UDP 2000)\n  [✓]      SDK instrumentation — \u003Clanguage> \u003Cversion>, \u003Cpackage> \u003Cversion>, \u003Cmiddleware>\n  [✓]      Sampling rule — default (reservoir \u003Cn>\u002Fs, rate \u003Cp>%), custom rule \u003Cname> (reservoir \u003Cn>\u002Fs, rate \u003Cp>% on \u003Cmatch>)\n  [✓]      IAM role — \u003Crole-name> has xray:PutTraceSegments + PutTelemetryRecords + GetSamplingRules + GetSamplingTargets\n  [✓]      Annotations — \u003Cindexable fields>\n  [✓]      Metadata — \u003Cdebug fields>\n  [✓]      Service map — generated from traces, \u003Csegment-count> segments\n  [✓]      CloudWatch ServiceLens — integrated\n  [OPTIONAL] X-Ray group — \u003Cgroup-name> (filter expression \u003Cexpr>)\nVERIFICATION_COMMANDS:\n  aws xray get-sampling-rules\n  aws xray get-sampling-targets\n  aws xray get-service-graph --start-time \u003CISO> --end-time \u003CISO>\n  aws ecs describe-task-definition --task-definition \u003Cfamily>\n```\n\n**Status marker semantics:**\n- `[✓]` — applied and verified.\n- `[✗]` — NOT applied or misconfigured. Cite the gap.\n- `[OPTIONAL]` — recommended but not required.\n- `[INPUT NEEDED]` — prerequisite value missing; operator must provide.\n\n**PREREQUISITES_MISSING verdict:** if any REQUIRED prerequisite is missing\n(IAM permissions, daemon \u002F Collector not running, SDK not instrumented,\nsampling rules not configured), the verdict is `PREREQUISITES_MISSING`.\n\n## References (load on demand)\n\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — 2024-2026 feature delta, SDK-vs-ADOT heuristics, edge-case catalog\n- [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md) — per-platform daemon deployment blocks (EC2, ECS Fargate, EKS, Lambda) plus the full daemon\u002Fsampling CLI sequence\n- [SDK instrumentation guide](references\u002Fsdk-instrumentation-guide.md) — language-by-language instrumentation and AWS SDK patching\n\n## Domain\n\nAWS CloudOps \u002F X-Ray Distributed Tracing Observability Provisioning.\n\n## Edge-case handling\n\nEdge-case catalog (cross-account, SQS\u002FEventBridge propagation, ECS EC2 host-IP, EKS limits, Lambda cold start, OTel migration, high-cardinality annotations, CMK grants): [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when deployment hits a corner case.\n\n## AWS documentation\n\n- **AWS X-Ray Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Faws-xray.html\n- **X-Ray Daemon** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-daemon.html\n- **X-Ray SDK** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-sdk.html\n- **X-Ray Sampling Rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-console-sampling.html\n- **X-Ray Service Map** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-services.html\n- **X-Ray Groups and Insights** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-insights.html\n- **CloudWatch ServiceLens** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonCloudWatch\u002Flatest\u002Fmonitoring\u002FServiceLens.html\n- **AWS Distro for OpenTelemetry (ADOT)** — https:\u002F\u002Faws-otel.github.io\u002F\n- **Lambda Powertools Tracing** — https:\u002F\u002Fdocs.powertools.aws.dev\u002Flambda\u002Fpython\u002Flatest\u002Fcore\u002Ftracer\u002F\n- **X-Ray CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fxray\u002F\n\n## References\n\n- `references\u002Fdaemon-and-sampling-guide.md` — full copy-pasteable CLI\n  command sequence for daemon deployment (EC2, ECS, EKS, Lambda),\n  sampling rule creation (default + custom), IAM role setup, group\n  creation, and Terraform \u002F CloudFormation equivalents.\n\n- `references\u002Fsdk-instrumentation-guide.md` — deep reference on SDK\n  instrumentation (Python, Node.js, Java, Go, .NET), AWS SDK patching,\n  annotation vs metadata, trace context propagation, OpenTelemetry \u002F ADOT\n  migration, full NEVER list, edge-case handling, and pre-flight safety\n  CLI.\n","# X-Ray Tracing Deployer\n\nAn AWS CloudOps agent skill that deploys AWS X-Ray distributed tracing\nwith correct production defaults. Emits a READY_TO_DEPLOY checklist\nverifying every configuration item.\n\n## Quick navigation\n\n| Need | Section |\n|---|---|\n| What MUST be in the response | \"STRICT output contract\" |\n| Why the deployment order matters | \"Reasoning framework\" |\n| What to verify before deploying | \"Prerequisites\" |\n| The ordered deployment steps | \"Deployment procedure\" |\n| Common silent-failure pitfalls | \"NEVER\" |\n| Platform-specific defaults | \"Platform matrix\" |\n| 2024-2026 feature changes | \"Recent AWS features\" |\n| Deep daemon + sampling CLI | `references\u002Fdaemon-and-sampling-guide.md` |\n| SDK instrumentation, OTel, full NEVER | `references\u002Fsdk-instrumentation-guide.md` |\n\n## STRICT output contract\n\nWhen this skill is invoked with an X-Ray tracing deployment request, the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in \"Output\nformat\" using the literal all-caps labels `SERVICE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines.\n\n### Required output structure\n\n1. `SERVICE: \u003Capplication-name>` — the application being traced.\n2. `VERDICT: READY_TO_DEPLOY` OR `VERDICT: PREREQUISITES_MISSING`.\n3. `CHECKLIST:` followed by indented lines with status markers\n   (`[✓]`, `[✗]`, `[OPTIONAL]`, `[INPUT NEEDED]`).\n4. `VERIFICATION_COMMANDS:` followed by indented `aws xray ...` commands.\n\n### FORBIDDEN output patterns\n\n- **No prose preamble before `SERVICE:`** — first non-empty line MUST be\n  `SERVICE:`.\n- **No markdown variants of labels** — write `VERDICT:`, not `**VERDICT:**`,\n  `### Verdict`, or `` `VERDICT` ``.\n- **No swapping verdict tokens** — exactly `READY_TO_DEPLOY` or\n  `PREREQUISITES_MISSING`.\n- **No omitting `VERIFICATION_COMMANDS:`** — include even when\n  PREREQUISITES_MISSING.\n- **No extra sections after `VERIFICATION_COMMANDS:`** — the checklist\n  block is the entire response.\n- **No status marker drift** — use only `[✓]`, `[✗]`, `[OPTIONAL]`,\n  `[INPUT NEEDED]`.\n\n### Perfect example (copy the shape exactly)\n\n```text\nSERVICE: payments-api-prod\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓]      Platform — ECS Fargate, cluster payments-prod\n  [✓]      Daemon — aws-xray-daemon:4.1 sidecar (UDP 2000), task definition payments-xray-sidecar:3\n  [✓]      SDK instrumentation — Python 3.11, aws-xray-sdk 2.13, middleware on Flask app\n  [✓]      Sampling rule — default (reservoir 1\u002Fs, rate 5%), custom rule payments-checkout (reservoir 10\u002Fs, rate 100% on POST \u002Fcheckout)\n  [✓]      IAM execution role — payments-task-exec has xray:PutTraceSegments + xray:PutTelemetryRecords\n  [✓]      IAM task role — payments-task has xray:PutTraceSegments + xray:PutTelemetryRecords + xray:GetSamplingRules + xray:GetSamplingTargets\n  [✓]      Annotations — region, environment, customer_id (indexable)\n  [✓]      Metadata — request_body_size, response_status (not indexable, for correlation)\n  [✓]      Service map — generated from traces, 4 segments (ALB, payments-api, DynamoDB, SQS)\n  [✓]      CloudWatch ServiceLens — integrated, service map visible in CloudWatch console\n  [OPTIONAL] X-Ray group — payments-checkout-group (filter expression annotation.region = \"us-east-1\")\nVERIFICATION_COMMANDS:\n  aws xray get-sampling-rules\n  aws xray get-sampling-targets\n  aws ecs describe-task-definition --task-definition payments-xray-sidecar:3\n  aws ecs describe-services --cluster payments-prod --services payments-api-prod\n  aws xray get-service-graph --start-time 2026-08-10T00:00:00Z --end-time 2026-08-10T23:59:59Z\n```\n\n## Reasoning framework (why the deployment order matters)\n\n1. **IAM FIRST** — without `xray:PutTraceSegments` and\n   `xray:PutTelemetryRecords` on the application's runtime role, the SDK\n   generates traces but the daemon cannot upload them. Traces are silently\n   dropped. This is the #1 X-Ray deployment failure.\n2. **Daemon (or OTel Collector) SECOND** — the X-Ray SDK sends segment\n   documents to `127.0.0.1:2000` (UDP). If no daemon is listening, the\n   SDK silently drops the segment. No error, no log, no trace.\n3. **SDK instrumentation THIRD** — the SDK captures incoming requests\n   (HTTP framework middleware) and downstream calls (SDK patches). Without\n   SDK patches for downstream AWS calls, only the entry segment is\n   captured — no downstream dependencies appear in the service map.\n4. **Sampling rules FOURTH** — sampling rules control WHICH requests are\n   traced. Without a custom rule, the default rule (reservoir 1\u002Fs, rate\n   5%) is applied. For high-traffic endpoints, this is too low; for\n   critical endpoints (checkout, payment), set a custom rule with\n   100% sampling.\n5. **Groups + insights FIFTH** — groups are saved trace filters for\n   recurring queries. Insights auto-detect anomalies (latency spikes,\n   error rate increases). Apply AFTER traces are flowing.\n6. **ServiceLens SIXTH** — ServiceLens integrates X-Ray traces with\n   CloudWatch metrics and logs. It is enabled at the account level, no\n   per-service config needed.\n\n## Prerequisites (verify before deployment)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| **IAM role with X-Ray permissions** | App runtime role needs `xray:PutTraceSegments`, `xray:PutTelemetryRecords`, `xray:GetSamplingRules`, `xray:GetSamplingTargets`. Without these, traces are silently dropped. | `aws iam list-attached-role-policies --role-name \u003Crole>` + `aws iam list-role-policies --role-name \u003Crole>` |\n| **X-Ray daemon \u002F OTel Collector** | Must be running and listening on UDP 2000 (X-Ray daemon) or gRPC 4317 (OTel Collector). Without it, the SDK drops segments. | `aws ecs describe-task-definition` (ECS) \u002F `kubectl get daemonset` (EKS) \u002F `systemctl status xray` (EC2) |\n| **SDK installed + middleware enabled** | The SDK must be a dependency AND the middleware\u002Fpatcher must be active. Installing the package without enabling the middleware captures nothing. | Check `requirements.txt` \u002F `package.json` \u002F `pom.xml` for `aws-xray-sdk` or `opentelemetry-*` |\n| **AWS region with X-Ray endpoint** | X-Ray is regional. The daemon resolves the regional endpoint. Ensure the region supports X-Ray. | `aws xray get-sampling-rules --region \u003Cregion>` |\n| **VPC endpoints (if private)** | If the app runs in a private VPC without NAT Gateway, an X-Ray VPC interface endpoint is needed. | `aws ec2 describe-vpc-endpoints --filter Name=service-name,Values=com.amazonaws.\u003Cregion>.xray` |\n| **ECS task definition (if ECS)** | The daemon must be a sidecar container in the SAME task definition as the app. | `aws ecs describe-task-definition --task-definition \u003Cfamily>` |\n| **EKS DaemonSet (if EKS)** | The daemon runs as a DaemonSet (one pod per node). The app pod's traffic to the daemon is via the node IP. | `kubectl get daemonset -n kube-system aws-xray-daemon` |\n| **Lambda layer \u002F Powertools (if Lambda)** | Lambda does NOT need the daemon — the runtime injects it. Use the X-Ray Lambda layer or Powertools for tracing. | `aws lambda get-function-configuration --function-name \u003Cname> --query 'Layers'` |\n| **KMS key (if encryption)** | X-Ray encrypts at rest with AWS-owned KMS by default. CMK needs grant on the X-Ray service role. | `aws xray get-encryption-config` |\n\n## Deployment procedure (apply in order)\n\n### Step 1: IAM permissions (application runtime role)\n\nThe application's runtime role (ECS task role, EC2 instance profile,\nLambda execution role, EKS pod IRSA role) needs X-Ray permissions.\n\n```bash\naws iam attach-role-policy \\\n  --role-name \u003Capp-role> \\\n  --policy-arn arn:aws:iam::aws:policy\u002FAWSXRayDaemonWriteAccess\n```\n\n`AWSXRayDaemonWriteAccess` grants:\n- `xray:PutTraceSegments`\n- `xray:PutTelemetryRecords`\n- `xray:GetSamplingRules`\n- `xray:GetSamplingTargets`\n- `xray:GetEncryptionConfig`\n\nIt does NOT grant read access to traces (`BatchGetTraces`,\n`GetServiceGraph`). Those are for operators \u002F CI roles, not the app.\n\nFor custom inline policy:\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [{\n    \"Effect\": \"Allow\",\n    \"Action\": [\n      \"xray:PutTraceSegments\",\n      \"xray:PutTelemetryRecords\",\n      \"xray:GetSamplingRules\",\n      \"xray:GetSamplingTargets\",\n      \"xray:GetEncryptionConfig\"\n    ],\n    \"Resource\": \"*\"\n  }]\n}\n```\n\n**NEVER forget `xray:GetSamplingRules` and `xray:GetSamplingTargets`.**\nWithout these, the SDK cannot fetch sampling rules and falls back to\nlocal default sampling (1\u002Fs, fixed). The central sampling rules you\nconfigure in the console are NEVER applied.\n\n### Step 2: X-Ray daemon deployment (by platform)\n\n#### EC2 (systemd)\n\nEC2 systemd install (daemon download, unit file, enable): [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for EC2 deployments.\n\n#### ECS Fargate (sidecar container)\n\nECS Fargate sidecar container definition (JSON) and localhost UDP 2000 rationale: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for ECS Fargate deployments.\n\n#### ECS EC2 (daemon as a service, NOT sidecar)\n\nOn ECS EC2, you can run the daemon as a separate ECS service (one daemon\ntask per instance) or a sidecar. The daemon-as-a-service pattern saves\nmemory but requires the app to send traces to the HOST IP on port 2000\n(NOT localhost). Set the `AWS_XRAY_DAEMON_ADDRESS` env var to\n`\u003Chost-ip>:2000`.\n\n#### EKS \u002F Kubernetes (DaemonSet)\n\nEKS DaemonSet manifest and node-IP downward-API injection: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for EKS deployments.\n\n#### Lambda (built-in — no daemon needed)\n\nLambda enable-tracing and Powertools layer CLI: [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md).\nLoad on demand for Lambda deployments.\n\n### Step 3: SDK instrumentation (by language)\n\nFull code examples in `references\u002Fsdk-instrumentation-guide.md`.\n\n| Language | Package | Middleware |\n|---|---|---|\n| **Python** | `aws-xray-sdk` | `XRayMiddleware(app)` for Flask\u002FDjango, `@xray_recorder.capture()` for functions |\n| **Node.js** | `aws-xray-sdk-core` | `aws-xray-sdk.express.openSegment(\u003Cname>)` for Express, `AWSXRay.captureAWS()` for AWS SDK |\n| **Java** | `aws-xray-recorder-sdk-core` | `@XRayEnabled` on JAX-RS resources, `AWSXRay.beginSegment()` for custom |\n| **Go** | `github.com\u002Faws\u002Faws-xray-sdk-go` | `xray.Handler(nil, http.HandlerFunc(handler))` for HTTP |\n| **.NET** | `AWSXRayRecorder` | `app.UseXRay(\"\u003Cname>\")` for ASP.NET Core |\n\n**Critical SDK patterns:**\n\n1. **Patch AWS SDK** — without `AWSXRay.captureAWS(AWS)` (Node.js) or\n   `aws_xray_sdk.core.patch_all()` (Python), downstream AWS calls do NOT\n   generate subsegments. The service map shows only the entry point.\n2. **Patch HTTP clients** — patch `requests` (Python), `http`\u002F`https`\n   (Node.js) to trace outbound HTTP calls to non-AWS APIs.\n3. **Annotations vs metadata** — annotations are indexable (use for\n   `customer_id`, `region`, `environment`). Metadata is NOT indexable\n   (use for request\u002Fresponse bodies, debug info).\n\n### Step 4: Sampling rules\n\n```bash\n# Default rule (always present, applied to all services without a custom match)\naws xray create-sampling-rule --cli-input-json '{\n  \"SamplingRule\": {\n    \"RuleName\": \"Default\",\n    \"RuleARN\": \"\",\n    \"ResourceARN\": \"*\",\n    \"Priority\": 10000,\n    \"FixedRate\": 0.05,\n    \"ReservoirSize\": 1,\n    \"ServiceName\": \"*\",\n    \"ServiceType\": \"*\",\n    \"Host\": \"*\",\n    \"HTTPMethod\": \"*\",\n    \"URLPath\": \"*\",\n    \"Version\": 1,\n    \"Attributes\": {}\n  }\n}'\n\n# Custom rule — 100% sampling for checkout endpoint\naws xray create-sampling-rule --cli-input-json '{\n  \"SamplingRule\": {\n    \"RuleName\": \"payments-checkout-100\",\n    \"ResourceARN\": \"*\",\n    \"Priority\": 100,\n    \"FixedRate\": 1.0,\n    \"ReservoirSize\": 10,\n    \"ServiceName\": \"payments-api\",\n    \"ServiceType\": \"*\",\n    \"Host\": \"*\",\n    \"HTTPMethod\": \"POST\",\n    \"URLPath\": \"\u002Fcheckout\u002F*\",\n    \"Version\": 1,\n    \"Attributes\": {}\n  }\n}'\n```\n\n**Sampling rule semantics:**\n- **Priority** — lower number = higher priority. Rules are evaluated in\n  priority order. The FIRST match wins.\n- **ReservoirSize** — guaranteed traces per second BEFORE the rate\n  applies. The reservoir ensures at least N traces\u002Fs even at low traffic.\n- **FixedRate** — fraction of requests ABOVE the reservoir to sample.\n  `1.0` = 100%, `0.05` = 5%.\n- **Matching** — a rule matches if ALL of `ServiceName`, `ServiceType`,\n  `Host`, `HTTPMethod`, `URLPath`, and `Attributes` match. `*` is\n  wildcard.\n\n**NEVER set FixedRate=1.0 on the Default rule for a high-traffic service.**\nThis generates massive trace volume, X-Ray costs scale with trace count,\nand the service map becomes noisy. Use a custom rule scoped to specific\nendpoints.\n\n### Step 5: Annotations and metadata\n\n```python\nfrom aws_xray_sdk.core import xray_recorder\n\n# Annotation — indexable, use for filtering in X-Ray console\nxray_recorder.put_annotation(\"customer_id\", \"cust-12345\")\nxray_recorder.put_annotation(\"region\", \"us-east-1\")\n\n# Metadata — NOT indexable, for debug context\nxray_recorder.put_metadata(\"request_body_size\", 1024)\nxray_recorder.put_metadata(\"feature_flags\", {\"new_checkout\": True})\n```\n\nAnnotations are indexed and searchable in the X-Ray console. Metadata\nis visible on individual traces but NOT searchable. Use annotations for\nfields you will filter on; use metadata for everything else.\n\n### Step 6: Groups and insights\n\n```bash\n# Group — saved filter expression\naws xray create-group \\\n  --group-name \"payments-checkout-group\" \\\n  --filter-expression 'annotation.region = \"us-east-1\" AND service(\"payments-api\") { fault = true }'\n\n# Insights — auto-detect anomalies (enabled by default, no config needed)\naws xray get-insight --insight-id \u003Cid>\n```\n\nGroups are saved filter expressions for recurring queries. Insights\nauto-detect latency spikes, error rate increases, and anomalous behavior.\nInsights are enabled by default — no config needed.\n\n### Step 7: CloudWatch ServiceLens\n\nServiceLens integrates X-Ray traces with CloudWatch metrics and logs. It\nis enabled at the account level — no per-service config needed. To\nverify:\n\n```bash\naws cloudwatch describe-alarms-for-metric \\\n  --namespace AWS\u002FXRay \\\n  --metric-name FaultRate\n```\n\nThe ServiceLens service map is visible in the CloudWatch console under\n\"ServiceLens\" > \"Service Map\".\n\n### Step 8: Verification\n\n```bash\naws xray get-sampling-rules\naws xray get-sampling-targets\naws xray get-service-graph --start-time \u003CISO> --end-time \u003CISO>\naws xray get-trace-summaries --start-time \u003CISO> --end-time \u003CISO>\naws xray get-groups\naws xray get-insight-summaries --start-time \u003CISO> --end-time \u003CISO>\n```\n\n## Latest X-Ray features (2024-2026)\n\n2024-2026 feature delta (Powertools v2, ADOT Collector, attribute-based sampling, Insights anomaly detection, cross-account ServiceLens, CMK, daemon 4.x maintenance mode, W3C): [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when choosing components.\n\n## Platform matrix\n\n| Platform | Daemon | SDK address | IAM role | Notes |\n|---|---|---|---|---|\n| **EC2** | systemd service | `127.0.0.1:2000` | Instance profile | Daemon runs as a background process |\n| **ECS Fargate** | Sidecar container | `127.0.0.1:2000` | Task role | Same task definition (awsvpc shared network) |\n| **ECS EC2** | Sidecar or daemon-service | `127.0.0.1:2000` or `\u003Chost-ip>:2000` | Task role | Daemon-service saves memory; sidecar is simpler |\n| **EKS** | DaemonSet | `\u003Cnode-ip>:2000` (downward API) | Pod IRSA role | DaemonSet = one daemon per node |\n| **Lambda** | Built-in (no daemon) | N\u002FA | Execution role | Enable `TracingConfig Mode=Active` |\n| **App Runner** | N\u002FA (managed) | N\u002FA | Instance role | Enable observability config with `Vendor=AWSXRay` |\n| **Elastic Beanstalk** | Instance or sidecar | `127.0.0.1:2000` | Instance profile | EB config has an X-Ray option |\n\n## NEVER (top 5 — full list of 14 in references)\n\n- NEVER deploy the X-Ray SDK without `xray:GetSamplingRules` and\n  `xray:GetSamplingTargets` on the application's runtime role. The SDK\n  fetches central sampling rules from the X-Ray API. Without these\n  permissions, the SDK falls back to local default (1\u002Fs, fixed) and the\n  rules you configure in the console are NEVER applied. #1 silent-failure.\n- NEVER run the X-Ray daemon \u002F OTel Collector without\n  `xray:PutTraceSegments` and `xray:PutTelemetryRecords`. The SDK\n  generates segments and sends them to the daemon, but the daemon\n  uploads them. Without upload permissions, traces are silently dropped.\n- NEVER set `FixedRate=1.0` on the Default sampling rule for high-traffic\n  services. This generates massive trace volume. X-Ray charges per trace\n  ingested. Use a custom rule scoped to specific endpoints.\n- NEVER forget to patch the AWS SDK (`AWSXRay.captureAWS()` \u002F\n  `aws_xray_sdk.core.patch_all()`). Without the patch, downstream AWS\n  calls (DynamoDB, S3, SQS) do NOT generate subsegments. The service map\n  shows only the entry point — no dependencies.\n- NEVER deploy the daemon as a separate ECS service on Fargate and point\n  the app to it via DNS. Fargate tasks cannot reach each other on\n  localhost. The daemon MUST be a sidecar in the same task definition.\n\n## Expert heuristic — choosing X-Ray SDK vs ADOT, sampling, and annotations\n\nSDK-vs-ADOT choice, reservoir\u002Frate tuning, annotation discipline, trace-context propagation, and cost control: [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when making design decisions.\n\n## Pre-flight safety checks (run before any deployment CLI)\n\n- **Confirm IAM role has all 5 X-Ray actions** (PutTraceSegments,\n  PutTelemetryRecords, GetSamplingRules, GetSamplingTargets,\n  GetEncryptionConfig). Use `AWSXRayDaemonWriteAccess` managed policy.\n- **Confirm daemon \u002F OTel Collector is running** and listening on UDP\n  2000 (X-Ray) or gRPC 4317 (OTel).\n- **Confirm SDK package is installed** and the middleware\u002Fpatcher is\n  active in the code.\n- **Confirm AWS SDK is patched** for downstream call tracing.\n- **Confirm trace context propagation** across all service boundaries.\n- **Confirm sampling rules** (check the Default rule and any custom\n  rules).\n- **Confirm X-Ray encryption config** (AWS-owned key vs CMK).\n- **For existing services, capture current sampling config for rollback.**\n\nFull CLI sequences for all checks in `references\u002Fdaemon-and-sampling-guide.md`.\n\n## Output format — MANDATORY literal labels\n\nWhen invoked with a tracing deployment request, your ENTIRE response MUST\nbe the checklist block below. The labels are **case-sensitive all-caps\nkeywords**. Do NOT write a preamble. Start with `SERVICE:` and stop after\nthe `VERIFICATION_COMMANDS:` block.\n\n```text\nSERVICE: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓]      Platform — \u003Cec2|ecs|eks|lambda|app-runner>, \u003Ccluster\u002Ffunction\u002Fdetail>\n  [✓]      Daemon — \u003Cdaemon-image:version> \u003Cdeployment-mode> (UDP 2000)\n  [✓]      SDK instrumentation — \u003Clanguage> \u003Cversion>, \u003Cpackage> \u003Cversion>, \u003Cmiddleware>\n  [✓]      Sampling rule — default (reservoir \u003Cn>\u002Fs, rate \u003Cp>%), custom rule \u003Cname> (reservoir \u003Cn>\u002Fs, rate \u003Cp>% on \u003Cmatch>)\n  [✓]      IAM role — \u003Crole-name> has xray:PutTraceSegments + PutTelemetryRecords + GetSamplingRules + GetSamplingTargets\n  [✓]      Annotations — \u003Cindexable fields>\n  [✓]      Metadata — \u003Cdebug fields>\n  [✓]      Service map — generated from traces, \u003Csegment-count> segments\n  [✓]      CloudWatch ServiceLens — integrated\n  [OPTIONAL] X-Ray group — \u003Cgroup-name> (filter expression \u003Cexpr>)\nVERIFICATION_COMMANDS:\n  aws xray get-sampling-rules\n  aws xray get-sampling-targets\n  aws xray get-service-graph --start-time \u003CISO> --end-time \u003CISO>\n  aws ecs describe-task-definition --task-definition \u003Cfamily>\n```\n\n**Status marker semantics:**\n- `[✓]` — applied and verified.\n- `[✗]` — NOT applied or misconfigured. Cite the gap.\n- `[OPTIONAL]` — recommended but not required.\n- `[INPUT NEEDED]` — prerequisite value missing; operator must provide.\n\n**PREREQUISITES_MISSING verdict:** if any REQUIRED prerequisite is missing\n(IAM permissions, daemon \u002F Collector not running, SDK not instrumented,\nsampling rules not configured), the verdict is `PREREQUISITES_MISSING`.\n\n## References (load on demand)\n\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — 2024-2026 feature delta, SDK-vs-ADOT heuristics, edge-case catalog\n- [Daemon and sampling guide](references\u002Fdaemon-and-sampling-guide.md) — per-platform daemon deployment blocks (EC2, ECS Fargate, EKS, Lambda) plus the full daemon\u002Fsampling CLI sequence\n- [SDK instrumentation guide](references\u002Fsdk-instrumentation-guide.md) — language-by-language instrumentation and AWS SDK patching\n\n## Domain\n\nAWS CloudOps \u002F X-Ray Distributed Tracing Observability Provisioning.\n\n## Edge-case handling\n\nEdge-case catalog (cross-account, SQS\u002FEventBridge propagation, ECS EC2 host-IP, EKS limits, Lambda cold start, OTel migration, high-cardinality annotations, CMK grants): [Advanced patterns](references\u002Fadvanced-patterns.md).\nLoad on demand when deployment hits a corner case.\n\n## AWS documentation\n\n- **AWS X-Ray Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Faws-xray.html\n- **X-Ray Daemon** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-daemon.html\n- **X-Ray SDK** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-sdk.html\n- **X-Ray Sampling Rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-console-sampling.html\n- **X-Ray Service Map** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-services.html\n- **X-Ray Groups and Insights** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fxray\u002Flatest\u002Fdevguide\u002Fxray-insights.html\n- **CloudWatch ServiceLens** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonCloudWatch\u002Flatest\u002Fmonitoring\u002FServiceLens.html\n- **AWS Distro for OpenTelemetry (ADOT)** — https:\u002F\u002Faws-otel.github.io\u002F\n- **Lambda Powertools Tracing** — https:\u002F\u002Fdocs.powertools.aws.dev\u002Flambda\u002Fpython\u002Flatest\u002Fcore\u002Ftracer\u002F\n- **X-Ray CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fxray\u002F\n\n## References\n\n- `references\u002Fdaemon-and-sampling-guide.md` — full copy-pasteable CLI\n  command sequence for daemon deployment (EC2, ECS, EKS, Lambda),\n  sampling rule creation (default + custom), IAM role setup, group\n  creation, and Terraform \u002F CloudFormation equivalents.\n\n- `references\u002Fsdk-instrumentation-guide.md` — deep reference on SDK\n  instrumentation (Python, Node.js, Java, Go, .NET), AWS SDK patching,\n  annotation vs metadata, trace context propagation, OpenTelemetry \u002F ADOT\n  migration, full NEVER list, edge-case handling, and pre-flight safety\n  CLI.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"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,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, xray, distributed-tracing, cloudops, deploy, observability, sampling-rules, opentelemetry","1","Jacky Chan — AWS Community Builder","aws-cloudops","Management","0.1.0","aws, xray, x-ray, distributed-tracing, cloudops, deploy, provisioning, observability, daemon, sampling-rules, service-map, opentelemetry, adot, servicelens","deploy","high","false","capability","Invoke when the user wants to enable X-Ray distributed tracing on a new application, add the X-Ray daemon to ECS \u002F EKS \u002F EC2 \u002F Lambda, create or validate custom sampling rules, instrument an SDK (Java, Python, Node.js, Go, .NET), set up CloudWatch ServiceLens, or migrate from X-Ray SDK to OpenTelemetry \u002F ADOT. Do NOT invoke for CloudWatch Logs metrics alone (use cloudwatch-alarm-auditor), for application performance monitoring without tracing (use cloudwatch-application-signals-deployer), or for pure log aggregation.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Requires an LLM agent runtime (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with xray, ec2, ecs, eks, lambda, iam, logs, and servicediscovery access. Works with Terraform aws_xray_* resources, CloudFormation AWS::XRay::* resources, and the AWS Distro for OpenTelemetry (ADOT) Collector.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fxray-tracing-deployer",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill xray-tracing-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill xray-tracing-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill xray-tracing-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",true,[64,70,74,78,81,85,89,93,97,101,105,109,113,117,121,125,129,133],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6804,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fec2-java-default-sampling.md",908,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fbaselines\u002Fec2-java-default-sampling.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fecs-fargate-otel-python.md",888,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fbaselines\u002Fecs-fargate-otel-python.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":80},"evals\u002Fbaselines\u002Flambda-powertools-annotations.md","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fbaselines\u002Flambda-powertools-annotations.md",{"path":82,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fbaselines\u002Fmissing-iam-permissions.md",801,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fbaselines\u002Fmissing-iam-permissions.md",{"path":86,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaselines\u002Foversampled-default-rule.md",751,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fbaselines\u002Foversampled-default-rule.md",{"path":90,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002Feval_config.yaml",1696,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Feval_config.yaml",{"path":94,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":95,"sourceHtmlUrl":96},"evals\u002Fevals.json",13315,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fevals.json",{"path":98,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":99,"sourceHtmlUrl":100},"evals\u002Fprompts\u002Fec2-java-default-sampling.md",690,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fprompts\u002Fec2-java-default-sampling.md",{"path":102,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":103,"sourceHtmlUrl":104},"evals\u002Fprompts\u002Fecs-fargate-otel-python.md",798,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fprompts\u002Fecs-fargate-otel-python.md",{"path":106,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":107,"sourceHtmlUrl":108},"evals\u002Fprompts\u002Flambda-powertools-annotations.md",739,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fprompts\u002Flambda-powertools-annotations.md",{"path":110,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":111,"sourceHtmlUrl":112},"evals\u002Fprompts\u002Fmissing-iam-permissions.md",583,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fprompts\u002Fmissing-iam-permissions.md",{"path":114,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":115,"sourceHtmlUrl":116},"evals\u002Fprompts\u002Foversampled-default-rule.md",620,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fevals\u002Fprompts\u002Foversampled-default-rule.md",{"path":118,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":119,"sourceHtmlUrl":120},"example\u002FREADME.md",8719,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fexample\u002FREADME.md",{"path":122,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fadvanced-patterns.md",5496,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":126,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fdaemon-and-sampling-guide.md",14006,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Freferences\u002Fdaemon-and-sampling-guide.md",{"path":130,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fsdk-instrumentation-guide.md",15239,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Freferences\u002Fsdk-instrumentation-guide.md",{"path":134,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":135,"sourceHtmlUrl":136},"skill.usf.yaml",4464,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002Fskill.usf.yaml",[138,145,152,159,166,173],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"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":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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":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},"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":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},"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":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},"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",[],[],{"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},"01M7ADQJJE352085XH6KMVHZTN","vpn-connection-deployer","Provisions AWS Site-to-Site VPN connections with production defaults: customer gateway (CGW), virtual private gateway (VPG) vs transit gateway (TGW) VPN attachment, VPN connection (IPSec), routing (static vs dynamic\u002FBGP), tunnel options (IKE versions, encryption algorithms, Phase 1\u002F2 SA lifetimes, dead peer detection), dual-tunnel redundancy, CloudWatch monitoring (TunnelState, TunnelDataIn\u002FOut), acceleration via Global Accelerator, redundant VPN connections, IPv6 support, and outside IP address types (public vs private NAT). Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Site-to-Site VPN, connecting an on-premises network to AWS, configuring BGP over VPN, setting up dual-tunnel redundancy, or attaching a VPN to a transit gateway. Triggers: create site-to-site vpn, customer gateway, virtual private gateway, vpn connection ipsec, bgp over vpn, dual tunnel redundancy, transit gateway vpn attachment, vpn cloudwatch monitoring, global accelerator vpn, vpn ipv6.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpn-connection-deployer\u002FSKILL.md",[],[]]