AWS Redshift database encryption

Question

Is it possible to use different encryption for different databases inside of single Redshift?

I other words, I mean, that in case(theoretical case) for example of stolen hard drive from AWS data center, hackers will be unable to decrypt all databases on this drive with the same key?

John Rotenstein · Accepted Answer · 2019-07-02 01:43:35Z

2

It appears that:

Each data block on disk encrypted with a different encryption key
Those encryption keys are then encrypted using a Database Encryption Key
That key is encrypted with a Cluster Encryption Key
That key is encrypted in AWS KMS with an encryption key specifically for Redshift in your account (as opposed to EC2, etc)

See: Amazon Redshift Database Encryption

answered Jul 2, 2019 at 1:43

John Rotenstein

273k28 gold badges456 silver badges541 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

alexanoid Over a year ago

thanks for your answer. Right now I'm choosing for multi-tenant solution between tenant per database or tenant per schema. Looks like tenant per schema is less secured approach for data in rest because all data keys will be encrypted with the same database encryption key instead of different database encryption keys as in case of tenant per database approach?

John Rotenstein Over a year ago

Every single disk block is encrypted with a different key. Each block holds 1MB of data. So, a 100MB database would involve at least 100 different encryption keys. These 100+ encryption keys are then encrypted with a Database Encryption Key before being stored.

alexanoid Over a year ago

Thanks. So in other words — tenant per schema is less secure approach vs tenant per database but still pretty solidly secured in general and can be also used as multi-tenant solution?

John Rotenstein Over a year ago

I'd say anything stored in Redshift is equally secure, from an "encryption-at-rest" standpoint. Ignoring encryption-at-rest, "tenant per schema" is less secure than "tenant per database" because it is possible that a badly configured GRANT permission could expose data to the wrong tenant. This is true for any database, not just Redshift. Of course, you should never give your customers direct access to a database, so it really comes down to whether your app is correctly coded to manage security.

Collectives™ on Stack Overflow

AWS Redshift database encryption

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related