If you’re running into issues with your AWS EC2 instant fleets showing an error message about reaching the maximum fleet count, don’t worry. Here’s how to understand and resolve the situation.
First, it’s important to know that instant EC2 fleets are supposed to have an unlimited quota. This means they shouldn’t be restricted by a maximum number of fleets, unlike standard fleets which are limited to 1,000 per region. The standard limit applies only to active, deleted, or terminating fleets, not to instant fleets.
If you run commands to describe your fleets and they return empty results across all states, and you’ve confirmed that no fleets exist in your account after checking the logs, it might be an internal issue with AWS. Sometimes the internal tracking for fleet numbers can get out of sync, leading to errors even when there are no actual fleets.
Since your account shows no fleets, but you’re still getting error messages like MaxFleetCountExceeded, it indicates a backend problem. The error code L-89D02A44 combined with NoSuchResourceException suggests that the system’s internal count might be incorrect, and that’s why it’s preventing new fleets from being launched.
The best way to fix this problem is to contact AWS Support directly through the AWS Support Center. When you reach out, include the specific request IDs related to your attempts. These identifiers will help AWS engineers trace what’s happening behind the scenes and identify the mismatch in fleet count. Support staff have access to internal logs and metrics that aren’t available to customers and can resolve the issue more effectively.
If your current support plan doesn’t provide timely responses needed for your production workloads, consider upgrading to a plan that offers faster support options. Quick assistance can save you time and keep your projects running smoothly.
For additional information, you can review AWS documentation on EC2 fleet quotas and fleet states for more details on how these limits and statuses work.