aws-amplify / aws-amplify/amplify-hosting

Amplify application access logs to cloudwatch or S3

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

Description

**Is your feature request related to a problem? Please describe.**
In the monitoring section amplify gives the support of the access logs but the time duration is not configurable.
I have a application that has daily request count of 1 Million and that is why the logs are not showing in the amplify console.

![image](https://user-images.githubusercontent.com/73189763/183892182-9a361a75-bb2b-4f39-bc30-ab89898b7dcc.png)

**Describe the solution you'd like**
There should be a way to filter the request based on the response status code.
There should be configuration to send these access logs to cloudwatch or S3 bucket.

**Additional context**
Since the number of incoming request is high the amplify console is not able to display the logs.

Contributor guide

Open the contributing guide

Research direction

Start in the Amplify console monitoring section and review how access logs are currently displayed for high-volume applications. Compare the requested response-status filtering and configurable delivery to CloudWatch or an S3 bucket, then define the supported configuration and verify that logs remain usable at the stated request volume.

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.