Cloud concept · Updated

Effective Permissions - Effective Permissions are the actions a principal is actually authorized to perform on a resource after all applicable policies, restrictions, and request conditions are evaluated.

In short

Assigned permissions do not necessarily equal usable access: authorization combines grants with organizational controls, resource policies, session restrictions, and request context. Understanding the resulting permissions helps engineers design least-privilege access and diagnose why an apparently allowed operation fails.

Cloud Concepts Hub →

6 key aspects of Effective Permissions

Effective permissions result from request-specific grants, applicable restrictions, trust relationships, and dependent operations, verified through complementary diagnostic methods.

01
Request-specific evaluation

Effective access depends on the principal, action, resource, and request context. Test the actual role session and condition values rather than assuming that every session of the same role has identical access.

02
Explicit-deny precedence

An applicable explicit deny overrides an allow in AWS IAM authorization. Identify the denying policy layer before adding permissions, because additional allows cannot override that deny.

03
Grants versus permission limits

Policies that grant access serve a different purpose from boundaries and organizational restrictions. A limit defines the maximum permitted scope but does not independently authorize an operation.

04
Principal and trust-path sensitivity

Resource-policy behavior depends on whether access is granted to a user, role, session, or another account. Cross-account requests and role assumption require careful evaluation of both trust and permissions.

05
Dependent-operation authorization

A high-level operation can require authorization against several resources or services. Reading an encrypted object, for example, can require both object-read permission and authorization to use its encryption key.

06
Evidence-based verification

Use policy simulation, access analysis, audit records, and controlled requests together. Each provides a different view, and none should be assumed to reproduce every aspect of a live authorization decision.

Cloud services for Effective Permissions

IAM defines identity permissions and boundaries, while Organizations establishes additional organizational limits. STS creates the temporary sessions whose credentials applications actually use, and services such as S3 evaluate those sessions against resource policies and service-specific controls. During troubleshooting, CloudTrail helps reconstruct the observed request, the IAM Policy Simulator tests supported policy scenarios, and IAM Access Analyzer identifies supported access relationships and policy issues. Together, these services help distinguish missing grants, explicit restrictions, trust problems, and context mismatches. Confirm the final result with a controlled request because simulation and analysis do not capture every live authorization dependency.

AWS OrganizationsAWS Organizations

AWS Organizations applies service control policies and, for supported resources and services, resource control policies as organizational permission limits. These controls can block access that identity or resource policies would otherwise allow.

Amazon S3Amazon S3

Amazon S3 demonstrates how identity policies, bucket policies, access point policies, and other applicable controls affect effective access. Bucket-level and object-level operations require different resource scopes, while encrypted objects can introduce additional key-authorization requirements.

AWS CloudTrailAWS CloudTrail

CloudTrail records supported API activity with caller identity, request details, and available error information that can support authorization investigations. Event coverage depends on the service, event type, and logging configuration; relevant data events may require explicit configuration.

Effective Permissions exam questions

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

MLA-C02 (beta)

An inference application uses an IAM role named FraudClient to invoke Amazon SageMaker AI real-time endpoints. During a blue/green deployment, requests to the existing endpoint succeed, but requests to the replacement endpoint return AccessDeniedException.

An ML engineer verifies the following:
• FraudClient's identity-based policy allows sagemaker:InvokeEndpoint on both endpoint ARNs.
• FraudClient has a permissions boundary that allows sagemaker:InvokeEndpoint on all resources but also explicitly denies that action when the resource is not the existing endpoint ARN, using NotResource.
• Both endpoints are healthy, and no other policies or network controls block the requests.

The application must invoke both endpoints during the transition, but it must not gain access to any other endpoint. Which change should the engineer make?

Show answerCORRECT ANSWER

Update the permissions boundary's Deny statement so that its NotResource list contains both the existing and replacement endpoint ARNs.

Listing both ARNs in NotResource makes the explicit deny inapplicable to those two endpoints while continuing to deny invocation of every other endpoint. The existing identity-based permissions and boundary Allow then permit invocation of both approved endpoints.

SAP-C03

A company uses AWS Organizations with all features enabled. It stores confidential objects in Amazon S3 buckets in its management account, a security tooling member account, and several workload member accounts. The security tooling account is a delegated administrator for multiple AWS services.

IAM roles in the company and in an external auditing firm's account have valid permissions to download selected objects. External auditors access the buckets directly without assuming roles in the company's accounts. The company must centrally deny all non-HTTPS object downloads, including otherwise-authorized downloads by external auditors. Otherwise-authorized HTTPS downloads must continue to work.

The company has enabled resource control policies (RCPs). It requires an organization-level preventive guardrail without maintaining individual bucket policies for this restriction. Data can be migrated to replacement buckets, and clients can be updated. These download workflows do not involve AWS service principals.

Which solution meets these requirements with the LEAST data migration?

Show answerCORRECT ANSWER

Migrate the management account's objects to replacement buckets in a member account and update the clients. Keep the other buckets in place. Attach an RCP to the organization root that explicitly denies s3:GetObject when aws:SecureTransport is false.

