Unable to push Glue job to GitHub. Empty connections list is now allowed if connection is specified.

0

Hi,

I am trying to Push the Glue job to GitHub repo. I have got added the access permissions to my role as specified in https://docs.aws.amazon.com/glue/latest/dg/edit-job-add-source-control-integration.html

I am getting the error as: Push to repository

Unable to push job <Glue_Job_Name> to GitHub at <GitHub_Repo_Name>/main. Empty connections list is now allowed if connection is specified. Unable to push job

AWS Admin, who has got FULL access to AWS is able to Push to GitHub repo. I have confirmed my GitHub repo privileges are Admin.

ravi_tb
asked 23 days ago113 views
3 Answers
1

Hi ravi_tb,

  • Here are some steps you can take to troubleshoot and resolve this issue:
  1. Verify Connection Settings: Ensure that your Glue job configuration includes the correct connection settings for accessing GitHub. The connections list should specify the GitHub connection that you've configured in AWS Glue. If the connections list is empty or incorrect, it can cause the error you're seeing.

2.Check IAM Permissions: Double-check the IAM permissions assigned to the role associated with your Glue job. The role should have the necessary permissions to access GitHub, including permissions to push code to the specified repository.

3.Review GitHub Repository Settings: Confirm that the GitHub repository you're trying to push to is correctly configured and that you have the necessary permissions (e.g., admin privileges) to push code to the repository. Also, ensure that the repository branch (e.g., main) exists and is accessible.

  1. Test Connectivity: Test the connectivity between AWS Glue and GitHub by manually pushing code to the repository using the same credentials and connection settings configured in your Glue job. This can help identify any connectivity issues or authentication problems.

5.Check for Errors in Glue Job Logs: Review the logs generated by your Glue job for any error messages or warnings that might provide additional insights into the issue. Look for any specific error messages related to the GitHub integration or connection settings.

answered 23 days ago
AWS
SUPPORT ENGINEER
reviewed 18 days ago
0

Thanks for your quick response @Panurangaswamy.

  1. I have validated with the AWS Admin for the same. He is able to perform Push operation. Can you specify how to check the Connection List explicitly.
  2. I have got updated the permissions based on the link provided --> https://docs.aws.amazon.com/glue/latest/dg/edit-job-add-source-control-integration.html#git-integration-permissions
  • AWSGlueServiceRole
  • AWSGlueConsoleFullAccess
  • glue:UpdateJobFromSourceControl
  • glue:UpdateSourceControlFromJob
  • s3:GetObject
  • s3:PutObject
  1. Yes. I got the Admin privilege
    1. Admin is able to do it. So I think no issues with Glue job.
ravi_tb
answered 23 days ago
0

To check the connection list explicitly in your Glue job configuration, you can follow these steps:

Navigate to the AWS Glue console: https://console.aws.amazon.com/glue/.

In the navigation pane, choose "Jobs."

Select the Glue job for which you're configuring the source control integration.

Scroll down to the "Connections" section in the job configuration.

Check the list of connections specified for the Glue job. Ensure that there is a connection configured for GitHub, and it is selected as the source control integration.

If there are multiple connections listed, verify that the correct GitHub connection is selected. If not, you may need to edit the job configuration to select the appropriate connection.

If the connection list appears to be correct and the AWS Admin is able to perform the push operation successfully, the issue may indeed lie with the permissions or configuration on your end. Double-check the IAM permissions assigned to your IAM role and ensure that they include the necessary permissions for interacting with GitHub (e.g., glue:UpdateJobFromSourceControl, glue:UpdateSourceControlFromJob). Additionally, ensure that your GitHub repository settings and permissions are correctly configured.

answered 23 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions