Pages generated with [slug] get a 404 only in amplify

### 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 read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d2skhgz4a0rx0t

### AWS Region

eu-west-1

### Amplify Hosting feature

Frontend builds

### Describe the bug

I build my site with a /xxx/[slug]. Where slug generate 4 pages.
In my local PC build generate 4 pages. With next start I can see the pages.
Running server.js under .next/standalone, it serve 4 pages.

Only on aws deploy I get a 404 for all slugs, even if log show the correct generation

### Expected behavior

I can get a 200 for these pages

### Reproduction steps

use [slug] next behavior

### Build Settings

_No response_

### Log output

```
# Put your logs below this line
├ ● /ciccio/[slug] (ISR: 3600 Seconds) 349 B 209 kB
├ ├ /ciccio/marketing-data-analyst
├ ├ /ciccio/software-quality-assurance-specialist
├ ├ /ciccio/junior-customer-due-diligence-employee
├ └ [+2 more paths]
```

### Additional information

_No response_