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

Reduce scope of IAM Policy for CloudWatch Logs #44

Conversation

mmontreuil
Copy link

@mmontreuil mmontreuil commented Nov 4, 2019

The IAM policy for the Lambda was ::* which seems like it was more permissive than necessary. This PR will reduce the scope to having the wildcard "${var.lambda_function_name}:log-stream:*" instead of all Cloudwatch logs. This should be a non-breaking change that has been tested with Terraform 0.11.14.

mmontreuil and others added 2 commits November 4, 2019 12:15
Further reducing IAM scope by limiting wildcard to just log-stream

Co-Authored-By: Michael Warkentin <mwarkentin@gmail.com>
@antonbabenko antonbabenko merged commit 20ff20a into terraform-aws-modules:terraform011 Nov 8, 2019
@antonbabenko
Copy link
Member

Thanks @mmontreuil !

v1.14.0 has been just released for Terraform 0.11 users.

@github-actions
Copy link

github-actions bot commented Nov 9, 2022

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants