Cloud concept · Updated

Role-Based Access Control - Role-Based Access Control assigns permissions to roles that represent responsibilities and grants identities access through their authorized roles.

In short

Role-Based Access Control (RBAC) separates permission definitions from individual users or workloads, making access easier to administer and review. In cloud environments, it supports consistent authorization across teams and accounts, but requires carefully scoped roles and controlled assignments to prevent excessive privileges.

Cloud Concepts Hub →

6 key aspects of Role-Based Access Control

RBAC centralizes permissions around responsibilities while depending on secure assignments, least privilege, lifecycle reviews, and complete authorization evaluation.

01
Permissions organized by responsibility

Define reusable roles around operational tasks rather than individual people. Keep permitted actions and resource scope explicit so a role name such as operator does not hide broad administrative access.

02
Controlled role assignment and assumption

Govern who can assign roles, change their permissions, or assume them. For cloud role sessions, evaluate the trust relationship separately from the permissions available after assumption.

03
Least privilege and separation of duties

Grant only the permissions needed for each responsibility and review combinations of assignments. Separate sensitive duties, such as approving a change and deploying it, where the control requires independent actors.

04
RBAC and ABAC composition

Use roles to define job capabilities and attributes to constrain which resources those capabilities apply to. Protect authorization-relevant tags and validate condition support for the specific API actions involved.

05
Lifecycle management and auditability

Review assignments after team changes and remove obsolete access. Record role assumptions and resource operations so engineers can connect actions to the responsible identity and session.

06
Effective authorization evaluation

Do not infer effective access solely from a role's attached permissions. Account for resource policies, explicit denies, session restrictions, organizational guardrails, and the platform's policy evaluation rules.

Role-Based Access Control exam questions

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

MLA-C02 (beta)

A company has two teams that use Amazon SageMaker AI. Model evaluators must invoke a designated staging endpoint but must not access the production endpoint. Production support engineers must inspect the production endpoint configuration by using DescribeEndpoint but must not invoke either endpoint. Employees sign in as IAM users and then assume roles. Access must be administered by job function rather than through individually maintained SageMaker policies.

The users currently have no SageMaker permissions. Only security administrators can modify IAM policies, roles, and team memberships. Which configuration meets these requirements?

Show answerCORRECT ANSWER

Create an evaluator role allowing InvokeEndpoint only on the staging endpoint and a support role allowing DescribeEndpoint only on the production endpoint. Configure trust policies and team-group policies so that each team can assume only its designated role.

This separates permissions by job responsibility and scopes each role to the required action and endpoint. Restricting both role trust and assumption permissions to the appropriate team prevents users from obtaining the other team's permissions.

AIP-C01

A company uses an Amazon Bedrock agent to help employees manage purchase orders. Purchasing analysts may view orders, while purchasing managers may view orders and approve payments. Both groups use the same application backend and agent. An action-group Lambda function calls an internal purchasing API that uses IAM authorization and supports separate read and approval permissions.

The backend validates enterprise identity tokens and can retrieve authoritative job-function assignments. Employees cannot call the purchasing API directly. However, employees can manipulate prompts and action parameters, so neither model output nor client-supplied role names can be trusted for authorization. The Lambda execution role currently permits both purchasing operations.

The company must enforce job-function permissions at the purchasing API, even when the agent proposes an unauthorized action. Which design meets these requirements?

Show answerCORRECT ANSWER

Create separate reader and approver IAM roles with appropriately scoped API permissions. Remove direct purchasing API permissions from the Lambda execution role. Bind each action invocation to a server-validated employee identity, check the employee's authoritative job-function assignment, and assume only the corresponding authorized role before signing the API request.

This separates permission definitions by business responsibility and controls role assignment using trusted identity and entitlement information. The purchasing API evaluates credentials for a role with only the appropriate permissions. Independent authorization before role assumption prevents prompts or generated action arguments from elevating an analyst to an approver.

SOA-C03

