Limits & Quotas
Use this guide to plan Cloudaware Patch Management at scale.
Cloudaware Patch Management does not impose a fixed limit on the number of customer instances that can be patched. To maintain stability, predictability, and control over rollback operations when needed, Cloudaware recommends organizing instances into patch groups. Practical limits may still vary by environment and are subject to change.
Typical Limits to Consider
- Maximum recommended number of hosts per job or wave.
- Reasonable concurrency levels per account or region.
- Timeouts for package operations on slow hosts.
- Retention periods for detailed job logs.
Design your processes to stay within safe bounds — for example, by splitting very large estates into multiple jobs and waves.