IT leadership wants one place to define backup plans and retention across supported AWS resources instead of configuring each service separately. Which service centralizes that backup management?

IT leadership that wants one place to define backup plans and retention across supported AWS resources—instead of configuring each service separately—should use AWS Backup. AWS Backup centralizes backup policies, schedules, lifecycle/retention rules, and vault management for many resource types (such as EBS, RDS, EFS, DynamoDB, and others as supported). For a municipality trying to impose consistent civic backup governance, that centralized control plane is the identify-level answer rather than piecing together ad hoc snapshot scripts per service forever.

Amazon CloudWatch dashboards visualize metrics; metric math does not define cross-service backup retention vaults. AWS Config conformance packs evaluate configuration compliance; they are not a backup service that creates and retains recovery points (and should not be imagined as deleting snapshots nightly as a backup strategy). Amazon EventBridge Scheduler can trigger time-based events but is not itself the centralized backup plan and vault system. Those tools may complement operations but do not replace AWS Backup's role.

Exam caveat: AWS Backup is about centralized backup management; snapshots inside individual services still exist conceptually, but the exam highlight is the unified policy brain. Also distinguish backup (recovery copies) from DR services such as Elastic Disaster Recovery.

Operational check citywide: define backup plans by criticality (for example nightly for permitting DBs, weekly for less critical file systems), assign resources via tags, verify jobs succeed into vaults with encryption and access policies, test restores quarterly, and watch retention so legal holds and public-records obligations are met without unbounded storage growth.