aws-amplify / aws-amplify/amplify-hosting

Could we have access logs

Open
#4,040 4 comments 0 reactions 0 assignees View on GitHub
hosting question
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?

![Image](https://github.com/user-attachments/assets/8da5c3fd-2b03-4e2a-95a9-fa5497af38ea)

### 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?

![Image](https://github.com/user-attachments/assets/8da5c3fd-2b03-4e2a-95a9-fa5497af38ea)

Contributor guide

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.