Skip to content

fix(permissionsBoundary): apply permissionsBoundary #535

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

Merged

Conversation

DubKF
Copy link

@DubKF DubKF commented Nov 24, 2022

This PR allows using a Permissions Boundary defined in the provider level e.g.

provider:
  name: aws
  runtime: python3.9
  # the permisions boundary goes here 
  rolePermissionsBoundary: arn:aws:iam::[account]:policy/permission_boundary  
  # ...

Previously, the boundary was only applied to the created lambda execution role, but was missing on the created roles for functions of the state machine as described in issue 395 some time ago.

We run into the same issue yesterday well using the newest version of serverless and this plugin. The submitted fix worked for us.

@DubKF
Copy link
Author

DubKF commented Nov 24, 2022

@lopburny Could you perhaps have a look and provide some guidance or workflow approval as I'm a 1st time contributor ;)

@lopburny
Copy link
Contributor

lopburny commented Dec 8, 2022

Hi @DubKF Thanks for this PR. Looks good to me.

@lopburny lopburny merged commit c4dd802 into serverless-operations:master Dec 8, 2022
@lopburny
Copy link
Contributor

🎉 This PR is included in version 3.12.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

ss-betseqnzr pushed a commit to BetSEQNZR/serverless-step-functions that referenced this pull request Sep 8, 2023
…ns_boundary

fix(permissionsBoundary): apply permissionsBoundary
@nabsource
Copy link

please add this option to the docs/readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants