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

Patch 450 #472

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Patch 450 #472

wants to merge 7 commits into from

Conversation

shuklaalok87
Copy link
Contributor

No description provided.

7. Repeat step number 2 - 6 to verify other "KMS key" in the region.</br>
8. Navigate to "Customer Managed Keys" under "Key Management Service" and select the "KMS key" that needs to modify to restrict the he number of users and roles that can perform encrypt and decrypt operation and have any wildcards.</br> <img src="/resources/aws/kms/kms-key-policy/step8.png"/>
7. Repeat step number 2 - 6 to verify other KMS keys in the region.</br>
8. Navigate to "Customer Managed Keys" under "Key Management Service" and select the "KMS key" that needs to modify to restrict the number of users and roles that can perform encrypt and decrypt operation and have any wildcards.</br> <img src="/resources/aws/kms/kms-key-policy/step8.png"/>
9. On the "Customer managed keys" page scroll down and on the "Key policy" tab click on the "Switch to policy view" button and replace the "Everyone" grantee ("AWS" : * ) from the Principal element value with an "AWS account ID" or "AWS ARN" and click on the "Save" changes button.</br> <img src="/resources/aws/kms/kms-key-policy/step9.png"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
9. On the "Customer managed keys" page scroll down and on the "Key policy" tab click on the "Switch to policy view" button and replace the "Everyone" grantee ("AWS" : * ) from the Principal element value with an "AWS account ID" or "AWS ARN" and click on the "Save" changes button.</br> <img src="/resources/aws/kms/kms-key-policy/step9.png"/>
9. On the "Customer managed keys" page scroll down and on the "Key policy" tab click on the "Switch to policy view" button and replace the "Everyone" grantee ("AWS" : * ) from the Principal element value with an "AWS account ID" or "AWS ARN" and click on the "Save" changes button.</br> <img src="/resources/aws/kms/kms-key-policy/step9.png"/>

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

step 9 and 6 image not present

7. Repeat step number 2 - 6 to verify other "KMS key" in the region.</br>
8. Navigate to "Customer Managed Keys" under "Key Management Service" and select the "KMS key" that needs to modify to restrict the he number of users and roles that can perform encrypt and decrypt operation and have any wildcards.</br> <img src="/resources/aws/kms/kms-key-policy/step8.png"/>
7. Repeat step number 2 - 6 to verify other KMS keys in the region.</br>
8. Navigate to "Customer Managed Keys" under "Key Management Service" and select the "KMS key" that needs to modify to restrict the number of users and roles that can perform encrypt and decrypt operation and have any wildcards.</br> <img src="/resources/aws/kms/kms-key-policy/step8.png"/>
9. On the "Customer managed keys" page scroll down and on the "Key policy" tab click on the "Switch to policy view" button and replace the "Everyone" grantee ("AWS" : * ) from the Principal element value with an "AWS account ID" or "AWS ARN" and click on the "Save" changes button.</br> <img src="/resources/aws/kms/kms-key-policy/step9.png"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

step 9 and 6 image not present

@alphadev4 alphadev4 added bug Something isn't working question Further information is requested reviewed Reviewed by reviewer labels Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested reviewed Reviewed by reviewer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants