# Encryption at Rest

Encryption at rest protects stored data by converting it into ciphertext that requires the appropriate cryptographic keys to read.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/encryption-at-rest

> Encryption at rest protects data stored in objects, disks, databases, snapshots, and backups from disclosure when the underlying storage is accessed without the required keys. In cloud environments, it combines storage encryption with key management and access controls, but it does not replace authorization, backups, or encryption in transit.

Practice exams covering Encryption at Rest: [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), [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), [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).

## 6 key aspects of Encryption at Rest

Effective encryption at rest combines appropriate storage coverage, controlled key access, verified configuration, and complementary security measures.

1. **Confidentiality for stored data**: Encryption makes stored content unreadable without the necessary keys. Its protection depends on the encryption boundary and whether an unauthorized party can also obtain decryption access.
2. **Server-side and client-side options**: Server-side encryption lets the storage service handle encryption and authorized decryption. Client-side encryption protects data before upload but requires the application or client tooling to manage encryption workflows and key access.
3. **Controlled key lifecycle**: Key permissions, rotation, disabling, and deletion affect both security and availability. Restrict destructive key operations and verify that recovery environments can use the keys required by their backups.
4. **Coverage across stored copies**: Assess primary storage, snapshots, backups, replicas, logs, and exports separately. Encryption settings and key requirements may differ when data moves between services, accounts, or Regions.
5. **Complementary security controls**: Use encryption at rest alongside least-privilege authorization, network protection, and auditing. It does not prevent an authorized application from returning plaintext or replace TLS for data in transit.
6. **Service-specific configuration and verification**: Check encryption defaults, selected keys, and existing-resource coverage rather than relying on a single account-level setting. Include encryption requirements in provisioning policies and test both normal access and recovery.

## Cloud services for Encryption at Rest

Amazon S3, Amazon EBS, and Amazon RDS apply encryption to object, block, and database storage respectively. AWS KMS provides key management for supported encryption configurations, separating control of keys from storage administration. A workload might store database records in encrypted RDS storage, application files in encrypted EBS volumes, and exports in encrypted S3 objects. Engineers must coordinate storage permissions and key permissions, preserve key access for restores, and configure TLS separately for network connections. Audit logs and configuration checks help confirm that the intended controls remain in place.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 encrypts all new object uploads at rest by default using server-side encryption with Amazon S3 managed keys. Other options include server-side encryption with AWS KMS keys, while applications can also encrypt content before uploading it.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon RDS supports KMS-based encryption at rest for database storage and associated logs, automated backups, and snapshots. Database connection encryption is a separate configuration, and converting an existing unencrypted database requires a supported migration workflow.

## Encryption at Rest exam questions

Real practice exam questions on Encryption at Rest, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

A company runs a Multi-AZ Amazon RDS for PostgreSQL DB instance with automated backups enabled. The DB instance is encrypted with a customer managed AWS KMS key. An administrator accidentally disabled the key 3 hours ago. The DB instance is now stopped with a status of inaccessible-encryption-credentials-recoverable. The key still exists, and its key policy has not changed.

A CloudOps engineer must restore database availability without losing committed data and with the least operational effort. Which action should the engineer take?

**Correct answer:** Re-enable the original KMS key, wait until the key is enabled, and start the existing DB instance.

**Explanation:** An RDS DB instance in inaccessible-encryption-credentials-recoverable can be recovered by restoring access to its KMS key and then starting the instance. RDS allows recovery in this state for seven days. Because the original key still exists and its permissions are unchanged, re-enabling it and starting the instance restores access without a data migration or snapshot restore.

### Question 2 (SAP-C03)

**Question:**

An insurance company stores 80 million regulated documents in an Amazon S3 general purpose bucket. Versioning has never been enabled. Each object is between 64 MB and 512 MB. All objects use SSE-KMS with a customer managed KMS key. The bucket's default encryption configuration references an alias that points to this key. Applications upload documents without specifying encryption headers.

