[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADPVJCHMN1YYCVHDK3RND1":3,"skill-same:01M7ADPVJCHMN1YYCVHDK3RND1":146},{"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},"01M7ADPVJCHMN1YYCVHDK3RND1","vpclattice-service-deployer",null,"Provisions Amazon VPC Lattice services with production defaults: service network creation (top-level routing plane), service (HTTP\u002FgRPC), target group (instance\u002FIP\u002FLambda\u002FALB), listener rules (path-based, header-based, method-based routing), IAM auth policy (service-level not rule-level), resource-based service policy, target group health checks (determines routing eligibility), cross-account service access, custom domain name mapping, service network VPC association, traffic splitting for canary deployments, access log delivery to CloudWatch\u002FS3, and pricing per GB processed. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a VPC Lattice service network, configuring. Triggers: create vpc lattice service network, vpc lattice target group, vpc lattice listener rule, vpc lattice auth policy, vpc lattice traffic splitting, vpc lattice custom domain, vpc lattice service network vpc association, vpc lattice cross-account access, vpc lattice access logs, vpc lattice health check.","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\u002Fvpclattice-service-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vpclattice-service-deployer\ndescription: 'Provisions Amazon VPC Lattice services with production defaults: service network creation (top-level routing plane), service (HTTP\u002FgRPC), target group (instance\u002FIP\u002FLambda\u002FALB), listener rules (path-based, header-based, method-based routing), IAM auth policy (service-level not rule-level), resource-based service policy, target group health checks (determines routing eligibility), cross-account service access, custom domain name mapping, service network VPC association, traffic splitting for canary deployments, access log delivery to CloudWatch\u002FS3, and pricing per GB processed. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a VPC Lattice service network, configuring. Triggers: create vpc lattice service network, vpc lattice target group, vpc lattice listener rule, vpc lattice auth policy, vpc lattice traffic splitting, vpc lattice custom domain, vpc lattice service network vpc association, vpc lattice cross-account access, vpc lattice access logs, vpc lattice health check.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with vpc-lattice access. Works with Terraform aws_vpclattice_service_network \u002F aws_vpclattice_service \u002F aws_vpclattice_target_group \u002F aws_vpclattice_listener resources and CloudFormation AWS::VpcLattice::ServiceNetwork \u002F Service \u002F TargetGroup templates.'\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: Networking\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, vpc-lattice, service-network, cloudops, deploy, networking, provisioning, auth-policy, traffic-splitting, canary, health-check\n  dependencies: aws-orchestrator\n  keywords: aws, vpc lattice, service network, lattice service, target group, listener rule, cloudops, deploy, provisioning, auth policy, traffic splitting, canary, custom domain, health check, access logs, cross-account\n  when_to_use: Invoke when the user wants to create an Amazon VPC Lattice service network, provision Lattice services (HTTP or gRPC), configure target groups (instance\u002FIP\u002FLambda\u002FALB), define listener rules (path-based, header-based, method-based routing), apply IAM auth policies at the service level, set up resource-based service policies, configure target group health checks, enable cross-account service access, map custom domain names, associate VPCs with a service network, configure traffic splitting for canary deployments, or deliver access logs to CloudWatch\u002FS3. Do NOT invoke for AWS Transit Gateway, VPC peering, ALB\u002FNLB provisioning, or API Gateway (HTTP API).\n---\n\n# VPC Lattice Service Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon VPC Lattice services\nwith correct defaults. The skill walks the operator through service\nnetwork creation, service and target group provisioning, listener rule\nconfiguration, IAM auth policy at the service level, health check setup,\ncross-account access, custom domain mapping, VPC association, traffic\nsplitting, and access log delivery. It captures topology and routing\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\ncreate VPC Lattice service network, VPC Lattice target group, VPC\nLattice listener rule, VPC Lattice auth policy, VPC Lattice traffic\nsplitting, VPC Lattice custom domain, VPC Lattice service network VPC\nassociation, VPC Lattice cross-account access, VPC Lattice access logs,\nVPC Lattice health check.\n\n## STRICT output contract\n\nWhen this skill is invoked with a VPC Lattice provisioning request\n(create a service network, configure a service, set up target groups,\ndefine listener rules, apply auth policy, configure traffic splitting,\nenable access logs, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\"\nsection using the literal all-caps labels `VPC_LATTICE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Service network (top-level routing plane) | Core Lattice model |\n| Step 2 — Target group (type selection + health checks) | Routing eligibility |\n| Step 3 — Service (HTTP\u002FgRPC) | Service provisioning |\n| Step 4 — Listener rules (path\u002Fheader\u002Fmethod routing) | Traffic routing |\n| Step 5 — IAM auth policy (service level, NOT rule level) | Auth model |\n| Step 6 — Resource-based service policy | Access control |\n| Step 7 — Service network VPC association | VPC enablement |\n| Step 8 — Cross-account service access | Multi-account topology |\n| Step 9 — Custom domain name mapping | DNS + TLS |\n| Step 10 — Traffic splitting (canary) | Weighted routing |\n| Step 11 — Access log delivery | Observability |\n| Step 12 — Pricing (per GB processed) | Cost model |\n| Step 13 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fauth-policy-and-access.md | Auth + policy detail |\n| references\u002Flistener-rules-and-health.md | Routing + health detail |\n| references\u002Fworked-examples.md | Step CLIs (network, service, association, domain) |\n| references\u002Ferror-handling.md | Failure triage |\n| references\u002Fadvanced-patterns.md | Recent features |\n\n## Mindset\n\n**One-line takeaway:** VPC Lattice is an application networking service\nthat connects, secures, and monitors communications across VPCs and\naccounts. The service network is the top-level routing plane (typically\n1 per account). Target group health check status determines whether a\ntarget receives traffic. The IAM auth policy applies at the SERVICE\nlevel — NOT at the individual listener rule level.\n\nThree misconceptions dominate VPC Lattice misdesign at provisioning\ntime:\n\n- **\"Auth policies can be scoped per listener rule.\"** They CANNOT. The\n  IAM auth policy attaches to the SERVICE resource, not individual\n  listener rules. If you need different auth semantics per path, you\n  need separate services — not separate rules within one service. A\n  baseline model may try to attach an auth policy to a specific rule;\n  this does not exist in the API.\n\n- **\"Unhealthy targets still receive traffic.\"** They do NOT. VPC\n  Lattice only routes to targets whose health check is passing. If ALL\n  targets in a target group are unhealthy, Lattice returns 503 (no\n  healthy targets). Health check configuration determines routing\n  eligibility, not an optional monitoring feature.\n\n- **\"The service network is per VPC.\"** It is NOT. The service network\n  is an account-level construct (up to 1 per account in the default\n  limit). VPCs are ASSOCIATED with a service network via VPC\n  association. Multiple VPCs (and cross-account VPCs) can be associated\n  with the same service network.\n\n## Configuration dependency graph (novel heuristic)\n\nVPC Lattice configurations are NOT independent. The service network\nmust exist before services. Target groups must exist before listener\nrules reference them. Health check status determines routing. IAM auth\npolicies apply at the service level. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies | Silent failure | Enables downstream |\n|---|---|---|---|\n| Service network | none (top-level construct) | 1 per account typical; VPCs must be associated | service + VPC association |\n| Target group | VPC (instance\u002FIP\u002FALB) or Lambda (function exists) | health check config determines routing — unhealthy targets receive NO traffic | listener rule + traffic splitting |\n| Service | service network exists; protocol chosen | service DNS name auto-assigned; auth policy attaches at service level | listener + auth policy |\n| Listener rule | service + listener + target group exist | rules evaluated in priority order; first match wins; default rule is fallback | routing decision per request |\n| IAM auth policy | service exists | attaches to SERVICE, not rules; must be explicitly put | auth enforcement for ALL paths |\n| Service policy (resource-based) | service exists | IAM resource policy controls who can invoke | cross-account invocation |\n| VPC association | service network + VPC exist | VPCs NOT associated cannot use Lattice DNS | in-VPC service reachability |\n| Cross-account association | service network + RAM share | other account must accept RAM share; then associate VPC | cross-account service access |\n| Custom domain | service + ACM cert in us-east-1 + DNS zone | cert must be in us-east-1 regardless of service region | custom URL for the service |\n| Traffic splitting | listener rule with weighted forwarding | weights are per TG within a rule; sum need not be 100 | canary \u002F blue-green routing |\n| Access logs | service network or service exists | delivery is async; first logs within minutes | observability \u002F audit trail |\n\n**The service-network-before-everything row is the one a baseline model\nmisses.** A service cannot exist without a service network. A VPC cannot\nuse Lattice routing without association. The auth policy cannot be\napplied without a service.\n\n**Cross-dependency gotchas:**\n- The IAM auth policy attaches at the SERVICE level and governs ALL\n  listener rules and ALL paths. You CANNOT scope auth to a specific\n  path or rule.\n- Target group health check status determines routing eligibility. If\n  the health check fails, Lattice routes ZERO traffic to that target.\n  If all targets are unhealthy, clients see 503.\n- VPC association is required for the VPC to resolve Lattice service DNS\n  names. Without association, instances in the VPC cannot reach the\n  service via its auto-assigned DNS name.\n- Cross-account access requires BOTH a RAM resource share (sharing the\n  service network) AND a resource-based service policy (allowing the\n  other account to invoke the service).\n- Custom domain names require an ACM certificate in us-east-1 (the\n  Lattice-managed TLS region), regardless of the service's region.\n\n## Expert heuristic: the three-tier Lattice model\n\nA baseline model says \"create a service.\" The correct heuristic\nrecognizes the three-tier hierarchy: service network (top) -> service\n(middle) -> target group + listener rules (bottom).\n\n```text\nAccount\n  └── Service Network (top-level routing plane, 1 per account typical)\n        ├── VPC Associations (which VPCs can use this network)\n        │     ├── VPC-A (vpc-aaa11122)\n        │     └── VPC-B (vpc-bbb22233)\n        ├── Service: payments-svc (HTTP)\n        │     ├── Auth Policy (IAM, at SERVICE level — covers ALL rules)\n        │     ├── Service Policy (resource-based, for cross-account)\n        │     ├── Listener (port 80, HTTP)\n        │     │     ├── Rule 1 (priority 10): path \u002Fv2\u002F* → TG-canary 20 + TG-stable 80\n        │     │     └── Rule 2 (default): path * → TG-stable 100\n        │     ├── Target Group: TG-stable (INSTANCE, port 8080, health \u002Fhealth)\n        │     └── Target Group: TG-canary (INSTANCE, port 8080, health \u002Fhealth)\n        └── Service: inventory-svc (gRPC)\n              └── ...\n```\n\n**Key implication:** every resource hangs off the service network. The\nservice network is the first thing to create, and its VPC associations\ndetermine which VPCs can reach the services.\n\n## Expert heuristic: health check determines routing eligibility\n\nExpert heuristic — health check determines routing eligibility — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Expert heuristic: auth policy scope (service, not rule)\n\nExpert heuristic — auth policy scope (service, not rule) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n## Prerequisites (verify before provisioning)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account + region | Lattice is regional | `aws sts get-caller-identity` |\n| VPC exists (instance\u002FIP\u002FALB TG) | Target groups reference VPC resources | `aws ec2 describe-vpcs --vpc-ids \u003Cvpc-id>` |\n| Lambda function exists (Lambda TG) | Lambda TG references function ARN | `aws lambda get-function --function-name \u003Cname>` |\n| ALB exists (ALB TG) | ALB TG references ALB ARN | `aws elbv2 describe-load-balancers` |\n| ACM cert in us-east-1 (custom domain) | Lattice custom domains require us-east-1 cert | `aws acm list-certificates --region us-east-1` |\n| Route53 zone (custom domain DNS) | Domain mapping needs a DNS zone | `aws route53 list-hosted-zones` |\n| IAM perms for auth policy | Auth policy requires `vpc-lattice:PutAuthPolicy` | Verify IAM policy |\n| Cross-account: RAM share configured | Cross-account needs RAM resource share | `aws ram list-resources` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Service network (top-level routing plane)\n\nThe service network is the top-level routing plane. It is an account-\nlevel construct — NOT a VPC-level construct. Typically one per account.\n\nStep 1 — create service network CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Auth type:** `AWS_IAM` enforces IAM auth by default (the auth policy\nstill needs PUT on each service). `NONE` means no IAM auth enforcement\nat the network level. **Limits:** 1 service network per account (soft),\n50 VPC associations per network, 1,000 services per network.\n\n## Step 2 — Target group (type selection + health checks)\n\nThe target group type must be chosen at creation and CANNOT be changed.\n\n| Type | Target | VPC required | Use case |\n|---|---|---|---|\n| INSTANCE | EC2 instance ID | Yes | EC2-based services |\n| IP | IP address | Yes | ECS awsvpc, ENI-attached |\n| LAMBDA | Lambda function ARN | No | Serverless functions |\n| ALB | ALB ARN | Yes | ALB with Lattice upstream |\n\nStep 2 — instance target group with health check CLI; Step 2 — Lambda target group CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n**Critical:** health check status determines routing eligibility. Verify:\n\nStep 2 — verify target health CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Step 3 — Service (HTTP\u002FgRPC)\n\nA service is a runnable unit within a service network. It gets an\nauto-assigned DNS name.\n\nStep 3 — create service CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Protocol:** HTTP and gRPC are supported. Set when creating the\nlistener (not the service). A service can have one listener per\nprotocol.\n\n## Step 4 — Listener rules (path\u002Fheader\u002Fmethod routing)\n\nListeners receive traffic for a service. Rules define routing based on\npath, header, and HTTP method. Rules are evaluated in priority order;\nfirst match wins.\n\nStep 4 — listener and routing rule CLIs (default, path, header) — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Step 5 — IAM auth policy (service level, NOT rule level)\n\nThe IAM auth policy enforces IAM-based authentication on the SERVICE.\nIt applies to ALL listener rules and ALL paths — you CANNOT scope auth\nto a specific rule.\n\nStep 5 — IAM auth policy CLI (service level) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n**Critical:** the auth policy is at the SERVICE level. If you need\ndifferent auth per path, split into separate services with separate\nauth policies.\n\n## Step 6 — Resource-based service policy\n\nThe resource-based service policy controls who can INVOKE the service\n(cross-account access). Separate from the IAM auth policy (which\ncontrols request-level auth).\n\nStep 6 — resource-based service policy CLI — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\nCombined with RAM sharing, this enables full cross-account service\naccess.\n\n## Step 7 — Service network VPC association\n\nVPCs must be ASSOCIATED with the service network to use Lattice DNS\nresolution and reach services. Without association, instances in the VPC\ncannot resolve Lattice service DNS names.\n\nStep 7 — service network VPC association CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n## Step 8 — Cross-account service access\n\nCross-account access requires RAM share + service policy.\n\nStep 8 — cross-account access CLI (RAM share + association) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n**Missing any of the four steps results in AccessDenied.**\n\n## Step 9 — Custom domain name mapping\n\nCustom domains map a user-facing DNS name to a Lattice service. The ACM\ncertificate MUST be in us-east-1 regardless of the service's region.\n\nStep 9 — custom domain mapping CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Critical:** ACM cert must be in us-east-1, and the cert's domain name\nmust match the custom domain.\n\n## Step 10 — Traffic splitting (canary)\n\nTraffic splitting routes a percentage of traffic to a canary target\ngroup via weighted forwarding in a listener rule. Weights are relative\n(not percentage); weights 1 and 4 produce the same 20\u002F80 split as 20\nand 80.\n\nStep 10 — traffic splitting (canary) CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n**Progressive canary (20 -> 50 -> 100%):** update rule weights with\n`update-rule` to shift traffic gradually.\n\n## Step 11 — Access log delivery\n\nAccess logs capture Lattice request details for observability and audit.\nDelivery is async; first logs appear within 5-10 minutes.\n\nStep 11 — access log delivery CLI — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n## Step 12 — Pricing (per GB processed)\n\n| Component | Pricing |\n|---|---|\n| GB processed | ~$0.025-0.10 per GB (varies by region) |\n| Service-hour | ~$0.015 per hour per service |\n| Target group, service network, custom domain | Free |\n| Access logs | CloudWatch\u002FS3 standard charges |\n\n**Key implication:** GB processed is the dominant cost driver. For\nhigh-traffic services, estimate monthly GB and multiply. The per-service\nhourly charge is minor for a small number of services.\n\n## Step 13 — Recent features\n\nStep 13 — recent features (2023-2026) — moved verbatim.\nFull detail: [Advanced Patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume auth policy can be scoped per listener rule.** The\n   IAM auth policy attaches to the SERVICE, not individual rules. It\n   governs ALL paths on the service. Need different auth per path?\n   Create separate services.\n\n2. **NEVER assume unhealthy targets receive traffic.** VPC Lattice\n   routes ZERO traffic to targets failing health checks. If all targets\n   in a TG are unhealthy, clients see 503. Always verify health check\n   status before expecting traffic.\n\n3. **NEVER skip VPC association with the service network.** VPCs NOT\n   associated cannot resolve Lattice service DNS names and cannot reach\n   services. Association is a prerequisite for in-VPC service access.\n\n4. **NEVER assume the service network is per VPC.** It is an account-\n   level construct (1 per account typical). Multiple VPCs are\n   ASSOCIATED with the same service network.\n\n5. **NEVER attempt cross-account access without RAM + service policy.**\n   Cross-account requires BOTH a RAM resource share AND a resource-based\n   service policy. Missing either results in AccessDenied.\n\n6. **NEVER request a custom domain ACM certificate outside us-east-1.**\n   Lattice custom domains require the ACM cert in us-east-1 regardless\n   of the service's region.\n\n7. **NEVER change the target group type after creation.** The type\n   (INSTANCE, IP, LAMBDA, ALB) is immutable. To change type, create a\n   new target group and update listener rules.\n\n8. **NEVER assume traffic splitting weights must sum to 100.** Weights\n   are relative. Weights 1 and 4 produce the same 20\u002F80 split as 20 and\n   80. Lattice normalizes.\n\n9. **NEVER forget the listener default action.** The default action is\n   the fallback when no rule matches. Without it, unmatched requests\n   fail.\n\n10. **NEVER assume access logs are real-time.** Log delivery is async;\n    first logs appear within 5-10 minutes.\n\n## Output format\n\n```text\nVPC_LATTICE: \u003Cservice-network-id> → \u003Cservice-id> (\u003Cservice-dns-name>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Service network: \u003Csn-id> (auth type: AWS_IAM | NONE)\n  [✓|✗] Target group: \u003Ctg-id> (type: INSTANCE | IP | LAMBDA | ALB, port: \u003Cport>)\n  [✓|✗] Health check: path \u003Cpath>, interval \u003Cn>s — targets \u003Cn>\u002F\u003Cn> healthy\n  [✓|✗] Service: \u003Csvc-id> (protocol: HTTP | gRPC, DNS: \u003Cdns-name>)\n  [✓|✗] Listener: \u003Clistener-id> (port \u003Cport>, protocol HTTP | gRPC)\n  [✓|✗] Listener rules: \u003Cn> rule(s) (path\u002Fheader\u002Fmethod match)\n  [✓|✗] Auth policy: IAM auth at SERVICE level (covers ALL rules) | None\n  [✓|✗] Service policy: resource-based policy (cross-account) | Same-account\n  [✓|✗] VPC association: \u003Cvpc-id> associated with \u003Csn-id> — ACTIVE\n  [✓|✗] Cross-account: RAM share to \u003Caccount-id> | Same-account\n  [✓|✗] Custom domain: \u003Cdomain> → \u003Cservice-dns> (ACM us-east-1) | Not configured\n  [✓|✗] Traffic splitting: canary \u003Cn>% \u002F stable \u003Cn>% | Single TG\n  [✓|✗] Access logs: CloudWatch | S3 | Disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws vpc-lattice get-service-network --service-network-identifier \u003Csn-id>\n  aws vpc-lattice get-service --service-identifier \u003Csvc-id>\n  aws vpc-lattice list-targets --target-group-identifier \u003Ctg-id>\n  aws vpc-lattice list-listeners --service-identifier \u003Csvc-id>\n  aws vpc-lattice list-rules --service-identifier \u003Csvc-id> --listener-identifier \u003Clistener-id>\n  aws vpc-lattice list-service-network-vpc-associations --service-network-identifier \u003Csn-id>\n```\n\n### Worked example — HTTP service with canary traffic splitting\n\n```text\nVPC_LATTICE: sni-aaa111 → svc-bbb222 (payments-svc-aaa.example.com)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Service network: sni-aaa111 (auth type: AWS_IAM)\n  [✓] Target group: tgc-stable (type: INSTANCE, port: 8080)\n  [✓] Health check: path \u002Fhealth, interval 30s — targets 3\u002F3 healthy\n  [✓] Service: svc-bbb222 (protocol: HTTP, DNS: payments-svc-aaa.example.com)\n  [✓] Listener: lstn-ccc333 (port 80, protocol HTTP)\n  [✓] Listener rules: 2 rules (path \u002Fv2\u002F* → canary split, default → stable)\n  [✓] Auth policy: IAM auth at SERVICE level (covers ALL rules)\n  [✓] Service policy: resource-based policy (cross-account for 999999999999)\n  [✓] VPC association: vpc-aaa11122 associated with sni-aaa111 — ACTIVE\n  [✓] Cross-account: RAM share to 999999999999\n  [✓] Custom domain: payments.internal.example.com → payments-svc-aaa.example.com (ACM us-east-1)\n  [✓] Traffic splitting: canary 20% \u002F stable 80%\n  [✓] Access logs: CloudWatch (\u002Faws\u002Fvpc-lattice)\n  [✓] Tags: Environment=production, Topology=canary\nVERIFICATION_COMMANDS:\n  aws vpc-lattice get-service-network --service-network-identifier sni-aaa111\n  aws vpc-lattice get-service --service-identifier svc-bbb222\n  aws vpc-lattice list-targets --target-group-identifier tgc-stable\n  aws vpc-lattice list-rules --service-identifier svc-bbb222 --listener-identifier lstn-ccc333\n  aws vpc-lattice list-service-network-vpc-associations --service-network-identifier sni-aaa111\n```\n\n## Error handling\n\nError handling deep dives — moved verbatim.\nFull detail: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Auth policy and access](references\u002Fauth-policy-and-access.md) — auth-scope heuristic, Step 5\u002F6\u002F8\u002F11 CLIs (auth policy, service policy, RAM cross-account, access logs)\n- [Listener rules and health](references\u002Flistener-rules-and-health.md) — health-check heuristic, Step 2\u002F4\u002F10 CLIs (target groups, listeners\u002Frules, canary)\n- [Worked examples](references\u002Fworked-examples.md) — Step 1\u002F3\u002F7\u002F9 CLIs (service network, service, VPC association, custom domain)\n- [Error handling](references\u002Ferror-handling.md) — 503 no healthy targets, cross-account AccessDenied, DNS, reachability, auth-policy fixes\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — recent features 2023-2026\n\n## Domain\n\nAWS CloudOps \u002F Amazon VPC Lattice Service Networking Provisioning &\nApplication-Layer Routing.\n\n## AWS documentation\n\n- **VPC Lattice Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fwhat-is-vpc-lattice.html\n- **Service networks** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fservice-networks.html\n- **Target groups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Ftarget-groups.html\n- **Listener rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Flisteners.html\n- **Auth policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fauth-policies.html\n- **Custom domains** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fcustom-domains.html\n- **Access logs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Faccess-logs.html\n- **Cross-account access** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fcross-account.html\n- **VPC Lattice pricing** — https:\u002F\u002Faws.amazon.com\u002Fvpc\u002Flattice\u002Fpricing\u002F\n","# VPC Lattice Service Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon VPC Lattice services\nwith correct defaults. The skill walks the operator through service\nnetwork creation, service and target group provisioning, listener rule\nconfiguration, IAM auth policy at the service level, health check setup,\ncross-account access, custom domain mapping, VPC association, traffic\nsplitting, and access log delivery. It captures topology and routing\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\ncreate VPC Lattice service network, VPC Lattice target group, VPC\nLattice listener rule, VPC Lattice auth policy, VPC Lattice traffic\nsplitting, VPC Lattice custom domain, VPC Lattice service network VPC\nassociation, VPC Lattice cross-account access, VPC Lattice access logs,\nVPC Lattice health check.\n\n## STRICT output contract\n\nWhen this skill is invoked with a VPC Lattice provisioning request\n(create a service network, configure a service, set up target groups,\ndefine listener rules, apply auth policy, configure traffic splitting,\nenable access logs, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\"\nsection using the literal all-caps labels `VPC_LATTICE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Service network (top-level routing plane) | Core Lattice model |\n| Step 2 — Target group (type selection + health checks) | Routing eligibility |\n| Step 3 — Service (HTTP\u002FgRPC) | Service provisioning |\n| Step 4 — Listener rules (path\u002Fheader\u002Fmethod routing) | Traffic routing |\n| Step 5 — IAM auth policy (service level, NOT rule level) | Auth model |\n| Step 6 — Resource-based service policy | Access control |\n| Step 7 — Service network VPC association | VPC enablement |\n| Step 8 — Cross-account service access | Multi-account topology |\n| Step 9 — Custom domain name mapping | DNS + TLS |\n| Step 10 — Traffic splitting (canary) | Weighted routing |\n| Step 11 — Access log delivery | Observability |\n| Step 12 — Pricing (per GB processed) | Cost model |\n| Step 13 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fauth-policy-and-access.md | Auth + policy detail |\n| references\u002Flistener-rules-and-health.md | Routing + health detail |\n| references\u002Fworked-examples.md | Step CLIs (network, service, association, domain) |\n| references\u002Ferror-handling.md | Failure triage |\n| references\u002Fadvanced-patterns.md | Recent features |\n\n## Mindset\n\n**One-line takeaway:** VPC Lattice is an application networking service\nthat connects, secures, and monitors communications across VPCs and\naccounts. The service network is the top-level routing plane (typically\n1 per account). Target group health check status determines whether a\ntarget receives traffic. The IAM auth policy applies at the SERVICE\nlevel — NOT at the individual listener rule level.\n\nThree misconceptions dominate VPC Lattice misdesign at provisioning\ntime:\n\n- **\"Auth policies can be scoped per listener rule.\"** They CANNOT. The\n  IAM auth policy attaches to the SERVICE resource, not individual\n  listener rules. If you need different auth semantics per path, you\n  need separate services — not separate rules within one service. A\n  baseline model may try to attach an auth policy to a specific rule;\n  this does not exist in the API.\n\n- **\"Unhealthy targets still receive traffic.\"** They do NOT. VPC\n  Lattice only routes to targets whose health check is passing. If ALL\n  targets in a target group are unhealthy, Lattice returns 503 (no\n  healthy targets). Health check configuration determines routing\n  eligibility, not an optional monitoring feature.\n\n- **\"The service network is per VPC.\"** It is NOT. The service network\n  is an account-level construct (up to 1 per account in the default\n  limit). VPCs are ASSOCIATED with a service network via VPC\n  association. Multiple VPCs (and cross-account VPCs) can be associated\n  with the same service network.\n\n## Configuration dependency graph (novel heuristic)\n\nVPC Lattice configurations are NOT independent. The service network\nmust exist before services. Target groups must exist before listener\nrules reference them. Health check status determines routing. IAM auth\npolicies apply at the service level. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies | Silent failure | Enables downstream |\n|---|---|---|---|\n| Service network | none (top-level construct) | 1 per account typical; VPCs must be associated | service + VPC association |\n| Target group | VPC (instance\u002FIP\u002FALB) or Lambda (function exists) | health check config determines routing — unhealthy targets receive NO traffic | listener rule + traffic splitting |\n| Service | service network exists; protocol chosen | service DNS name auto-assigned; auth policy attaches at service level | listener + auth policy |\n| Listener rule | service + listener + target group exist | rules evaluated in priority order; first match wins; default rule is fallback | routing decision per request |\n| IAM auth policy | service exists | attaches to SERVICE, not rules; must be explicitly put | auth enforcement for ALL paths |\n| Service policy (resource-based) | service exists | IAM resource policy controls who can invoke | cross-account invocation |\n| VPC association | service network + VPC exist | VPCs NOT associated cannot use Lattice DNS | in-VPC service reachability |\n| Cross-account association | service network + RAM share | other account must accept RAM share; then associate VPC | cross-account service access |\n| Custom domain | service + ACM cert in us-east-1 + DNS zone | cert must be in us-east-1 regardless of service region | custom URL for the service |\n| Traffic splitting | listener rule with weighted forwarding | weights are per TG within a rule; sum need not be 100 | canary \u002F blue-green routing |\n| Access logs | service network or service exists | delivery is async; first logs within minutes | observability \u002F audit trail |\n\n**The service-network-before-everything row is the one a baseline model\nmisses.** A service cannot exist without a service network. A VPC cannot\nuse Lattice routing without association. The auth policy cannot be\napplied without a service.\n\n**Cross-dependency gotchas:**\n- The IAM auth policy attaches at the SERVICE level and governs ALL\n  listener rules and ALL paths. You CANNOT scope auth to a specific\n  path or rule.\n- Target group health check status determines routing eligibility. If\n  the health check fails, Lattice routes ZERO traffic to that target.\n  If all targets are unhealthy, clients see 503.\n- VPC association is required for the VPC to resolve Lattice service DNS\n  names. Without association, instances in the VPC cannot reach the\n  service via its auto-assigned DNS name.\n- Cross-account access requires BOTH a RAM resource share (sharing the\n  service network) AND a resource-based service policy (allowing the\n  other account to invoke the service).\n- Custom domain names require an ACM certificate in us-east-1 (the\n  Lattice-managed TLS region), regardless of the service's region.\n\n## Expert heuristic: the three-tier Lattice model\n\nA baseline model says \"create a service.\" The correct heuristic\nrecognizes the three-tier hierarchy: service network (top) -> service\n(middle) -> target group + listener rules (bottom).\n\n```text\nAccount\n  └── Service Network (top-level routing plane, 1 per account typical)\n        ├── VPC Associations (which VPCs can use this network)\n        │     ├── VPC-A (vpc-aaa11122)\n        │     └── VPC-B (vpc-bbb22233)\n        ├── Service: payments-svc (HTTP)\n        │     ├── Auth Policy (IAM, at SERVICE level — covers ALL rules)\n        │     ├── Service Policy (resource-based, for cross-account)\n        │     ├── Listener (port 80, HTTP)\n        │     │     ├── Rule 1 (priority 10): path \u002Fv2\u002F* → TG-canary 20 + TG-stable 80\n        │     │     └── Rule 2 (default): path * → TG-stable 100\n        │     ├── Target Group: TG-stable (INSTANCE, port 8080, health \u002Fhealth)\n        │     └── Target Group: TG-canary (INSTANCE, port 8080, health \u002Fhealth)\n        └── Service: inventory-svc (gRPC)\n              └── ...\n```\n\n**Key implication:** every resource hangs off the service network. The\nservice network is the first thing to create, and its VPC associations\ndetermine which VPCs can reach the services.\n\n## Expert heuristic: health check determines routing eligibility\n\nExpert heuristic — health check determines routing eligibility — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Expert heuristic: auth policy scope (service, not rule)\n\nExpert heuristic — auth policy scope (service, not rule) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n## Prerequisites (verify before provisioning)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account + region | Lattice is regional | `aws sts get-caller-identity` |\n| VPC exists (instance\u002FIP\u002FALB TG) | Target groups reference VPC resources | `aws ec2 describe-vpcs --vpc-ids \u003Cvpc-id>` |\n| Lambda function exists (Lambda TG) | Lambda TG references function ARN | `aws lambda get-function --function-name \u003Cname>` |\n| ALB exists (ALB TG) | ALB TG references ALB ARN | `aws elbv2 describe-load-balancers` |\n| ACM cert in us-east-1 (custom domain) | Lattice custom domains require us-east-1 cert | `aws acm list-certificates --region us-east-1` |\n| Route53 zone (custom domain DNS) | Domain mapping needs a DNS zone | `aws route53 list-hosted-zones` |\n| IAM perms for auth policy | Auth policy requires `vpc-lattice:PutAuthPolicy` | Verify IAM policy |\n| Cross-account: RAM share configured | Cross-account needs RAM resource share | `aws ram list-resources` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Service network (top-level routing plane)\n\nThe service network is the top-level routing plane. It is an account-\nlevel construct — NOT a VPC-level construct. Typically one per account.\n\nStep 1 — create service network CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Auth type:** `AWS_IAM` enforces IAM auth by default (the auth policy\nstill needs PUT on each service). `NONE` means no IAM auth enforcement\nat the network level. **Limits:** 1 service network per account (soft),\n50 VPC associations per network, 1,000 services per network.\n\n## Step 2 — Target group (type selection + health checks)\n\nThe target group type must be chosen at creation and CANNOT be changed.\n\n| Type | Target | VPC required | Use case |\n|---|---|---|---|\n| INSTANCE | EC2 instance ID | Yes | EC2-based services |\n| IP | IP address | Yes | ECS awsvpc, ENI-attached |\n| LAMBDA | Lambda function ARN | No | Serverless functions |\n| ALB | ALB ARN | Yes | ALB with Lattice upstream |\n\nStep 2 — instance target group with health check CLI; Step 2 — Lambda target group CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n**Critical:** health check status determines routing eligibility. Verify:\n\nStep 2 — verify target health CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Step 3 — Service (HTTP\u002FgRPC)\n\nA service is a runnable unit within a service network. It gets an\nauto-assigned DNS name.\n\nStep 3 — create service CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Protocol:** HTTP and gRPC are supported. Set when creating the\nlistener (not the service). A service can have one listener per\nprotocol.\n\n## Step 4 — Listener rules (path\u002Fheader\u002Fmethod routing)\n\nListeners receive traffic for a service. Rules define routing based on\npath, header, and HTTP method. Rules are evaluated in priority order;\nfirst match wins.\n\nStep 4 — listener and routing rule CLIs (default, path, header) — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n## Step 5 — IAM auth policy (service level, NOT rule level)\n\nThe IAM auth policy enforces IAM-based authentication on the SERVICE.\nIt applies to ALL listener rules and ALL paths — you CANNOT scope auth\nto a specific rule.\n\nStep 5 — IAM auth policy CLI (service level) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n**Critical:** the auth policy is at the SERVICE level. If you need\ndifferent auth per path, split into separate services with separate\nauth policies.\n\n## Step 6 — Resource-based service policy\n\nThe resource-based service policy controls who can INVOKE the service\n(cross-account access). Separate from the IAM auth policy (which\ncontrols request-level auth).\n\nStep 6 — resource-based service policy CLI — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\nCombined with RAM sharing, this enables full cross-account service\naccess.\n\n## Step 7 — Service network VPC association\n\nVPCs must be ASSOCIATED with the service network to use Lattice DNS\nresolution and reach services. Without association, instances in the VPC\ncannot resolve Lattice service DNS names.\n\nStep 7 — service network VPC association CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n## Step 8 — Cross-account service access\n\nCross-account access requires RAM share + service policy.\n\nStep 8 — cross-account access CLI (RAM share + association) — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n**Missing any of the four steps results in AccessDenied.**\n\n## Step 9 — Custom domain name mapping\n\nCustom domains map a user-facing DNS name to a Lattice service. The ACM\ncertificate MUST be in us-east-1 regardless of the service's region.\n\nStep 9 — custom domain mapping CLI — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Critical:** ACM cert must be in us-east-1, and the cert's domain name\nmust match the custom domain.\n\n## Step 10 — Traffic splitting (canary)\n\nTraffic splitting routes a percentage of traffic to a canary target\ngroup via weighted forwarding in a listener rule. Weights are relative\n(not percentage); weights 1 and 4 produce the same 20\u002F80 split as 20\nand 80.\n\nStep 10 — traffic splitting (canary) CLI — moved verbatim.\nFull detail: [Listener rules and health](references\u002Flistener-rules-and-health.md).\n\n**Progressive canary (20 -> 50 -> 100%):** update rule weights with\n`update-rule` to shift traffic gradually.\n\n## Step 11 — Access log delivery\n\nAccess logs capture Lattice request details for observability and audit.\nDelivery is async; first logs appear within 5-10 minutes.\n\nStep 11 — access log delivery CLI — moved verbatim.\nFull detail: [Auth policy and access](references\u002Fauth-policy-and-access.md).\n\n## Step 12 — Pricing (per GB processed)\n\n| Component | Pricing |\n|---|---|\n| GB processed | ~$0.025-0.10 per GB (varies by region) |\n| Service-hour | ~$0.015 per hour per service |\n| Target group, service network, custom domain | Free |\n| Access logs | CloudWatch\u002FS3 standard charges |\n\n**Key implication:** GB processed is the dominant cost driver. For\nhigh-traffic services, estimate monthly GB and multiply. The per-service\nhourly charge is minor for a small number of services.\n\n## Step 13 — Recent features\n\nStep 13 — recent features (2023-2026) — moved verbatim.\nFull detail: [Advanced Patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume auth policy can be scoped per listener rule.** The\n   IAM auth policy attaches to the SERVICE, not individual rules. It\n   governs ALL paths on the service. Need different auth per path?\n   Create separate services.\n\n2. **NEVER assume unhealthy targets receive traffic.** VPC Lattice\n   routes ZERO traffic to targets failing health checks. If all targets\n   in a TG are unhealthy, clients see 503. Always verify health check\n   status before expecting traffic.\n\n3. **NEVER skip VPC association with the service network.** VPCs NOT\n   associated cannot resolve Lattice service DNS names and cannot reach\n   services. Association is a prerequisite for in-VPC service access.\n\n4. **NEVER assume the service network is per VPC.** It is an account-\n   level construct (1 per account typical). Multiple VPCs are\n   ASSOCIATED with the same service network.\n\n5. **NEVER attempt cross-account access without RAM + service policy.**\n   Cross-account requires BOTH a RAM resource share AND a resource-based\n   service policy. Missing either results in AccessDenied.\n\n6. **NEVER request a custom domain ACM certificate outside us-east-1.**\n   Lattice custom domains require the ACM cert in us-east-1 regardless\n   of the service's region.\n\n7. **NEVER change the target group type after creation.** The type\n   (INSTANCE, IP, LAMBDA, ALB) is immutable. To change type, create a\n   new target group and update listener rules.\n\n8. **NEVER assume traffic splitting weights must sum to 100.** Weights\n   are relative. Weights 1 and 4 produce the same 20\u002F80 split as 20 and\n   80. Lattice normalizes.\n\n9. **NEVER forget the listener default action.** The default action is\n   the fallback when no rule matches. Without it, unmatched requests\n   fail.\n\n10. **NEVER assume access logs are real-time.** Log delivery is async;\n    first logs appear within 5-10 minutes.\n\n## Output format\n\n```text\nVPC_LATTICE: \u003Cservice-network-id> → \u003Cservice-id> (\u003Cservice-dns-name>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Service network: \u003Csn-id> (auth type: AWS_IAM | NONE)\n  [✓|✗] Target group: \u003Ctg-id> (type: INSTANCE | IP | LAMBDA | ALB, port: \u003Cport>)\n  [✓|✗] Health check: path \u003Cpath>, interval \u003Cn>s — targets \u003Cn>\u002F\u003Cn> healthy\n  [✓|✗] Service: \u003Csvc-id> (protocol: HTTP | gRPC, DNS: \u003Cdns-name>)\n  [✓|✗] Listener: \u003Clistener-id> (port \u003Cport>, protocol HTTP | gRPC)\n  [✓|✗] Listener rules: \u003Cn> rule(s) (path\u002Fheader\u002Fmethod match)\n  [✓|✗] Auth policy: IAM auth at SERVICE level (covers ALL rules) | None\n  [✓|✗] Service policy: resource-based policy (cross-account) | Same-account\n  [✓|✗] VPC association: \u003Cvpc-id> associated with \u003Csn-id> — ACTIVE\n  [✓|✗] Cross-account: RAM share to \u003Caccount-id> | Same-account\n  [✓|✗] Custom domain: \u003Cdomain> → \u003Cservice-dns> (ACM us-east-1) | Not configured\n  [✓|✗] Traffic splitting: canary \u003Cn>% \u002F stable \u003Cn>% | Single TG\n  [✓|✗] Access logs: CloudWatch | S3 | Disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws vpc-lattice get-service-network --service-network-identifier \u003Csn-id>\n  aws vpc-lattice get-service --service-identifier \u003Csvc-id>\n  aws vpc-lattice list-targets --target-group-identifier \u003Ctg-id>\n  aws vpc-lattice list-listeners --service-identifier \u003Csvc-id>\n  aws vpc-lattice list-rules --service-identifier \u003Csvc-id> --listener-identifier \u003Clistener-id>\n  aws vpc-lattice list-service-network-vpc-associations --service-network-identifier \u003Csn-id>\n```\n\n### Worked example — HTTP service with canary traffic splitting\n\n```text\nVPC_LATTICE: sni-aaa111 → svc-bbb222 (payments-svc-aaa.example.com)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Service network: sni-aaa111 (auth type: AWS_IAM)\n  [✓] Target group: tgc-stable (type: INSTANCE, port: 8080)\n  [✓] Health check: path \u002Fhealth, interval 30s — targets 3\u002F3 healthy\n  [✓] Service: svc-bbb222 (protocol: HTTP, DNS: payments-svc-aaa.example.com)\n  [✓] Listener: lstn-ccc333 (port 80, protocol HTTP)\n  [✓] Listener rules: 2 rules (path \u002Fv2\u002F* → canary split, default → stable)\n  [✓] Auth policy: IAM auth at SERVICE level (covers ALL rules)\n  [✓] Service policy: resource-based policy (cross-account for 999999999999)\n  [✓] VPC association: vpc-aaa11122 associated with sni-aaa111 — ACTIVE\n  [✓] Cross-account: RAM share to 999999999999\n  [✓] Custom domain: payments.internal.example.com → payments-svc-aaa.example.com (ACM us-east-1)\n  [✓] Traffic splitting: canary 20% \u002F stable 80%\n  [✓] Access logs: CloudWatch (\u002Faws\u002Fvpc-lattice)\n  [✓] Tags: Environment=production, Topology=canary\nVERIFICATION_COMMANDS:\n  aws vpc-lattice get-service-network --service-network-identifier sni-aaa111\n  aws vpc-lattice get-service --service-identifier svc-bbb222\n  aws vpc-lattice list-targets --target-group-identifier tgc-stable\n  aws vpc-lattice list-rules --service-identifier svc-bbb222 --listener-identifier lstn-ccc333\n  aws vpc-lattice list-service-network-vpc-associations --service-network-identifier sni-aaa111\n```\n\n## Error handling\n\nError handling deep dives — moved verbatim.\nFull detail: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Auth policy and access](references\u002Fauth-policy-and-access.md) — auth-scope heuristic, Step 5\u002F6\u002F8\u002F11 CLIs (auth policy, service policy, RAM cross-account, access logs)\n- [Listener rules and health](references\u002Flistener-rules-and-health.md) — health-check heuristic, Step 2\u002F4\u002F10 CLIs (target groups, listeners\u002Frules, canary)\n- [Worked examples](references\u002Fworked-examples.md) — Step 1\u002F3\u002F7\u002F9 CLIs (service network, service, VPC association, custom domain)\n- [Error handling](references\u002Ferror-handling.md) — 503 no healthy targets, cross-account AccessDenied, DNS, reachability, auth-policy fixes\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — recent features 2023-2026\n\n## Domain\n\nAWS CloudOps \u002F Amazon VPC Lattice Service Networking Provisioning &\nApplication-Layer Routing.\n\n## AWS documentation\n\n- **VPC Lattice Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fwhat-is-vpc-lattice.html\n- **Service networks** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fservice-networks.html\n- **Target groups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Ftarget-groups.html\n- **Listener rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Flisteners.html\n- **Auth policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fauth-policies.html\n- **Custom domains** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fcustom-domains.html\n- **Access logs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Faccess-logs.html\n- **Cross-account access** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc-lattice\u002Flatest\u002Fug\u002Fcross-account.html\n- **VPC Lattice pricing** — https:\u002F\u002Faws.amazon.com\u002Fvpc\u002Flattice\u002Fpricing\u002F\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, vpc-lattice, service-network, cloudops, deploy, networking, provisioning, auth-policy, traffic-splitting, canary, health-check","1","Jacky Chan — AWS Community Builder","aws-cloudops","Networking","0.1.0","aws, vpc lattice, service network, lattice service, target group, listener rule, cloudops, deploy, provisioning, auth policy, traffic splitting, canary, custom domain, health check, access logs, cross-account","deploy","high","false","capability","Invoke when the user wants to create an Amazon VPC Lattice service network, provision Lattice services (HTTP or gRPC), configure target groups (instance\u002FIP\u002FLambda\u002FALB), define listener rules (path-based, header-based, method-based routing), apply IAM auth policies at the service level, set up resource-based service policies, configure target group health checks, enable cross-account service access, map custom domain names, associate VPCs with a service network, configure traffic splitting for canary deployments, or deliver access logs to CloudWatch\u002FS3. Do NOT invoke for AWS Transit Gateway, VPC peering, ALB\u002FNLB provisioning, or API Gateway (HTTP API).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with vpc-lattice access. Works with Terraform aws_vpclattice_service_network \u002F aws_vpclattice_service \u002F aws_vpclattice_target_group \u002F aws_vpclattice_listener resources and CloudFormation AWS::VpcLattice::ServiceNetwork \u002F Service \u002F TargetGroup templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fvpclattice-service-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 vpclattice-service-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill vpclattice-service-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill vpclattice-service-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5548,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fiam-auth-policy-service-level.md",585,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fbaselines\u002Fiam-auth-policy-service-level.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Flambda-target-with-domain-and-logs.md",606,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fbaselines\u002Flambda-target-with-domain-and-logs.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-vpc-association.md",572,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fbaselines\u002Fmissing-vpc-association.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fservice-network-http-service.md",575,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fbaselines\u002Fservice-network-http-service.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fweighted-canary-traffic-split.md",588,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fbaselines\u002Fweighted-canary-traffic-split.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1854,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9260,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fiam-auth-policy-service-level.md",483,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fprompts\u002Fiam-auth-policy-service-level.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Flambda-target-with-domain-and-logs.md",544,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fprompts\u002Flambda-target-with-domain-and-logs.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-vpc-association.md",430,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fprompts\u002Fmissing-vpc-association.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fservice-network-http-service.md",616,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fprompts\u002Fservice-network-http-service.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fweighted-canary-traffic-split.md",522,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fevals\u002Fprompts\u002Fweighted-canary-traffic-split.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7744,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",1365,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fauth-policy-and-access.md",9539,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Freferences\u002Fauth-policy-and-access.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1483,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Flistener-rules-and-health.md",14189,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Freferences\u002Flistener-rules-and-health.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",1910,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4507,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpclattice-service-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"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",[],[]]