zoph-io / subnet-watcher Goto Github PK

New from AWS: https://aws.amazon.com/about-aws/whats-new/2023/08/amazon-vpc-ip-address-utilization-metrics-aws-resources/

Amazon VPC IP Address Manager (IPAM) now supports three new CloudWatch metrics — VpcIPUsage, SubnetIPUsage, and PublicIPv4PoolIPUsage, that allow you to identify underutilized or near full capacity IP address ranges, optimizing your IP address usage on AWS. These metrics proactively track IP address usage across resources such as Amazon Virtual Private Clouds (Amazon VPCs), subnets, and Public IPv4 Pools. You can also set alarms for these metrics in Amazon CloudWatch to receive notifications when an IP address usage threshold is breached. Moreover, for a consolidated view of all IP address-related insights, these metrics are available on the IPAM Dashboard.

The VpcIPUsage metric measures the percentage of IPs allocated to subnets within an Amazon VPC, out of the Amazon VPC’s total IP address space. The SubnetIPUsage metric represents the percentage of IPs that are active, out of the subnet’s total IP address space. The PublicIPv4PoolIPUsage metric measures the number of Elastic IP addresses (EIPs) allocated from the pool, divided by the total number of IPs in the pool. Using these metrics, you can configure CloudWatch to alarm you if any of your resource’s IP address usage goes beyond a certain percentage, so you can take proactive action before the resource runs out of IP addresses. For example, you can associate a secondary IPv4 CIDR to your VPC proactively when your IP address for the VPC reaches 90% usage.

These metrics are available within Amazon VPC IPAM in all commercial AWS Regions, including the AWS GovCloud (US) Regions, but excluding China (Beijing, operated by Sinnet) and China (Ningxia, operated by NWCD).

To learn more, view the Amazon VPC IPAM documentation. There is no additional charge for using this feature. For details on Amazon VPC IPAM pricing, visit our pricing page.