Cloud concept · Updated

Mutual TLS - Mutual TLS is a TLS configuration in which both communicating peers authenticate each other with digital certificates while encrypting data in transit.

In short

Ordinary HTTPS typically authenticates only the server, whereas mutual TLS also requires the client to prove its identity using a certificate and its corresponding private key. This helps cloud workloads reject untrusted peers, but it requires certificate lifecycle management and separate authorization policies.

Cloud Concepts Hub →

6 key aspects of Mutual TLS

Effective mTLS requires mandatory peer authentication, precise identity validation, separate authorization, complete connection coverage, and reliable certificate operations.

01
Bidirectional certificate authentication

Both peers validate certificates and verify possession of the corresponding private keys. Configure the server to require a valid client certificate rather than merely requesting one optionally.

02
Explicit trust and identity validation

Trust stores define accepted certificate authorities, while certificate identity checks determine which peer is expected. Restrict accepted identities and certificate usages instead of treating every certificate from a trusted authority as equally privileged.

03
Authentication separate from authorization

mTLS establishes an authenticated peer identity but does not determine which operations that peer may perform. Apply application or proxy authorization policies to the validated identity.

04
Connection-specific protection

mTLS protects the connection on which its handshake occurs, not every downstream connection. Document termination points and independently secure proxy-to-backend and service-to-service traffic.

05
Certificate lifecycle management

Automate issuance and renewal, protect private keys, and rotate trust bundles without interrupting workloads. Establish an explicit response for compromised identities because revocation enforcement is not universal.

06
Distinct from infrastructure encryption

Encrypted network links and managed inter-node encryption do not necessarily authenticate application peers with certificates. Match each control to the required traffic path, identity boundary, and threat model.

Cloud services for Mutual TLS

AWS Private CA can supply certificates for application or proxy identities, while workloads on Amazon EKS enforce mTLS and authorize authenticated peers. Application Load Balancer can validate client certificates at an application entry point, but its backend connection is a separate security boundary. AWS IoT Core applies certificate-based authentication to device connections and uses policies for authorization. Amazon EMR and SageMaker AI illustrate the broader inter-resource encryption requirement: their encryption settings must be evaluated for the specific traffic and authentication guarantees they provide. An architecture can combine these controls, but enabling encryption in one service does not establish mTLS across every connection.

AWS Private Certificate AuthorityAWS Private Certificate Authority

AWS Private CA can issue private certificates used by applications and proxies for mTLS. It supplies certificate authority capabilities, but workloads still need secure key handling, certificate delivery, renewal automation, and peer-validation configuration.

AWS IoT CoreAWS IoT Core

AWS IoT Core supports X.509 client-certificate authentication over TLS for device connections. Device certificates establish identity, while AWS IoT policies determine which messaging operations and resources the device can access.

Amazon EMRAmazon EMR

EMR security configurations enable in-transit encryption for supported cluster components and require appropriate certificate material for TLS-based protections. Evaluate each component's protocol and authentication behavior rather than assuming that all encrypted cluster traffic uses mTLS.

Amazon SageMakerAmazon SageMaker

SageMaker AI supports enabling inter-container traffic encryption for supported distributed training jobs. This addresses an inter-resource encryption requirement but should not be equated with a configurable, application-wide mTLS identity and authorization policy.

Mutual TLS exam questions

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

SOA-C03

A company exposes a device-ingestion API through an Application Load Balancer (ALB). The ALB validates device client certificates against a trust store before forwarding requests. The application does not perform certificate validation.

The company begins migrating devices to a new private certificate authority (CA). Devices using the original CA still connect successfully, but devices using the new CA fail during the TLS handshake. The new devices present complete, unexpired certificate chains and possess the matching private keys. All devices trust the ALB's server certificate and support its TLS security policy. The ALB trust store contains only the original CA's certificates.

A CloudOps engineer must restore connectivity for migrated devices while continuing to accept devices using the original CA. Certificate validation must remain enforced at the ALB.

Which action should the engineer take?

Show answerCORRECT ANSWER

Upload a CA certificate bundle containing both the original and new CA chains to Amazon S3, and update the existing ALB trust store to use that bundle.

The ALB must trust both issuing CA chains during the migration. Updating its trust store with a bundle containing both chains allows it to validate certificates from both device populations while continuing to enforce client certificate authentication.

SAP-C03

A manufacturer is deploying a telemetry ingestion service on Amazon EC2 instances across three Availability Zones. Thousands of gateways connect to a single DNS endpoint. Each gateway has a unique client certificate issued by AWS Private CA and trusts the manufacturer's private CA hierarchy for server certificates.

An audit requires each backend instance to verify the connecting gateway's possession of its certificate's private key during the TLS handshake that the instance processes. The application must then authorize telemetry submissions based on the authenticated certificate identity. Authentication performed by an intermediary and conveyed through HTTP headers does not satisfy the requirement. The service does not require content-based routing.

