Instaclustr has recently released support for provisioning Amazon Web Services based Cassandra clusters with encrypted EBS and encrypted backups. This support brings two big benefits for our customers:
- By utilising encrypted EBS (plus encrypted backups), customers may be able to meet compliance requirements that mandate encryption of data at rest.
- Customers always retain control of the “master key” for their data. Should you wish to remove Instaclustr access to your data, you can simply remove the rights for Instaclustr managed systems to access your master key.
You can find more information about AWS’s EBS encryption here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html. Importantly, AWS claims, and our testing shows, that enabling EBS encryption has negligible, if any, impact on performance.
Using EBS encryption with Instaclustr is easy:
- Create a new key through AWS and grant permissions to Instaclustr’s AWS account to access it.
- Register the key through the Encryption Keys tab of the Instaclustr Account page. The registration process will check that permissions are set up properly.
- Select the key from the drop down box when creating a new cluster or add a data center to an existing cluster. That key will then be used when provisioning EBS volumes and to encrypt the automatic backups our system makes (to S3).
There are detailed, step-by-step instructions for these steps in our help article here: https://support.instaclustr.com/hc/en-us/articles/226565607. One note – it’s not possible to change an existing cluster to encrypted EBS in-place. However, you can migrate a cluster to encrypted EBS without downtime by adding a second data center with encryption, cutting your app over to that data center and then decommissioning the existing data center.
I mentioned that one of the advantages of using encrypted EBS is that it gives you the power to securely remove Instaclustr access to your data should you need to (of course, we plan to do a good enough job that you never want to). This power also comes with responsibility – should you remove our access to your key your cluster will stop working (once the cached key expires) and we will not be able to recover data without access to the key. So – make sure you’ve got good procedures in place to manage this access – any issues arising from change you make to key settings won’t be covered by SLAs.
We think this feature will be of use to many of our customers. If you have any technical questions about this feature or issues getting it set up please contact email@example.com. As always, please feel free to contact me directly at firstname.lastname@example.org should you have any general comments or requests for features.