Close
logodocs

Configure AWS Secrets Manager Integration

This feature is currently in public beta. Functionality and documentation may change.

Secret store integrations allow you to use your existing third-party secret stores with strongDM. Your credentials are stored in a tool that is controlled by you, and those credentials are never transmitted to strongDM in any form. If you would like to learn more about how this integration works and why you might wish to use it, please read the Secret Stores Reference.

This guide will walk you through how to integrate AWS Secrets Manager with strongDM and how to use it to connect to resources.

Set up AWS Secrets Manager

To get started with AWS Secrets Manager, store credentials to some of your resources in it and note the correct paths to those credentials. Then, set up your Relay server to be able to authorize to the Secrets Manager with an access key.

Set up your credentials

Set up your credentials in AWS Secrets Manager. This should be as simple as heading to Secrets Manager in the AWS Management Console and following the prompts to create your first secret.

You may choose to organize your credentials by slug (e.g., postgres) or namespace/path (e.g., /credentials/databases/postgres). Either way, when asked for the path to your secret later, this name is that path.

Authenticate with AWS

You can authenticate your Gateway server with AWS in one of two ways.

Option 1: access keys

  1. Get an access key for AWS and set the necessary environment variables on your Relay server (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY).
  2. Edit the file /etc/sysconfig/sdm-proxy (unless you have moved or renamed your sdm-proxy file) and add the following lines, substituting your ID and key:
    AWS_ACCESS_KEY_ID=aswf234rt4rsag4t3g
    AWS_SECRET_ACCESS_KEY=23452321h2893hf2ioufh2938229fh2oufgh23890fh29fh23bif2f0928hf02f3n2bf290fn9230f
  3. Restart the sdm-proxy service (with something like sudo systemctl restart sdm-proxy, depending on your distribution).

Option 2: IAM

  1. In your AWS Management Console, navigate to IAM, click on Role, and click on Create Role.
  2. Select EC2 for Service.
  3. In the policy, select SecretsManagerReadWrite, and click Next.
  4. Add the role name and description, and then go to EC2 and click on Instances.
  5. Select the instance that houses the Gateway, and click on Actions > Security > Modify IAM Role.
  6. Choose the name of the IAM role created earlier.

Configure the Secret Store with the Admin UI

Once you have AWS Secrets Manager set up, credentials stored, and your Relay server able to access said credentials, it's time to integrate the secret store with strongDM.

1.In the Admin UI, go to Network > Secret Stores. 2. Click the add secret store button. 3. On the Add Secret Store form, set the following:

Secret Stores Settings
Secret Stores Settings

  1. Display Name: Enter a name. This name will show up in the Admin UI.
  2. Secret Store Type: Select AWS Secrets Manager.
  3. Region: Fill the AWS region (e.g., us-west-2) for your AWS Secrets Manager.

If you've configured the Relay server correctly for secret store access and authorization, you will see the green online indicator.

Now, create a resource that uses the secret store, assign it to a Role that is assigned to a User, and verify that you can connect.

  1. In the Admin UI, add a new resource such as a Server or Datasource and choose the AWS Secrets Manager Secret Store type.
  2. Fill out the information for a resource whose credentials you have stored in your secret store.
  3. Select the AWS secret store you created for the Secret Store field, and then fill in the path to the secrets that you've stored in your secret store.
  4. Submit the form.
  5. Go to Roles, create a Role with an access rule that grants access to the resource, and assign the Role to the User.
  6. Log in as that User in your local GUI (or have the User do so, if not yours) and verify that the resource exists, test a connection, and execute a query.

Congratulations, you've connected to a resource using secret stores.

Installation — Previous
Configure Secret Store Integrations
Next — Installation
Configure GCP Secret Manager Integration