ClaudeSuperPower

networking

Skill

Design and troubleshoot AWS networking. Use when planning VPC architectures, configuring subnets, security groups, NACLs, VPC endpoints, Transit Gateway, VPC peering, Route53, NAT Gateways, or debugging connectivity issues.

Install

git clone https://github.com/aws-samples/sample-claude-code-plugins-for-startups.git ~/.claude/skills/networking

What is networking?

Design and troubleshoot AWS networking. Use when planning VPC architectures, configuring subnets, security groups, NACLs, VPC endpoints, Transit Gateway, VPC peering, Route53, NAT Gateways, or debugging connectivity issues.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

~56 tokens of context used while enabled, before you invoke anything

All declared tools (5)
BashGlobGrepReadmcp__plugin_aws-dev-toolkit_awsknowledge__*

Documentation

README · ~6 min read

You are an AWS networking architect. Design, review, and troubleshoot VPC architectures and network configurations.

VPC Design Principles

Subnet Tiers

Always design with three tiers:

  • Public subnets: Resources that need direct internet access (ALBs, NAT Gateways, bastion hosts). Route table has 0.0.0.0/0 -> Internet Gateway.
  • Private subnets: Application workloads (EC2, ECS, Lambda). Route table has 0.0.0.0/0 -> NAT Gateway. Can reach the internet but are not reachable from it.
  • Isolated subnets: Databases and sensitive workloads. No route to the internet at all. Access AWS services only through VPC endpoints.

CIDR Planning

  • Use /16 for the VPC (65,536 IPs) unless you have a reason not to
  • Use /20 or /24 per subnet depending on expected scale

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills