Separate Elastic IP (EIP) cost for NAT Gateway in AWS Pricing Calculator

When you create a NAT Gateway in AWS, an Elastic IP (EIP) is indeed automatically associated with it. This is necessary because the NAT Gateway needs a static public IP address to allow instances in private subnets to communicate with the internet.

Regarding the AWS Pricing Calculator and cost structure:

1. The hourly cost of a NAT Gateway does not include the cost of the associated Elastic IP. These are billed as separate line items.

2. However, there is no additional charge for the Elastic IP when it's associated with a running NAT Gateway. AWS only charges for Elastic IPs that are not associated with running instances or are associated with stopped instances.

3. The primary costs for NAT Gateways are:

• An hourly charge for each hour the NAT Gateway is provisioned and available
• Data processing charges for each gigabyte of data processed through the NAT Gateway

There are scenarios where additional EIP costs could apply when using NAT Gateways:

1. If you allocate an EIP but don't immediately associate it with a NAT Gateway, you'll be charged for the unassociated EIP.

2. If you delete a NAT Gateway but forget to release its associated EIP, you'll be charged for the now-unassociated EIP.

3. If you have multiple NAT Gateways (for example, one per Availability Zone for high availability), each will require its own EIP, but as long as they're associated with running NAT Gateways, there won't be additional EIP charges.

When using the AWS Pricing Calculator, you should focus on the NAT Gateway hourly and data processing charges, as the EIP cost is effectively included as long as the NAT Gateway is running.
Sources
Billing NAT Gateway | AWS re:Post
Is there no longer a remapping cost for Elastic IPs? | AWS re:Post
how to provide static ip address for external system to whitelist my ec2 in private subnet ip address in aws? | AWS re:Post
Amazon VPC Pricing
Bill on NAT gateways | AWS re:Post

I believe the 2 answers are incorrect. That’s how it used to be before AWS started charging for a public IPs back in FEB last year. All public IPV4 addresses are now chargeable whether in use or not.

There is a charge for all Elastic IP addresses whether they are in use (allocated to a resource, like an EC2 instance) or idle (created in your account but unallocated).

AWS charges for all public IPv4 addresses, including public IPv4 addresses associated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#eip-pricing

https://aws.amazon.com/vpc/pricing/