By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Glue error 400

0

I set up AdministratorAccess for my role, this is a master level policy for this role to pass all the services, specially is AWS Glue, I want to create crawler for build etl pipeline and pour data to database in catalog of AWS Glue, but I stuck in the error 400 denied access. I tried many way like:

  • Change the credit card, set default on it
  • Add permission many times, still failed.
  • Gonzalo Herreros EXPERT
    a year ago

    Where do you see that error? Notice one this is the role use to create the crawler and another the one the crawler uses to run.

Topics
StorageAnalyticsSecurity, Identity, & Compliance
Tags
Amazon Simple Storage ServiceAWS GlueIAM Policies
Language
English
rePost-User-2748522
asked a year ago385 views
1 Answer
0

understand that you're encountering an error while trying to set up a crawler in AWS Glue, even though you have AdministratorAccess for your role. Here are a few steps you can follow to troubleshoot the issue:

Verify the role: Ensure that the role you've created and attached the AdministratorAccess policy to is the same role being used by the AWS Glue crawler. Make sure the trust policy for this role allows AWS Glue to assume the role.

Check the AWS Glue service role: By default, AWS Glue uses a service-linked role named "AWSGlueServiceRole". Ensure that this role exists in your AWS account, and it has the necessary permissions, such as "AWSGlueServiceRole" managed policy.

Verify S3 bucket permissions: Ensure that the role you're using with AWS Glue has the necessary permissions to access the S3 bucket where your data resides. You might need to add an S3 bucket policy or modify the access control list (ACL) to grant the required permissions.

Review CloudTrail logs: Check the AWS CloudTrail logs for any errors or access issues related to your AWS Glue crawler. This can help you identify the exact cause of the error and take appropriate action.

Use the AWS Management Console: If you're using the AWS CLI or SDKs, try creating the crawler through the AWS Management Console to ensure there are no syntax or input errors in your commands.

Region restrictions: Ensure that you are operating in a region where AWS Glue is available, and the resources you're trying to access are in the same region.

Confirm AWS Glue is enabled: In some cases, the AWS Glue service might not be enabled on your account. Contact AWS Support to verify if AWS Glue is enabled, and request activation if it's not.

If you've tried all these steps and the issue persists, I recommend reaching out to AWS Support for further assistance. They will be able to diagnose the issue and provide a solution based on your specific account and configuration.

Good luck, and let me know if you have any other questions or need further assistance.

Best regards, Ismael

AWS
Ismael Murillo
answered a year 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

Relevant content