Problem: GitHub personal access token expired

The solution uses a GitHub personal access token to access the Landing Zone Accelerator on AWS code repository. If you have set an expiration date on the access token, the token’s privilege is revoked when it expires. You will see an error when trying to run the Source stage and action of the Installer or Core pipeline. For example:

Could not access the GitHub repository: "landing-zone-accelerator-on-aws". The access token might be invalid or has been revoked. Edit the pipeline to reconnect with GitHub.

Resolution

Option 1 (releases as of version 1.3.1): Use the Landing Zone Accelerator automated GitHub token update functionality

1. Create a new GitHub personal access token and update the secret value in AWS Secrets Manager.

   Note

   Saving the updated value in Secrets Manager will invoke the UpdatePipelineGithubToken Lambda function, which automates the process of updating the GitHub Personal Access Token in CodePipeline.

2. Retry the failed Source stage of the affected pipeline.

Option 2 : (releases before version 1.3.1): Update access token in AWS CodePipeline

1. Create a new GitHub personal access token and update the pipeline structure with the new token. For step-by-step instructions, see Configure authentication (Github version 1 source actions) in the AWS CodePipeline User Guide.

2. Retry the failed Source stage of the affected pipeline.