AWS codebuild: Rename CodeConnections to AWS CodeConnections in docs
Summary
Terminology update replacing 'CodeConnections' with 'AWS CodeConnections' throughout the multiple access tokens guide. No substantive content or security guidance changed.
Security assessment
The only change is a branding/terminology rename of the service name to 'AWS CodeConnections'. The surrounding IAM policy and credential guidance is unchanged, so there is no new security content or vulnerability fix.
Evidence
+Step 1: Create a Secrets Manager secret or a AWS CodeConnections connectionStep 2: Grant CodeBuild project IAM role access to Secrets Manager secretsStep 3: Configure Secrets Manager or AWS CodeConnections tokensAdditional setup options
Diff
diff --git a/codebuild/latest/userguide/multiple-access-tokens.md b/codebuild/latest/userguide/multiple-access-tokens.md index 49717c4..8aebe74 100644 --- a//codebuild/latest/userguide/multiple-access-tokens.md +++ b//codebuild/latest/userguide/multiple-access-tokens.md @@ -7 +7 @@ -Step 1: Create a Secrets Manager secret or a CodeConnections connectionStep 2: Grant CodeBuild project IAM role access to Secrets Manager secretsStep 3: Configure Secrets Manager or CodeConnections tokensAdditional setup options +Step 1: Create a Secrets Manager secret or a AWS CodeConnections connectionStep 2: Grant CodeBuild project IAM role access to Secrets Manager secretsStep 3: Configure Secrets Manager or AWS CodeConnections tokensAdditional setup options @@ -17 +17 @@ You can set your source credentials at three different levels: - 2. **Source level credentials for a specific repository:** This is when a Secrets Manager secret or CodeConnections connection is defined on a project source. These credentials will only be used for operations on the specified source repository. This allows you to set up multiple access tokens with different permission scopes in the same project, and not use the default account level credentials. + 2. **Source level credentials for a specific repository:** This is when a Secrets Manager secret or AWS CodeConnections connection is defined on a project source. These credentials will only be used for operations on the specified source repository. This allows you to set up multiple access tokens with different permission scopes in the same project, and not use the default account level credentials. @@ -26 +26 @@ You can set your source credentials at three different levels: - * Step 1: Create a Secrets Manager secret or a CodeConnections connection + * Step 1: Create a Secrets Manager secret or a AWS CodeConnections connection @@ -30 +30 @@ You can set your source credentials at three different levels: - * Step 3: Configure Secrets Manager or CodeConnections tokens + * Step 3: Configure Secrets Manager or AWS CodeConnections tokens @@ -37 +37 @@ You can set your source credentials at three different levels: -## Step 1: Create a Secrets Manager secret or a CodeConnections connection +## Step 1: Create a Secrets Manager secret or a AWS CodeConnections connection @@ -39 +39 @@ You can set your source credentials at three different levels: -Use the following instructions to create a Secrets Manager secret or a CodeConnections connection: +Use the following instructions to create a Secrets Manager secret or a AWS CodeConnections connection: @@ -56 +56 @@ Use the following instructions to create a Secrets Manager secret or a CodeConne -Before you continue, you must have access to the token created in Secrets Manager or CodeConnections. +Before you continue, you must have access to the token created in Secrets Manager or AWS CodeConnections. @@ -58 +58 @@ Before you continue, you must have access to the token created in Secrets Manage -To grant CodeBuild project IAM role access to Secrets Manager or CodeConnections, you must add the following IAM policy. +To grant CodeBuild project IAM role access to Secrets Manager or AWS CodeConnections, you must add the following IAM policy. @@ -145 +145 @@ JSON -## Step 3: Configure Secrets Manager or CodeConnections tokens +## Step 3: Configure Secrets Manager or AWS CodeConnections tokens @@ -147 +147 @@ JSON -You can set your source credentials at three different levels with either Secrets Manager or CodeConnections tokens. +You can set your source credentials at three different levels with either Secrets Manager or AWS CodeConnections tokens. @@ -149 +149 @@ You can set your source credentials at three different levels with either Secret -### Configure Secrets Manager or CodeConnections tokens as account level credentials +### Configure Secrets Manager or AWS CodeConnections tokens as account level credentials @@ -151 +151 @@ You can set your source credentials at three different levels with either Secret -You can configure a Secrets Manager secret or CodeConnections connection as an account level credential and use it in a project. +You can configure a Secrets Manager secret or AWS CodeConnections connection as an account level credential and use it in a project. @@ -168 +168 @@ AWS Management Console - 3. If you chose **CodeConnections** , choose to use an existing connection or create a new connection. + 3. If you chose **AWS CodeConnections** , choose to use an existing connection or create a new connection. @@ -200 +200 @@ Use the following command to configure a Secrets Manager secret: -Use the following command to configure a CodeConnections connection: +Use the following command to configure a AWS CodeConnections connection: @@ -217 +217 @@ You can now use the token in your build project and run it. For more information -To use Secrets Manager secrets or CodeConnections connections as source level credentials, directly reference the token in CodeBuild project, and start a build. +To use Secrets Manager secrets or AWS CodeConnections connections as source level credentials, directly reference the token in CodeBuild project, and start a build.