- Newest
- Most votes
- Most comments
Also experiencing the same issue. This is for private repositories in an organisation. Many other repositories with same config working fine, only a select few this is happening for (~5)
The error you're encountering with AWS CodeBuild failing to get a JIT (Just-In-Time) token from GitHub is related to permissions and configuration issues between your GitHub repository and AWS CodeBuild.
Based on the error message "GitHub runner JIT configuration unavailable: ResourceNotFoundException," there are several potential causes:
- Insufficient GitHub PAT permissions: Your fine-grained Personal Access Token may not have all the required permissions. For GitHub Actions workflows, the PAT needs specific permissions including:
actions:readandactions:writecontents:readworkflows:writeadministration:read(for organization repositories)
- Organization-level restrictions: Since you mentioned TroniusGaming organization, there might be organization-level settings restricting the use of self-hosted runners or JIT configuration. Organization admins may need to:
- Enable GitHub Actions for the organization
- Allow the repository to create and use self-hosted runners
- Verify no policies are blocking AWS CodeBuild's access
-
Repository settings: Check that GitHub Actions is enabled for your specific repository and that the workflow permissions are properly configured.
-
Connection configuration: The connection between AWS CodeBuild and GitHub might not be properly configured to handle the JIT runner registration process.
To resolve this issue:
- Review and update your PAT permissions to ensure they include all required scopes
- Ask your organization administrator to check organization-level GitHub Actions settings
- Verify repository settings allow the use of self-hosted runners
- Consider recreating the connection between AWS CodeBuild and GitHub
- Check that your workflow file correctly specifies the runner configuration
If the issue persists after these steps, you may need to contact AWS Support for more specific guidance on the CodeBuild integration with GitHub Actions.
Sources
Failling to deploy docker image with .Net app to Lightsail | AWS re:Post
AWS VPN Client wont open browser for SSO on MacOS | AWS re:Post
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 10 months ago

all the PAT permission you mentioned are present there are permission to the repo to create and use self hosted runners github actions is enabled for the repo and connection should be fine, since i created this builder project, it is not behind vpn, and we do not have github enterprise so using the PAT is should be accisable from anywhere