[Bug]: Issue with AWS Glue Job script_location Not Recognizing S3 Path in Terraform

[Prashanteppalpalli]

Terraform Core Version

Terraform v1.5.7

AWS Provider Version

provider registry.terraform.io/hashicorp/aws v5.70.0

Affected Resource(s)

aws_glue_job resource

Expected Behavior

The AWS Glue job should recognize the script_location specified in the Terraform configuration and successfully create the job without errors.

Actual Behavior

The Terraform apply process was successfull but when I go to the AWS console --> Glue console --> ETL jobs --> My job --> Script section, it shows error and says [s3..amazonaws.com] getObject: NoSuchKey: The specified key does not exist.

Manual intervention from AWS console works fine and creates that script file in s3 location but via terraform it give below error.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_glue_job" "example" {
  name     = "example-job"
  role_arn = aws_iam_role.example.arn
  command {
    name            = "glueetl"
    script_location = "s3://your-bucket-name/path/to/your-script.py"
    python_version  = "3"
  }
  # other configurations
}

Steps to Reproduce

terraform init terraform apply

Debug Output

NA

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hey @Prashanteppalpalli 👋 Thank you for taking the time to raise this! Something you mentioned stuck out to me:

Manual intervention from AWS console works fine and creates that script file in s3 location

Are you saying that the file specified in script_location does not yet exist, and that you're relying on the AWS Console to create it for you?