Following a security review, the company must move all existing documents and future uploads to a different customer managed KMS key. At the end of the migration, the original KMS key must be disabled, and every document must remain readable at its existing bucket name and object key. Application changes are not permitted. Uploads can be paused during migration, and the company has a complete S3 Inventory report. Separate controls prevent unauthorized encryption configuration changes.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Create a new customer managed KMS key and grant the required permissions. Configure bucket default encryption to use its ARN. Run an S3 Batch Operations Copy job that copies every object onto itself with SSE-KMS explicitly using the new key ARN. Verify successful replacement and encryption settings for every object before disabling the original key and resuming uploads.

**Explanation:** Changing default encryption protects future uploads but does not modify existing objects. The Batch Operations Copy job replaces each existing object with a copy encrypted under the new key while retaining its bucket name and object key. Every object is within the operation's size limit. After complete verification, disabling the original key does not affect the replacement objects, and future uploads inherit the new default.

### Question 3 (CLF-C02)

**Question:**

A company stores documents in Amazon S3 using server-side encryption with a customer managed encryption key. An application's IAM role has permission to read the required S3 objects, but requests fail because the role is not authorized to decrypt them. The company must allow the application to read the documents without changing their encryption. Which solution meets this requirement?

**Correct answer:** Grant the application's role permission to decrypt using the customer managed key in AWS KMS.

**Explanation:** Reading objects encrypted with a customer managed KMS key requires both S3 read permission and authorization to use the key for decryption. Allowing the role to decrypt with the relevant key addresses the missing authorization without changing encryption.

### Question 4 (DVA-C02)

**Question:**

An AWS Lambda function uses a customer managed AWS KMS key for server-side encryption of its environment variables. After a security administrator schedules the key for deletion, invocations that require a new execution environment begin failing with a KMS error. The key's waiting period has not expired, and the function's execution role still has the required permissions. A developer must restore the function without replacing the key or rewriting the environment variables. Which solution meets these requirements?

**Correct answer:** Cancel the scheduled key deletion, explicitly enable the original key, and retry the function invocation.

**Explanation:** A key pending deletion cannot perform cryptographic operations. Canceling deletion changes its state to Disabled, so it must then be enabled. Restoring the original key allows Lambda to decrypt the existing environment configuration without rewriting it.

### Question 5 (DOP-C02)

**Question:**

A company archives application logs under the logs/ prefix of an Amazon S3 general purpose bucket. The bucket uses SSE-KMS with a customer managed KMS key. A collector role successfully uploads and reads logs.

The key policy's only cryptographic-use grant permits the collector role to perform kms:GenerateDataKey and kms:Decrypt. The grant requires kms:ViaService to equal s3.us-east-1.amazonaws.com and uses a StringLike condition requiring kms:EncryptionContext:aws:s3:arn to match arn:aws:s3:::company-log-archive/logs/*. The role's IAM policy allows the required KMS operations on this key. Its S3 permissions restrict access to the logs/ prefix.

A DevOps engineer enables S3 Bucket Keys to reduce KMS request costs. New uploads that use an S3 Bucket Key fail with KMS access denied errors. No other policies or permissions have changed.

The engineer must restore uploads while retaining S3 Bucket Keys, SSE-KMS with the existing key, and the collector's restriction to the logs/ prefix. Which change meets these requirements?

**Correct answer:** Change the encryption-context condition to require arn:aws:s3:::company-log-archive, retain the existing kms:ViaService condition, and retain the prefix restrictions in the S3 permissions.

**Explanation:** With S3 Bucket Keys, the KMS encryption context contains the bucket ARN rather than an individual object ARN. Allowing that bucket ARN restores key use through S3. Object-prefix authorization must remain enforced through S3 permissions because the bucket-level KMS encryption context cannot distinguish prefixes.

### Question 6 (SAA-C03)

**Question:**

A company operates a data lake that stores millions of objects in Amazon S3. Ingestion applications and transformation jobs frequently upload and read these objects. All objects must use server-side encryption with a designated customer-managed AWS KMS key. During peak processing, the applications experience throttling. Investigation confirms that requests to AWS KMS, rather than Amazon S3 request rates or network bandwidth, are limiting throughput. The company cannot increase its KMS request quota or use additional KMS keys.

Which solution will reduce the throttling with the least change to the applications while maintaining the encryption requirement?

**Correct answer:** Enable S3 Bucket Keys in the bucket's default SSE-KMS encryption configuration, retaining the designated customer-managed KMS key.

