boto3.client("s3").head_bucket does not throw NoSuchBucket as per documentation

[tim-finnigan]

Original issue here: boto/boto3#4092

ref: P127336178

[anentropic]

Some related earlier issues:

• Error handling is STILL completely unreliable and unusable #305
• Enum aws_sdk_s3::error::GetObjectErrorKind doesn't include NoSuchBucket #364
• Very partial list of errors defined in smithy S3 model #376

[tim-finnigan]

Thanks for sharing those, here's another related issue: #255. We heard back from an S3 documentation writer who updated this page: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html

This is now highlighted in a Note for better visibility:

So while the error below is documented:

It cannot be handled client-side due to the limitations described in the Note. Please use the Provide feedback to send any additional feedback directly to the S3 team regarding this.

[github-actions]

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[anentropic]

So... this will never get fixed?

The documentation change in API_HeadBucket does nothing to clarify the situation for Boto3 users who find a NoSuchBucket exception class on the S3 client instance that never gets raised. To all intents and purposes it still looks like the thing you should catch for the 404 case.

Is it all so auto-generated that it's impossible to put a specific note in the Boto3 docs?