# Encryption

Encryption is the process of transforming readable data into ciphertext using a cryptographic algorithm and a key to protect its confidentiality.

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

> Encryption helps prevent unauthorized parties from understanding data stored in cloud systems or transmitted over networks. Its effectiveness depends on protecting cryptographic keys, controlling decryption permissions, and applying encryption wherever sensitive data travels or persists.

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

Effective encryption combines appropriate cryptography, coverage of stored and transmitted data, secure key management, and complementary security controls.

1. **Confidentiality through cryptography**: Encryption makes data unreadable without the appropriate key. It reduces the impact of exposed storage or intercepted traffic, but it does not stop an authorized application from disclosing decrypted data.
2. **Protection at rest and in transit**: Stored data and network traffic require separate protections. Encrypt databases, volumes, objects, and backups while also configuring TLS for each relevant network connection.
3. **Key management and access control**: Protect key administration and decryption permissions with least privilege and audit their use. Include key retention and availability in recovery planning because encrypted backups are unusable without their required keys.
4. **Envelope encryption**: A data key encrypts the payload, while another key protects the data key. This pattern supports efficient bulk encryption and centralized control over key usage.
5. **Encryption boundaries**: Server-side encryption protects data within the service's storage workflow, while client-side encryption protects data before upload. Identify where plaintext exists and where TLS connections terminate rather than assuming protection is end to end.
6. **Defense in depth and shared responsibility**: Combine encryption with identity controls, monitoring, secure application design, and recoverable backups. Managed cloud encryption reduces implementation work but does not automatically satisfy every compliance requirement.

## Cloud services for Encryption

AWS KMS supplies key management for encryption integrations in Amazon S3, Amazon EBS, and Amazon RDS. These storage services apply encryption within their own data paths, while key permissions determine whether authorized workloads can use KMS-protected data. AWS Certificate Manager supplies certificates for supported Elastic Load Balancing configurations to protect incoming connections with TLS. Engineers must separately evaluate load-balancer-to-application and application-to-database connections. Together, these services provide building blocks for protecting stored and transmitted data, but teams still need least-privilege permissions, monitoring, appropriate configuration, and tested recovery procedures.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 automatically applies server-side encryption with Amazon S3 managed keys to new object uploads by default. Teams can select other supported encryption options, including AWS KMS keys, and require HTTPS through bucket policy controls.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon RDS supports encryption at rest using AWS KMS keys, covering encrypted database storage and associated backups and snapshots. Database connections require separate TLS configuration, with enforcement options depending on the database engine.

## Encryption exam questions

Real practice exam questions on Encryption, 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 (SAA-C03)

**Question:**

A healthcare company runs an application on Amazon EC2 that produces 100 MB diagnostic files. The application uploads the files to a third-party archival service over HTTPS. A new security requirement states that each file must be encrypted before it leaves the EC2 instance and that the archival provider must never receive the ability to decrypt it. The company wants centralized control over decryption permissions without operating its own key management infrastructure. Plaintext encryption keys must not be persisted. Which solution meets these requirements?

**Correct answer:** Use AWS KMS GenerateDataKey to obtain a plaintext data key and an encrypted copy. Encrypt each file locally with an established encryption library, remove the plaintext key from memory after use, and upload the encrypted file and encrypted data key.

**Explanation:** This approach uses envelope encryption. The file is encrypted before upload, and only the encrypted data key is stored with it. Authorized applications can recover the data key through KMS, while the archival provider cannot decrypt the file without permission to use the protecting KMS key.

### Question 3 (SAP-C03)

**Question:**

An insurance company operates a centralized Amazon S3 ingestion bucket in a security account. Applications in several workload accounts upload claim documents by using IAM roles. The applications do not specify encryption headers, and the company cannot change the upload code. The bucket currently uses its original default encryption configuration.

Starting at a scheduled cutover, compliance requires newly uploaded documents to be encrypted with a key whose policy and enabled state the security team controls. The security team must be able to suspend decryption by disabling that key without changing S3 access policies. Existing documents are outside the scope of this change. Uploads must continue to succeed without encryption headers, including multipart uploads. Appropriate cross-account S3 permissions are already configured, and separate governance controls prevent changes to the approved encryption configuration or explicit encryption overrides.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Configure the bucket's default encryption to use SSE-KMS with the full ARN of a customer managed KMS key in the bucket's Region. Configure the key policy and application-role policies to permit the required cross-account kms:GenerateDataKey and kms:Decrypt operations.

