Closed rbracewell closed 1 year ago
'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.'
Hey @rbracewell , sorry for the long silence on this issue, but thanks for creating an issue for this suggestion!
Is there any way you track these charges or have a way to determine when it's better to have the NAT local for costs? If so, is there any specific cost or billing data you use in that determination? Or any specific AWS CLI commands or APIs to get specific data?
Havent looked at ways to surface this yet was hoping tools like Steampipe and this mod had such a control.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
Hey @rbracewell, sorry for the delayed response.
I have checked various docs and API responses of aws_ec2transit and other vpc_ tables but could not find a way to map or track the above information. Please help us with your insights and findings if you have any.
Hey @rbracewell, We are closing this issue because we have not heard from you. Please feel free to reopen the issue if you want to share or discuss anything.
When you centralize NAT gateway using Transit Gateway, you pay an extra Transit Gateway data processing charge — compared to the decentralized approach of running a NAT gateway in every VPC. In some edge cases when you send huge amounts of data through NAT gateway from a VPC, keeping the NAT local in the VPC to avoid the Transit Gateway data processing charge might be a more cost-effective option.
Refer to AWS whitepaper.
It would be nice to surface a control to track this if possible.