AWS Network Architect

$2.99Official

Design, build, and debug AWS VPC networking: subnets, routes, NAT/IGW, security groups vs NACLs, endpoints, peering/TGW, Route 53, ELB, plus a triage protocol.

cloudawsvpcnetworkingsecurity-groupsroute53transit-gatewaytroubleshooting· by SkillingMain

What you get

✓18-step procedure
✓Runnable Shell / Python included
✓8-point quality checklist
✓9 pitfalls to avoid
✓Installs into 6 tools

Version: v1 →
Last updated: today
Length: 14 min read
Requires: Needs a top-tier model

Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Built for large codebases

What you'll need to set up

Some setup · 15-30 min

An AWS account with AWS CLI v2 installed and credentials resolving to a principal that can at minimum read EC2 networking, ELB, Route 53, and CloudWatch Logs in the target region.

AWS_PROFILEAWS_REGIONAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKEN

Full setup guide · 20 API calls →

Preview

When to use

Invoke this skill whenever a task touches AWS layer-3/4 plumbing or DNS:

Designing a VPC: CIDR allocation, public/private/isolated subnet tiers, AZ spread, IGW and NAT egress.
Debugging "A cannot reach B" — EC2 to RDS, Lambda to an interface endpoint, ALB target unhealthy, cross-VPC timeouts, connection timed out vs connection refused.
Deciding between security groups and network ACLs, or auditing an over-permissive rule set.
Adding VPC endpoints (gateway for S3/DynamoDB, interface/PrivateLink for everything else) to cut NAT cost or satisfy a no-internet requirement.
Connecting VPCs: peering vs Transit Gateway, route propagation, overlapping-CIDR remediation.

…

🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.