2 Answers
- Newest
- Most votes
- Most comments
2
You're right. And you can reduce the NAT GW costs by using a shared egress VPC architecture. It would reduce the number of NAT GWs you need (less cost) but also allow you to deploy centralized egress filtering if that is something you would value from security perspective. Thing to keep in mind is that NAT GWs don't have infinite bandwidth, so you should keep an eye on usage.
- Business case for shared NAT GWs https://carriagereturn.nl/aws/vpc/nat/tgw/cost/saving/2022/02/07/sharing-natgw.html
- Shared egress VPC https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/centralized-egress-to-internet.html
- Monitoring NAT GW usage https://cloudonaut.io/nat-gateway-monitoring-with-cloudwatch-metrics-and-alarms/
1
Check out the blog post Identify and optimize public IPv4 address usage on AWS. It covers the use of NAT gateway and ALB, and provides cost comparison with all public IP, among other items
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
what will happen If I share the NATGateway with the help of Resource Access Manager?
NAT GWs can not be shared with RAM. Actually RAM only work with very limited set of resources. Check the documentation for details.
Thanks much Kallu. Let me go through the document and finalize which one would be best for me!