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

Potentially overly permissive roles found at template.yaml #61

Open
jana-learning opened this issue Sep 13, 2024 · 0 comments
Open

Potentially overly permissive roles found at template.yaml #61

jana-learning opened this issue Sep 13, 2024 · 0 comments

Comments

@jana-learning
Copy link

At the "template.yaml" file, sfExecuteAWSService role has “ds:CreateIdentityPoolDirectory” and “ds:DeleteDirectory” permissions assigned. In an enterprise environment, that does seem overly permissive. Why are those required? Perhaps there's a valid use case?

That role also has the “s3:CreateBucket” permission without any reference to an arn resource. Would it be possible to pre-provision the required bucket(s), add that resource(s) arn to the "s3:Get*" permissions?

Will removing those permissions break the functionality of the CTI adapter and associated lambdas?

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

No branches or pull requests

1 participant