Backup Notion to Amazon S3
For teams that already live on AWS. Point Backup Notion at your bucket and every scheduled backup arrives as portable Markdown, under your IAM policies, your region, and your lifecycle rules.
14-day free trial · 2-minute setup
The Backup Notion dashboard running a scheduled backup: scanning 704 pages, exporting them to Markdown, collecting 1,212 media files, and uploading 633 megabytes to Amazon S3, with a history of past runs below.
Notion to Amazon S3 in three steps
01
Connect Notion
Sign in with Notion and share the teamspaces you want protected. The access is read-only.
02
Add your bucket
Provide the bucket name, region, and a scoped access key. S3-compatible storage works too: Backblaze B2, Cloudflare R2, MinIO.
03
Pick a schedule
Daily, weekly, or monthly. Backups upload directly to your bucket, and retention is whatever your lifecycle policy says it is.
Everything in your workspace
Every backup covers all pages and nested subpages, databases with their properties, images, PDFs, and attachments from the teamspaces you authorize, exported as clean Markdown that mirrors your workspace structure. Pro plans include comments too.
Amazon S3 questions
Which permissions does the access key need?
s3:PutObject on the prefix you choose, nothing else. We recommend a dedicated IAM user scoped to a single prefix in the bucket.
Does this work with S3-compatible providers?
Yes. Anything that speaks the S3 API works by setting a custom endpoint: Backblaze B2, Cloudflare R2, DigitalOcean Spaces, MinIO.
What does the object layout look like?
One object per backup: your optional prefix plus a timestamped ZIP, for example notion-backups/2026-06-12-0400.zip. Inside is Markdown mirroring your workspace structure, your media, and an offline viewer.
How are my credentials stored?
The access key pair is encrypted in a vault, separate from application tables, and fetched only at upload time. It is never written to logs.
What about data residency?
Your bucket, your region. Backups go straight to it and we keep nothing at rest, which tends to make security reviews short.
Can I manage retention with lifecycle rules?
Yes. Backups are plain objects, so expiration and storage-class transitions work like they do for anything else in the bucket. We only ever write; we never delete from your bucket.
Is there a size limit?
Backups stream as a single PUT, which S3 caps at 5 GB per object. That is far above typical workspace archives. If your export is larger, talk to us.
What about encryption at rest?
Objects inherit your bucket's encryption configuration, whether that's default SSE-S3 or your own KMS keys. Transfer happens over TLS.
Or send backups somewhere else
Your workspace took years to build. Backing it up takes 2 minutes.
14-day free trial. Cancel anytime. Your backups stay in your storage.