**Explanation:** SSE-KMS bucket default encryption applies to new uploads that omit encryption headers, so application changes are unnecessary. A customer managed key allows the security team to control its policy and disable it to suspend decryption. Cross-account writers need authorization in both the key policy and their identity policies; multipart uploads require both kms:GenerateDataKey and kms:Decrypt. Changing the default does not re-encrypt existing objects, which are explicitly out of scope.

### Question 4 (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 5 (CLF-C02)

**Question:**

A company encrypts its customer records at rest and uses HTTPS when transmitting them. To reduce costs, a manager proposes removing the company's backups because the records are already protected by encryption. The company must be able to recover records that employees accidentally delete. Which assessment should guide the company's decision?

**Correct answer:** Backups should be retained because encryption protects the confidentiality of records but does not recover deleted records.

**Explanation:** Encryption helps prevent unauthorized parties from understanding data. Recoverable backups address a different security need: restoring data after deletion or loss.

## Practice Encryption in a full exam

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

- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 6 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 5 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 4 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 1 question
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 1 question

## What is Encryption

Encryption converts readable plaintext into ciphertext that can be recovered through decryption with the appropriate key. Its primary security benefit is confidentiality: someone who obtains an encrypted disk, backup, or network transmission should not be able to understand its contents without the necessary key. In cloud environments, managed encryption capabilities reduce the work required to protect data, but customers must still configure access controls and select protections appropriate to their workloads.

Encryption at rest protects stored data, including objects, database files, virtual machine volumes, snapshots, and backups. For example, an engineering team can encrypt a database and its backups so that access to underlying storage alone does not expose customer records. Encryption in transit protects data moving between systems, commonly through Transport Layer Security, or TLS. A web application should use HTTPS for browser traffic and separately protect connections between its application servers and database. Encrypting storage does not automatically encrypt these network connections.

Symmetric encryption uses the same secret key for encryption and decryption and is commonly used for large amounts of data. Asymmetric cryptography uses a mathematically related public and private key pair and supports functions such as secure key establishment and digital signatures. Engineers should use established protocols and supported cryptographic libraries rather than design their own encryption schemes.

Cloud services commonly use envelope encryption: a data key encrypts the data, and another key protects that data key. This allows services to handle large datasets efficiently while centralizing control over the keys that protect data keys. Key management includes controlling usage permissions, auditing operations, planning rotation, and ensuring that keys remain available for authorized recovery. Losing or deleting a required key can make otherwise healthy data unrecoverable. Rotating a key does not necessarily re-encrypt existing data.

Server-side encryption means the service encrypts data after receiving it and decrypts it for authorized requests. Client-side encryption means an application encrypts data before sending it to the service. Client-side encryption can limit the provider's access to plaintext, but it increases application complexity and can restrict server-side searching or processing. An authorized user may still receive plaintext from a server-side encrypted resource, so encryption does not replace identity policies or least-privilege access.

Encryption has operational trade-offs. Cryptographic processing, key-service requests, and key storage can introduce costs or latency. Key-service availability and permissions can affect application availability, so teams should test restore procedures and investigate decryption failures alongside ordinary access failures. Managed services simplify implementation, but defaults, key ownership options, and coverage differ between services.

For certification questions, distinguish confidentiality from other security goals. Encryption alone does not guarantee integrity, availability, regulatory compliance, or protection against an application that legitimately decrypts data and then exposes it. Authenticated encryption and correctly configured TLS add integrity protections, while backups and resilient architectures address availability. Hashing is not reversible encryption, and encoding such as Base64 provides no confidentiality. Under the shared responsibility model, AWS protects its underlying infrastructure while customers remain responsible for their data, permissions, and applicable encryption configuration.

## Learn Encryption in lessons

8 short lessons on Encryption in 6 certification courses.

- AIB-C01 (beta): Encryption: protecting data at rest and in transit (Premium), https://app.blowstack.com/lessons/encryption-protecting-data-at-rest-and-in-transit-aib-c01
- SAA-C03: Encryption: confidentiality boundaries (Premium), https://app.blowstack.com/lessons/encryption-confidentiality-boundaries-saa-c03
- SAP-C03: Encryption: server-side encryption boundaries (Premium), https://app.blowstack.com/lessons/encryption-server-side-encryption-boundaries-sap-c03
- AIF-C01: Encryption: protecting cloud data (Premium), https://app.blowstack.com/lessons/encryption-protecting-cloud-data-aif-c01
- DOP-C02: Digital Signatures vs Encryption: authenticity and confidentiality (Premium), https://app.blowstack.com/lessons/digital-signatures-vs-encryption-authenticity-and-confidentiality-dop-c02
- CLF-C02: Encryption: protecting data confidentiality (Premium), https://app.blowstack.com/lessons/encryption-protecting-data-confidentiality-clf-c02
