-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
[Bug] API Gateway not tracked #38
Comments
Most of the requsets fall under apigateway:POST/PUT/PATCH/DELETE/GET but there are specific method resources involved too. |
Hey @iamgeef, Thanks for raising this issue. It looks like there was a conflict between the V1/V2 API Gateway permissions (as they share the same IAM prefix). I'll look into the issue and get back to you, hopefully within a few days. |
Hi @iamgeef, Thanks again for raising. This issue has been fixed and should be in v0.42.0. Let me know if you still have any issues. |
Using Terraform to create api gateway resources I noticed that none of the actions were being logged in the iamlive policy.
Confirmed it on my end using the CLI with
aws --region ap-southeast-2 apigateway get-rest-apis
Other CLI calls such as
aws sts get-caller-identity
do work in the same iamlive session.This is the iamlive command being used:
iamlive --set-ini --profile default --mode proxy
The text was updated successfully, but these errors were encountered: