Werk #19286: Fix AWS EC2 limits to use actual Service Quotas API values
| Component | Checks & agents | ||||||
| Title | Fix AWS EC2 limits to use actual Service Quotas API values | ||||||
| Date | May 20, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
Previously, the Amazon Web Services (AWS) check for EC2 limits had an option to fetch limits from the AWS API, but several limits were still using hardcoded defaults instead:
- VPC Elastic IP addresses: hardcoded to 5 — now read from the AWS Service Quotas API (quota: "EC2-VPC Elastic IPs")
- VPC security groups: hardcoded to 2500 — now read from the AWS Service Quotas API (quota: "VPC security groups per Region")
- VPC security groups of elastic network interface: hardcoded to 5 — now read from the AWS Service Quotas API (quota: "Security groups per network interface")
If you've raised any of these quotas above their defaults in your AWS account, the AWS/EC2 Limits service will now reflect your actual quota.