Introduction to encryption
In some cases, Indicium needs access to a secure location for storing encryption keys:
- When encrypting key values such as passwords, client secrets or API keys.
- When using the Encrypt and Decrypt process actions.
- When scaling to multiple Indicium instances.
It is very important to back up these keys. If you lose these keys, the encrypted data in the database can no longer be used and cannot be recovered in any way.
Without this setup, calling the Encrypt and Decrypt process actions in your application will result in an error.
This manual describes how to centralize the storage of this certificate in AWS.
Store encryption keys on AWS
When using Indicium on AWS, encryption keys must be saved in the AWS Secrets Manager.
To give the Elastic BeanStalk EC2 instance access to the Secrets Manager:
In your Elastic Beanstalk EC2 instance, select the Security tab.
Click the Identity and Access Management (IAM) link.
Click Add permissions.
Click Create inline policy.
In the JSON tab, paste the JSON code fragment below.
Click Save to save the new policy. Indicium can now access the AWS Secrets manager.
In the above JSON code fragment:
regionwith, for example, “eu-west-1”.
account-idwith your account number.
secret-prefixwith the prefix you want your encryption keys in the Secrets Manager to be named.
For example, if your prefix is “indicium/dataprotection-test”, you should give access to “indicium/dataprotection-test-*” with the wildcard character.
- In the
appsettings.jsonconfiguration file, add the following code:
Indicium will automatically add a new key with the configured prefix every 90 days.
Do not delete old keys! When deleting old keys, Indicium cannot decrypt the old data.