developmentseed / developmentseed/s3-browser-uploader
Unable to see logs on AWS Amplify
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When building out the CDK tooling for AWS Amplify, I was unable to get logging for our compute instances to work. The logstream appears to be unpopulated. I attempted to fix this by manually created the Log Group ([commits](https://github.com/developmentseed/s3-browser-uploader/compare/6811a095ae243ab64fdf1787a07abcd46fec1ac6...145c32db141f73286c40b6fec34d3ca496cdec9d)) but it appears to be unused.
Acceptance criteria: Deployed AWS Amplify application populates logs associated with compute.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the CDK tooling and deploy the AWS Amplify application to reproduce the empty log stream for the compute instances. Inspect the configured logging resources and compare them with the manually created Log Group mentioned in the issue. Done means the deployed application populates logs associated with compute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100