# AWS Backup

> Central backup policies for AWS resources. Neon branches cover the Neon side.

- Verdict: My default
- Vendor: AWS
- Layer: [Accounts, identity and cost](https://cloudlesslabs.com/stack/layers/accounts.md). Job: Backups
- Last reviewed: 18 October 2026, by Nicolas Dao (Cloudless Labs, Sydney)
- Web page: https://cloudlesslabs.com/stack/aws-backup/. The whole stack in one file: https://cloudlesslabs.com/stack/brief.md

Backups defined as code, in one place.

## Use it when

- Any AWS database, volume or file system holding client data.

## Provisioning

Official Pulumi package · Official Terraform provider

## Instead, consider

- [Neon (serverless Postgres)](https://cloudlesslabs.com/stack/neon/index.md): Neon: branches and point-in-time restore.

## Where it fits

- [An AWS foundation for a client](https://cloudlesslabs.com/stack/use-cases/aws-foundation.md): pick 3. Backup policies as code.

## Related

- [Accounts, identity and cost](https://cloudlesslabs.com/stack/layers/accounts.md): every tool in this layer, with its verdict
- [The whole stack in one file](https://cloudlesslabs.com/stack/brief.md): every use case and tool, for questions that span many
- [Map of every Markdown file on cloudlesslabs.com, with what each one answers](https://ask.cloudlesslabs.com)