What is the maximum count of objects, rules and other configuration based objects be used in F5-ASM, AFM & APM

There is no limitation built into the software, because the software is meant to handle various hardware and even future hardware. You can add as much as your hardware can handle.

All operating systems have limits, explicitly stated or not, that a software must operate within, on top of the limits it sets for itself. As automation - not a bad thing in itself - has become a fad (read "not sensible"), there is a lot of pressure for F5 admins to just do it anyhow in order to meet the "business requirement". So this is a question we do need an answer for in planning for hundreds or thousands of objects to be created as the result of the automation process.

It is not hard to get the limits of CentOS, which F5 is based on, from its source code, but not easy to get the limits of the other things. And I suppose we'd need to know particularly the supported limits, ones that would not impact on performance and service availability.

Thanks for sharing your real world experience.

You could talk to your sales representatives or professional services for some advice on sizing your deployment. Unfortunately there is no single magic number to determine the maximum size of a deployment. ASM/APM I know to be trickier to size up, especially if you add in features such as the real-time policy builder.

As the others stated, the deployment size would be limited by your hardware's overall capacity. In terms of number of objects, I've been told it's simply limited by the available memory, but that obviously would change based on your expected number of current connections and other factors.