Skip to content

Aws fix 500 errors

Derek Hudson requested to merge aws-fix-500-errors into master

All Submissions:

  • [YES] I have added an explanation of what changes in this merge do and why we should include it?
  • [NA] I have updated the documentation accordingly.
  • [YES] I have added tests to cover my changes.
  • [YES] All new and existing tests passed.
  • [YES] My code follows the code style of this project.
  • [YES] I ran lint checks locally prior to submission.

What is the current behavior?

500 errors in AWS when the behavior should be to respond with 401 or 400 errors.

What is the new behavior?

Now responds with 401 errors when certain things happen (mostly invalid data partition IDs).

Does this introduce a breaking change?

  • [NO]

Any relevant logs, error output, etc?

(If it’s long, please paste to and insert the link here.)

Other information

Merge request reports