Identity and access management for AWS Key Management Service
AWS Identity and Access Management (IAM) helps you securely control access to AWS resources. Administrators control who can be authenticated (signed in) and authorized (have permissions) to use AWS KMS resources. For more information, see Using IAM policies with AWS KMS.
Key policies are the primary mechanism for controlling access to KMS keys in AWS KMS. Every KMS key must have a key policy. You can also use IAM policies and grants, along with key policies, to control access to your KMS keys. For more information, see KMS key access and permissions.
You can also share a customer managed key with other AWS accounts through AWS Resource Access Manager (AWS RAM). A
shared KMS key has a second key policy, named AWS_RAM, which AWS RAM creates and
manages. Consumers of the resource share get the permissions in its managed permission. You
control who can share your KMS keys with AWS RAM permissions, such as
ram:CreateResourceShare, and with kms:PutKeyPolicy permission on the
KMS key. For more information about controlling and monitoring shared KMS keys, see Security best practices for sharing KMS keys.
If you are using an Amazon Virtual Private Cloud (Amazon VPC), you can create an interface VPC endpoint to AWS KMS powered by AWS PrivateLink. You can also use VPC endpoint policies to determine which principals can access your AWS KMS endpoint, which API calls they can make, and which KMS key they can access.