Cloud concept · Updated

Access Control - Access control determines which identities can perform which actions on which resources under specified conditions.

In short

Access control turns security requirements into enforceable permissions for people, applications, and cloud services. It limits unauthorized activity while preserving legitimate operations, including the ability to deliver logs, run health checks, and investigate incidents.

Cloud Concepts Hub →

6 key aspects of Access Control

Effective access control combines scoped permissions, layered enforcement, explicit service authorization, and evidence-driven validation without confusing infrastructure placement with security boundaries.

01
Identity, action, resource, and context

Evaluate the requester, requested operation, target resource, and relevant conditions together. Authentication proves identity; authorization determines whether that identity may perform the operation.

02
Least privilege and temporary access

Scope permissions to the task and prefer temporary workload or federated role credentials over embedded long-lived keys. Review unused permissions and provide controlled, auditable emergency access.

03
Layered policy evaluation

Consider identity policies, resource policies, organizational restrictions, and session limits when diagnosing access decisions. In AWS, an applicable explicit deny overrides an allow, and permission-limiting policies do not independently grant access.

04
Separation of location and authorization

Treat Regions, Availability Zones, and edge locations as infrastructure placement and delivery concepts, not automatic permission boundaries. Apply explicit controls when access must be constrained by geography or destination.

05
Service-to-service permissions

Give workloads and delivery services the permissions needed to invoke dependencies and publish telemetry. Check role trust, destination policies, and encryption-key access rather than assuming that enabling a feature completes its authorization setup.

06
Observable and testable enforcement

Test both permitted and denied operations, and preserve evidence of policy changes and access failures. Distinguish authorization failures from network, logging-configuration, and destination-selection problems.

Cloud services for Access Control

IAM defines permissions for engineers, workloads, and service interactions. Lambda and API Gateway apply those permissions to execution and invocation paths, while CloudFront adds separate viewer and origin access controls at the delivery layer. CloudWatch receives operational telemetry, and CloudTrail records supported activity for auditing and investigation. These services require independent authorization checks: permission to invoke an application does not imply permission to publish its logs or read its audit records. Troubleshoot each producer-to-destination relationship, including role trust, resource policies, encryption permissions, and logging configuration.

Amazon CloudWatchAmazon CloudWatch

CloudWatch provides logs, metrics, and alarms whose publishing, viewing, and administration require appropriate permissions. For log-delivery troubleshooting, inspect producer permissions, destination policies where applicable, and encryption settings separately from alarm configuration.

AWS LambdaAWS Lambda

Lambda separates a function's execution-role permissions from permissions that allow callers or services to invoke it. Missing execution-role permissions can prevent CloudWatch Logs delivery even when the function runs.

Amazon API GatewayAmazon API Gateway

API Gateway supports request authorization through mechanisms that vary by API type, including IAM authorization and authorizers. Logging must also be configured with the permissions and destinations required by the selected API type and logging feature.

Amazon CloudFrontAmazon CloudFront

CloudFront can restrict viewer access with signed URLs or cookies and use origin access control for supported origins. Viewer authorization, origin authorization, and log-delivery permissions are separate configurations.

AWS CloudTrailAWS CloudTrail

CloudTrail records supported account and API activity for access investigations and change auditing. Configure the necessary event coverage, including data events where required, and protect both log delivery and access to the resulting records.

Access Control exam questions

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

AIB-C01 (beta)

A manufacturer runs AI training projects for many business units in a shared AWS account. Operations staff must be able to stop Amazon SageMaker AI training jobs only for their assigned project. Projects and jobs change frequently, so the company wants authorization to adapt without maintaining a separate list of job identifiers in each operator's policy. The central security team maintains authoritative project assignments. Which access-control design BEST meets these requirements?

Show answerCORRECT ANSWER

Allow operators to stop training jobs when the job's Project tag matches their centrally assigned principal tag, and prevent operators from changing either authorization tag.

Tag-based IAM conditions can enforce project-specific access without listing individual jobs. Centrally controlling the principal and resource tags prevents operators from changing the attributes to obtain access to another project's jobs.

MLA-C02 (beta)

A monitoring application uses an IAM role to check the status of Amazon SageMaker AI endpoints and send test inference requests to one endpoint named fraud-canary. The role's identity-based policy allows sagemaker:DescribeEndpoint on all endpoints and sagemaker:InvokeEndpoint only on the fraud-canary endpoint ARN. A permissions boundary attached to the role allows only sagemaker:DescribeEndpoint on all endpoints.

Status checks succeed, but test inference requests receive AccessDenied errors. No service control policies, resource policies, session policies, or explicit denies affect these requests. The application must retain its status-checking permissions, and the permissions boundary must continue to limit inference access to fraud-canary even if broader identity-based policies are attached later.

Which change meets these requirements?

Show answerCORRECT ANSWER

Update the permissions boundary to retain its DescribeEndpoint permission and add sagemaker:InvokeEndpoint only on the fraud-canary endpoint ARN.

