Glue Version Control didn't load the repository from GitLab using the access token

The issue you're experiencing with AWS Glue's Git integration and GitLab could be related to a few factors:

1. Enterprise GitLab Account Restrictions: There might be specific restrictions or configurations in your enterprise GitLab account that are preventing AWS Glue from accessing the repositories, even with a Personal Access Token (PAT) that has owner permissions.

2. GitLab Groups: It's worth noting that AWS Glue's GitLab integration currently does not support GitLab Groups. If your enterprise repositories are organized within GitLab Groups, this could explain why they're not visible in Glue.

3. Token Scopes: Although you mentioned granting full read and write access, double-check that the PAT for your enterprise account includes all necessary scopes. For GitLab integration with AWS Glue, you typically need scopes like 'api', 'read_repository', and 'write_repository'.

4. Repository Visibility: Ensure that the repository visibility settings in your enterprise GitLab account are compatible with external access. Some enterprise configurations might restrict repository visibility even for authenticated users.

5. Network or Firewall Issues: Your enterprise GitLab instance might have network restrictions or firewall rules that prevent AWS Glue from accessing it, while your personal GitLab account doesn't have such restrictions.

6. AWS Glue Permissions: Verify that your AWS IAM permissions include the necessary actions for Git integration, such as 'glue:UpdateJobFromSourceControl' and 'glue:UpdateSourceControlFromJob'.

To troubleshoot:

• Double-check all permissions and scopes on your enterprise GitLab PAT.
• Ensure your enterprise GitLab repositories are not part of GitLab Groups.
• Verify network access from AWS to your enterprise GitLab instance.
• Review your enterprise GitLab account settings for any restrictions on external integrations.

If the issue persists after these checks, you may need to contact your enterprise GitLab administrator or AWS support for further assistance, as there could be enterprise-specific configurations affecting the integration.

Sources
Using Git version control systems in AWS Glue - AWS Glue
AWS Glue now supports GitLab, BitBucket in its Git integration feature
Serverless Data Integration – AWS Glue Features – AWS

Hi, I trust you have a user who has owner permissions to the given private repo and that user created a Personal Access Token. Make sure that you have provided read_api/api, read_repository, write_repository permissions otherwise it won't work. As of now it seems like the you did not granted appropriate permissions or there is implicit deny in the project/repo.