Cloud concept · Updated

Encryption in Transit - Encryption in transit protects data with cryptography while it moves between systems, applications, or networks.

In short

Encryption in transit prevents observers on a network path from reading protected data and, with correctly configured secure protocols, helps detect tampering and authenticate communicating endpoints. In cloud architectures, it applies to internet traffic, internal service communication, and hybrid or multi-cloud connections, independently of encryption at rest.

Cloud Concepts Hub →

6 key aspects of Encryption in Transit

Effective encryption in transit requires secure protocols, authenticated peers, explicit protection boundaries, and ongoing operational validation.

01
Confidentiality, integrity, and authentication

Use secure protocols that protect payload confidentiality and detect modification, together with appropriate peer authentication. Encryption without validating the intended peer can leave traffic vulnerable to interception.

02
Explicit protection boundaries

Document where each TLS session, VPN tunnel, or encrypted link begins and ends. Re-encrypt subsequent segments when required, and recognize that termination points can access plaintext.

03
Private connectivity is not encryption

Dedicated circuits and private network paths reduce exposure but do not inherently encrypt application traffic. Treat connectivity, encryption, and access control as separate design decisions.

04
Application, network, and link protection

TLS protects application connections, IPsec protects traffic between tunnel endpoints, and MACsec protects supported Layer 2 links. Select the mechanism according to the required boundary rather than treating these technologies as interchangeable.

05
Certificate and protocol lifecycle

Track certificate expiration, automate renewal where supported, and maintain appropriate trust stores and TLS policies. Test certificate deployment and hostname validation rather than assuming certificate issuance completes the configuration.

06
Independent protection for stored data

Encryption at rest does not protect data crossing a network, and transport encryption does not protect stored copies. Configure and verify both controls where the workload requires them.

Cloud services for Encryption in Transit

AWS Site-to-Site VPN encrypts network traffic between gateway endpoints, while AWS Client VPN protects remote-client connections. Direct Connect supplies dedicated connectivity, with MACsec available on supported connections, but broader protection can still require IPsec or application TLS. Elastic Load Balancing provides application-facing TLS termination or passthrough options, and AWS Certificate Manager manages certificates for supported integrations. Amazon S3 supports HTTPS and policy-based enforcement of secure transport. Together, these services address different segments of a data path; engineers must verify that no required segment becomes unencrypted after a gateway or proxy terminates a connection.

AWS Site-to-Site VPNAWS Site-to-Site VPN

Uses IPsec tunnels to encrypt traffic between an on-premises or other supported customer gateway and AWS. It can also participate in supported VPN-over-Direct-Connect designs when dedicated connectivity requires network-layer encryption.

AWS Direct ConnectAWS Direct Connect

Provides dedicated network connectivity to AWS without encryption by default. Supported connections offer MACsec for the customer-router-to-Direct-Connect-device link; application TLS or an appropriate IPsec overlay can protect broader paths.

AWS Client VPNAWS Client VPN

Provides TLS-based VPN connectivity for remote clients accessing AWS and connected networks. Its encrypted tunnel ends at the VPN service, so application-level encryption may still be needed for traffic beyond that boundary.

Amazon S3Amazon S3

Supports HTTPS for encrypted object transfers. Bucket policies can deny requests that do not use secure transport through the aws:SecureTransport condition, with appropriate handling of AWS service principals where needed; server-side object encryption is a separate at-rest control.

Encryption in Transit exam questions

Real practice exam questions on Encryption in Transit, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIF-C01

A company runs an AI application and a self-hosted model inference server on separate Amazon EC2 instances in private subnets. The application currently sends confidential prompts to the inference server over HTTP. A security review requires that network observers cannot read or alter the prompts without detection and that the application verifies it is communicating with the intended inference server. Which change meets these requirements?

Show answerCORRECT ANSWER

Configure HTTPS using TLS 1.2 or later and require the application to validate the server certificate's trust chain, expiration, and hostname.

TLS protects prompts against network eavesdropping and undetected modification. Validating the server certificate also helps confirm that the application is connecting to the intended inference server.

SOA-C03

A company exposes an upload API through Amazon CloudFront with a custom HTTPS origin. The distribution currently accepts both HTTP and HTTPS viewer requests. An audit finds that some clients submit uploads over HTTP even though the API documentation specifies HTTPS.

A new requirement states that CloudFront must reject HTTP viewer requests without redirecting them or forwarding them to the origin. HTTPS requests must continue to work. The origin connection is already configured to use HTTPS only.

Which change should a CloudOps engineer make?

