Limits/quotas (transparency & increase)

Why important?

Hidden limits are a common go-live blocker. Transparent quotas plus a process to increase them are critical for scaling and planning.

How measured?

• 0 = Limits/quotas opaque, adjustments unclear/impossible
• 1 = Little information, adjustments ad-hoc only
• 2 = Documented, but processes/SLAs unclear
• 3 = Transparent quotas + defined process to request increases
• 4 = Self-service/automation + clear SLAs/docs
• 5 = Very transparent + API/automated + auditable processes evidenced
• N/A = no reliable evidence

Sources / Evidence

• https://docs.ionos.com/cloud/security/network-security-groups/nsg-faqs
• https://docs.ionos.com/cloud/support/general-information/service-catalog
• https://docs.stackit.cloud/products/compute-engine/server/basics/regions-and-availability-zones/
• https://aws.amazon.com/servicequotas/
• https://docs.stackit.cloud/products/runtime/kubernetes-engine/basics/quotas-and-limits/
• https://support.us.ovhcloud.com/hc/en-us/articles/22188629448339-Increasing-Public-Cloud-Quotas
• https://www.open-telekom-cloud.com/service-description
• https://docs.oracle.com/en-us/iaas/Content/General/Concepts/servicelimits.htm
• https://docs.plusserver.com/de/container/managed-kubernetes/introduction/limits-and-quotas/
• https://upcloud.com/docs/getting-started/upcloud-essentials/
• https://community.exoscale.com/product/compute/instances/overview/
• https://docs.hetzner.com/cloud/general/faq/
• https://www.scaleway.com/en/docs/organizations-and-projects/additional-content/organization-quotas/

Validation questions (RFP)

• How transparent are limits/quotas? Is there a self-service process to increase them? What are the SLAs?

Scores comparison