Error 502 after adding storage and functions

[ianclark84]

How did you install the Amplify CLI?

NPM

If applicable, what version of Node.js are you using?

21.5.

Amplify CLI Version

12.10.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

Describe the bug

On two separate projects now I've suddenly seen Error 502 when loading the site hosting with Ampilfy hosting, seemingly out of nowhere. I just started a new project this morning to and was adding basic features like functions and storage. Hosting was working perfectly fine beforehand, and then after adding a couple of Functions and Storage I started getting Error 502 again. I removed those resources but the issue with Hosting remains.

Expected behavior

I expected no compromise to the Hosting service after adding Storage and Functions.

Reproduction steps

I don't know what caused this. One minute everything was fine, then after making very ordinary updates to project I started getting Error 502 on the hosting.

Project Identifier

57bedee65270cb8b99ef67b917be3c38

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[ianclark84]

This had something to do with rewrites and redirects. I removed those and it resolved. I had

</^[^.]+$|.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|woff2|ttf|map|json|webp)$)([^.]+$)/> redirectng to ./index.html which has never been an issue in the past but something is different with this project, presumably requiring a new redirect.