AWS Secrets

Updated 2 years ago by Admin

The AWS Secrets Manager secures, stores, and controls access to tokens, passwords, certificates, and other secrets in modern computing. The AWS Secrets Manager extension provides your pipeline with access to AWS secrets.

Please note this feature is disabled on Drone Cloud. This feature is only available when self-hosting.
AWS Secrets integration is provided by an extension and is only available if your system administrator has installed the extension.

AWS Secrets
AWS Secrets

Creating Secrets

Create a secret from the AWS console. In the below example we store the Docker username and password.


Accessing Secrets

Once our secrets are stored in AWS, we can update our yaml configuration file to request access to our secrets. First we define a secret resource in our yaml for each external secret. We include the path to the secret, and the name or key of value we want to retrieve:

1  ---
2 kind: pipeline
3 name: default
4
5 steps:
6 - name: build
7 image: alpine
8
9 ---
10 kind: secret
11 name: username
12 get:
13 path: prod/docker
14 name: username
15
16 ---
17 kind: secret
18 name: password
19 get:
20 path: prod/docker
21 name: password
22 ...

We can then reference the named secrets in our pipeline:

1  kind: pipeline
2 name: default
3
4 steps:
5 - name: build
6 image: alpine
7 environment:
8 USERNAME:
9 from_secret: username
10 PASSWORD:
11 from_secret: password
12
13 ---
14 kind: secret
15 name: username
16 get:
17 path: prod/docker
18 name: username
19
20 ---
21 kind: secret
22 name: password
23 get:
24 path: prod/docker
25 name: password
26
27 ...


How did we do?