🐛 Networking problem on AppRunner
- Dominant language
- No language data
- Stars
- 301
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
few month ago i reported some DNS-resolver issues on App Runner.
This issue was already fixed (AWS support told me).
Right now, for something like week we start receiving strange HTTP response codes from our websites and services released on
App Runner. Mostly its 503 and 502 error codes. I contacted paid AWS Support but for 5 days without any fix or solution relation.
From start i think it can be problem on our side but then we start receiving HTTP errors from more and more services using App Runner. For example we are using it for Next.js with SSR. Today i discover SSR pages are broken but static sites just forwarded trough Next.js are okay so i think its another networking problem.
Someone with same issues? We are using App Runner in Ireland (eu-west-1)
Contributor guide
Research direction
Start by reviewing the reported 502 and 503 responses from App Runner in eu-west-1, comparing the affected Next.js SSR services with static sites forwarded through Next.js. The issue names no repository files or tests; done would require identifying and reproducing the networking failure or documenting a confirmed cause and fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100