Amazon S3 supports RCP enforcement. A root-attached RCP applies to applicable resources in member accounts, including delegated administrator accounts, but not to management-account resources. Migrating only the management-account data brings all the specified buckets within scope with the least migration. The explicit deny blocks non-HTTPS downloads by internal and external IAM principals, while HTTPS requests remain eligible under their existing permissions.

SOA-C03

A CloudOps engineer updates an AWS CloudFormation stack to add an Amazon CloudWatch Logs log group. Creation fails with AccessDenied for logs:CreateLogGroup. CloudTrail identifies the stack's dedicated execution role as the caller.

The engineer verifies the following configuration:
• The execution role's identity policy allows logs:CreateLogGroup on the required log group ARN.
• The member account is directly under the Workloads organizational unit (OU), which is directly under the organization root.
• The root and member account each have the FullAWSAccess service control policy (SCP) attached.
• The OU has only a custom allow-list SCP. It allows the existing deployment actions but does not include logs:CreateLogGroup.
• No applicable policy contains an explicit deny. No permissions boundary, session policy, or other control restricts the request. All other permissions required for the update are available.

Which change will resolve the failure while preserving the OU's restrictions on unrelated actions?

Show answerCORRECT ANSWER

Add an allow for logs:CreateLogGroup on the required log group ARN to the OU's custom SCP.

With allow-list SCPs, the action must be allowed at every level from the root through the OUs to the account. The OU currently does not allow this action. Adding the scoped allow removes that organizational restriction, while the execution role's existing identity policy grants access. Unrelated actions remain restricted.

Practice Effective Permissions in a full exam

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

Start a free practice exam

What is Effective Permissions

3 min read

Effective permissions describe the outcome of authorization evaluation for a particular principal, action, resource, and request context. They are not simply the permissions written in a user's policy or attached to a role. A request can be allowed by one policy but blocked by another control, or it can depend on attributes such as resource tags, source network, authentication method, or the identity of the current session. Consequently, effective permissions should be evaluated against a concrete request rather than treated as a static list.

Cloud authorization commonly combines identity-based grants, resource-based grants, inherited organizational controls, and temporary-session restrictions. In AWS, relevant controls can include IAM policies, resource policies, permissions boundaries, session policies, service control policies, resource control policies where supported, and VPC endpoint policies when the request traverses the endpoint. These controls serve different purposes. A permissions boundary or service control policy limits permissions but does not itself grant access. An endpoint policy also does not replace the permissions required by the target service.

For ordinary AWS IAM authorization, requests begin with an implicit deny unless an applicable authorization path grants access. An applicable explicit deny overrides an allow. However, it is incorrect to describe every policy as participating in a simple intersection. Identity-based and resource-based grants combine differently depending on the account relationship and the principal named in the resource policy. Within the same account, a resource-policy grant directly to an IAM user or role session can behave differently from a grant to a role ARN, particularly when permissions boundaries or session policies contain only implicit denials. Applicable explicit denies still take precedence.

For example, an application role might have an identity policy allowing object reads, while its permissions boundary allows only listing storage buckets. The identity-policy grant alone cannot authorize the read beyond that boundary. A separate failure could arise when the requested object uses a customer managed encryption key: permission to read the object does not automatically authorize the required key operation. Authorization must succeed for the dependent service operation as well.

Cross-account access usually requires authorization on both sides: the calling identity needs permission, and the target resource or role must trust the caller through the appropriate policy. Role assumption also creates a new authorization context. The role's policies and any session restrictions govern subsequent requests; the caller's original permissions are not automatically carried into the assumed-role session. Authentication success therefore does not establish that the intended resource operation is authorized.

To troubleshoot a denial, first capture the actual caller, including the assumed-role session, requested action, resource ARN, account, Region, and relevant condition values. Inspect the error and available audit events, then examine each applicable policy layer. Distinguish an explicit deny from a missing allow, an incorrect resource ARN, an unmet condition, or a dependent permission failure. Changing an identity policy cannot repair an explicit organizational deny. Likewise, granting a bucket-level action does not necessarily grant an object-level action because their resource scopes differ.

The IAM Policy Simulator helps test supported policy combinations and supplied context values before deployment or during investigation. Its results are diagnostic evidence, not a guarantee that a live request will succeed: resource-policy support, cross-account scenarios, and service-specific controls have limitations. IAM Access Analyzer complements simulation by identifying supported external, internal, or unused access and validating policies. An external-access finding shows that a resource policy permits access from outside the configured zone of trust; it does not prove that a particular external caller has every permission required for a successful request.

Layered authorization supports delegation and limits the impact of mistakes, but it increases troubleshooting complexity. Keep policies scoped and understandable, test both intended access and intended denials, and verify changes using controlled requests. Avoid broad administrator grants as a diagnostic shortcut, and allow for policy propagation delays before concluding that a carefully scoped correction failed.

Learn Effective Permissions in lessons

7 short lessons on Effective Permissions in 7 certification courses.

and 1 more lesson

Open the lessons