How to Configure RDS Postgres Encryption at REST
You set up rds postgres encryption at rest when you create a new database instance. For existing unencrypted databases, you take a snapshot, encrypt the copy, and restore it. Teams use this cloud storage setting to protect disks, automated backups, and read replicas. Still, disk encryption does not control what logged-in users can read or change. When database roles have broad privileges, any active session can pull sensitive records in plain text. How rds postgres encryption at rest works in
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up rds postgres encryption at rest when you create a new database instance. For existing unencrypted databases, you take a snapshot, encrypt the copy, and restore it.
Teams use this cloud storage setting to protect disks, automated backups, and read replicas. Still, disk encryption does not control what logged-in users can read or change. When database roles have broad privileges, any active session can pull sensitive records in plain text.
How rds postgres encryption at rest works in practice
Cloud storage encryption protects the physical disks underneath your database instance. You choose a managed key when you launch the database in your cloud account. The cloud platform then encrypts all storage volumes, automated backups, and snapshots with that key.
You cannot turn on storage encryption directly on an already running unencrypted database. Instead, you must stop writes and take a final snapshot of the instance. Next, you copy that snapshot and enable encryption using your chosen key during the copy step. Finally, you restore a new database instance from that encrypted snapshot copy. You then point your app to the new database endpoint.
Once the instance is running, the storage engine decrypts blocks by default when the database reads them. This means encryption at rest only stops attackers who steal physical disks or raw backup files. To any user or app that logs in, the data looks normal.
How database roles interact with encrypted storage
Because the storage layer decrypts data on read, you must lock down database roles. In PostgreSQL, the special role name PUBLIC grants privileges to every role on the system. By default, PUBLIC gets rights to connect to databases and create temporary tables. It also gets rights to run functions and procedures unless the owner revokes those defaults.
In PostgreSQL 15 and later, regular users cannot create objects in the public schema by default. On older databases, admins must revoke that create right from PUBLIC to keep schemas safe. Admins also set up group roles to manage permissions when many users need access. Users then join the group role to get their read or write rights.
Encryption at Rest + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
You can grant the read privilege on whole tables or only on specific columns. Even with column grants, static roles still leave a wide operational gap. The read privilege also allows bulk exports from the table. Once a user logs in, disk encryption is no longer in the path.
What storage encryption solves and the gap it leaves open
Storage encryption checks an important audit box for stolen drives and unmounted snapshots. Cloud identity rules and database roles decide who can log in to the instance. Neither layer inspects or controls what individual queries do during a live session.
When an engineer or support tool connects with a shared read role, every row returns unmasked by default. A single query can return thousands of emails, phone numbers, card numbers, or national IDs. Also, shared database roles make it hard to tie a specific query back to one person. To protect live data, teams need controls that work at the query and result level.
Run guardrails and masking on the Postgres connection
Role grants and firewall rules are needed setup. Setup alone cannot check single SQL statements or mask sensitive rows in a response. By design, hoop.dev sits inline in the Postgres protocol beside Postgres, RDS, or Aurora as a sidecar for your Postgres. On every production query from an engineer or AI agent, hoop.dev decides whether to pass, mask, block, or hold it for approval.
First, hoop.dev guardrails refuse disallowed drops or deletes before they run, and risky statements can pause for human review. Next, hoop.dev data masking rewrites sensitive fields in returned rows in memory. Furthermore, hoop.dev holds SOC 2 Type II and logs every statement and verdict per resource. Check out the project on GitHub.
Frequently asked questions
Can I turn on encryption at rest on an existing unencrypted RDS Postgres instance?
No, you must take a snapshot, copy it with encryption turned on, and restore a new instance. After the new encrypted instance is ready, you switch your app traffic over to it.
Does rds postgres encryption at rest hide sensitive columns from database users?
No, the storage layer decrypts data by default for any authenticated database session. Users with read rights see plain text unless you add column rules or result masking.
How do I limit which columns a PostgreSQL user can read?
You can grant the read privilege on specific columns of a table rather than the whole table. For dynamic protection on full tables, you can also apply data masking to rewrite sensitive fields in results.
Related guides
In this post