aws-amplify / aws-amplify/amplify-hosting

The system displayed a 500 error for a period of time, then resumed normal operation.

Open
#4,079 2 comments 5 reactions 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [x] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [x] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [x] I have removed any sensitive information from my code snippets and submission.

### Amplify Hosting feature

Frontend builds

### Is your feature request related to a problem? Please describe:

Is your feature request related to a problem? Please describe:

AWS Region
ap-northeast-1

Amplify Hosting feature
Build settings

Frontend framework
Next.js

Next.js version
14.2.3

Next.js router
App Router

Describe the bug
The system displayed a 500 error for a period of time, then resumed normal operation.

```
2026-01-27T06:32:06.006Z
LOGS Name: bootstrap State: Already subscribed Types: [Platform, Function]
2026-01-27T06:32:06.050Z
ln: failed to create symbolic link '/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output': Read-only file system
2026-01-27T06:32:06.051Z
ln: failed to create symbolic link '/tmp/app/app/app': Read-only file system
2026-01-27T06:32:06.053Z
ln: failed to create symbolic link '/tmp/app/node_modules/node_modules': Read-only file system
2026-01-27T06:32:06.056Z
ln: failed to create symbolic link '/tmp/app/public/public': Read-only file system
2026-01-27T06:32:06.077Z
ln: failed to create symbolic link '/tmp/app/.next/static/static': Read-only file system
2026-01-27T06:32:06.080Z
ln: failed to create symbolic link '/tmp/app/.next/types/types': Read-only file system
2026-01-27T06:32:06.083Z
ln: failed to create symbolic link '/tmp/app/.next/server/chunks/chunks': Read-only file system
```

Expected behavior
I need to know the specific cause and how to prevent the error from happening in the future.

Reproduction steps
Error 500 occurs for a period of time, then operates normally.

Build Settings

```
version: 1
frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- yarn run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- .next/cache/**/*
- node_modules/**/*
```

Log output

```
2026-01-27T06:32:06.006Z
LOGS Name: bootstrap State: Already subscribed Types: [Platform, Function]
2026-01-27T06:32:06.050Z
ln: failed to create symbolic link '/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output': Read-only file system
2026-01-27T06:32:06.051Z
ln: failed to create symbolic link '/tmp/app/app/app': Read-only file system
2026-01-27T06:32:06.053Z
ln: failed to create symbolic link '/tmp/app/node_modules/node_modules': Read-only file system
2026-01-27T06:32:06.056Z
ln: failed to create symbolic link '/tmp/app/public/public': Read-only file system
2026-01-27T06:32:06.077Z
ln: failed to create symbolic link '/tmp/app/.next/static/static': Read-only file system
2026-01-27T06:32:06.080Z
ln: failed to create symbolic link '/tmp/app/.next/types/types': Read-only file system
2026-01-27T06:32:06.083Z
ln: failed to create symbolic link '/tmp/app/.next/server/chunks/chunks': Read-only file system
```

Describe how you'd like this feature to work
I need to know the specific cause and how to prevent the error from happening in the future.

### Describe how you'd like this feature to work

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

Contributor guide

Open the contributing guide

Research direction

Start with the Amplify Hosting Frontend builds entry point, the Next.js 14.2.3 App Router context, and the supplied Build Settings and log output. Compare the transient 500 period with normal operation, focusing on the reported read-only filesystem failures for .next, node_modules, public, and application paths. Done means identifying the specific cause and documenting a verified way to prevent recurrence.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, next.js
Domain
ci-cd, cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.