vpclattice-service-deployer
Provisions Amazon VPC Lattice services with production defaults: service network creation (top-level routing plane), service (HTTP/gRPC), target group (instance/IP/Lambda/ALB), 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/S3, 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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-24
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- vpclattice-service-deployer
- license
- Apache-2.0
- metadata
- { "tags": "aws, vpc-lattice, service-network, cloudops, deploy, networking, provisioning, auth-policy, traffic-splitting, canary, health-check", "phase": "1", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "Networking", "version": "0.1.0", "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", "task_type": "deploy", "complexity": "high", "entry_point": "false", "skill_class": "capability", "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/IP/Lambda/ALB), 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/S3. Do NOT invoke for AWS Transit Gateway, VPC peering, ALB/NLB provisioning, or API Gateway (HTTP API).", "dependencies": "aws-orchestrator", "requires_llm": "true", "verdict_shape": "READY_TO_DEPLOY | PREREQUISITES_MISSING", "lifecycle_status": "active", "supports_pipeline": "true" }
- description
- Provisions Amazon VPC Lattice services with production defaults: service network creation (top-level routing plane), service (HTTP/gRPC), target group (instance/IP/Lambda/ALB), 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/S3, 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.
- compatibility
- 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 / aws_vpclattice_service / aws_vpclattice_target_group / aws_vpclattice_listener resources and CloudFormation AWS::VpcLattice::ServiceNetwork / Service / TargetGroup templates.
02 资源文件 20
- 参考文档eval/test-cases.yaml5.4 KB
- 参考文档evals/baselines/iam-auth-policy-service-level.md585 B
- 参考文档evals/baselines/lambda-target-with-domain-and-logs.md606 B
- 参考文档evals/baselines/missing-vpc-association.md572 B
- 参考文档evals/baselines/service-network-http-service.md575 B
- 参考文档evals/baselines/weighted-canary-traffic-split.md588 B
- 参考文档evals/eval_config.yaml1.8 KB
- 参考文档evals/evals.json9.0 KB
- 参考文档evals/prompts/iam-auth-policy-service-level.md483 B
- 参考文档evals/prompts/lambda-target-with-domain-and-logs.md544 B
- 参考文档evals/prompts/missing-vpc-association.md430 B
- 参考文档evals/prompts/service-network-http-service.md616 B
- 参考文档evals/prompts/weighted-canary-traffic-split.md522 B
- 参考文档examples/README.md7.6 KB
- 参考文档references/advanced-patterns.md1.3 KB
- 参考文档references/auth-policy-and-access.md9.3 KB
- 参考文档references/error-handling.md1.4 KB
- 参考文档references/listener-rules-and-health.md13.9 KB
- 参考文档references/worked-examples.md1.9 KB
- 参考文档skill.usf.yaml4.4 KB
03 SKILL.md 正文
VPC Lattice Service Deployer
An AWS CloudOps agent skill that provisions Amazon VPC Lattice services with correct defaults. The skill walks the operator through service network creation, service and target group provisioning, listener rule configuration, IAM auth policy at the service level, health check setup, cross-account access, custom domain mapping, VPC association, traffic splitting, and access log delivery. It captures topology and routing decisions, explains why each default matters, and emits a READY_TO_DEPLOY checklist with copy-pasteable verification commands.
Activation keywords
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.
STRICT output contract
When this skill is invoked with a VPC Lattice provisioning request
(create a service network, configure a service, set up target groups,
define listener rules, apply auth policy, configure traffic splitting,
enable access logs, or a partial configuration), the agent MUST respond
with the READY_TO_DEPLOY checklist defined in the "Output format"
section using the literal all-caps labels VPC_LATTICE:, VERDICT:,
CHECKLIST:, and VERIFICATION_COMMANDS:. Do NOT preface the checklist
with prose, headings, or disclaimers — emit the block as the first lines
of the response. This contract is what assertion-based evals and
downstream provisioning pipelines rely on; deviating from the literal
labels breaks automation silently.
If any prerequisite is missing, the verdict is PREREQUISITES_MISSING
with a specific gap citation in the checklist (marked [✗]), and
READY_TO_DEPLOY MUST NOT also appear.
Quick navigation
| Section | When to read |
|---|---|
| Prerequisites | Always — verify before provisioning |
| Step 1 — Service network (top-level routing plane) | Core Lattice model |
| Step 2 — Target group (type selection + health checks) | Routing eligibility |
| Step 3 — Service (HTTP/gRPC) | Service provisioning |
| Step 4 — Listener rules (path/header/method routing) | Traffic routing |
| Step 5 — IAM auth policy (service level, NOT rule level) | Auth model |
| Step 6 — Resource-based service policy | Access control |
| Step 7 — Service network VPC association | VPC enablement |
| Step 8 — Cross-account service access | Multi-account topology |
| Step 9 — Custom domain name mapping | DNS + TLS |
| Step 10 — Traffic splitting (canary) | Weighted routing |
| Step 11 — Access log delivery | Observability |
| Step 12 — Pricing (per GB processed) | Cost model |
| Step 13 — Recent features | Latest |
| NEVER do these things | Review before signing off |
| Output format | The literal checklist template |
| references/auth-policy-and-access.md | Auth + policy detail |
| references/listener-rules-and-health.md | Routing + health detail |
| references/worked-examples.md | Step CLIs (network, service, association, domain) |
| references/error-handling.md | Failure triage |
| references/advanced-patterns.md | Recent features |
Mindset
One-line takeaway: VPC Lattice is an application networking service that connects, secures, and monitors communications across VPCs and accounts. The service network is the top-level routing plane (typically 1 per account). Target group health check status determines whether a target receives traffic. The IAM auth policy applies at the SERVICE level — NOT at the individual listener rule level.
Three misconceptions dominate VPC Lattice misdesign at provisioning time:
-
"Auth policies can be scoped per listener rule." They CANNOT. The IAM auth policy attaches to the SERVICE resource, not individual listener rules. If you need different auth semantics per path, you need separate services — not separate rules within one service. A baseline model may try to attach an auth policy to a specific rule; this does not exist in the API.
-
"Unhealthy targets still receive traffic." They do NOT. VPC Lattice only routes to targets whose health check is passing. If ALL targets in a target group are unhealthy, Lattice returns 503 (no healthy targets). Health check configuration determines routing eligibility, not an optional monitoring feature.
-
"The service network is per VPC." It is NOT. The service network is an account-level construct (up to 1 per account in the default limit). VPCs are ASSOCIATED with a service network via VPC association. Multiple VPCs (and cross-account VPCs) can be associated with the same service network.
Configuration dependency graph (novel heuristic)
VPC Lattice configurations are NOT independent. The service network must exist before services. Target groups must exist before listener rules reference them. Health check status determines routing. IAM auth policies apply at the service level. Use this graph to sequence provisioning.
| Configuration | Hard dependencies | Silent failure | Enables downstream |
|---|---|---|---|
| Service network | none (top-level construct) | 1 per account typical; VPCs must be associated | service + VPC association |
| Target group | VPC (instance/IP/ALB) or Lambda (function exists) | health check config determines routing — unhealthy targets receive NO traffic | listener rule + traffic splitting |
| Service | service network exists; protocol chosen | service DNS name auto-assigned; auth policy attaches at service level | listener + auth policy |
| Listener rule | service + listener + target group exist | rules evaluated in priority order; first match wins; default rule is fallback | routing decision per request |
| IAM auth policy | service exists | attaches to SERVICE, not rules; must be explicitly put | auth enforcement for ALL paths |
| Service policy (resource-based) | service exists | IAM resource policy controls who can invoke | cross-account invocation |
| VPC association | service network + VPC exist | VPCs NOT associated cannot use Lattice DNS | in-VPC service reachability |
| Cross-account association | service network + RAM share | other account must accept RAM share; then associate VPC | cross-account service access |
| 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 |
| Traffic splitting | listener rule with weighted forwarding | weights are per TG within a rule; sum need not be 100 | canary / blue-green routing |
| Access logs | service network or service exists | delivery is async; first logs within minutes | observability / audit trail |
The service-network-before-everything row is the one a baseline model misses. A service cannot exist without a service network. A VPC cannot use Lattice routing without association. The auth policy cannot be applied without a service.
Cross-dependency gotchas:
- The IAM auth policy attaches at the SERVICE level and governs ALL listener rules and ALL paths. You CANNOT scope auth to a specific path or rule.
- Target group health check status determines routing eligibility. If the health check fails, Lattice routes ZERO traffic to that target. If all targets are unhealthy, clients see 503.
- VPC association is required for the VPC to resolve Lattice service DNS names. Without association, instances in the VPC cannot reach the service via its auto-assigned DNS name.
- Cross-account access requires BOTH a RAM resource share (sharing the service network) AND a resource-based service policy (allowing the other account to invoke the service).
- Custom domain names require an ACM certificate in us-east-1 (the Lattice-managed TLS region), regardless of the service's region.
Expert heuristic: the three-tier Lattice model
A baseline model says "create a service." The correct heuristic recognizes the three-tier hierarchy: service network (top) -> service (middle) -> target group + listener rules (bottom).
Account
└── Service Network (top-level routing plane, 1 per account typical)
├── VPC Associations (which VPCs can use this network)
│ ├── VPC-A (vpc-aaa11122)
│ └── VPC-B (vpc-bbb22233)
├── Service: payments-svc (HTTP)
│ ├── Auth Policy (IAM, at SERVICE level — covers ALL rules)
│ ├── Service Policy (resource-based, for cross-account)
│ ├── Listener (port 80, HTTP)
│ │ ├── Rule 1 (priority 10): path /v2/* → TG-canary 20 + TG-stable 80
│ │ └── Rule 2 (default): path * → TG-stable 100
│ ├── Target Group: TG-stable (INSTANCE, port 8080, health /health)
│ └── Target Group: TG-canary (INSTANCE, port 8080, health /health)
└── Service: inventory-svc (gRPC)
└── ...
Key implication: every resource hangs off the service network. The service network is the first thing to create, and its VPC associations determine which VPCs can reach the services.
Expert heuristic: health check determines routing eligibility
Expert heuristic — health check determines routing eligibility — moved verbatim. Full detail: Listener rules and health.
Expert heuristic: auth policy scope (service, not rule)
Expert heuristic — auth policy scope (service, not rule) — moved verbatim. Full detail: Auth policy and access.
Prerequisites (verify before provisioning)
| Prerequisite | Why it matters | How to verify |
|---|---|---|
| AWS account + region | Lattice is regional | aws sts get-caller-identity |
| VPC exists (instance/IP/ALB TG) | Target groups reference VPC resources | aws ec2 describe-vpcs --vpc-ids <vpc-id> |
| Lambda function exists (Lambda TG) | Lambda TG references function ARN | aws lambda get-function --function-name <name> |
| ALB exists (ALB TG) | ALB TG references ALB ARN | aws elbv2 describe-load-balancers |
| ACM cert in us-east-1 (custom domain) | Lattice custom domains require us-east-1 cert | aws acm list-certificates --region us-east-1 |
| Route53 zone (custom domain DNS) | Domain mapping needs a DNS zone | aws route53 list-hosted-zones |
| IAM perms for auth policy | Auth policy requires vpc-lattice:PutAuthPolicy |
Verify IAM policy |
| Cross-account: RAM share configured | Cross-account needs RAM resource share | aws ram list-resources |
If any prerequisite is missing, output VERDICT: PREREQUISITES_MISSING
and cite the specific gap.
Step 1 — Service network (top-level routing plane)
The service network is the top-level routing plane. It is an account- level construct — NOT a VPC-level construct. Typically one per account.
Step 1 — create service network CLI — moved verbatim. Full detail: Worked examples.
Auth type: AWS_IAM enforces IAM auth by default (the auth policy
still needs PUT on each service). NONE means no IAM auth enforcement
at the network level. Limits: 1 service network per account (soft),
50 VPC associations per network, 1,000 services per network.
Step 2 — Target group (type selection + health checks)
The target group type must be chosen at creation and CANNOT be changed.
| Type | Target | VPC required | Use case |
|---|---|---|---|
| INSTANCE | EC2 instance ID | Yes | EC2-based services |
| IP | IP address | Yes | ECS awsvpc, ENI-attached |
| LAMBDA | Lambda function ARN | No | Serverless functions |
| ALB | ALB ARN | Yes | ALB with Lattice upstream |
Step 2 — instance target group with health check CLI; Step 2 — Lambda target group CLI — moved verbatim. Full detail: Listener rules and health.
Critical: health check status determines routing eligibility. Verify:
Step 2 — verify target health CLI — moved verbatim. Full detail: Listener rules and health.
Step 3 — Service (HTTP/gRPC)
A service is a runnable unit within a service network. It gets an auto-assigned DNS name.
Step 3 — create service CLI — moved verbatim. Full detail: Worked examples.
Protocol: HTTP and gRPC are supported. Set when creating the listener (not the service). A service can have one listener per protocol.
Step 4 — Listener rules (path/header/method routing)
Listeners receive traffic for a service. Rules define routing based on path, header, and HTTP method. Rules are evaluated in priority order; first match wins.
Step 4 — listener and routing rule CLIs (default, path, header) — moved verbatim. Full detail: Listener rules and health.
Step 5 — IAM auth policy (service level, NOT rule level)
The IAM auth policy enforces IAM-based authentication on the SERVICE. It applies to ALL listener rules and ALL paths — you CANNOT scope auth to a specific rule.
Step 5 — IAM auth policy CLI (service level) — moved verbatim. Full detail: Auth policy and access.
Critical: the auth policy is at the SERVICE level. If you need different auth per path, split into separate services with separate auth policies.
Step 6 — Resource-based service policy
The resource-based service policy controls who can INVOKE the service (cross-account access). Separate from the IAM auth policy (which controls request-level auth).
Step 6 — resource-based service policy CLI — moved verbatim. Full detail: Auth policy and access.
Combined with RAM sharing, this enables full cross-account service access.
Step 7 — Service network VPC association
VPCs must be ASSOCIATED with the service network to use Lattice DNS resolution and reach services. Without association, instances in the VPC cannot resolve Lattice service DNS names.
Step 7 — service network VPC association CLI — moved verbatim. Full detail: Worked examples.
Step 8 — Cross-account service access
Cross-account access requires RAM share + service policy.
Step 8 — cross-account access CLI (RAM share + association) — moved verbatim. Full detail: Auth policy and access.
Missing any of the four steps results in AccessDenied.
Step 9 — Custom domain name mapping
Custom domains map a user-facing DNS name to a Lattice service. The ACM certificate MUST be in us-east-1 regardless of the service's region.
Step 9 — custom domain mapping CLI — moved verbatim. Full detail: Worked examples.
Critical: ACM cert must be in us-east-1, and the cert's domain name must match the custom domain.
Step 10 — Traffic splitting (canary)
Traffic splitting routes a percentage of traffic to a canary target group via weighted forwarding in a listener rule. Weights are relative (not percentage); weights 1 and 4 produce the same 20/80 split as 20 and 80.
Step 10 — traffic splitting (canary) CLI — moved verbatim. Full detail: Listener rules and health.
Progressive canary (20 -> 50 -> 100%): update rule weights with
update-rule to shift traffic gradually.
Step 11 — Access log delivery
Access logs capture Lattice request details for observability and audit. Delivery is async; first logs appear within 5-10 minutes.
Step 11 — access log delivery CLI — moved verbatim. Full detail: Auth policy and access.
Step 12 — Pricing (per GB processed)
| Component | Pricing |
|---|---|
| GB processed | ~$0.025-0.10 per GB (varies by region) |
| Service-hour | ~$0.015 per hour per service |
| Target group, service network, custom domain | Free |
| Access logs | CloudWatch/S3 standard charges |
Key implication: GB processed is the dominant cost driver. For high-traffic services, estimate monthly GB and multiply. The per-service hourly charge is minor for a small number of services.
Step 13 — Recent features
Step 13 — recent features (2023-2026) — moved verbatim. Full detail: Advanced Patterns.
NEVER do these things
-
NEVER assume auth policy can be scoped per listener rule. The IAM auth policy attaches to the SERVICE, not individual rules. It governs ALL paths on the service. Need different auth per path? Create separate services.
-
NEVER assume unhealthy targets receive traffic. VPC Lattice routes ZERO traffic to targets failing health checks. If all targets in a TG are unhealthy, clients see 503. Always verify health check status before expecting traffic.
-
NEVER skip VPC association with the service network. VPCs NOT associated cannot resolve Lattice service DNS names and cannot reach services. Association is a prerequisite for in-VPC service access.
-
NEVER assume the service network is per VPC. It is an account- level construct (1 per account typical). Multiple VPCs are ASSOCIATED with the same service network.
-
NEVER attempt cross-account access without RAM + service policy. Cross-account requires BOTH a RAM resource share AND a resource-based service policy. Missing either results in AccessDenied.
-
NEVER request a custom domain ACM certificate outside us-east-1. Lattice custom domains require the ACM cert in us-east-1 regardless of the service's region.
-
NEVER change the target group type after creation. The type (INSTANCE, IP, LAMBDA, ALB) is immutable. To change type, create a new target group and update listener rules.
-
NEVER assume traffic splitting weights must sum to 100. Weights are relative. Weights 1 and 4 produce the same 20/80 split as 20 and 80. Lattice normalizes.
-
NEVER forget the listener default action. The default action is the fallback when no rule matches. Without it, unmatched requests fail.
-
NEVER assume access logs are real-time. Log delivery is async; first logs appear within 5-10 minutes.
Output format
VPC_LATTICE: <service-network-id> → <service-id> (<service-dns-name>)
VERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING
CHECKLIST:
[✓|✗] Service network: <sn-id> (auth type: AWS_IAM | NONE)
[✓|✗] Target group: <tg-id> (type: INSTANCE | IP | LAMBDA | ALB, port: <port>)
[✓|✗] Health check: path <path>, interval <n>s — targets <n>/<n> healthy
[✓|✗] Service: <svc-id> (protocol: HTTP | gRPC, DNS: <dns-name>)
[✓|✗] Listener: <listener-id> (port <port>, protocol HTTP | gRPC)
[✓|✗] Listener rules: <n> rule(s) (path/header/method match)
[✓|✗] Auth policy: IAM auth at SERVICE level (covers ALL rules) | None
[✓|✗] Service policy: resource-based policy (cross-account) | Same-account
[✓|✗] VPC association: <vpc-id> associated with <sn-id> — ACTIVE
[✓|✗] Cross-account: RAM share to <account-id> | Same-account
[✓|✗] Custom domain: <domain> → <service-dns> (ACM us-east-1) | Not configured
[✓|✗] Traffic splitting: canary <n>% / stable <n>% | Single TG
[✓|✗] Access logs: CloudWatch | S3 | Disabled
[✓|✗] Tags: <key=value list>
VERIFICATION_COMMANDS:
aws vpc-lattice get-service-network --service-network-identifier <sn-id>
aws vpc-lattice get-service --service-identifier <svc-id>
aws vpc-lattice list-targets --target-group-identifier <tg-id>
aws vpc-lattice list-listeners --service-identifier <svc-id>
aws vpc-lattice list-rules --service-identifier <svc-id> --listener-identifier <listener-id>
aws vpc-lattice list-service-network-vpc-associations --service-network-identifier <sn-id>
Worked example — HTTP service with canary traffic splitting
VPC_LATTICE: sni-aaa111 → svc-bbb222 (payments-svc-aaa.example.com)
VERDICT: READY_TO_DEPLOY
CHECKLIST:
[✓] Service network: sni-aaa111 (auth type: AWS_IAM)
[✓] Target group: tgc-stable (type: INSTANCE, port: 8080)
[✓] Health check: path /health, interval 30s — targets 3/3 healthy
[✓] Service: svc-bbb222 (protocol: HTTP, DNS: payments-svc-aaa.example.com)
[✓] Listener: lstn-ccc333 (port 80, protocol HTTP)
[✓] Listener rules: 2 rules (path /v2/* → canary split, default → stable)
[✓] Auth policy: IAM auth at SERVICE level (covers ALL rules)
[✓] Service policy: resource-based policy (cross-account for 999999999999)
[✓] VPC association: vpc-aaa11122 associated with sni-aaa111 — ACTIVE
[✓] Cross-account: RAM share to 999999999999
[✓] Custom domain: payments.internal.example.com → payments-svc-aaa.example.com (ACM us-east-1)
[✓] Traffic splitting: canary 20% / stable 80%
[✓] Access logs: CloudWatch (/aws/vpc-lattice)
[✓] Tags: Environment=production, Topology=canary
VERIFICATION_COMMANDS:
aws vpc-lattice get-service-network --service-network-identifier sni-aaa111
aws vpc-lattice get-service --service-identifier svc-bbb222
aws vpc-lattice list-targets --target-group-identifier tgc-stable
aws vpc-lattice list-rules --service-identifier svc-bbb222 --listener-identifier lstn-ccc333
aws vpc-lattice list-service-network-vpc-associations --service-network-identifier sni-aaa111
Error handling
Error handling deep dives — moved verbatim. Full detail: Error handling.
References (load on demand)
- Auth policy and access — auth-scope heuristic, Step 5/6/8/11 CLIs (auth policy, service policy, RAM cross-account, access logs)
- Listener rules and health — health-check heuristic, Step 2/4/10 CLIs (target groups, listeners/rules, canary)
- Worked examples — Step 1/3/7/9 CLIs (service network, service, VPC association, custom domain)
- Error handling — 503 no healthy targets, cross-account AccessDenied, DNS, reachability, auth-policy fixes
- Advanced patterns — recent features 2023-2026
Domain
AWS CloudOps / Amazon VPC Lattice Service Networking Provisioning & Application-Layer Routing.
AWS documentation
- VPC Lattice Guide — https://docs.aws.amazon.com/vpc-lattice/latest/ug/what-is-vpc-lattice.html
- Service networks — https://docs.aws.amazon.com/vpc-lattice/latest/ug/service-networks.html
- Target groups — https://docs.aws.amazon.com/vpc-lattice/latest/ug/target-groups.html
- Listener rules — https://docs.aws.amazon.com/vpc-lattice/latest/ug/listeners.html
- Auth policies — https://docs.aws.amazon.com/vpc-lattice/latest/ug/auth-policies.html
- Custom domains — https://docs.aws.amazon.com/vpc-lattice/latest/ug/custom-domains.html
- Access logs — https://docs.aws.amazon.com/vpc-lattice/latest/ug/access-logs.html
- Cross-account access — https://docs.aws.amazon.com/vpc-lattice/latest/ug/cross-account.html
- VPC Lattice pricing — https://aws.amazon.com/vpc/lattice/pricing/
04 同仓库更多 Skills
xray-tracing-deployer
Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL / method / service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry / ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS / EKS / Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.
wellarchitected-workload-auditor
Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.
wellarchitected-review-operator
Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer / get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.
wafv2-web-acl-deployer
Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB/API Gateway/CloudFront, or configuring CAPTCHA/Challenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.
wafv2-web-acl-auditor
Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow/bypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.
waf-rule-deployer
Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.