The role's effective permissions are constrained by both its identity-based policies and its permissions boundary. Adding the scoped invocation permission to the boundary enables the existing identity-based allow, preserves status checks, and prevents future identity-based policies from expanding inference access beyond fraud-canary.

SAP-C03

A company stores compliance logs in an Amazon S3 bucket in a security account. An existing bucket policy allows the CloudTrail service principal to deliver logs, with permissions restricted to the company's trail by an aws:SourceArn condition. Analyst roles in the security account have identity-based policies that allow them to read the logs.

A new requirement states that all requests to this bucket and its objects made directly with IAM principal credentials must pass through a designated S3 VPC endpoint. The restriction must remain effective even if an administrator later grants additional S3 permissions to an IAM principal. CloudTrail must continue delivering logs directly to the bucket. A separate governance control prevents unauthorized changes to the bucket policy.

Which bucket policy change meets these requirements?

Show answerCORRECT ANSWER

Retain the existing CloudTrail allow statement. Add an explicit deny for s3:* on the bucket and its objects, with Principal set to *, that applies when aws:SourceVpce does not equal the designated endpoint ID and aws:PrincipalIsAWSService is false.

The two conditions are evaluated together. Direct IAM requests outside the designated endpoint are explicitly denied, regardless of additional identity-based allows. Direct requests from the CloudTrail service principal are excluded from this deny by aws:PrincipalIsAWSService. The existing trail-scoped allow continues to authorize CloudTrail delivery.

Practice Access Control in a full exam

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

Start a free practice exam

What is Access Control

3 min read

Access control answers a practical question: may this requester perform this action on this resource in this context? A requester can be a person, application, workload role, or cloud service. Authentication establishes identity; authorization evaluates whether a requested operation is permitted. Successful sign-in does not imply permission to read a database, change a firewall, or view security logs.

Cloud platforms commonly express permissions through policies attached to identities or resources. Roles collect permissions that users or workloads can assume, while attributes such as resource tags, organization membership, source network, or session characteristics can influence decisions. For example, a deployment role might update an application but lack permission to read its production secrets. Temporary role credentials reduce dependence on long-lived access keys, although their permissions and session duration still require careful design.

Least privilege means granting only the actions, resources, and conditions required for a task. In AWS, requests are implicitly denied unless applicable policies allow them, and an applicable explicit deny overrides an allow. Effective authorization can also depend on permissions boundaries, session policies, organization policies, and resource policies. A permissions boundary or service control policy limits possible permissions; it does not grant permissions by itself. Cross-account access often requires both permission for the caller and an appropriate trust or resource policy in the destination account.

Infrastructure location and authorization are separate concerns. An AWS Region is a geographic area containing multiple Availability Zones, which provide separate infrastructure locations for resilient deployments. Edge locations serve functions such as content delivery closer to viewers and are not Availability Zones. IAM is a global service within an AWS partition, while many resources and their permissions reference a particular Region. Deploying across Availability Zones improves availability but does not automatically change access rights. Likewise, selecting a Region does not create a geographic access restriction; enforce such requirements with appropriate policies and service-specific controls.

Access control operates at multiple layers. Network rules determine whether traffic can reach an endpoint, while application and identity policies determine what requests are accepted. A reachable API can still reject an unauthorized request, and a correctly authorized request can fail because routing or firewall rules block connectivity. Public content delivered through an edge location also does not require a publicly accessible origin: a distribution can authorize origin requests while restricting viewers through signed URLs or cookies.

Monitoring pipelines need their own permissions. A Lambda function can execute successfully yet fail to write logs if its execution role lacks the necessary CloudWatch Logs permissions. API Gateway logging requires the appropriate logging configuration and delivery permissions for the API type. CloudFront log delivery requires compatible destination settings and permissions for the selected logging mechanism. Check encryption-key permissions where relevant, destination policies, account and Region selection, and whether the relevant logging feature is enabled before interpreting missing records as an absence of activity.

Health checks illustrate the difference between connectivity and authorization. A health-check request can fail because a firewall blocks the checker, TLS settings are incompatible, or the endpoint requires credentials the checker does not supply. Prefer a narrowly scoped health endpoint that reveals little information rather than weakening authorization for the entire application. Similarly, give log producers permission to write only to intended destinations, and separate log-reading privileges from permissions to delete logs or disable collection.

The main trade-off is precision versus operational complexity. Broad permissions simplify initial setup but increase the damage possible from mistakes or compromised credentials. Highly restrictive policies can break deployments and obscure monitoring failures. Use tested policy changes, access-denied evidence, policy analysis, and periodic permission reviews to refine access. Audit logs provide evidence of activity, but they are not themselves an enforcement mechanism, and an administrator label does not guarantee unrestricted access through every policy layer.

Learn Access Control in lessons

14 short lessons on Access Control in 9 certification courses.

and 8 more lessons

Open the lessons