Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Please include APIGateway ID in related logs #68

Closed
piaverous opened this issue Sep 6, 2022 · 1 comment
Closed

Comments

@piaverous
Copy link

piaverous commented Sep 6, 2022

When running yatas --details, API Gateway related logs only include stage names, and not the API Gateway's identifier.

This means that in a setup in which I have multiple API Gateways with a single stage each (the stage always being called "default"), I get identical logs.

Logs I obtain :

❌ AWS_APG_001 ApiGateways logs are sent to Cloudwatch - 0/9
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
	Cloudwatch logs are not enabled on default
❌ AWS_APG_002 ApiGateways are protected by an ACL - 0/9
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
	Stage default is not protected by ACL
❌ AWS_APG_003 ApiGateways have tracing enabled - 0/9
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default
	Tracing is not enabled on default

Logs I would like :

❌ AWS_APG_001 ApiGateways logs are sent to Cloudwatch - 0/9
	Cloudwatch logs are not enabled on stage default in APG xxxxxxxx
	Cloudwatch logs are not enabled on stage default in APG yyyyyyyy
	Cloudwatch logs are not enabled on stage default in APG zzzzzzzz
	Cloudwatch logs are not enabled on stage default in APG aaaaaaaa
	Cloudwatch logs are not enabled on stage default in APG bbbbbbbb
	Cloudwatch logs are not enabled on stage default in APG cccccccc
	Cloudwatch logs are not enabled on stage default in APG dddddddd
	Cloudwatch logs are not enabled on stage default in APG eeeeeeee
	Cloudwatch logs are not enabled on stage default in APG ffffffff
❌ AWS_APG_002 ApiGateways are protected by an ACL - 0/9
	Stage default in APG xxxxxxxx is not protected by ACL
	Stage default in APG yyyyyyyy is not protected by ACL
	Stage default in APG zzzzzzzz is not protected by ACL
	Stage default in APG aaaaaaaa is not protected by ACL
	Stage default in APG bbbbbbbb is not protected by ACL
	Stage default in APG cccccccc is not protected by ACL
	Stage default in APG dddddddd is not protected by ACL
	Stage default in APG eeeeeeee is not protected by ACL
	Stage default in APG ffffffff is not protected by ACL
❌ AWS_APG_003 ApiGateways have tracing enabled - 0/9
	Tracing is not enabled on stage default in APG xxxxxxxx
	Tracing is not enabled on stage default in APG yyyyyyyy
	Tracing is not enabled on stage default in APG zzzzzzzz
	Tracing is not enabled on stage default in APG aaaaaaaa
	Tracing is not enabled on stage default in APG bbbbbbbb
	Tracing is not enabled on stage default in APG cccccccc
	Tracing is not enabled on stage default in APG dddddddd
	Tracing is not enabled on stage default in APG eeeeeeee
	Tracing is not enabled on stage default in APG ffffffff
@StanGirard
Copy link
Contributor

Fixed in new release. Thanks for the issues.

481b0b2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants