KMS key policies and grants

5 minutes 5 Questions

AWS Key Management Service (KMS) key policies and grants are fundamental mechanisms for controlling access to encryption keys in AWS, essential knowledge for Solutions Architects managing complex organizational structures. **Key Policies** Key policies are resource-based policies attached to KMS keys that define who can access and manage the key. Every KMS key must have exactly one key policy, which serves as the primary access control mechanism. Key policies use JSON syntax similar to IAM policies, specifying principals, actions, resources, and conditions. Key policies can grant permissions to: - AWS accounts and IAM users/roles - AWS services for integrated encryption - Cross-account principals for multi-account architectures A critical element is the root account statement, which enables IAM policies to grant KMS permissions. Removing this can lock you out of the key permanently. **Grants** Grants provide a more flexible, programmatic way to delegate temporary KMS permissions. They are particularly useful when: - AWS services need to use keys on your behalf - You need to provide time-limited access - Permissions must be delegated dynamically at runtime Grants support a subset of KMS operations and can include constraints like encryption context requirements. They can be revoked at any time and are ideal for scenarios requiring fine-grained, temporary access. **Organizational Considerations** For complex organizations, combining key policies with grants enables: - Centralized key management with distributed usage - Cross-account encryption strategies - Service-linked encryption for AWS managed services - Compliance with separation of duties requirements **Best Practices** - Use key policies for permanent administrative access - Leverage grants for operational and temporary access - Implement least privilege principles - Enable CloudTrail logging for audit trails - Consider AWS Organizations SCPs for additional guardrails Understanding these mechanisms helps architects design secure, scalable encryption strategies across multi-account environments.

KMS Key Policies and Grants - Complete Guide

Why KMS Key Policies and Grants Are Important

AWS Key Management Service (KMS) key policies and grants are fundamental to securing sensitive data in AWS environments. They control who can use and manage encryption keys, which is critical for organizations handling regulated data, multi-account architectures, and complex access requirements. Understanding these concepts is essential for the Solutions Architect Professional exam as they frequently appear in scenarios involving cross-account access, least privilege implementation, and organizational security.

What Are KMS Key Policies?

A KMS key policy is a resource-based policy attached to a KMS key. It is the primary method for controlling access to KMS keys. Every KMS key must have exactly one key policy.

Key characteristics:
- Key policies are mandatory - unlike most AWS resources where resource policies are optional
- They define the trust boundary for the key
- They can grant access to IAM principals, AWS accounts, and AWS services
- Maximum size is 32 KB

Default Key Policy

When you create a KMS key through the console, the default key policy:
- Grants the AWS account (root user) full access to the key
- Enables IAM policies to grant access to the key
- Allows key administrators and key users to be defined

What Are KMS Grants?

Grants are an alternative mechanism to provide temporary, programmatic access to KMS keys. They are particularly useful when:
- Access needs to be delegated dynamically
- AWS services need to use keys on behalf of users
- You need fine-grained, time-limited permissions

Grant characteristics:
- Created using the CreateGrant API
- Can be revoked at any time using RevokeGrant or RetireGrant
- Support delegation through GranteePrincipal and RetiringPrincipal
- Eventually consistent (may take up to 5 minutes to propagate)

How Key Policies Work

Access to a KMS key requires:
1. The key policy must allow the action (or enable IAM policies)
2. If IAM policies are enabled, the IAM policy must also allow the action

Key policy statement components:
- Sid: Statement identifier
- Effect: Allow or Deny
- Principal: Who receives the permission
- Action: KMS actions permitted (e.g., kms:Encrypt, kms:Decrypt)
- Resource: Always "*" for key policies (refers to the key itself)
- Condition: Optional conditions for access

Cross-Account Access Pattern

To enable cross-account KMS key access:
1. The key policy in Account A must allow Account B (or specific principals in Account B)
2. An IAM policy in Account B must grant the principal permission to use the key

Common Grant Operations

Grants support these operations:
- Encrypt, Decrypt, ReEncrypt
- GenerateDataKey, GenerateDataKeyWithoutPlaintext
- DescribeKey
- CreateGrant (for delegation)
- RetireGrant