Which architecture meets these requirements?

Show answerCORRECT ANSWER

Configure a Network Load Balancer with a TCP listener and a TCP target group on the application's TLS port. Install server certificates issued by AWS Private CA on the instances. Configure each application to require and validate gateway client certificates against the private CA hierarchy and authorize requests using the validated identity.

A TCP listener and TCP target group forward the TLS connection without terminating it. Each backend performs the handshake directly with the gateway, presents its server certificate, and verifies the gateway's client certificate and proof of private-key possession. The application can then apply authorization policies to the authenticated gateway identity.

DVA-C02

A company exposes a billing microservice through an Amazon API Gateway Regional REST API. Other microservices call the API through a custom domain name that already has a valid server certificate. The company issues each calling microservice a workload certificate and a corresponding private key from its internal certificate authority (CA).

A security requirement states that API Gateway must reject callers that cannot prove possession of a valid company-issued workload certificate during connection establishment. Callers must not be able to bypass this requirement by using the API's default execute-api endpoint.

Which solution should a developer implement?

Show answerCORRECT ANSWER

Enable mutual TLS on the custom domain using an S3 truststore containing the internal CA certificate chain. Disable the default execute-api endpoint, and configure callers to present their workload certificates and prove possession of the corresponding private keys while validating the server certificate.

Mutual TLS lets API Gateway validate caller certificates against the configured CA truststore and requires callers to prove possession of their private keys. Callers also validate the server. Disabling the default execute-api endpoint prevents requests from bypassing the custom domain's certificate requirement.

Practice Mutual TLS in a full exam

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

Start a free practice exam

What is Mutual TLS

3 min read

Mutual TLS, commonly abbreviated mTLS, combines transport encryption with certificate-based authentication of both endpoints. In a typical connection, the client validates the server certificate and expected server identity, and the server requests and validates a client certificate. Each endpoint proves possession of the private key associated with its certificate during the TLS handshake; private keys are not transmitted. Successful authentication establishes who the peers are, while TLS protects the confidentiality and integrity of their traffic.

Trust depends on more than presenting a certificate. Configure trusted certificate authorities, validate certificate chains and validity periods, and enforce appropriate certificate usages. Clients must verify the intended server identity, usually through a DNS name in the certificate's subject alternative name. Servers should map validated client identities to explicit access policies. A certificate issued by a trusted authority does not automatically entitle its holder to every operation.

In cloud environments, mTLS commonly protects service-to-service connections, internal APIs, and device connections. For example, a payments service can accept connections only from workloads presenting certificates issued for approved application identities. On Kubernetes, applications or service-mesh proxies can perform the handshake. Strict enforcement matters: a configuration that accepts both authenticated TLS and plaintext connections leaves a bypass path. Network policies and security groups complement mTLS by limiting reachability, but they do not provide certificate-based peer authentication.

Encryption boundaries must be evaluated for every connection segment. If a load balancer terminates client mTLS, the original authenticated TLS session ends there. A separate connection to the backend needs its own encryption and, when required, mutual authentication. Forwarding a validated client identity in an HTTP header does not make the backend connection mTLS. Protect that connection and prevent callers from bypassing the trusted proxy or injecting identity headers.

For inter-resource encryption questions, distinguish mTLS from broader encryption-in-transit controls. Amazon EKS does not automatically provide mTLS between application pods; workloads need an appropriate application or proxy configuration. Amazon EMR security configurations enable supported in-transit protections, but the authentication properties vary by component and protocol. Amazon SageMaker AI provides an inter-container traffic encryption option for supported distributed training jobs; that setting should not be treated as a general-purpose application mTLS policy. Verify the actual traffic paths and authentication guarantees rather than assuming that an encryption setting implies mutual certificate validation.

Similarly, automatic network encryption between supported Nitro-based EC2 instances is infrastructure-level protection, not application mTLS. Its eligibility and network-path requirements determine coverage, and it does not establish application certificate identities. Use TLS or mTLS when application-level authentication or protection across additional network paths is required.

The main operational trade-off is public key infrastructure complexity. Automate certificate issuance, renewal, trust-bundle distribution, and safe rotation. Protect private keys, prefer distinct workload identities over shared certificates, and design overlapping trust periods when changing certificate authorities. Define how compromised certificates are revoked or otherwise rejected; revocation checking is implementation-dependent. Test expired certificates, untrusted issuers, incorrect server names, missing client certificates, and unauthorized but valid identities. Monitor handshake failures and renewal failures, and account for handshake cost and proxy overhead when sizing high-connection-rate systems.

Learn Mutual TLS in lessons

8 short lessons on Mutual TLS in 4 certification courses.

and 2 more lessons

Open the lessons