Page History
...
| Code Block | ||
|---|---|---|
| ||
"encryptionProvider": {
"_comments_implementation": [
"Maven coordinates of the encryption provider",
"default is: com.accenture.aspire:aspire-encryption-provider"
],
"implementation": "com.accenture.aspire:aspire-aws-kms-encryption-provider"
}, |
There are two ways of configuring the encryption provider through Properties or Settings File (click each link to see more details)
Regardless of which way it is used to configure the provider, the following parameters will be used:
| Parameter | Required | Default | Description |
|---|---|---|---|
| roleARN | no | null | (Optional) If the KMS service must be accessed through the assumption of an IAM role, specify the role ARN. Role Assumption is recommended so the base account won't have direct access to the resources. If not specified, the base account will be used to execute the encryption/decryption calls directly. |
| keyARN | yes | N/A | The KMS key ARN. |
| region | yes | N/A | The AWS region on which the KMS service will be used |
| accessKey | no | null | (Optional) Specify the access key if static credentials must be used for the base account. If this is not specified the Default Credential Provider Chain will be used. |
| secretKey | no | null | (Optional) Specify the secret key if static credentials must be used for the base account. If this is not specified the Default Credential Provider Chain will be used. |
How to create a KMS Key suitable for Aspire?
...
Overview
Content Tools