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

Chore/lambda event source mapping #54

Merged
merged 5 commits into from
Dec 8, 2024

Conversation

crispy101
Copy link
Contributor

Change alternatvie to #53
This is to allow the role to tag "event-source-mapping" resources, which can't be identified by any qualifiers, e.g.
arn:aws:lambda:ap-southeast-2:123456789012:event-source-mapping:1bfc3b83-2c0a-49d8-b7b6-ed1dfcc099b6

While on it, we might as well merge the ones below to this new item, as they all are about EventSourceMapping. Thoughts, @TheOrangePuff ?

            "lambda:ListEventSourceMappings",
            "lambda:CreateEventSourceMapping",
            "lambda:DeleteEventSourceMapping",

@crispy101 crispy101 requested a review from a team as a code owner December 8, 2024 22:49
@crispy101 crispy101 requested review from AdamJHall, gowrizrh and TheOrangePuff and removed request for a team, AdamJHall and gowrizrh December 8, 2024 22:49
aaronmedina-dev
aaronmedina-dev approved these changes Dec 8, 2024
resources: [
`arn:aws:lambda:${region}:${accountId}:event-source-mapping:*`,
],
actions: ["lambda:TagResource"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also needs untag 🙂

@crispy101 crispy101 merged commit 243e494 into main Dec 8, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

3 participants