Issues with AWS Glue Version Control and Bitbucket Integration

Hi AWS Forum Community,

I am currently facing some challenges while trying to integrate AWS Glue with Bitbucket using the version control feature, and I would appreciate any guidance or insights from the community.

According to the AWS Glue documentation, for Bitbucket integration, a "Personal access token" is required, and this token is supposed to be the "Repository Access Token" provided by the Bitbucket repository. The documentation suggests setting permissions as follows:

Bitbucket Permissions:

• Workspace membership: read, write
• Projects: write, admin read
• Repositories: read, write, admin, delete

However, I've encountered confusion because the permissions mentioned seem to align more with Bitbucket's "app password" in the personal settings rather than the "Repository Access Token." I have tried both types of tokens, but unfortunately, I'm still facing issues.

Moreover, I've experimented with using both the repository creator's name and the organization name as the repo owner's name, but I haven't had any success in getting the workspace, repository, and branch to appear in the dropdown for selection.

If anyone has successfully integrated AWS Glue with Bitbucket and encountered similar issues or has any recommendations, I would greatly appreciate your input. Additionally, if there are any specific steps or configurations that I might be missing, please feel free to share.