We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using master-level keys for this in suboptimal. Better to create a specific IAM role for this purpose, which will require these permissions:
{ "Statement": [ { "Sid": "Stmt1349790264045", "Action": [ "ec2:AttachVolume", "ec2:CreateSnapshot", "ec2:CreateTags", "ec2:CreateVolume", "ec2:DeleteSnapshot", "ec2:DeleteTags", "ec2:DeleteVolume", "ec2:DescribeInstanceAttribute", "ec2:DescribeSnapshots", "ec2:DescribeVolumeAttribute", "ec2:DescribeVolumeStatus", "ec2:DescribeVolumes", "ec2:DescribeRegions", "ec2:DetachVolume", "ec2:ModifyInstanceAttribute", "ec2:ModifySnapshotAttribute", "ec2:ModifyVolumeAttribute" ], "Effect": "Allow", "Resource": [ "*" ] }, { "Sid": "Stmt1349790290507", "Action": [ "route53:ChangeResourceRecordSets" ], "Effect": "Allow", "Resource": [ "arn:aws:route53:::hostedzone/*" ] } ] }
I'll add this to the docs.
The text was updated successfully, but these errors were encountered:
mikery
No branches or pull requests
Using master-level keys for this in suboptimal. Better to create a specific IAM role for this purpose, which will require these permissions:
I'll add this to the docs.
The text was updated successfully, but these errors were encountered: