#15 Advanced AWS Networking

Pitfalls That You Should Avoid When Designing A Network Architecture

Don't miss our blog post Advanced AWS Networking: Pitfalls That You Should Avoid, the written version of this podcast episode.

AWS offers shiny and powerful networking services. However, you should know about the pitfalls when designing advanced networking architectures for AWS. I will share some pitfalls that came to my attention when consulting clients to get the most out of AWS.

You will learn how to answer the following questions:

VPC Peering or Transit Gateway?

A Transit Gateway simplifies peering VPCs. However, there is a baseline costs of $36.00 per month for each VPC attached to the Transit Gateway.

NAT Gateway or Public Subnet?

Adding NAT Gateways to your architecture costs $96.00 per month for 3 availability zones. Also, the costs for outbound network traffic will increase by 50%. From a economical point of view it makes sense to place workloads with high outgoing network throughput into public subnets.

VPC Endpoints or NAT Gateway?

Always add VPC Endpoints for S3 and DynamoDB. But do the math, when adding VPC Endpoints for other AWS services to your network. Using a NAT Gateway might be cheaper.

CloudFront or Akamai, Cloudflare, Fastly …?

When choosing a CDN provider besides CloudFront, make sure you have taken into account the additional costs for outbound traffic.

Route 53 Resolver or Public Hosted Zone?

Share Route 53 Outbound Resolvers between VPCs and AWS accounts to reduce costs. Think about using Public Hosted Zones instead of paying $180.00 per month for an Route 53 Inbound Resolver.

Amazon Web Services in Action a comprehensive introduction to computing, storing, and networking in the AWS cloud. You'll find clear, relevant coverage of all the essential AWS services you to know, emphasizing best practices for security, high availability and scalability. Buy now!!

We ask for feedback! Please rate or review our podcast on Apple Podcasts or wherever you listen to your favorite shows. Or send us a message via Twitter (Andreas and Michael) or LinkedIn (Andreas and Michael).

Episode source