aws-amplify / aws-amplify/amplify-hosting
Could we have access logs
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Environment information
```plain text
Keep getting this error:
Unable to load access logs
You can try to fetch the logs again, or reach out to support if the problem persists
Support link leads here.
```
### Describe the bug
Keep getting this error:
Unable to load access logs
You can try to fetch the logs again, or reach out to support if the problem persists
Support link leads here. Could you make them accessible in cloudwatch?

### Reproduction steps
Keep getting this error:
Unable to load access logs
You can try to fetch the logs again, or reach out to support if the problem persists
Support link leads here. Could you make them accessible in cloudwatch?

Contributor guide
Research direction
The issue names no repository files, tests, or entry points; begin by locating the access-log retrieval path and the hosting infrastructure configuration. Confirm how access logs are currently produced, then define and verify a supported way for users to access them in CloudWatch without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100