I have a NAT Gateway with multiple EIPs. Does AWS charge for the extra EIPs?

I’ve never seen a NAT gateway with multiple EIPs. What I deploy and see is multiple NAT gateways with a single EIP. Deploy a NAT gateway in each AZ with a single EIP. There isn’t a way for a NAT gateway to use multiple EIPs.

I’m wondering if the question isn’t worded correctly.

Come February you will be charged for each public IPV4 in use.

To ensure efficient use of Elastic IP addresses, we impose a small hourly charge if an Elastic IP address is not associated with a running instance, or if it is associated with a stopped instance or an unattached network interface. While your instance is running, you are not charged for one Elastic IP address associated with the instance, but you are charged for any additional Elastic IP addresses associated with the instance. reference: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#eip-pricing

However, starting from Feb 1, 2024 you will be charged for every EIPs you provision in your account, attached and not attached. That is including the primary EIP attached to the NAT gateway

Hi,

I don't agree with above answers, so let me share my opinion on this edge case.

Elastic IP addresses An Elastic IP address is a public IPv4 address you can allocate to your AWS account, as opposed to a specific resource. Using an Elastic IP address instead of an EC2 public IPv4 address allows you to manage how it is associated with resources in your VPC. You can disassociate and reassociate an Elastic IP address without releasing it back to the Amazon pool. Today, there is no charge for the first Elastic IP (EIP) address you associate with a running instance, but you are charged for each additional EIP, and for idle EIPs assigned to your account. Starting February 1, 2024, the new charges will apply to all Elastic IP addresses in your AWS account.

In this paragraph EC2 is just example, NAT Gateways works the same in this case.

More details you can find by the link

All EIPs, including the primary one, will be charged at the public rate

https://aws.amazon.com/blogs/networking-and-content-delivery/identify-and-optimize-public-ipv4-address-usage-on-aws/