Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error occurred (403) when calling the HeadObject operation: Forbidden for missing field #4138

Closed
2 tasks
DJ-C opened this issue May 21, 2024 · 2 comments
Closed
2 tasks
Assignees
Labels
feature-request This issue requests a feature.

Comments

@DJ-C
Copy link

DJ-C commented May 21, 2024

Describe the feature

With buckets enabled with "Requester Pays" feature, missing --request-payer flag results in fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden. It takes a while to figure reason so providing a helpful message can be helpful.

Use Case

It might be frustrating to get access denied instead of missing required field message.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

SDK version used

Boto3

Environment details (OS name and version, etc.)

Mac, Linux

@DJ-C DJ-C added feature-request This issue requests a feature. needs-triage This issue or PR still needs to be triaged. labels May 21, 2024
@tim-finnigan tim-finnigan self-assigned this May 22, 2024
@tim-finnigan tim-finnigan added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label May 22, 2024
@tim-finnigan
Copy link
Contributor

Hi @DJ-C thanks for reaching out. You referenced an AWS CLI parameter but this repository is for the Boto3 Python SDK. Either way, both the CLI and Boto3 use the S3 HeadObject API, so we would need to reach out to the S3 team to review a request involving the API. Please create a new issue in our cross-SDK repository detailing the steps to reproduce for further action on this issue.

@tim-finnigan tim-finnigan removed investigating This issue is being investigated and/or work is in progress to resolve the issue. needs-triage This issue or PR still needs to be triaged. labels May 22, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request This issue requests a feature.
Projects
None yet
Development

No branches or pull requests

2 participants