F5 Distributed Cloud currently allows API Rate Limit rules to be defined for a maximum of 20 endpoints. Our environment has more than 1,000 API endpoints, so this limit is insufficient for our requirements.

Additionally, when API Rate Limit is configured, it replaces the general Custom Rate Limit configuration. We need to maintain a general rate limit while applying separate rate limits to specific API endpoints.

We request the following improvements:

• Increase the API Rate Limit endpoint limit from 20 to at least 500, preferably 1,000+ endpoints.

• Allow Custom Rate Limit Parameters and API Rate Limit configurations to be managed independently.

Currently, these two configurations are available as separate options under Rate Limiting, but selecting one replaces the other. We would like to be able to use both configurations simultaneously, with a general Custom Rate Limit and additional API-specific Rate Limit policies.