Show answerCORRECT ANSWER

Set the Viewer Protocol Policy to HTTPS Only for every cache behavior that serves the API.

HTTPS Only causes CloudFront to reject HTTP viewer requests with HTTP 403 rather than redirecting or forwarding them to the origin. HTTPS viewer requests remain supported, and the existing origin policy protects the separate origin connection.

SCS-C03

A financial company replicates transaction records from an on-premises application to an application running on Amazon EC2. Traffic uses a dedicated AWS Direct Connect connection with MACsec enabled between the company's edge router and the Direct Connect device. The replication protocol currently sends records in plaintext.

An audit requires cryptographic protection continuously from the on-premises application process to the EC2 application process. Network devices and intermediate services must not have access to plaintext records. The company can change application connection settings but must retain the existing network path.

Which change meets these requirements?

Show answerCORRECT ANSWER

Configure the replication client to use TLS directly to the EC2 application, validate the server certificate's trust chain and hostname, and require encrypted connections on the application listener.

TLS established directly between the replication client and the EC2 application protects records across the entire required path without exposing plaintext to intermediate network devices or services. Certificate validation authenticates the intended server, and requiring encrypted connections prevents plaintext fallback.

Practice Encryption in Transit in a full exam

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

Start a free practice exam

What is Encryption in Transit

3 min read

Encryption in transit protects data while it travels between endpoints, such as a browser and an application, an application and a database, or an on-premises network and a cloud network. Secure protocols combine encryption with integrity protection and endpoint authentication to defend against interception and modification. This differs from encryption at rest, which protects stored data on disks, databases, and object storage. A workload commonly needs both: encrypting a database volume does not encrypt a client's database connection.

Transport Layer Security, or TLS, is widely used to protect application traffic. HTTPS is HTTP carried over TLS; database clients and other application protocols can also use TLS. Clients should validate the server certificate's trust chain, expiration, and hostname rather than merely establish an encrypted session. Mutual TLS additionally authenticates the client using a certificate. Use supported modern protocol versions, normally TLS 1.2 or TLS 1.3, with security policies appropriate to the workload.

The protection boundary depends on where encryption starts and terminates. For example, an HTTPS connection from a browser to a load balancer protects that segment only. If the load balancer forwards requests to application servers using HTTP, the backend segment is unencrypted. Configuring HTTPS to the targets creates a separate encrypted connection; it does not automatically provide the same certificate-validation behavior as a browser. Check the specific proxy or load balancer's backend authentication capabilities. A TLS-terminating intermediary can access plaintext, so this architecture is not equivalent to encryption that remains intact between the original client and final application.

Hybrid connectivity requires separating private connectivity from cryptographic protection. AWS Site-to-Site VPN uses IPsec to encrypt traffic between a customer gateway device and an AWS VPN endpoint, commonly across the internet. AWS Direct Connect provides dedicated connectivity but does not encrypt traffic by default. When confidentiality is required, use application TLS, an appropriate IPsec VPN design over Direct Connect, or MACsec where supported. These mechanisms protect different portions of the path and can be combined.

MACsec provides Layer 2 encryption on supported Direct Connect connections between the customer router and the Direct Connect device. It is not end-to-end encryption from an on-premises application to a cloud workload, and availability depends on connection capabilities and location. For hybrid or multi-cloud designs, identify every provider, carrier, gateway, and termination point rather than assuming that one encrypted link protects the entire route. VPN gateways decrypt tunnel traffic before forwarding it, so application TLS can remain valuable beyond the tunnel boundary.

Operational trade-offs include cryptographic processing, handshake latency, certificate lifecycle management, and reduced visibility for network inspection. VPN encapsulation can also reduce the effective maximum transmission unit, causing fragmentation or stalled transfers if path MTU discovery is blocked. Troubleshooting should distinguish certificate or protocol negotiation failures from routing, firewall, DNS, and tunnel problems. Test the intended hostname and inspect negotiated protocols, certificate chains, and actual backend connection settings.

Private subnets, security groups, private endpoints, and dedicated circuits constrain connectivity but do not themselves guarantee encryption. Likewise, an encrypted connection does not authorize the caller or protect plaintext at a compromised endpoint. Under the shared responsibility model, cloud providers offer secure protocols and managed capabilities, while customers remain responsible for selecting suitable configurations, enforcing secure access, and validating every required traffic segment.

Learn Encryption in Transit in lessons

12 short lessons on Encryption in Transit in 7 certification courses.

and 6 more lessons

Open the lessons