A company's CloudOps engineers use IAM users in a single AWS account. Each engineer performs routine monitoring and occasionally performs approved recovery work. During monitoring sessions, engineers must be able to inspect EC2 instances but must not be able to restart them. Engineers must deliberately switch to a separate session to perform recovery actions. Neither type of session may modify IAM resources.

The company wants to maintain permissions centrally by operational responsibility rather than maintain separate permissions for each engineer. An existing access-management process can authorize approved users to assume designated roles. The IAM users have no direct permissions to operate EC2 instances, and no other policies grant access.

Which configuration meets these requirements?

Show answerCORRECT ANSWER

Create separate monitoring and recovery IAM roles. Give the monitoring role only the required EC2 inspection permissions and the recovery role only the required inspection and approved recovery permissions. Authorize approved engineers to assume the appropriate roles, and grant neither role IAM modification permissions.

Separate roles maintain permissions by operational responsibility. Monitoring sessions cannot perform recovery actions, and engineers must assume the recovery role to obtain those permissions. Omitting IAM modification permissions from both roles satisfies the restriction because no other policies grant access.

Practice Role-Based Access Control in a full exam

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

Start a free practice exam

What is Role-Based Access Control

3 min read

Role-Based Access Control (RBAC) organizes authorization around responsibilities rather than maintaining a separate permission set for every identity. Administrators define roles such as auditor, application operator, and database administrator, associate permissions with those roles, and authorize users or workloads to use them. Authentication establishes who an identity is; RBAC helps determine what that identity may do. Group membership commonly simplifies role assignments, but a group and a role are not necessarily the same object.

A practical design starts with job functions and operational tasks. An auditor might read configuration and audit records without changing infrastructure. An application operator might restart services and inspect logs without modifying identity policies. Scope matters as much as the permitted actions: an operator responsible for a development environment should not automatically receive equivalent access to production. Review role assignments when people change teams, and separate routine administration from emergency access.

Cloud platforms implement these relationships differently. In AWS, IAM roles have trust policies that define which principals may assume them and permissions policies that define allowed operations. AWS Security Token Service issues temporary credentials for role sessions. IAM Identity Center permission sets can provision IAM roles into assigned AWS accounts, allowing centrally managed workforce access. An IAM role is an identity mechanism, however, not proof that an authorization design uses RBAC: its policies can implement RBAC, attribute-based access control, or a combination.

RBAC and attribute-based access control (ABAC) answer different design questions. RBAC commonly grants access because an identity holds an approved responsibility, such as developer. ABAC evaluates attributes of the principal, resource, or request. For example, a developer role could allow supported operations only when the resource's Project tag matches the principal's Project tag. This hybrid approach retains role-based job permissions while using attributes to distinguish projects, reducing the need for a separate role for every project and responsibility combination.

Tag-based authorization requires governance, not just a condition in a policy. Restrict who can change authorization-relevant resource tags, principal tags, and session tags. Where supported, require appropriate tags during resource creation and constrain the supplied values. Otherwise, an identity might retag a resource or manipulate an attribute to gain unintended access. Check support for each service, action, resource type, and condition key; tag conditions do not apply uniformly to every API operation.

RBAC makes access reviews understandable, but fine-grained environments can produce role proliferation, while overly broad shared roles create excessive access. Role hierarchies are supported in some RBAC systems but should not be assumed across cloud providers. Separation of duties also requires explicit design: assigning both deployment and approval privileges to one person can defeat the intended control even if each role looks reasonable independently.

When troubleshooting AWS authorization, first distinguish failure to assume a role from failure to perform an operation after assuming it. Inspect the caller, trust relationship, required assumption permissions, session attributes, requested action, and target resource. Then evaluate relevant identity and resource policies, permissions boundaries, session policies, and organization policies. Boundaries and service control policies do not grant permissions, and applicable explicit denies override allows. Resource-based grants have additional evaluation nuances, so an attached role policy alone does not describe every possible access path. Test intended access and expected denials, and use audit records to confirm which session made the request.

Learn Role-Based Access Control in lessons

12 short lessons on Role-Based Access Control in 7 certification courses.

and 6 more lessons

Open the lessons