As of February 1, 2024, AWS will implement a $0.005 per IP per hour charge for all public IPv4 addresses, excluding Bring Your Own IPs (BYOIP). This change may result in an increased cost of operations and a need for closer budget management for AWS customers.

Optimizing Public IPv4 Usage in AWS Services**

  • Amazon EC2

    • Disable auto-assignment of public IPv4 addresses and use Amazon EC2 Instance Connect for secure instance access.
  • Amazon Elastic Load Balancer and AWS Global Accelerator

    • Manage inbound internet traffic to optimize public IPv4 utilization.
  • Virtual Private Cloud (VPC)

    • Prioritize private subnet usage, utilize VPN for remote access, and implement NAT Gateway for secure internet access.
  • Amazon RDS and Opensearch

    • Place database instances in private subnets for increased security and reduced need for public IPs.
  • Cross-account Resource Access

    • Utilize VPC Peering, Transit Gateways, and AWS Resource Access Manager to efficiently manage resources across accounts and limit public IPv4 usage.