**Explanation:** S3 Bucket Keys allow S3 to use a time-limited bucket-level key to create object data keys, substantially reducing requests to AWS KMS. This reduces pressure on the KMS request quota while preserving SSE-KMS encryption with the designated customer-managed key. Applications that rely on the bucket's default encryption do not need changes.

## Practice Encryption at Rest in a full exam

Questions on Encryption at Rest in each practice exam, with every answer option and an explanation for each:

- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 9 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 8 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 7 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 1 question

## What is Encryption at Rest

Encryption at rest protects data while it is stored rather than traveling across a network or being processed in memory. An encryption algorithm transforms readable plaintext into ciphertext using a cryptographic key. Authorized systems can recover the original data through decryption. Typical targets include object storage, virtual machine disks, database files, snapshots, backups, and application-generated exports.

The main objective is confidentiality: obtaining stored bytes alone should not reveal their contents without access to the necessary keys. This helps reduce exposure from lost storage media, improperly handled backups, or unauthorized access to underlying storage. However, encryption does not automatically prevent access through a legitimate application or cloud API. If an attacker gains permissions that allow a service to retrieve and decrypt data, storage encryption may not stop that access.

Cloud platforms commonly offer server-side encryption, where the storage service encrypts data before persisting it and decrypts it for authorized reads. This is often transparent to applications. Client-side encryption instead encrypts data before uploading it, placing responsibility for encryption and decryption in the application or client tooling. Disk-level, database-level, and application-level encryption protect different boundaries, so engineers should select controls according to the threat model rather than assume every encryption option provides identical protection.

Key management is as important as the encryption algorithm. Managed services often use envelope encryption: a data key encrypts the stored data, and a separate key protects that data key. Access policies, auditing, rotation, and deletion controls govern how keys can be used. Customer-managed keys can provide additional policy and lifecycle control, but they introduce operational responsibilities. Disabling or deleting a required key can make otherwise healthy data unavailable. Rotating a key does not necessarily re-encrypt existing data.

For example, Amazon S3 encrypts all new object uploads at rest by default using server-side encryption. An organization can choose AWS Key Management Service keys when it needs additional control over key permissions and auditing. Amazon EBS supports encrypted volumes and snapshots, while Amazon RDS supports encryption for database storage and associated artifacts such as automated backups. Defaults and migration procedures differ by service, so enabling an account setting or changing a default should not be assumed to encrypt every existing resource retroactively.

Encryption at rest and encryption in transit address different stages of the data lifecycle. Encrypting a stored customer report does not protect its download over an unencrypted connection; TLS is needed for network protection. Likewise, HTTPS does not establish that the destination stores the report encrypted. Neither control by itself protects data while an application is actively processing it.

Under the shared responsibility model, the provider secures the underlying infrastructure, while customers remain responsible for appropriate configuration, permissions, and key choices for their workloads. Practical designs also cover replicas, temporary files, logs, exports, and backup copies. Managed encryption often has low application overhead, but key-service requests, quotas, costs, and recovery dependencies still matter. Test restores and key access before relying on an encrypted backup for recovery.

## Learn Encryption at Rest in lessons

11 short lessons on Encryption at Rest in 6 certification courses.

- AIF-C01: Encryption at Rest: protecting stored data (Premium), https://app.blowstack.com/lessons/encryption-at-rest-protecting-stored-data-aif-c01
- SOA-C03: Encryption at Rest: storage encryption settings (Premium), https://app.blowstack.com/lessons/encryption-at-rest-storage-encryption-settings-soa-c03
- SAP-C03: Encryption at Rest: customer-managed key lifecycle (Premium), https://app.blowstack.com/lessons/encryption-at-rest-customer-managed-key-lifecycle-sap-c03
- CLF-C02: Encryption in Transit vs. Encryption at Rest (Premium), https://app.blowstack.com/lessons/encryption-in-transit-vs-encryption-at-rest-clf-c02
- DOP-C02: Encryption at Rest: protection boundaries for stored telemetry (Premium), https://app.blowstack.com/lessons/encryption-at-rest-protection-boundaries-for-stored-telemetry-dop-c02
- SAA-C03: Encryption at Rest: storage encryption coverage (Premium), https://app.blowstack.com/lessons/encryption-at-rest-storage-encryption-coverage-saa-c03
