Skip to main content

Configure AWS Backups

Use this guide to configure scheduled AWS backups through Cloudaware.

Confirm Asset Coverage​

In Cloudaware CMDB, confirm that the target assets are discovered and have ownership context:

  • AWS account.
  • Region.
  • Application or business service.
  • Environment.
  • Owner or team.
  • Service tier or RPO/RTO target.

Typical supported AWS workloads include:

  • EBS-root EC2 instances, backed up as AMIs with EBS snapshots.
  • RDS instances and clusters, backed up as RDS snapshots.

Define Backup Intent​

Apply a backup policy tag to the asset or to the parent object from which the asset inherits backup policy. A common pattern is:

gig-backup=3d-10w-12m

This example keeps:

  • 3 daily backups.
  • 10 weekly backups.
  • 12 monthly backups.

Use AWS Backup Tags for supported tag patterns.

Configure Backup Windows​

Choose backup windows that avoid peak workload periods. For large environments:

  • Stagger schedules across accounts and regions.
  • Run lower-tier workloads outside critical backup windows.
  • Keep high-priority production workloads aligned with their RPO targets.

Enable Jobs​

After tags and schedules are in place, Cloudaware runs backup jobs according to policy. Jobs create backup media, tag it with source and policy metadata, and rotate old media according to retention.

Use Verify Backup Status to confirm successful backup creation.