Feature request: Additional HTTP Error Code Exceptions

[kazu728]

Use case

ref: https://github.com/aws-powertools/powertools-lambda-python/blob/develop/aws_lambda_powertools/event_handler/exceptions.py

I need to handle additional HTTP error codes, specifically 413 (Payload Too Large). I notice that the current exceptions.py only implements a subset of HTTP error codes (400, 401, 404, 500).
While I understand I can extend ServiceError to create my own custom exceptions, this creates inconsistency in my codebase where some errors come from PowerTools and others from my custom definitions.

Are there plans to expand the list of predefined exceptions to cover more HTTP status codes?
What is the rationale behind which HTTP errors are currently implemented vs. those that aren't?

Solution/User Experience

Add status code

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[anafalcao]

Hello @kazu728 !
Thank you for opening this issue. You raise a valid point about the current subset of implemented HTTP status codes. The initial selection of HTTP error codes was based on project decisions made at that time, but I believe would be beneficial to incorporate 413. We could add the API calls CommomErrors, meaning adding 403, 413, 408 e 503. Do you suggest others?

Would you like to submit a PR with these changes?

[kazu728]

Thank you for deaIing with this issue. I do not suggest any other changes.

Would you like to submit a PR with these changes?

Yes, I will submit it.

[leandrodamascena]

Hi @kazu728! Please let me know if you have time to submit a PR in the next 2 weeks. I'm not pushing, but since we are planing the release, we'd like to add this.

I totally understand if you can't, we're all busy.

[kazu728]

Sorry, I will deal with this issue by the weekend.

[leandrodamascena]

Hey @kazu728! Thanks a lot.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments 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.