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

Limit the resources VMClarity can manage in AWS #6

Merged
2 commits merged into from
Nov 28, 2022
Merged

Conversation

ghost
Copy link

@ghost ghost commented Nov 18, 2022

For security VMClarity should only be able to manage the exact resources
it needs to manage to do its job.

This commit changes the IAM policy for VMClarity so that it can snapshot
VMs or Volumes anywhere in the AWS account, but only manage instances
and volumes within the VMClarity VPC.

installation/aws/VmClarity.cfn Outdated Show resolved Hide resolved
installation/aws/VmClarity.cfn Outdated Show resolved Hide resolved
installation/aws/VmClarity.cfn Show resolved Hide resolved
installation/aws/VmClarity.cfn Show resolved Hide resolved
For security VMClarity should only be able to manage the exact resources
it needs to manage to do its job.

This commit changes the IAM policy for VMClarity so that it can snapshot
VMs or Volumes anywhere in the AWS account, but only manage instances
and volumes within the VMClarity VPC.
@ghost ghost force-pushed the vmclarity_iam_policy branch from 98afc5b to 67a78ea Compare November 22, 2022 10:38
@ghost ghost merged commit 375bdc2 into main Nov 28, 2022
@ghost ghost deleted the vmclarity_iam_policy branch November 28, 2022 09:14
This pull request was closed.
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.

None yet

3 participants