# AWS Key Management Service (AWS KMS)

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms)

> AWS Key Management Service (AWS KMS) is a managed service that makes it easy for you to create and control the cryptographic keys used to secure your data across AWS services and in your applications.

Practice exams covering AWS Key Management Service (AWS KMS): [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 9 key features of AWS Key Management Service (AWS KMS)

AWS Key Management Service (AWS KMS) is a secure and centralized service designed to manage cryptographic keys, offering seamless integration with AWS services, fine-grained access control, auditing capabilities, automatic key rotations, and high availability.

1. **Centralized Key Management**: AWS KMS allows you to centralize control over the cryptographic keys used to protect your data. The service provides a single place to manage keys, which simplifies the management process and enhances security.
2. **Integrated with AWS Services**: It is seamlessly integrated with other AWS services, making it easier to encrypt data stored in these services. For example, you can use KMS keys to encrypt data in S3 buckets, EBS volumes, and RDS databases.
3. **Customer Managed KMS Keys**: AWS KMS enables you to create and manage your own customer managed KMS keys. These keys can control access to data encryption keys that encrypt and decrypt your data.
4. **Access Control**: KMS provides detailed access control policies, allowing you to specify who can use your keys and under what conditions. This includes the ability to implement IAM policies and grants.
5. **Auditing and Compliance**: The service integrates with AWS CloudTrail to provide logs of all key usage. This helps in auditing, tracking key usage, and demonstrating compliance with regulatory requirements.
6. **Automatic Rotations**: AWS KMS supports the automatic rotation of eligible symmetric encryption KMS keys with AWS KMS-generated key material at configurable intervals from 90 to 2560 days, which can enhance security by changing the key material regularly without changing the application code that uses them.
7. **High Availability and Durability**: Deployed within AWSâs managed, secure, and resilient infrastructure, KMS is designed to be both highly available and durable, ensuring that your cryptographic keys are always accessible and protected.
8. **Non-exportable KMS Keys**: AWS KMS provides no mechanism to export plaintext KMS keys.
9. **Key Aliases**: An alias is a user-friendly name associated with a KMS key and can be used instead of the key ID in many AWS KMS API operations.

## Where AWS Key Management Service (AWS KMS) is used

AWS Key Management Service (AWS KMS) is used for encrypting data across AWS services, managing cloud application keys, digital signing, ensuring regulatory compliance through controlled key management, and providing secure key storage with automatic rotation.

1. **Encrypting Data**: AWS KMS enables users to easily encrypt data stored in various AWS services such as S3, EBS, RDS, and Redshift, ensuring that sensitive information is protected at rest. Through the integration of KMS with these services, encryption and decryption processes are streamlined, providing a secure and efficient method for protecting data.
2. **Managing Keys for Cloud Applications**: Developers can utilize AWS KMS to manage cryptographic keys for their cloud-based applications. This includes creating, rotating, and controlling usage policies for encryption keys, enabling secure access to application data. KMS simplifies the key management process, reducing the risk associated with handling keys directly and ensuring compliance with security policies.
3. **Digital Signing**: AWS KMS also supports digital signing, allowing users to ensure the integrity and authenticity of their documents and code. By signing data using a private key managed in KMS, users can verify the senderâs identity and that the data has not been tampered with, enhancing trust and security for digital transactions and distributions.
4. **Regulatory Compliance**: Organizations subject to regulatory requirements related to data protection can leverage AWS KMS to help meet compliance obligations. KMS provides mechanisms for key management and encryption that align with standards such as GDPR, HIPAA, and PCI-DSS, offering detailed key usage logs and the ability to control and monitor access to keys.
5. **Secure Key Storage and Rotation**: AWS KMS is designed to securely store encryption keys in a centralized service, reducing the risk of unauthorized access. It supports automatic key rotation, which enhances security by regularly changing the encryption keys. This helps in maintaining confidentiality and integrity of the data over time without manual intervention.

## How AWS Key Management Service (AWS KMS) is priced

AWS KMS pricing includes monthly fees for customer managed CMKs, charges based on the volume of cryptographic request operations, additional fees for specialized operations like data key pair generation, and potential costs for using KMS with integrated AWS services.

- **Key Storage**: Each customer managed KMS key costs $1 per month, prorated hourly, including each primary and replica multi-Region key and keys using imported material, CloudHSM, or an external key store. AWS managed and AWS owned KMS keys have no creation or storage charge.
- **Requests Pricing**: AWS KMS charges for the requests made to the service, which includes cryptographic operations such as encrypt, decrypt, and generateDataKey, among others. The price depends on the volume of requests, with the first tier of requests typically included for free and additional requests charged at a per-request rate.
- **Data Key Pair Generation and Asymmetric Operations**: Requests to GenerateDataKeyPair and GenerateDataKeyPairWithoutPlaintext, and requests such as Sign, Verify, Encrypt, Decrypt, and GetPublicKey that reference asymmetric KMS keys, are excluded from the free tier.
- **Key Rotation**: For automatic or on-demand rotation, the first and second rotations each add $1 per month, prorated hourly, to the key's storage cost. Subsequent rotations do not add further charges.
- **CloudHSM-backed Key Store Costs**: Using a CloudHSM-backed key store incurs standard AWS CloudHSM charges in addition to AWS KMS charges.

## Services AWS Key Management Service (AWS KMS) works with

- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: AWS KMS protects encryption keys used by API Gateway to encrypt cached API responses at rest.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: AWS KMS encrypts data that AppFlow stores while processing flows. You can select a customer managed key to control access to that data.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: AWS KMS protects encrypted data that Athena reads and the query results it writes to Amazon S3. Athena workgroups can also use KMS keys to encrypt stored query information.
- **[Amazon Augmented AI (Amazon A2I)](https://blowstack.com/tools/cloud-services-hub/amazon-augmented-ai-(amazon-a2i))**: AWS KMS can encrypt human review output written by Amazon A2I to Amazon S3. The flow definition specifies the key, and the execution role needs permission to use it.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: AWS KMS protects Aurora database storage, automated backups, snapshots, and replicas for encrypted clusters. Customer managed keys let you control access to the encrypted database.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: AWS KMS protects the storage, backups, and snapshots of encrypted Aurora Serverless databases. The database's KMS key remains in use as compute capacity scales.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: AWS KMS can protect Bedrock resources such as model customization data, custom models, and stored agent or knowledge base information. Supported configurations let you select customer managed keys.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: AWS KMS can encrypt data stored by AgentCore Memory using a customer managed key. Key policies control whether AgentCore can encrypt and decrypt that memory data.
- **[Amazon Braket](https://blowstack.com/tools/cloud-services-hub/amazon-braket)**: AWS KMS can protect Braket Hybrid Jobs storage and job output stored in Amazon S3. You can configure customer managed keys for supported job encryption settings.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: AWS KMS can protect S3 objects served through CloudFront using origin access control. The KMS key policy grants the CloudFront distribution permission to decrypt the encrypted origin objects.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: AWS KMS can encrypt CloudWatch Logs log groups and CloudWatch Logs Insights query results. CloudWatch also publishes KMS metrics that can be used in dashboards and alarms.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: AWS KMS can encrypt source code and associated analysis artifacts used by CodeGuru Reviewer. You can choose a customer managed key when associating a repository.
- **[Amazon CodeWhisperer](https://blowstack.com/tools/cloud-services-hub/amazon-codewhisperer)**: AWS KMS can protect CodeWhisperer customization data derived from private repositories. A customer managed key gives you control over access to the stored customization data.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: AWS KMS encrypts verification codes and temporary passwords that Cognito passes to custom email and SMS sender Lambda functions. The sender function uses KMS to decrypt the value before delivering it.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: AWS KMS can encrypt Comprehend analysis output, training data storage, and custom model artifacts. Supported jobs accept customer managed keys for output or processing volumes.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: AWS KMS protects Connect data such as stored recordings, reports, and customer profile information. Supported storage configurations let you select customer managed keys.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: AWS KMS can encrypt records buffered in a Firehose stream and protect delivery to KMS-encrypted S3 destinations. Firehose uses its configured permissions to generate data keys and access encrypted destination data.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: AWS KMS encrypts DataZone domain data, including catalog metadata. You can configure a customer managed key when creating a domain.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: AWS KMS encrypts data stored by DevOps Guru, including operational analysis data. You can configure a customer managed key through the service's encryption settings.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: AWS KMS protects encrypted DocumentDB storage, backups, and snapshots. The selected key controls access to the encrypted cluster data.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: AWS KMS protects DynamoDB tables and their indexes, streams, and backups through encryption at rest. Tables can use AWS owned, AWS managed, or customer managed keys.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: AWS KMS supports EC2 Nitro Enclaves with attestation-based authorization for cryptographic operations. KMS can return encrypted responses that only an enclave matching the key policy's attestation requirements can decrypt.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: AWS KMS enables Auto Scaling groups to launch instances with customer-key-encrypted EBS volumes. The Auto Scaling service-linked role needs appropriate key permissions and grants.
- **[Amazon ECS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-ecs-anywhere)**: AWS KMS protects customer-key-encrypted Secrets Manager secrets and Systems Manager parameters injected into ECS Anywhere tasks. The task execution role needs permission to decrypt those values.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: AWS KMS protects the data keys used to encrypt EBS volumes and snapshots. EBS encryption also protects data moving between an instance and its attached encrypted volumes.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: AWS KMS can encrypt container images stored in ECR repositories. ECR creates KMS grants to encrypt image layers when pushed and decrypt them when pulled.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: AWS KMS can protect ECS managed storage and encrypted session logs for ECS Exec. ECS tasks can also receive customer-key-encrypted secrets through the task execution role.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: AWS KMS protects encrypted EFS file systems at rest. A customer managed key can control access to file data, while EFS manages encryption transparently for clients.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: AWS KMS provides envelope encryption for Kubernetes API data stored by EKS, including Kubernetes Secrets. Supported configurations let you supply a customer managed key.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: AWS KMS protects supported ElastiCache deployments and backups through encryption at rest. Customer managed keys can be selected for supported cache configurations.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: AWS KMS integrates with EMR security configurations to protect local disk data and data stored in Amazon S3. EMRFS can use KMS keys for server-side or client-side encryption.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS KMS can encrypt events stored by EventBridge event buses and archives. Customer managed keys can also protect data handled by supported EventBridge Pipes configurations.
- **[Amazon Forecast](https://blowstack.com/tools/cloud-services-hub/amazon-forecast)**: AWS KMS can encrypt Forecast datasets and forecasting resources with customer managed keys. Forecast uses an authorized role to access the key during data processing.
- **[Amazon Fraud Detector](https://blowstack.com/tools/cloud-services-hub/amazon-fraud-detector)**: AWS KMS encrypts Fraud Detector data at rest, including stored event data. You can configure a customer managed key to control encryption of supported resources.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: AWS KMS protects FSx file system data and backups at rest. Supported file system types let you select a customer managed key when creating the file system.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: AWS KMS protects GuardDuty findings exported to Amazon S3. The destination configuration specifies a customer managed key whose policy allows GuardDuty to generate data keys.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: AWS KMS encrypts HealthLake data stores at rest. You can select a customer managed key when creating a data store to control access to its protected health information.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: AWS KMS encrypts Inspector findings reports exported to Amazon S3. Export requests specify a KMS key, and its policy must authorize Inspector to use it.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: AWS KMS protects Kendra index data and supported data source information at rest. You can specify a customer managed key when creating an index.
- **[Amazon Keyspaces (for Apache Cassandra)](https://blowstack.com/tools/cloud-services-hub/amazon-keyspaces-(for-apache-cassandra))**: AWS KMS protects Keyspaces tables through encryption at rest. Tables can use an AWS owned key or a customer managed key.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: AWS KMS encrypts records stored in Kinesis data streams. Producers and consumers require the appropriate KMS permissions when a stream uses a customer managed key.
- **[Amazon Kinesis Video Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-video-streams)**: AWS KMS encrypts media stored in Kinesis video streams. You can select a customer managed key when creating a stream.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: AWS KMS protects stored Lex bot information and can encrypt conversation audio logs. Supported bot and logging configurations let you select customer managed keys.
- **[Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail)**: AWS KMS backs the encryption of Lightsail instance disks, block storage disks, and their snapshots. Lightsail manages this encryption automatically rather than exposing customer key selection.
- **[Amazon Location Service](https://blowstack.com/tools/cloud-services-hub/amazon-location-service)**: AWS KMS protects stored Location Service data, including tracker and geofence collection data. Supported resources can use customer managed keys for additional control.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: AWS KMS encrypts Macie sensitive data discovery results stored in Amazon S3. Macie also needs permission to decrypt customer-key-encrypted S3 objects that it analyzes.
- **[Amazon Managed Blockchain](https://blowstack.com/tools/cloud-services-hub/amazon-managed-blockchain)**: AWS KMS protects data stored by Managed Blockchain, including supported network and node storage. Supported resource configurations allow customer managed keys.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: AWS KMS protects sensitive workspace data stored by Managed Grafana, including credentials. The service manages the encryption used for this stored data.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: AWS KMS protects application state and other stored application data in Managed Service for Apache Flink. Supported application encryption settings allow customer managed keys.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: AWS KMS encrypts metrics stored in Managed Service for Prometheus workspaces. A workspace can use a customer managed key selected during creation.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: AWS KMS encrypts data stored on MSK brokers. Provisioned clusters can use customer managed keys, and MSK also integrates with KMS-encrypted Secrets Manager secrets for SASL/SCRAM authentication.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: AWS KMS protects MWAA environment data, including its metadata database, queues, and logs. You can select a customer managed key when creating an environment.
- **[Amazon MemoryDB for Redis](https://blowstack.com/tools/cloud-services-hub/amazon-memorydb-for-redis)**: AWS KMS protects MemoryDB data and snapshots through encryption at rest. You can choose a customer managed key when creating a cluster.
- **[Amazon Monitron](https://blowstack.com/tools/cloud-services-hub/amazon-monitron)**: AWS KMS protects Monitron data stored at rest. Monitron manages the encryption keys used by the service.
- **[Amazon MQ](https://blowstack.com/tools/cloud-services-hub/amazon-mq)**: AWS KMS encrypts messages stored by Amazon MQ brokers. Supported broker configurations let you choose a customer managed key.
- **[Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune)**: AWS KMS protects encrypted Neptune database storage, backups, snapshots, and replicas. The cluster's selected key controls access to its encrypted data.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: AWS KMS encrypts OpenSearch Service domain data at rest, including indexes and automated snapshots. OpenSearch Serverless encryption policies can also select customer managed keys for collections.
- **[Amazon Personalize](https://blowstack.com/tools/cloud-services-hub/amazon-personalize)**: AWS KMS can encrypt Personalize dataset groups and associated data at rest. Import and export roles also need KMS permissions when accessing encrypted S3 data.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: AWS KMS can protect Amazon Q Developer customization data derived from private code repositories. Customer managed keys provide control over access to that stored data.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: AWS KMS protects Q Business application data, including indexed enterprise content. You can configure a customer managed key when creating an application.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: AWS KMS protects QuickSight SPICE data at rest. Customer managed keys let you control encryption of SPICE datasets and revoke access through key permissions.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: AWS KMS protects encrypted RDS database storage, automated backups, snapshots, and read replicas. You can select a customer managed key when creating an encrypted database.
- **[Amazon RDS Proxy](https://blowstack.com/tools/cloud-services-hub/amazon-rds-proxy)**: AWS KMS protects Secrets Manager credentials that RDS Proxy retrieves to authenticate to databases. The proxy's IAM role needs permission to decrypt secrets encrypted with a customer managed key.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: AWS KMS protects encrypted Redshift databases and snapshots. Redshift Serverless namespaces can also use customer managed keys.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: AWS KMS can protect Rekognition resources such as Custom Labels model artifacts and Face Liveness output. Supported operations accept a customer managed key for stored data.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: AWS KMS holds the asymmetric signing key used by Route 53 DNSSEC signing. Route 53 uses the key to sign DNSKEY records for a public hosted zone.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: AWS KMS protects S3 objects through SSE-KMS and dual-layer server-side encryption with KMS keys. S3 Bucket Keys can reduce the number of KMS requests needed for SSE-KMS objects.
- **[Amazon S3 Glacier](https://blowstack.com/tools/cloud-services-hub/amazon-s3-glacier)**: AWS KMS encryption remains in place when SSE-KMS-encrypted S3 objects move into S3 Glacier storage classes. Restoring or reading those objects still requires access to their KMS keys.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: AWS KMS can encrypt SageMaker notebook storage, training and processing volumes, model artifacts, and other supported resources. Jobs can specify customer managed keys for storage and output encryption.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: AWS KMS can protect Data Wrangler processing volumes and data exported to Amazon S3. The execution role needs permission to use the keys protecting input and output data.
- **[Amazon SageMaker Ground Truth](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-ground-truth)**: AWS KMS can encrypt Ground Truth labeling output and supported processing storage. Labeling jobs can specify a customer managed key for output written to Amazon S3.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: AWS KMS can encrypt security data stored in Security Lake's S3 data lake. A customer managed key must authorize Security Lake and the subscribers that need to read the encrypted data.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: AWS KMS supports client-side encryption of received emails that SES delivers to Amazon S3. An SES receipt rule can specify the KMS key used to protect each message.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: AWS KMS encrypts messages stored in encrypted SNS topics. Topic publishers need appropriate KMS permissions when using a customer managed key.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: AWS KMS encrypts messages stored in SQS queues configured for SSE-KMS. Producers and consumers require KMS permissions appropriate to sending and receiving encrypted messages.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: AWS KMS can encrypt asynchronous Textract analysis results delivered to Amazon S3. The request can specify a customer managed key for that output.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: AWS KMS encrypts Timestream data at rest. Timestream for LiveAnalytics databases can use customer managed keys.
- **[Amazon Timestream for InfluxDB](https://blowstack.com/tools/cloud-services-hub/amazon-timestream-for-influxdb)**: AWS KMS backs encryption of the storage used by Timestream for InfluxDB database instances. KMS also protects the Secrets Manager secrets holding database credentials.
- **[Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe)**: AWS KMS can encrypt transcription output written to Amazon S3. Transcription jobs can specify a customer managed key and an execution role authorized to use it.
- **[Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate)**: AWS KMS can encrypt Translate asynchronous batch output and stored parallel data. Supported requests let you specify a customer managed key.
- **[Amazon Verified Permissions](https://blowstack.com/tools/cloud-services-hub/amazon-verified-permissions)**: AWS KMS protects Verified Permissions policy store data at rest. The service uses encryption to protect stored authorization policies and related information.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS KMS supports interface VPC endpoints so workloads can make KMS requests without traversing the public internet. Endpoint policies can further restrict which KMS operations and keys are accessible.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: AWS KMS protects encrypted WorkSpaces root and user volumes. You can select a customer managed key when provisioning encrypted WorkSpaces.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: AWS KMS protects stored WorkSpaces Applications data and can protect persistent user content stored in S3. Customer-key-encrypted home folders require key permissions for the service's storage access role.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: AWS KMS protects WorkSpaces Secure Browser resources such as stored browser settings and user access logging settings. Supported resources can use customer managed keys.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: AWS KMS protects sensitive configuration used by Amplify, including supported backend secret storage. Amplify environments use KMS permissions to access encrypted secrets and parameters.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: AWS KMS encrypts stored copies of App Runner source repositories and service logs. You can specify a customer managed key in the service encryption configuration.
- **[AWS AppConfig](https://blowstack.com/tools/cloud-services-hub/aws-appconfig)**: AWS KMS can encrypt configuration data stored in the AppConfig hosted configuration store and deployed configuration data. Supported resources let you specify a customer managed key.
- **[AWS Application Discovery Service](https://blowstack.com/tools/cloud-services-hub/aws-application-discovery-service)**: AWS KMS protects discovery data stored by Application Discovery Service. Encryption safeguards the collected server configuration and utilization information at rest.
- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: AWS KMS protects encrypted EBS volumes used in the Application Migration Service staging area and launched target instances. Replication and launch settings support customer managed keys.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: AWS KMS protects AppSync data at rest, including encrypted API caches. AppSync manages the encryption used for its cache storage.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: AWS KMS encrypts Audit Manager evidence and assessment data. You can configure a customer managed key for Audit Manager's stored data.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: AWS KMS protects backups stored in Backup vaults. Cross-account and cross-Region copies require suitable key policies, and some backup types retain encryption tied to the source resource's key.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: AWS KMS can protect EBS volumes attached to Batch compute instances. A Batch compute environment can use an EC2 launch template that specifies encrypted volumes and a customer managed key.
- **[AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets)**: AWS KMS can protect budget notifications sent through encrypted SNS topics. The key policy must allow the Budgets service to use the key for notification delivery.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: AWS KMS protects private keys stored by ACM. ACM uses KMS encryption context and grants to make certificate private keys available to authorized integrated services.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: AWS KMS can protect SNS topics used to deliver notifications to AWS Chatbot. Customer managed key policies must permit the access required for encrypted-topic notification delivery.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: AWS KMS protects supported Clean Rooms analysis resources and results. Customer managed keys can also protect data used by Clean Rooms ML.
- **[AWS Cloud9](https://blowstack.com/tools/cloud-services-hub/aws-cloud9)**: AWS KMS protects sensitive Cloud9 environment data, including stored SSH credentials. KMS-backed EBS encryption can also protect the development environment's instance storage.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation provisions and manages KMS keys, aliases, and replica keys as stack resources. Templates can define key policies, automatic rotation, and deletion safeguards.
- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: AWS KMS can use a CloudHSM cluster as a custom key store. Cryptographic operations for keys in that store run in the connected HSM cluster under your control.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records KMS API activity, including key administration and cryptographic operations. KMS keys can also encrypt CloudTrail log files and CloudTrail Lake event data stores.
- **[AWS CodeArtifact](https://blowstack.com/tools/cloud-services-hub/aws-codeartifact)**: AWS KMS encrypts packages and metadata stored in CodeArtifact domains. A domain can use a customer managed key selected when it is created.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: AWS KMS can encrypt CodeBuild output artifacts and supported build storage. Build service roles need key permissions to read encrypted inputs and write encrypted artifacts.
- **[AWS CodeCommit](https://blowstack.com/tools/cloud-services-hub/aws-codecommit)**: AWS KMS encrypts repository data stored in CodeCommit. CodeCommit uses KMS-backed encryption transparently when storing and retrieving repository contents.
- **[AWS CodeConnections](https://blowstack.com/tools/cloud-services-hub/aws-codeconnections)**: AWS KMS protects sensitive connection data stored by CodeConnections, including credentials used to connect to external source providers. The service manages encryption of that stored information.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: AWS KMS can protect CodeDeploy deployment bundles stored in Amazon S3. The role used to retrieve a deployment revision needs permission to decrypt the bundle's KMS key.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: AWS KMS encrypts artifacts stored in CodePipeline artifact buckets. Customer managed keys support controlled artifact access, including appropriately configured cross-account pipeline actions.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: AWS KMS protects Compute Optimizer data stored at rest. The service manages encryption of the operational data used to generate recommendations.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported KMS resource configurations and evaluates keys with managed or custom rules. KMS can also encrypt configuration snapshots and history files delivered to Amazon S3.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: AWS KMS can encrypt the CloudTrail logs and AWS Config data used by a Control Tower landing zone. Landing zone encryption settings can specify a customer managed key.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: AWS KMS protects data assets stored by Data Exchange. Import and export workflows also require appropriate key access when using KMS-encrypted S3 objects.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: AWS KMS protects DMS replication storage, connection information, and other stored migration data. Replication instances and supported endpoints can use customer managed keys.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: AWS KMS enables DataSync to read and write SSE-KMS-encrypted objects in Amazon S3. The task's access role and key policies must authorize the required encryption and decryption operations.
- **[AWS DeepRacer](https://blowstack.com/tools/cloud-services-hub/aws-deepracer)**: AWS KMS protects supported DeepRacer training resources and stored model artifacts. Customer managed keys can be configured for model encryption.
- **[AWS Device Farm](https://blowstack.com/tools/cloud-services-hub/aws-device-farm)**: AWS KMS protects Device Farm data stored at rest, including uploaded testing assets. Device Farm manages the encryption used for its stored service data.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: AWS KMS protects supported Directory Service data at rest. Directory Service uses KMS-backed encryption to safeguard stored directory information.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: AWS KMS can protect EBS volumes provisioned for Elastic Beanstalk environments. Environment settings can enable volume encryption and select a customer managed key.
- **[AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery)**: AWS KMS protects encrypted replication volumes and recovery instance volumes used by Elastic Disaster Recovery. Replication settings and launch templates can specify customer managed keys.
- **[AWS Entity Resolution](https://blowstack.com/tools/cloud-services-hub/aws-entity-resolution)**: AWS KMS can encrypt Entity Resolution workflow output and supported intermediate data. Workflow configurations can specify a customer managed key for results written to Amazon S3.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: AWS KMS protects Fargate ephemeral storage. Supported ECS cluster configurations let you use a customer managed key for the ephemeral storage of Fargate tasks.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: AWS KMS can protect Fault Injection Service experiment logs delivered to encrypted S3 buckets or CloudWatch Logs groups. The experiment role and key policy must permit access to the encrypted logging destination.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: AWS KMS protects Glue Data Catalog metadata, job bookmarks, connection passwords, and supported job output. Glue security configurations define the keys used for S3 data, logs, and bookmarks.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: AWS KMS can encrypt DataBrew job output written to Amazon S3. Jobs can specify a customer managed key, and their execution roles need permission to use it.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: AWS KMS protects sensitive IAM Identity Center data stored at rest. Encryption safeguards stored identity and configuration information.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: IAM policies work with KMS key policies and grants to authorize key administration and cryptographic operations. Conditions can restrict key use to particular services, encryption contexts, or principals.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: AWS KMS protects sensitive IoT Core data stored at rest. IoT rules that retrieve customer-key-encrypted Secrets Manager secrets also require KMS permissions in their configured role.
- **[AWS IoT Device Defender](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-defender)**: AWS KMS can protect Device Defender notifications delivered through encrypted SNS topics. The key policy must permit the IoT service to publish encrypted audit or security notifications.
- **[AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management)**: AWS KMS can protect IoT Device Management job documents stored in Amazon S3. Roles used to provide access to customer-key-encrypted job documents need permission to decrypt them.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: AWS KMS protects Secrets Manager secrets made available to Greengrass components. The core device's token exchange role needs decryption permission when those secrets use a customer managed key.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: AWS KMS protects IoT SiteWise data at rest. You can configure a customer managed key for supported SiteWise storage encryption.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: AWS KMS protects encrypted S3 data accessed through Lake Formation. Registered data location roles need key permissions so Lake Formation can provide authorized access to encrypted lake data.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS KMS protects Lambda environment variables and supported deployment artifacts and execution state. You can select customer managed keys for supported function encryption settings.
- **[AWS Launch Wizard](https://blowstack.com/tools/cloud-services-hub/aws-launch-wizard)**: AWS KMS can protect encrypted storage provisioned by Launch Wizard deployments. Supported deployment settings let you choose customer managed keys for resources such as EBS volumes.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: AMS can administer KMS keys through managed operational procedures and change requests. This includes supported key creation and configuration changes for encryption used by managed workloads.
- **[AWS Migration Hub](https://blowstack.com/tools/cloud-services-hub/aws-migration-hub)**: AWS KMS protects migration information stored by Migration Hub and its supported migration workflow features. Encryption safeguards stored discovery and migration tracking data.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: AWS KMS encrypts Network Firewall resource data at rest. Supported firewall resources can use a customer managed key through their encryption configuration.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: KMS key policies can use Organizations condition keys to restrict access to principals in an organization or organizational unit. Service control policies can also restrict key administration and cryptographic operations across member accounts.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: AWS KMS protects EBS volumes on Outposts using keys managed in the parent AWS Region. Outposts requires connectivity to the Region for operations that need access to those keys.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: AWS KMS supports PrivateLink interface endpoints for private access to its API. Endpoint policies can restrict the keys and operations available through an endpoint.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: AWS KMS can encrypt application and assessment data stored by Resilience Hub. Application encryption settings can specify a customer managed key.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: Resource Groups and Tag Editor can organize and tag supported KMS key resources. Tags can also participate in IAM policies that control access to KMS keys.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: AWS KMS encrypts the secret values stored by Secrets Manager. Each secret can use an AWS managed key or a customer managed key, with decryption authorized when the secret is retrieved.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub evaluates KMS security controls, including controls for key rotation, deletion, and overly broad decryption permissions. Failed checks become findings that can feed remediation workflows.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: Service Catalog products can provision KMS keys and aliases through their CloudFormation templates. Product constraints and launch roles control who can deploy and manage those encryption resources.
- **[AWS Signer](https://blowstack.com/tools/cloud-services-hub/aws-signer)**: AWS KMS protects sensitive signing data stored by AWS Signer. The service manages encryption for its stored signing assets.
- **[AWS Snow Family](https://blowstack.com/tools/cloud-services-hub/aws-snow-family)**: AWS KMS protects the encryption keys used for Snow Family jobs and devices. Job creation can specify a customer managed key to protect the credentials and key material needed to unlock a device.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: AWS KMS can encrypt Step Functions state machine and activity data with customer managed keys. This protects stored workflow definitions and execution data.
- **[AWS Storage Gateway](https://blowstack.com/tools/cloud-services-hub/aws-storage-gateway)**: AWS KMS can protect data stored by Storage Gateway in AWS, including supported volumes, tapes, and S3 objects. Gateway and storage configurations select the keys used for supported encryption options.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: AWS KMS encrypts Parameter Store SecureString values and can protect Session Manager session data and logs. Systems Manager permissions must allow the relevant users, instances, or services to use the selected keys.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: AWS KMS enables Transfer Family servers and workflows to access SSE-KMS-encrypted S3 objects. User and workflow roles need key permissions to decrypt downloads and encrypt uploads.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: Trusted Advisor includes security checks concerning KMS key configuration. These checks help identify encryption key settings that need attention.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: AWS KMS can encrypt sensitive Verified Access trust provider information. Supported encryption settings let you select a customer managed key.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: AWS KMS can protect WAF logs delivered to an SSE-KMS-encrypted S3 bucket. The key policy must authorize the log delivery service to generate data keys.
- **[AWS Well-Architected Tool](https://blowstack.com/tools/cloud-services-hub/aws-well-architected-tool)**: AWS KMS protects Well-Architected Tool data at rest. The service manages encryption of stored workload and review information.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: AWS KMS encrypts X-Ray trace data stored at rest. You can configure X-Ray to use a customer managed key instead of its default encryption.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: AWS KMS protects encrypted EBS volumes and AMI snapshots created by Image Builder. Image distribution configurations support key permissions needed to copy or share encrypted images.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS KMS can protect Network Load Balancer access logs delivered to Amazon S3. The customer managed key policy must allow the log delivery service to encrypt those logs.
- **[Red Hat OpenShift Service on AWS (ROSA)](https://blowstack.com/tools/cloud-services-hub/red-hat-openshift-service-on-aws-(rosa))**: AWS KMS can protect EBS storage used by ROSA clusters. Supported cluster configurations let you select a customer managed key for encrypted storage.
- **[VMware Cloud on AWS](https://blowstack.com/tools/cloud-services-hub/vmware-cloud-on-aws)**: AWS KMS protects the key material used for vSAN encryption in VMware Cloud on AWS. This safeguards datastore contents at rest.

## AWS Key Management Service (AWS KMS) exam questions

Real practice exam questions on AWS Key Management Service (AWS KMS), with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A media company must retain proprietary model artifacts from its AI content-generation system for five years. An external archive provider will store the artifacts but will not run inference or otherwise process them. Governance policy requires that the provider cannot read the artifacts, even with its storage administrator privileges, while authorized company staff must be able to recover them. Which approach should the governance lead approve?

**Correct answer:** Encrypt the artifacts within the company's environment before transfer, using an established client-side encryption solution backed by a company-controlled AWS KMS key. Withhold decryption permissions from the provider and retain the required key for authorized recovery.

**Explanation:** Encrypting before transfer ensures the archive provider receives only ciphertext. Keeping decryption authority within the company prevents the provider's storage privileges from revealing the contents. Retaining the required key allows authorized staff to recover the artifacts throughout the retention period.

### Question 2 (MLA-C02 (beta))

**Question:**

A company stores Amazon SageMaker AI model artifacts in Amazon S3 using server-side encryption with a customer managed AWS KMS key. During a key replacement, an administrator updates the alias alias/ml-artifacts to reference a new KMS key and schedules the original key for deletion. New artifact uploads succeed, but deploying a model from an artifact uploaded before the replacement fails. The underlying KMS error is KMSInvalidStateException.

The engineer confirms that the deployment execution role has s3:GetObject permission and that the IAM and key policies authorize decryption with both keys. The original key's deletion waiting period has not expired. The company must restore deployment without rewriting the existing artifacts.

Which action should the engineer take?

**Correct answer:** Cancel deletion of the original key, and then enable that key.

**Explanation:** Existing S3 objects remain encrypted under the original key after an alias is redirected. A key pending deletion cannot decrypt data. Canceling deletion places the key in the Disabled state, so the engineer must also enable it to restore access to the existing artifacts.

### Question 3 (SAP-C03)

**Question:**

A healthcare company is replacing ECDSA signatures on short-lived treatment authorization decisions. A central service signs each decision by using AWS KMS, and downstream services verify the signature before acting. The new signatures must provide at least NIST security category 3 protection against quantum attacks. Signing private keys must remain in AWS KMS.

The downstream services already support the required post-quantum verification algorithms. However, an integration gateway imposes two fixed transport options: a Base64-encoded signature in a response header with a maximum value length of 4,096 ASCII bytes, or an unencoded signature in a binary response-body field with a maximum length of 4,096 bytes. These limits apply to the signature alone. Compression, fragmentation, and external signature retrieval are not permitted.

Which implementation meets all the requirements?

**Correct answer:** Create an AWS KMS ML-DSA-65 signing key and return each signature as unencoded bytes in the binary response-body field.

**Explanation:** ML-DSA-65 provides NIST security category 3 protection and produces 3,309-byte signatures. An unencoded signature fits within the 4,096-byte binary field. AWS KMS performs signing without exporting the private key.

### Question 4 (SOA-C03)

**Question:**

A company stores API tokens as AWS Systems Manager Parameter Store SecureString parameters encrypted with the same customer managed AWS KMS key. An operations role has broad read-only Systems Manager permissions and kms:Decrypt permission on the key.

The role must retain access to parameter metadata and other application tokens, but must not retrieve any version of /production/payments/api-token. An existing policy explicitly denies ssm:GetParametersByPath on all resources. A CloudOps engineer also explicitly denies ssm:GetParameter and ssm:GetParameters on the restricted parameter's ARN. Testing shows that the role can still retrieve the restricted token's current plaintext value through another read operation.

Which additional change will prevent this retrieval while preserving the role's required access?

**Correct answer:** Add an explicit Deny for ssm:GetParameterHistory on the restricted parameter's ARN.

**Explanation:** GetParameterHistory can return all versions of a parameter, including its current version. The role's KMS permission allows it to request decrypted values through this operation. Denying GetParameterHistory for the restricted parameter closes this remaining retrieval path while preserving metadata access and access to other tokens. The existing global deny already blocks recursive path retrieval.

### Question 5 (SCS-C03)

**Question:**

A company archives confidential records encrypted directly with the AWS KMS Encrypt API. One archive uses a single-Region symmetric KMS key with AWS-generated material. A second archive uses a single-Region symmetric KMS key with imported material. The company retains a protected external backup of the imported material.

An administrator schedules both KMS keys for deletion, and the waiting periods expire. Both key resources are permanently deleted. The company retains the ciphertext and original alias names but has no other copies of the records.

The recovery team proposes creating replacement KMS keys and recreating the original aliases. Which assessment of the company's ability to recover the records through AWS KMS APIs is correct?

**Correct answer:** Neither archive can be recovered through AWS KMS. A replacement key cannot decrypt ciphertext bound to a permanently deleted KMS key, even if the replacement contains the same imported material.

**Explanation:** Permanent deletion destroys the KMS key resource and prevents AWS KMS from decrypting ciphertext associated with it. AWS-generated symmetric material cannot be exported for customer recovery. An external backup of imported material can restore deleted or expired material to an existing compatible key, but it cannot recreate a permanently deleted KMS key's identity.

### Question 6 (CLF-C02)

**Question:**

A company uses a customer managed symmetric encryption key with AWS-generated key material to protect application data. Company policy requires the key material to rotate automatically every year. The application must continue using the same key identifier. Which solution meets these requirements?

**Correct answer:** Enable automatic key rotation with a one-year rotation period for the existing key in AWS KMS.

**Explanation:** AWS KMS supports automatic rotation for customer managed symmetric encryption keys with AWS-generated key material. Rotation changes the cryptographic material while retaining the key identifier and preserving the ability to decrypt data encrypted with earlier key material.

### Question 7 (DEA-C01)

**Question:**

A data platform stores encrypted data keys alongside application-encrypted datasets. A migration job must use the AWS KMS ReEncrypt API to move the existing encrypted data keys from a legacy customer managed symmetric KMS key to a replacement customer managed symmetric KMS key in the same account and Region.

The job must not receive plaintext data keys, encrypt new data keys, or re-encrypt data keys in the reverse direction. Both KMS key policies enable the account to delegate permissions through IAM policies. The job's IAM role currently has no KMS permissions, and no other policies or grants authorize its use of either key.

Which custom IAM policy configuration meets these requirements with the least privilege?

**Correct answer:** Allow kms:ReEncryptFrom on the legacy key ARN, and allow kms:ReEncryptTo on the replacement key ARN.

**Explanation:** KMS checks ReEncryptFrom permission on the source key and ReEncryptTo permission on the destination key. These narrowly scoped permissions allow only the required migration direction. KMS performs the re-encryption internally without returning plaintext to the job, and neither permission authorizes standalone Encrypt or Decrypt calls.

### Question 8 (DOP-C02)

**Question:**

A company replicates new objects from an Amazon S3 bucket in a production account in us-east-1 to a compliance account in us-west-2. Replication works for objects encrypted with SSE-S3. Applications have started uploading objects encrypted with a customer managed AWS KMS key in us-east-1, but these objects are not being replicated.

The company requires all future SSE-KMS objects to be replicated and the replicas to be encrypted with a designated customer managed KMS key in us-west-2. The destination bucket currently uses SSE-S3 default encryption. S3 Bucket Keys are disabled on both buckets. The replication role has all required S3 permissions but no KMS permissions. Both KMS key policies currently authorize only security administrators. The replication configuration does not include settings for SSE-KMS objects.

Which change should a DevOps engineer automate to meet these requirements?

**Correct answer:** Enable SseKmsEncryptedObjects in the replication rule's source selection criteria and set ReplicaKmsKeyID to the designated us-west-2 key ARN. Grant the replication role kms:Decrypt on the source key and kms:Encrypt on the destination key in its IAM policy, and update both key policies to authorize that role for the corresponding operations.

**Explanation:** SSE-KMS replication requires explicit selection of SSE-KMS source objects and a replica encryption key in the destination Region. S3 assumes the replication role, which needs authorization to decrypt with the source key and encrypt with the destination key. The destination account's key policy must also authorize the cross-account role. Destination bucket default encryption does not override the replica key specified in the replication rule.

### Question 9 (DVA-C02)

**Question:**

A developer is reviewing two designs for an on-premises application that stores confidential files in Amazon S3. Design 1 uploads files over HTTPS using server-side encryption with customer-provided keys (SSE-C); the company generates and retains those keys in its on-premises vault. Design 2 uses the AWS Encryption SDK to encrypt files on premises before uploading them, with a customer managed symmetric AWS KMS key whose key material is generated by AWS KMS. The security team wants to distinguish customer control of keys from actual custody of key material. Which finding should the developer document?

**Correct answer:** Design 1 sends the supplied encryption key to S3 for server-side operations. Design 2 encrypts files locally, but AWS KMS still holds the KMS key material used to protect the data keys.

**Explanation:** SSE-C requires the client to provide the encryption key to S3 over HTTPS. S3 uses the key but does not persist it. In Design 2, file encryption occurs on premises, yet the AWS-generated wrapping key remains protected within AWS KMS. Client-side encryption therefore does not, by itself, mean that all key material remains outside AWS.

### Question 10 (ANS-C01)

**Question:**

A company hosts example.com in a Route 53 public hosted zone managed by its security account. The zone is DNSSEC-signed and has a working chain of trust from the DNS root. The security team has delegated payments.example.com to a separate Route 53 public hosted zone in an application account. All application workloads run in eu-west-1. The company requires external DNSSEC-validating resolvers to authenticate answers for payments.example.com through the existing chain of trust. The security team will make any necessary changes to the parent zone. Which implementation meets these requirements?

**Correct answer:** Create a customer managed asymmetric ECC_NIST_P256 KMS key with SIGN_VERIFY usage in us-east-1. Use it to create the child zone's key-signing key, enable DNSSEC signing, and publish the corresponding DS record in the example.com hosted zone.

**Explanation:** Route 53 requires a customer managed asymmetric ECC_NIST_P256 KMS key with SIGN_VERIFY usage in us-east-1 for its key-signing key. Signing the child zone and publishing its DS record in the signed parent zone connects the child to the existing chain of trust, allowing external validating resolvers to authenticate its answers.

### Question 11 (SAA-C03)

**Question:**

A company operates an application in two AWS Regions. Each deployment must decrypt records locally without depending on the availability of the other Region. The records are encrypted with a symmetric multi-Region AWS KMS key that has a primary key in one Region and a replica key in the other Region.

Both deployments use the same IAM role. The role's IAM policy allows kms:Decrypt on both key ARNs. Decryption succeeds with the primary key but fails with an access denied error when the application explicitly specifies the replica key ARN. The primary key policy enables the account to delegate key-use permissions through IAM policies. The replica key policy allows only a security administrator role to administer the key and does not enable IAM delegation. Both keys are enabled, and no KMS grants or explicit denies apply.

Which change will allow both deployments to meet the requirements with least privilege?

**Correct answer:** Add a statement to the replica key policy that allows the application role to perform kms:Decrypt on that key.

**Explanation:** Related multi-Region KMS keys share key material but have independently managed key policies. Explicitly authorizing the application role to decrypt with the replica resolves the missing permission while preserving local operation and limiting access to the required action and key.

## Practice AWS Key Management Service (AWS KMS) in a full exam

Questions on AWS Key Management Service (AWS KMS) in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 38 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 36 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 29 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 25 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 20 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 19 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 17 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 11 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 7 questions
- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 6 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 4 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 3 questions

## What is AWS Key Management Service (AWS KMS)

AWS Key Management Service (AWS KMS) is a managed service provided by Amazon Web Services that enables clients to create and control cryptographic keys that secure data. These keys can be used to encrypt data stored in various AWS services and ensure that access to this data is tightly controlled and logged, enhancing the overall security posture of an organization's cloud infrastructure.

AWS KMS is designed to be both secure and highly available, utilizing multiple physical locations for redundancy, and is seamlessly integrated with other AWS services, making it a versatile component in the AWS ecosystem for managing data encryption. AWS KMS offers a range of features aimed at simplifying the process of key management while providing robust security controls.

AWS KMS applies resource quotas and request quotas independently for each account and Region. Quotas are adjustable except for the on-demand rotation resource quota and the AWS CloudHSM key store request quota.

AWS KMS supports three types of KMS keys: customer managed keys, AWS managed keys, and AWS owned keys.

Customer-managed KMS keys give users full authority over the key lifecycle, policies, and usage, whereas AWS-managed KMS keys are created, managed, and used on the customer's behalf by AWS services.

By default, KMS keys are stored and usable only in their creation Region. Multi-Region KMS keys can be used interchangeably across Regions, but creating them moves key material across Region boundaries within AWS KMS, which can affect data residency and sovereignty requirements.

The customer managed key quota is 100,000 keys per account per Region, counting keys regardless of key specification or state. AWS managed and AWS owned keys do not count against this quota.

AWS KMS also supports digital signing with asymmetric key pairs.

Security in AWS KMS is multi-faceted, incorporating hardware security modules (HSMs) underpinning the service to securely generate, store, and manage cryptographic keys. The service complies with various compliance programs to ensure that data protection meets the rigorous standards required for sensitive and regulated data.

AWS KMS keys created in AWS KMS are protected by FIPS 140-3 Security Level 3 validated hardware security modules.

All requests to AWS KMS must use TLS, and AWS KMS hosts accept only TLS cipher suites that provide perfect forward secrecy.

For symmetric keys, AWS KMS also supports custom key stores under your control, backed by AWS CloudHSM or your own external key manager outside AWS.

AWS CloudTrail logs requests against customer managed and AWS managed KMS keys. Customers do not have visibility into AWS owned key usage in CloudTrail.

Moreover, AWS KMS facilitates the encryption process by integrating with other AWS services. This integration allows data encrypted in one service, such as Amazon S3 for storage, to be seamlessly decrypted by another service authorized to use the same key, such as Amazon EC2 for computing, without complex key management and exchange protocols. This not only simplifies operational models but also enhances security by ensuring that encrypted data can remain protected throughout its lifecycle within the AWS ecosystem.

AWS KMS also includes features for controlling access to cryptographic keys. Fine-grained policies can be applied to customer managed KMS keys, allowing organizations to specify who can use these keys and under what conditions. This is complemented by the capability to temporally disable keys or schedule their deletion, providing further mechanisms to enforce data protection policies and regulatory compliance.

In summary, AWS Key Management Service offers a comprehensive, integrated solution for managing cryptographic keys within the AWS cloud environment. Its focus on security, compliance, and integration makes it a critical tool for organizations of all sizes as they navigate the complexities of data encryption and protection in the cloud. By simplifying key management and enforcing strict security controls, AWS KMS plays a pivotal role in modern cloud security strategies, enabling businesses to protect sensitive information and meet their compliance obligations with confidence.

## Learn AWS Key Management Service (AWS KMS) in lessons

20 short lessons on AWS Key Management Service (AWS KMS) in 10 certification courses.

- AIB-C01 (beta): AWS KMS: protecting data with controlled encryption keys (Premium), https://app.blowstack.com/lessons/aws-kms-protecting-data-with-controlled-encryption-keys-aib-c01
- MLA-C02 (beta): AWS KMS: Key policies and grants (Premium), https://app.blowstack.com/lessons/aws-kms-key-policies-and-grants-mla-c02
- SAP-C03: AWS CloudHSM vs AWS KMS: dedicated HSMs or managed key services (Premium), https://app.blowstack.com/lessons/aws-cloudhsm-vs-aws-kms-dedicated-hsms-or-managed-key-services-sap-c03
- AIF-C01: AWS KMS: managed encryption keys (Premium), https://app.blowstack.com/lessons/aws-kms-managed-encryption-keys-aif-c01
- SOA-C03: AWS KMS: service-integrated encryption at rest (Premium), https://app.blowstack.com/lessons/aws-kms-service-integrated-encryption-at-rest-soa-c03
- SCS-C03: AWS CloudHSM vs AWS KMS: choosing key custody (Premium), https://app.blowstack.com/lessons/aws-cloudhsm-vs-aws-kms-choosing-key-custody-scs-c03
