crashappsec / crashappsec/chalk
improve error messages for s3 sink errors
- Dominant language
- Nim
- Stars
- 436
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
currently when s3 sink fails the only error message you get is `403: Permission Denied` without too much information why it was denied. we should add a couple of common reasons why that might of happened as otherwise debugging IAM stuff is not fun:
* creds dont have access to the bucket in the uri
* if its MFA session, session token must be provided
* how to test local creds with vanilla aws cli
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the S3 sink error-handling path and inspect how a 403 permission error is currently reported. Done means the error includes the listed bucket-access, MFA session-token, and vanilla AWS CLI credential-testing guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, nim
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100