Encryption at rest and in transit
Encryption protects data in two states. Data at rest sits in storage; data in transit moves between systems. AWS services offer encryption for both, and the customer decides how to use it. Data at rest · Data in transit
How it works
- At rest: storage services encrypt data with keys. AWS KMS creates and controls those keys and integrates with services such as Amazon S3, Amazon EBS and Amazon RDS.
- In transit: TLS encrypts connections. AWS Certificate Manager issues and renews the TLS certificates.
- Private paths: AWS PrivateLink keeps traffic on the Amazon network instead of the internet.
| State | Protects | AWS tools |
|---|---|---|
| At rest | Data in storage | AWS KMS keys, server-side encryption in S3, EBS, RDS |
| In transit | Data moving between systems | TLS with ACM certificates, AWS PrivateLink, VPN |
Exam cues
- If the question says manage the keys that encrypt stored data, think AWS KMS.
- If the question says HTTPS certificates, think ACM.
- If the question says protect data moving over the network, think encryption in transit (TLS).
- If the question says encrypt an existing unencrypted RDS instance, think snapshot copy with encryption and restore, because RDS encryption is set at creation.
Remember
- KMS keys never leave AWS KMS unencrypted.
- RDS encryption is set at creation; encrypt a snapshot copy and restore it to encrypt an existing unencrypted instance.
Trap: TLS certificates protect data in transit, not at rest. For stored data, the answer is server-side encryption with AWS KMS keys.
Da documentação da AWS (8)
- Data at rest is data persisted in non-volatile storage, such as block storage, object storage, databases and archives; encryption and access controls reduce the risk of unauthorized access to it.
- Data in transit is data sent from one system to another, inside a workload or between services and end users; protecting it preserves confidentiality and integrity.
- Encryption transforms content so it is unreadable without the secret key needed to decrypt it back to plaintext.
- AWS Key Management Service (AWS KMS) creates and controls the keys used to encrypt and sign data; KMS keys are protected by FIPS 140-3 Security Level 3 validated HSMs and never leave AWS KMS unencrypted.
- AWS KMS integrates with other AWS services to encrypt data at rest or in transit; common uses are encrypting Amazon EBS volumes, Amazon S3 buckets and Amazon RDS databases.
- AWS Certificate Manager (ACM) creates, stores and renews public and private SSL/TLS certificates that protect AWS websites and applications.
- AWS PrivateLink keeps traffic between a VPC or on-premises network and services on the Amazon backbone, so it does not traverse the internet.
- An Amazon RDS DB instance can be encrypted only when it is created; to encrypt an existing one, copy an unencrypted snapshot with encryption and restore it.
Encryption defaults and key ownership
AWS services offer encryption defaults and settings for stored data. Knowing which service applies a default and who controls a key helps you choose the right setting. S3 defaults · KMS keys
How it works
- Amazon S3 automatically encrypts new object uploads with server-side encryption using S3 managed keys (SSE-S3). CloudTrail log files delivered to S3 use SSE-S3 by default, or server-side encryption with a KMS key (SSE-KMS) when you choose a key. S3 · CloudTrail
- AWS Storage Gateway uses TLS for data in transit and SSE-S3 by default for data it stores in S3. New Amazon Redshift provisioned clustersA group of CloudHSM devices managed together as the backing key store. are encrypted by default, except that the change does not affect clusters restored from snapshots. Storage Gateway · Redshift
- Choose encryption at rest when creating an Amazon EFS file system. You cannot add it to an unencrypted file system later.
- Choose a KMS key type by who controls it. You create and control customer managed keys; an AWS service creates AWS managed keys in your account and owns AWS owned keys.
Exam cues
- If the question says new S3 uploads without an encryption setting, think SSE-S3, because S3 encrypts new uploads automatically.
- If the question says full control of a KMS key, think customer managed key, because you create and control it.
- If the question says add encryption to an existing unencrypted EFS file system, think creation time, because its encryption setting cannot be added later.
Remember
- Since January 5, 2023, S3 encrypts new uploads with SSE-S3 using AES-256, at no extra cost or performance impact.
- Since January 10, 2025, new Redshift provisioned clusters are encrypted by default; the change does not affect clusters restored from snapshots.
- AWS managed keys are a legacy type; AWS owned keys are used by services for encryption by default.
Trap: Encryption defaults differ by service. EFS encryption at rest is set at creation, while S3 automatically encrypts new uploads.
Da documentação da AWS (6)
- Since January 5, 2023, Amazon S3 automatically encrypts all new object uploads with SSE-S3 (AES-256) at no additional cost and with no performance impact.
- CloudTrail log files delivered to S3 are encrypted by default with SSE-S3, or with SSE-KMS if you choose a KMS key.
- AWS Storage Gateway encrypts data in transit with TLS and, by default, encrypts the data it stores in Amazon S3 with SSE-S3.
- Amazon EFS encryption at rest is set when the file system is created and can't be added to an unencrypted file system later.
- Since January 10, 2025, new Amazon Redshift provisioned clusters are encrypted by default; clusters restored from snapshots are not affected.
- KMS keys are customer managed keys (you create and control them), AWS managed keys (created in your account by a service, a legacy type) and AWS owned keys (owned by a service, used for encryption by default).
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 9 flashcards em lista
What is the difference between encryption at rest and encryption in transit on AWS?
- At rest: protects stored data, such as in Amazon S3, Amazon EBS or a database
- In transit: protects data moving between systems, usually with TLS
Which AWS service creates and controls the keys used to encrypt data in services such as Amazon S3, Amazon EBS and Amazon RDS?
AWS Key Management Service (AWS KMS). Its keys stay inside FIPS 140-3 validated HSMs and never leave unencrypted.
A website on AWS needs a TLS certificate for HTTPS that renews automatically. Which AWS service provides it?
AWS Certificate Manager (ACM). It creates, stores and renews SSL/TLS certificates, which encrypt data in transit.
Why is encrypting data stored on AWS one of the benefits of cloud security?
Encrypted data is unreadable without the key, so a stolen copy of storage is useless; AWS services make encryption a setting, managed with AWS KMS.
Which AWS service creates and controls encryption keys that can protect an Amazon RDS database?
AWS Key Management Service (AWS KMS) creates and controls keys and integrates with Amazon RDS encryption.
A company uploads new objects to Amazon S3 without configuring encryption. Are they stored unencrypted?
No. Since January 5, 2023, S3 encrypts all new uploads with SSE-S3 (AES-256) automatically, at no extra cost.
Which of these encrypt data by default with no setting to change: CloudTrail log files, Storage Gateway data in S3, a new Amazon EFS file system created through the API?
CloudTrail log files (SSE-S3) and Storage Gateway data (SSE-S3, plus TLS in transit). EFS encryption at rest is a setting chosen when the file system is created.
Are new Amazon Redshift provisioned clusters encrypted by default?
Yes, since January 10, 2025, unless they are restored from a snapshot.
Which three kinds of KMS keys exist, and which one does a customer fully control?
Customer managed keys (full control), AWS managed keys (created by a service in your account) and AWS owned keys (owned by the service).