Adding Credentials to Secrets Manager

Back when you set up your workstation, at the beginning of this course, you will have set your Github credentials to enable either Nuget or Maven to access the required packages. The build stage of the pipeline also needs access to these same credentials, and we’re using the AWS Secrets Manager service to make them available. Before we get to deploying and running the pipeline, let’s briefly show how you can set these credentials in Secrets Manager.

Configuring & Running the Script

Step 1: set the Github credential variables in VS Code

For this lab, you’ll use the “create-github-secrets.zsh” script that’s in the “/scripts/setup” folder of the “aws-connectedcar-common” repository. Before running this script, open it in VS Code and paste in the appropriate values for the two variables on lines 3-4:

Step 2: Run the create-github-secrets.zsh script in the terminal

Once you’ve pasted in your Github credentials for these two variables, run the script to add the two secrets.

Verifying the Secrets in the Console

Step 3: verify the newly added secrets in the console

Before moving on, let’s just verify these new secrets in the console. Navigate to the Secrets Manager service in the console, where you should see two secrets listed, as shown below:

To verify the values for these secrets, click on the secret name, then click on the “Retrieve secret value” button on the “Secret value” panel, part way down the page. You should see the key/value entries, as shown below, at the bottom of the page: