networking

Design and troubleshoot AWS networking architectures and connectivity configurations.

15|20|Updated May 11, 2026

Search Tags:#aws #networking #vpc #route53 #transit gateway #security groups #subnets

Ready to run

npx skills add https://github.com/awslabs/startups --skill networking-awslabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: networking
Source: https://github.com/awslabs/startups/tree/main/solution-architecture/plugins/aws-dev-toolkit/skills/networking
Command: npx skills add https://github.com/awslabs/startups --skill networking-awslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps AWS teams design, review, and troubleshoot complex networking environments by providing architectural guidance for VPCs, connectivity, security controls, and DNS configurations.

Core Features & Use Cases

VPC Architecture Design: Creates production-ready subnet layouts, CIDR plans, routing strategies, NAT Gateway designs, and VPC endpoint configurations.
Network Security and Connectivity Review: Analyzes security groups, NACLs, Transit Gateway, VPC peering, and connectivity issues using AWS networking best practices.
Use Case: Help an engineering team review a multi-account AWS network design, identify scaling risks, and recommend improvements for availability, security, and cost efficiency.

Quick Start

Use the networking skill to review my AWS VPC architecture and recommend improvements for security, availability, and cost optimization.

Frequently Asked Questions about networking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a production-ready AWS VPC architecture with proper subnetting and routing?▼

To design a production-ready AWS VPC architecture, you need a structured subnet layout, a non-overlapping CIDR allocation plan, routing strategies, and NAT Gateway configurations. This involves planning high availability patterns across multiple Availability Zones to ensure network resilience.

What is the best way to troubleshoot AWS Transit Gateway connectivity and routing issues?▼

Troubleshooting AWS Transit Gateway connectivity requires analyzing route tables, security group rules, and VPC peering configurations to identify misconfigurations. By applying AWS networking best practices, you can isolate traffic flow issues and resolve routing conflicts across multi-account environments.

How do I review AWS security groups and NACLs to identify network scaling risks?▼

Reviewing AWS security groups and NACLs involves analyzing inbound and outbound rule sets against scaling risks and connectivity requirements. This process validates network security controls, identifies overly permissive access, and recommends improvements for availability and cost efficiency.

Can I use this approach to plan Route53 DNS configurations for a multi-account AWS network?▼

Yes, you can plan Route53 DNS configurations for a multi-account AWS network by integrating routing strategies with endpoint configurations. This approach ensures reliable name resolution across VPC peering and Transit Gateway deployments while maintaining security boundaries.

When should I use VPC peering instead of a Transit Gateway for AWS network connectivity?▼

You should use VPC peering for simple one-to-one AWS network connectivity, while Transit Gateway is better for complex many-to-many connectivity. Transit Gateway deployments simplify routing management and scaling across multiple VPCs, reducing the operational overhead of peering connections.

Why does my AWS VPC endpoint configuration fail to resolve private DNS records?▼

AWS VPC endpoint configuration fails to resolve private DNS records when Route53 inbound endpoints or subnet route tables are misconfigured. Debugging network connectivity scenarios requires verifying endpoint policies, DNS settings, and security group controls to restore traffic flow.