AWS does not provide any CloudWatch (CW) metrics to monitor available IPs in VPC subnets. It can be difficult to avoid shortages and get alerted when you are approaching the limit.
Subnet-Watcher monitors the remaining free IP addresses in AWS VPC subnets (both public and private) using some CloudWatch custom metrics. It also sets up alerts to provide complete visibility on your VPC CIDR IP space.
AvailableIpAddressCount- Number of IP Addresses availableTotalIpAddressCount- Quantity of Total IP Addresses in subnet (based on CIDR size minus the 5 AWS reserved Ips)AvailableIpAddressPercent- Percentage of available IP AddressesAvailableNetworkInterface- Number of Elastic Network Interfaces Available (ENI) in VPC (withstatus=available)
AWS recently released VPC IPAM, however, I have not been able to find any benefits from it and it seems to be a costly solution to this problem.
Change it in the Makefile
| Parameter | Description | Required | Default Value |
|---|---|---|---|
| Product | Name of the Product | yes |
subnet-watcher |
| Project | Name of your Project | yes |
|
| Environment | Name of your environment | yes |
|
| AWSRegion | Used AWS Region (target of deployment) | yes |
eu-west-1 |
| AlertsRecipient | Recipient of SNS Message (Alerts) | yes |
|
| PercentageRemainingWarning | Percentage Remaining IP for alerting | yes |
20 |
Optional: You can modify the CloudFormation template to specify the VPC_ID (empty by default) as an environment variable, which will cause the check to be performed on the specified VPC.
$ make deploy
I was inspired by the following projects and decided to create my own version that met my specific needs and included some additional features.