aws-amplify / aws-amplify/amplify-hosting

Amplify access logs missing URL path of custom domain in Amplify Console Experience

Open
#3,922 2 comments 3 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

Access logs

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

Access log do not contain any information about the URL path of amplify custom domain and if there turns out to be an issue with when any of the URL with different resource paths then amplify is not adding up these details on access logs which is creating a problem.

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

While trying to test using different URL path like /test/{user} then the access log only contains information about the root domain without any resource path being appended. In the case of testing with different resource path and if any of the resource path error out then there has to be a way of showing information about the path that has been errored out. Currently, it is not possible which is creating an issue in identifying the URL path which is causing issue.

Contributor guide

Open the contributing guide

Research direction

The issue does not name any repository files, tests, or entry points. Start by locating the Amplify Hosting access-log implementation and reproducing a request to a custom domain path such as /test/{user}; done means the access log identifies the requested resource path when that request succeeds or errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.