AWS Key Management System
Tableau Server has three Key Management System (KMS) options that allow you to enable encryption at rest. Two of these require the Server Management add-on, while a local one is available with all installations of Tableau Server.
Beginning in version 2019.3, Tableau Server added these KMS options:
- A local KMS that is available with all installations. For details, see Tableau Server Key Management System.
- An AWS-based KMS that comes as part of the Server Management add-on. This is described below.
Beginning in version 2021.1, Tableau Server added another KMS option:
- An Azure-based KMS that comes as part of the Server Management add-on. For details, see Azure Key Vault.
With the release of version 2019.3, Tableau Server supports the AWS key management system (KMS) as part of the Server Management add-on.
AWS KMS for encryption at rest
AWS KMS is available as part of the Server Management Add-on to Tableau Server. For more information see About Tableau Server Management Add-on.
If your organisation is deploying Data Extract Encryption at Rest, then you may optionally configure Tableau Server to use AWS as the KMS for extract encryption. To enable AWS KMS, you must deploy Tableau Server in AWS EC2. In the AWS scenario, Tableau Server uses the AWS KMS customer master key (CMK) to generate an AWS data key(Link opens in a new window). Tableau Server uses the AWS data key as the root master key for all encrypted extracts. However, even when configured for AWS KMS, the native Java keystore and local KMS are still used for secure storage of secrets on Tableau Server. The AWS KMS is only used to encrypt the root master key for encrypted extracts.
Using AWS to encrypt the master root key provides better security properties by not storing the master key under the same permissions as the extracts.
The key hierarchy when Tableau Server is configured with AWS KMS
Configure AWS KMS for Tableau Server encrypted extracts
To use the AWS customer master key (CMK) to encrypt the root key in the Tableau Server KMS hierarchy, you must configure Tableau Server as described in this section.
Before you begin, verify that you meet the following requirements:
- Tableau Server must be deployed in AWS EC2
- Tableau Server must be configured with a Server Management Add-on licence. See About Tableau Server Management Add-on.
- You must have administrative control of a customer master key (CMK) created in AWS Key Management Service
Step 1: Create CMK and set key policy for Tableau Server in AWS
The following procedures are performed in the AWS KMS service. References are included to AWS documentation.
- Create the CMK that you will use for Tableau Server. See the AWS topic, Creating Keys(Link opens in a new window).
- Update the server instance’s IAM role.
Tableau Server needs to be able to authenticate with AWS KMS using the instance’s IAM role. The role needs to have a policy attached to it. The policy should be giving the instance permissions to call the "GenerateDataKey" and "Decrypt" actions on the CMK. See IAM Roles for Amazon EC2(Link opens in a new window)..
In a multinode deployment of Tableau Server, all nodes of the server must be running under roles that have this policy (or equivalent) attached. You can assign the same role to all nodes in the cluster.
- At a minimum, the CMK must have a key policy where the
Effectis set to
Prinicpal(the IAM role that is attached to the server instances) the
Decrypt. See Using Key Policies in AWS KMS(Link opens in a new window).
Step 2: Collect AWS configuration parameters
You will need the full ARN string from AWS KMS. This string is in the "General configuration" section of the AWS KMS management pages. The ARN is presented in this format: arn:aws:kms:<region>:<account>:key/<CMK_ID>, for example,
You will also need to specify the AWS region, which is also included in the ARN string. In the example above, the region is
us-west-2. The region is where your KMS instance resides. In the next step, you will need to specify a region as shown in the Region column in the Amazon API Gateway table(Link opens in a new window).
Step 3: Configure Tableau Server for AWS KMS
Run the following command on Tableau Server. This command will restart the server:
tsm security kms set-mode aws --aws-region "<region>" --key-arn "arn:aws:kms:<region>:<account_number>:key/<CMK_ID>"
--key-arnoption takes a direct string copy from the ARN in the "General configuration" section of the AWS KMS management pages.
For example, if your AWS KMS instance is running in us-west-2 region, your account number is 867530990073, and your CMK key is 1abc23de-fg45-6hij-7k89-1l0mn1234567, then the command would be as follows:
tsm security kms set-mode aws --aws-region "us-west-2" --key-arn "arn:aws:kms:us-west-2:867530990073:key/1abc23de-fg45-6hij-7k89-1l0mn1234567"
Step 4: Enable encryption at rest
Step 5: Validate installation
Run the following command:
tsm security kms status
The following information may be returned:
- The ARN (ID) of the customer master key (CMK)
- The region the CMK is in
- The ID of the root master key (RMK) in use. The RMK is a key that is encrypted by the CMK. Tableau Server decrypts the CMK by making calls to AWS KMS. The RMK is then used to encrypt/decrypt the master extract key (MEK). The RMK can change, but there will be only one at a time.
- KMS stores a collection of master extract keys (MEKs). Each MEK has:
- An ID, for example, 8ddd70df-be67-4dbf-9c35-1f0aa2421521
- Either a “encrypt or decrypt key” or “decrypt-only key” status. If a key is "encrypt or decrypt", Tableau Server will encrypt new data with it. Otherwise, the key will only be used for decryption
- A creation timestamp, for example, "Created at: 2019-05-29T23:46:54Z."
- First transition to encrypt and decrypt: a timestamp indicating when the key became an encrypt or decrypt key.
- Transition to decrypt-only: a timestamp indicating when the key transitioned to decrypt-only.
View logs after you encrypt and decrypt extracts:
Publish extracts to your site and then encrypt them. See Extract Encryption at Rest.
Access the extracts with Tableau Desktop or with Web Authoring on a browser (this will decrypt the extracts for use).
Search the vizqlserver_node log files for the
AwsKmsEncryptionEnvelopestrings. The default location of the logs are at
Log entry examples that indicate successful configuration include the following:
- Decrypted the RMK with ID 1abc23de-fg45-6hij-7k89-1l0mn1234567 using the CMK with ARN arn:aws:kms:us-west-2:867530990073:key/1234567d-a6ba-451b-adf6-3179911b760f
- Using RMK with ID 1abc23de-fg45-6hij-7k89-1l0mn1234567 to decrypt KMS store
For publishing and extract refreshes related to KMS, search the backgrounder logs. For more information about logs, see Tableau Server Logs and Log File Locations.
In a multi-node setup for AWS KMS, the
tsm security kms status command may report healthy (OK) status, even if another node in the cluster is misconfigured. The KMS status check only reports on the node where the Tableau Server Administration Controller process is running and does not report on the other nodes in the cluster. By default the Tableau Server Administration Controller process runs on the initial node in the cluster.
Therefore, if another node is misconfigured such that Tableau Server is unable to access the AWS CMK, those nodes may report Error states for various services, which will fail to start.
If some services fail to start after you have set KMS to the AWS mode, then run the following command to revert to local mode:
tsm security kms set-mode local.
Refresh AWS CMK
Refreshing the AWS CMK is a task that you perform with AWS. By default, the AWS CMK will refresh once a year. See the AWS topic, How Automatic Key Rotation Works(Link opens in a new window). Since the ARN and region do not change, you do not need to update the KMS configuration on Tableau Server for normal CMK refresh scenarios.
After AWS CMK refreshes, you must regenerate the internal RMK and MEKs on Tableau Server. You should also re-encrypt all extracts with the new CMK:
- Run the
tsm security regenerate-internal-tokenscommand to regenerate all internal keys on Tableau Server, including the RMK and MEKs used for extract encryption.
tabcmd reencryptextracts <site-name>to re-encrypt extracts on a given site. Run this command on every site where you are storing encrypted extracts. Depending on the number of encrypted extracts on the site, this operation could consume significant server processing load. Consider running this operation outside of business hours. See Extract Encryption at Rest.
Regenerate RMK and MEK on Tableau Server
To regenerate the root master key and the master encryption keys on Tableau Server, run the
tsm security regenerate-internal-tokens command.
A server backup can be taken in AWS mode with no additional configurations or procedures. The backup contains encrypted copies of the RMK and MEKs. Decrypting the keys requires access and control of the AWS CMK.
For the restore scenario, the server being restored to can be in either KMS mode, including Local. The only requirement is that the server the backup is being restored to has decrypt access to the CMK the backup itself used.
Upon restore, the MEKs from the backup are imported as decrypt-only keys. The RMK is not migrated over. A new RMK is generated as part of the installation/restore process.