Cloud concept · Updated

Authentication - Authentication is the process of verifying the claimed identity of a person, application, or device before treating it as that identity.

In short

Cloud systems use authentication to establish which identity is making a request by validating credentials or other evidence. It is distinct from authorization, which determines what that identity may do, and is essential for protecting administrative access, application data, and service-to-service communication.

Cloud Concepts Hub →

6 key aspects of Authentication

Effective authentication combines trustworthy identity evidence, appropriate factors, secure credential handling, and controlled sessions while keeping permission decisions separate.

01
Verification of a claimed identity

Authentication validates evidence associated with a person, workload, or device. Prefer individually attributable identities over shared credentials so activity can be investigated and access can be removed precisely.

02
Separation from authorization

Successful authentication does not guarantee access to a resource. Investigate credential failures separately from policy-based denials, because they require different fixes.

03
Multifactor protection

MFA combines different factor categories to reduce dependence on a single credential. Use phishing-resistant methods where supported, especially for privileged and root access.

04
Human and workload credentials

People typically use interactive sign-in, while workloads use mechanisms such as temporary credentials, certificates, and signed requests. Avoid embedding a human user's credentials in application code.

05
Federation and trusted identity providers

Federation allows a system to accept identity assertions or tokens from a trusted provider. Validate the issuer, intended audience, signature, and expiration as required by the protocol rather than merely checking that a token exists.

06
Credential and session lifecycle

Credentials and sessions need controlled issuance, expiration, renewal, and revocation. Prefer temporary credentials where practical, and account for the fact that password changes may not terminate existing sessions.

Cloud services for Authentication

For workforce access, IAM Identity Center connects users to AWS accounts through centralized sign-in and optional external identity providers. IAM defines roles and permissions, while AWS STS supplies temporary credentials used for authenticated API requests. For customer-facing applications, Amazon Cognito user pools handle user authentication, and identity pools can obtain temporary AWS credentials when needed. These services address different identity populations and stages of access: verifying identity, establishing a session, and applying permissions remain distinct responsibilities even when the user experiences a single sign-in flow.

Amazon CognitoAmazon Cognito

Amazon Cognito user pools provide authentication for application users, including sign-in and federation with supported identity providers. Cognito identity pools can exchange supported identity evidence for temporary AWS credentials, separating application user authentication from access to AWS resources.

Authentication exam questions

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

CLF-C02

A company runs an inventory application in its on-premises data center. The application uses an AWS SDK configured with an IAM user's access key ID and secret access key to call AWS APIs. How does the SDK use these credentials to establish the application's identity when sending requests?

Show answerCORRECT ANSWER

It uses the secret access key to sign each request and includes the access key ID so AWS can validate the signature.

AWS SDKs sign API requests using the configured credentials. AWS uses the access key ID to identify the credentials and validates the signature to authenticate the requester without receiving the secret access key.

DVA-C02

A developer is troubleshooting an application on Amazon EC2 that uses an AWS SDK and its default credential provider chain to read an Amazon DynamoDB table. The instance has an IAM role, but the application environment might also contain AWS credentials. Reads succeed, but an audit indicates that the requests might be using an unexpected identity.

The developer must determine the exact IAM user or assumed-role session that authenticates the application's requests, without logging credentials or changing permissions policies. Which approach meets these requirements?

Show answerCORRECT ANSWER

Call AWS STS GetCallerIdentity using the same credential provider as the DynamoDB client, and record the returned ARN.

GetCallerIdentity returns the identity represented by the credentials used to authenticate the call. Using the same credential provider as the DynamoDB client identifies the actual IAM user or assumed-role session rather than merely the role configured for the instance. The returned ARN is not a secret credential.

ANS-C01

A financial services company is migrating a transaction API to Amazon EC2 instances in private subnets across three Availability Zones. Client applications use mutual TLS (mTLS) with certificates issued by the company's private certificate authority. Security policy requires each application instance to verify the client's possession of its private key during the TLS handshake. The application cannot accept client identity conveyed through HTTP headers, and decrypted transaction data must not be available to the load balancer. The company needs a managed load balancing solution that distributes connections across healthy instances and supports an Auto Scaling group. Which configuration meets these requirements?

Show answerCORRECT ANSWER

Configure a Network Load Balancer with a TCP listener on port 443 and a TCP target group on the application's TLS port. Configure each application instance to terminate TLS and validate client certificates.

The TCP listener and TCP target group forward the encrypted TLS traffic without terminating TLS at the NLB. Each application instance participates directly in the client's mTLS handshake and verifies proof of possession of the client private key. The NLB can distribute connections to healthy Auto Scaling group instances across Availability Zones.

Practice Authentication in a full exam

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

Start a free practice exam

What is Authentication

3 min read

Authentication answers the question, “Who is making this request?” A person, application, or device claims an identity and presents evidence that a trusted system validates. That evidence might be a password, a cryptographic signature, a security key, or a token issued by a trusted identity provider. Authentication establishes confidence in an identity; it does not automatically establish that a request is permitted.

Authentication and authorization are separate decisions. An engineer might successfully sign in to a cloud console but receive an access-denied response when attempting to delete a database. The sign-in established the engineer’s identity, while authorization policies rejected the requested action. For exam questions, credentials and identity verification generally indicate authentication, while permissions, policies, and allowed actions indicate authorization.

Cloud platforms authenticate both human users and workloads. People commonly use an interactive sign-in process with multifactor authentication, or MFA. Applications typically use temporary credentials, signed requests, certificates, or tokens rather than interactive passwords. For example, an application running on a virtual machine can obtain temporary credentials through an attached workload role instead of storing a permanent secret in its source code.

In AWS, IAM users can have passwords for console access and access keys for programmatic access. These are different credentials: a console password is not used to sign AWS CLI requests. AWS API requests commonly use Signature Version 4, which proves possession of the secret access key without transmitting that secret in the request. Temporary AWS credentials also include a session token and expire after a defined period.

Roles provide assumable identities with permissions and are commonly used with temporary credentials. An IAM group is different: it organizes IAM users for permission management and cannot sign in or authenticate independently. The AWS account root user is also distinct from an IAM user. Protect root access with MFA, avoid using it for routine work, and avoid creating root access keys.

MFA requires evidence from different factor categories, such as something a user knows and something the user possesses. Two passwords do not constitute two factors. Phishing-resistant methods, such as appropriately implemented FIDO security keys or passkeys, provide stronger protection against credential phishing than passwords combined with manually entered one-time codes. MFA does not grant permissions or make an already issued session immune to theft.

Federation lets a cloud platform trust authentication performed by an external identity provider. An employee can sign in through a corporate identity system and obtain a cloud session without maintaining a separate long-lived cloud password. Single sign-on improves usability and centralizes identity administration, but the identity provider becomes a critical dependency that requires strong security and recovery procedures.

Authentication design balances security, usability, and operational complexity. Short-lived credentials reduce the useful lifetime of stolen credentials but require reliable renewal. Long-lived secrets require secure storage, rotation, and revocation. Engineers should avoid shared identities, prevent credentials and tokens from entering logs or repositories, and monitor sign-in and API activity. Disabling an account or changing a password does not necessarily invalidate every existing session immediately; session expiration and revocation behavior must be understood separately.

Learn Authentication in lessons

4 short lessons on Authentication in 2 certification courses.

Open the lessons