aws-networking

Plan and implement secure AWS networking architectures with VPCs, subnets, and security groups.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/tomz/agent-skills --skill aws-networking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-networking
Source: https://github.com/tomz/agent-skills/tree/main/aws-networking
Command: npx skills add https://github.com/tomz/agent-skills --skill aws-networking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AWS networking guidance for designing, securing, and operating robust, scalable AWS networks across VPCs, subnets, security controls, edge services, and connectivity patterns.

Core Features & Use Cases

  • VPC design and subnet planning for multi-AZ deployments.
  • Security posture with Security Groups, NACLs, and edge services like ALB/NLB, CloudFront, and Route 53.
  • Connectivity patterns using Transit Gateway and PrivateLink for centralized or hub-and-spoke architectures.
  • Observability and governance with VPC Flow Logs, monitoring, and cost-aware design considerations.
  • Use cases include migrating monoliths to a well-segmented VPC, building per-environment networks, and multi-region connectivity.

Quick Start

Create a secure, multi-AZ VPC design blueprint including subnets, routing, and security groups.

Frequently Asked Questions about aws-networking

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

FAQPage Schema
What is the best way to design a secure multi-AZ AWS VPC architecture?

A secure multi-AZ AWS VPC architecture requires segmenting subnets across availability zones and enforcing least privilege with Security Groups and NACLs. This strategy ensures network isolation, scalable connectivity, and deterministic infrastructure changes suitable for automated environment reproducibility.

How do I configure Transit Gateway and PrivateLink for AWS hub-and-spoke connectivity?

Configuring Transit Gateway and PrivateLink for AWS hub-and-spoke connectivity establishes centralized routing and private access to services. This connectivity pattern simplifies multi-VPC or hybrid network topologies while maintaining secure, scalable communication without exposing traffic to the public internet.

When do I need NACLs instead of Security Groups for AWS network isolation?

You need NACLs instead of Security Groups when requiring stateless subnet-level firewall protection in your AWS network. NACLs provide explicit allow/deny rules for traffic filtering at the network perimeter, complementing stateful Security Groups which operate at the instance interface level for least privilege enforcement.

How do I use VPC Flow Logs for monitoring and cost-aware AWS network governance?

Using VPC Flow Logs for monitoring AWS network governance involves capturing IP traffic metadata to analyze traffic patterns and security postures. This observability data enables cost-aware design adjustments, identifies anomalous routing behavior, and verifies isolation compliance across multi-AZ deployments.

Does this AWS networking guidance support migrating monoliths to well-segmented VPCs?

Yes, this AWS networking guidance supports migrating monoliths to well-segmented VPCs by providing deterministic blueprints for subnet planning and edge services. It enforces isolation and least privilege best practices, ensuring monolithic components are separated into secure, scalable per-environment networks.