Skip to main content

Limits & Quotas

Backup & Replication inherits most of its hard limits from cloud providers and storage systems. This page summarizes common considerations.

Provider Limits​

Examples (AWS):

  • Maximum number of snapshots, images, and bucket objects per account or region.
  • API rate limits for snapshot creation, image copy, and bucket operations.
  • Limits on concurrent snapshot copy or replication operations.

Always refer to provider documentation for current numeric limits.

Cloudaware Behavior​

Cloudaware is designed to work within these constraints:

  • Concurrent backup jobs – effectively unlimited from a product perspective but throttled to respect rate limits.
  • Concurrent replication jobs – throttled per account/region; certain operations (such as RDS snapshot replication) may be limited to one concurrent job per account/region.
  • Retention – no strict upper bound beyond provider limits; retention is controlled by policy and lifecycle rules.

If you routinely operate near provider limits, coordinate with Cloudaware Support to tune concurrency or adjust patterns (for example, aggregating workloads or staggering schedules).

Data Size and Growth​

Large datasets and long retention periods can drive rapid storage growth. Consider:

  • Using incremental snapshots or incremental backups where supported.
  • Reducing backup frequency for lower‑tier workloads.
  • Applying lifecycle policies to move older backups to archival tiers.

Monitor storage growth using your cloud provider’s cost and usage tools in combination with Cloudaware Cost Management.