-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
Use Inline Policies instead of Managed #607
Comments
This improvement sounds good. Please make a PR, which will be included as a breaking change in the upcoming major release. |
Great! I will try to make a PR in the next days 🙂 |
This issue has been automatically marked as stale because it has been open 30 days |
I'm just waiting on a response on my PR 🙂 - no reason for going stale. |
This issue has been automatically marked as stale because it has been open 30 days |
I would very much appreciate a (second) review of my PR, @antonbabenko 😃 |
Is your request related to a new offering from AWS?
No.
Is your request related to a problem? Please describe.
Using customer-managed policies is not directly a problem but since the policies are only used for the Lambda function it would be cleaner to use inline policies, IMO. See also Managed policies and inline policies.
Describe the solution you'd like.
I would suggest replacing
aws_iam_policy
andaws_iam_role_policy_attachment
resources (for additional "JSON" policies) withaws_iam_role_policy
.For example, changing
to
The same applies to resources related to
Additional policies (list of JSON)
.Describe alternatives you've considered.
The alternative is keeping it the way it is now 🙂
Additional context
If you agree with my suggestion, I'm happy to create a PR with the necessary changes 🙃
The text was updated successfully, but these errors were encountered: