Skip to content

Make it easier to use service integrations that require events permissions #33

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

Closed
Octogonapus opened this issue Mar 11, 2022 · 3 comments · Fixed by #34
Closed

Make it easier to use service integrations that require events permissions #33

Octogonapus opened this issue Mar 11, 2022 · 3 comments · Fixed by #34

Comments

@Octogonapus
Copy link
Contributor

Is your request related to a new offering from AWS?

No, this relates to an existing offering.

Is your request related to a problem? Please describe.

I would like it to be easier to use service integrations that require events permissions. E.g. the step functions integration. Without setting the proper events permissions, you will get an error similar to this: Error: AccessDeniedException: 'arn:aws:iam::xxxx:role/step-functions-role' is not authorized to create managed-rule.. This has caused prior issues like #11 (which was also related to other permissions issues addressed in #19 and #24).

Describe the solution you'd like.

Add the relevant default_resources to each events block inside the aws_service_policies such that users can write events = true for services that require these permissions.
Custom resources must be allowed, if the requires it.

Describe alternatives you've considered.

Currently, users must write out the full resources for the events permissions. This works, but it is verbose and repetitive.

Additional context

@github-actions
Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@antonbabenko
Copy link
Member

This issue has been resolved in version 2.6.0 🎉

@github-actions
Copy link

I'm going to lock this issue 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 similar to this, 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 Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants