AWS codebuild: Rename CodeConnections to AWS CodeConnections in troubleshooting
Summary
Cosmetic terminology update replacing the product name "CodeConnections" with "AWS CodeConnections" in the table of contents entry, the troubleshooting section heading, the "Issue:" text, and the remediation bullet about the Bitbucket webhook permission email. No procedural, permission, or configuration guidance changed.
Security assessment
The only substantive edit is the branding string "CodeConnections" -> "AWS CodeConnections" across four lines. The surrounding content still concerns missing privilege scopes and Bitbucket webhook permissions, but nothing about required permissions, scopes, roles, or remediation steps was added, removed, or altered, so there is no new security guidance or vulnerability fix.
Evidence
+## Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with AWS CodeConnections
Diff
diff --git a/codebuild/latest/userguide/troubleshooting.md b/codebuild/latest/userguide/troubleshooting.md index 0d1108d..3d7c3f8 100644 --- a//codebuild/latest/userguide/troubleshooting.md +++ b//codebuild/latest/userguide/troubleshooting.md @@ -7 +7 @@ -Apache Maven builds reference artifacts from the wrong repositoryBuild commands run as root by defaultBuilds might fail when file names have non-U.S. English charactersBuilds might fail when getting parameters from Amazon EC2 Parameter StoreCannot access branch filter in the CodeBuild consoleCannot view build success or failureBuild status not reported to source providerCannot find and select the base image of the Windows Server Core 2019 platformEarlier commands in buildspec files are not recognized by later commandsError: "Access denied" when attempting to download cacheError: "BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE" when using a custom build imageError: "Build container found dead before completing the build. build container died because it was out of memory, or the Docker image is not supported. ErrorCode: 500"Error: "Cannot connect to the Docker daemon" when running a buildError: "CodeBuild is not authorized to perform: sts:AssumeRole" when creating or updating a build projectError: "Error calling GetBucketAcl: Either the bucket owner has changed or the service role no longer has permission to called s3:GetBucketAcl"Error: "Failed to upload artifacts: Invalid arn" when running a buildError: "Git clone failed: Unable to access 'your-repository-URL': SSL certificate problem: Self signed certificate"Error: "The bucket you are attempting to access must be addressed using the specified endpoint" when running a buildError: "This build image requires selecting at least one runtime version."Error: "QUEUED: INSUFFICIENT_SUBNET" when a build in a build queue failsError: "Unable to download cache: RequestError: Send request failed caused by: x509: Failed to load system roots and no roots provided"Error: "Unable to download certificate from S3. AccessDenied"Error: "Unable to locate credentials"RequestError timeout error when running CodeBuild in a proxy serverThe bourne shell (sh) must exist in build imagesWarning: "Skipping install of runtimes. runtime version selection is not supported by this build image" when running a buildError: "Unable to verify JobWorker identity"Build failed to startAccessing GitHub metadata in locally cached buildsAccessDenied: The bucket owner for the report group does not match the owner of the S3 bucket...Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with CodeConnectionsError: "Sorry, no terminal at all requested - can't get input" when building with the Ubuntu install commandBitbucket builds fail with authentication errors after using Secrets Manager OAuth +Apache Maven builds reference artifacts from the wrong repositoryBuild commands run as root by defaultBuilds might fail when file names have non-U.S. English charactersBuilds might fail when getting parameters from Amazon EC2 Parameter StoreCannot access branch filter in the CodeBuild consoleCannot view build success or failureBuild status not reported to source providerCannot find and select the base image of the Windows Server Core 2019 platformEarlier commands in buildspec files are not recognized by later commandsError: "Access denied" when attempting to download cacheError: "BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE" when using a custom build imageError: "Build container found dead before completing the build. build container died because it was out of memory, or the Docker image is not supported. ErrorCode: 500"Error: "Cannot connect to the Docker daemon" when running a buildError: "CodeBuild is not authorized to perform: sts:AssumeRole" when creating or updating a build projectError: "Error calling GetBucketAcl: Either the bucket owner has changed or the service role no longer has permission to called s3:GetBucketAcl"Error: "Failed to upload artifacts: Invalid arn" when running a buildError: "Git clone failed: Unable to access 'your-repository-URL': SSL certificate problem: Self signed certificate"Error: "The bucket you are attempting to access must be addressed using the specified endpoint" when running a buildError: "This build image requires selecting at least one runtime version."Error: "QUEUED: INSUFFICIENT_SUBNET" when a build in a build queue failsError: "Unable to download cache: RequestError: Send request failed caused by: x509: Failed to load system roots and no roots provided"Error: "Unable to download certificate from S3. AccessDenied"Error: "Unable to locate credentials"RequestError timeout error when running CodeBuild in a proxy serverThe bourne shell (sh) must exist in build imagesWarning: "Skipping install of runtimes. runtime version selection is not supported by this build image" when running a buildError: "Unable to verify JobWorker identity"Build failed to startAccessing GitHub metadata in locally cached buildsAccessDenied: The bucket owner for the report group does not match the owner of the S3 bucket...Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with AWS CodeConnectionsError: "Sorry, no terminal at all requested - can't get input" when building with the Ubuntu install commandBitbucket builds fail with authentication errors after using Secrets Manager OAuth @@ -75 +75 @@ Use the information in this topic to help you identify, diagnose, and address is - * Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with CodeConnections + * Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with AWS CodeConnections @@ -704 +704 @@ For more information, see [Specify runtime versions in the buildspec file](./bui -## Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with CodeConnections +## Error: "Your credentials lack one or more required privilege scopes" when creating a CodeBuild project with AWS CodeConnections @@ -706 +706 @@ For more information, see [Specify runtime versions in the buildspec file](./bui -**Issue:** When creating a CodeBuild project with CodeConnections, you don't have permission to install a Bitbucket webhook. +**Issue:** When creating a CodeBuild project with AWS CodeConnections, you don't have permission to install a Bitbucket webhook. @@ -717 +717 @@ For more information, see [Specify runtime versions in the buildspec file](./bui - * To accept the new permission, you should have received an email with a subject titled **Action required - Scopes for AWS CodeStar have changed** sent by Bitbucket, `[email protected]`. The email contains a link to grant the webhook permissions to your existing CodeConnections Bitbucket app installation. + * To accept the new permission, you should have received an email with a subject titled **Action required - Scopes for AWS CodeStar have changed** sent by Bitbucket, `[email protected]`. The email contains a link to grant the webhook permissions to your existing AWS CodeConnections Bitbucket app installation.