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.

Sign up for GitHub

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

Jump to bottom

About that AmazonEC2FullAccess requirement #28

Open
jfsmith-at-coveo opened this issue May 10, 2019 · 0 comments
Open

About that AmazonEC2FullAccess requirement #28

jfsmith-at-coveo opened this issue May 10, 2019 · 0 comments

Comments

@jfsmith-at-coveo
Copy link

I was wondering how you would justify such a far-ranging authorization policy. In the code I only see ec2.describeInstances() and ec2.terminateInstances() being used. From what I can see, if I give those two -- and only those -- to my Lambda, it will work. So why would you say that full access is required?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jfsmith-at-coveo