Exam Tips: Answering Questions on KMS Key Policies and Grants

1. Cross-Account Scenarios
When a question involves cross-account access to encrypted resources, remember that both the key policy AND an IAM policy in the accessing account are required. Look for answers that mention updating both.

2. Grants vs Key Policies
Choose grants when the scenario mentions:
- Temporary access requirements
- AWS services needing to use keys on your behalf
- Programmatic, dynamic access delegation
- Integration with services like EBS, RDS, or Redshift

Choose key policies when:
- Permanent access control is needed
- Defining administrative boundaries
- Setting up cross-account trust relationships

3. Key Policy Root Access
If a question asks about being locked out of a KMS key, the answer often involves the root account. Ensure key policies include root account access to prevent lockout scenarios.

4. Service-Linked Roles
When AWS services need to use KMS keys, they often use grants created through service-linked roles. Recognize this pattern in questions about encrypted EBS volumes or RDS instances.

5. Condition Keys
Watch for scenarios requiring conditional access. Common KMS condition keys include:
- kms:ViaService: Restrict key usage to specific AWS services
- kms:CallerAccount: Restrict to specific accounts
- kms:GrantIsForAWSResource: Limit grant creation to AWS services

6. Key Deletion and Grants
Remember that deleting a KMS key invalidates all grants. In disaster recovery scenarios, this affects all resources encrypted with that key.

7. Eventually Consistent Grants
If a question mentions timing issues with newly created grants, remember grants are eventually consistent. The solution might involve using a grant token for immediate use.

8. Organizational Complexity
In multi-account scenarios with AWS Organizations, consider:
- Using AWS RAM to share KMS keys across accounts
- Service Control Policies (SCPs) can restrict KMS actions
- Key policies combined with organizational boundaries
Test mode:
More KMS key policies and grants questions
30 questions (total)

Other Design Solutions for Organizational Complexity concepts

Account structure for organizational requirementsAmazon InspectorAmazon S3 Storage LensAmazon VPC networking conceptsAutomatic failure recovery architecturesAWS Backup serviceAWS BudgetsAWS Certificate Manager (ACM)AWS CloudTrailAWS Compute OptimizerAWS container networking servicesAWS Control TowerAWS Cost ExplorerAWS Direct ConnectAWS Elastic Disaster RecoveryAWS Global InfrastructureAWS IAM Identity CenterAWS Key Management Service (KMS)AWS Network FirewallAWS OrganizationsAWS Pricing CalculatorAWS PrivateLinkAWS Region and Availability Zone selectionAWS Resource Access Manager (RAM)AWS Savings PlansAWS Security HubAWS Site-to-Site VPNAWS Transit GatewayAWS Trusted AdvisorCentralized logging strategiesCentralized security event notificationsCertificate management best practicesCo-location connectivityConnectivity among multiple VPCsCost allocation tagging strategiesCross-account access managementCross-account resource sharingData backup strategiesDesigning DR solutions for RTO/RPO requirementsEffective backup and restoration strategiesEncryption strategies for data at restEncryption strategies for data in transitEvaluating VPC connectivity optionsHybrid DNS with Route 53 ResolverIAM Access AnalyzerIAM policies and permissionsIAM users, groups, and rolesIP addressing and CIDR blocksLanding zone designMonitoring cost and usageMulti-account event notificationsMulti-account governance modelsMulti-site disaster recoveryNetwork ACLsNetwork latency requirementsNetwork segmentation and subnettingNetwork traffic monitoringOn-premises DNS integrationOn-premises to cloud integrationPilot light disaster recoveryPurchasing options impact on cost and performanceRecovery Point Objectives (RPO)Recovery Time Objectives (RTO)Reserved InstancesRoute tables for securityScale-up vs scale-out architecturesSecurity auditing strategiesSecurity groupsService Control Policies (SCPs)Spot InstancesThird-party identity provider integrationTransitive routing in AWSTroubleshooting traffic flowsVPC endpoints for service integrationsVPC Flow LogsVPC peering connectionsWarm standby disaster recovery