Manage access to Amazon Q Developer for third-party integration
For third-party integrations, you must use the AWS Key Management Service (KMS) to manage access to Amazon Q Developer instead of IAM policies that are neither identity-based or resource-based.
Allow administrators to use customer managed keys to update role policies
The following example key policy grants permission to use customer managed keys
(CMK)
The kms:ViaService condition key limits the use of a KMS key to requests from
specified AWS services. Additionally, it’s used to deny permission to use a KMS key when the
request comes from particular services. With the condition key, you can limit who can use CMK for
encrypting or decrypting content. For more information, see kms:ViaService
With KMS encryption context, you have an optional set of key-value pairs that can be included
in cryptographic operations with symmetric encryption KMS keys to enhance authorization and
auditability. The encryption context can be used to verify the integrity and authenticity of
encrypted data, control access to symmetric encryption KMS keys in key policies and IAM policies,
and identify and categorize cryptographic operations in AWS CloudTrail logs. For more information,
see Encryption context