# Identity and Access Management in Deadline Cloud AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use Deadline Cloud resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [Audience](#security_iam_audience) + [Authenticating with identities](#security_iam_authentication) + [Managing access using policies](#security_iam_access-manage) + [How Deadline Cloud works with IAM](security_iam_service-with-iam.md) + [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md) + [AWS managed policies for Deadline Cloud](security-iam-awsmanpol.md) + [Service roles](security-iam-service-roles.md) + [Troubleshooting AWS Deadline Cloud identity and access](security_iam_troubleshoot.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS Deadline Cloud identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How Deadline Cloud works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### Federated identity As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials. A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials. For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # How Deadline Cloud works with IAM Before you use IAM to manage access to Deadline Cloud, learn what IAM features are available to use with Deadline Cloud. **IAM features you can use with AWS Deadline Cloud** | IAM feature | Deadline Cloud support | | --- | --- | | [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes | | [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No | | [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes | | [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes | | [Policy condition keys (service-specific)](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes | | [ACLs](#security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Yes | | [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes | | [Forward access sessions (FAS)](#security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#security_iam_service-with-iam-roles-service) | Yes | | [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | No | To get a high-level view of how Deadline Cloud and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Identity-based policies for Deadline Cloud **Supports identity-based policies:** Yes Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. ### Identity-based policy examples for Deadline Cloud To view examples of Deadline Cloud identity-based policies, see [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md). ## Resource-based policies within Deadline Cloud **Supports resource-based policies:** No Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Policy actions for Deadline Cloud **Supports policy actions:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. To see a list of Deadline Cloud actions, see [Actions defined by AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html#deadline-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in Deadline Cloud use the following prefix before the action: ``` deadline ``` To specify multiple actions in a single statement, separate them with commas. ``` "Action": [ "deadline:action1", "deadline:action2" ] ``` To view examples of Deadline Cloud identity-based policies, see [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md). ## Policy resources for Deadline Cloud **Supports policy resources:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` To see a list of Deadline Cloud resource types and their ARNs, see [Resources defined by AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html#deadline-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions defined by AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html#deadline-actions-as-permissions). To view examples of Deadline Cloud identity-based policies, see [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md). ## Policy condition keys for Deadline Cloud **Supports service-specific policy condition keys:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. To see a list of Deadline Cloud condition keys, see [Condition keys for AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html#deadline-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html#deadline-actions-as-permissions). To view examples of Deadline Cloud identity-based policies, see [Identity-based policy examples for Deadline Cloud](security_iam_id-based-policy-examples.md). ## ACLs in Deadline Cloud **Supports ACLs:** No Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. ## ABAC with Deadline Cloud **Supports ABAC (tags in policies):** Yes Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys. If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**. For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*. ## Using temporary credentials with Deadline Cloud **Supports temporary credentials:** Yes Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Forward access sessions for Deadline Cloud **Supports forward access sessions (FAS):** Yes Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). ## Service roles for Deadline Cloud **Supports service roles:** Yes A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. **Warning** Changing the permissions for a service role might break Deadline Cloud functionality. Edit service roles only when Deadline Cloud provides guidance to do so. ## Service-linked roles for Deadline Cloud **Supports service-linked roles:** No A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. For details about creating or managing service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service. # Identity-based policy examples for Deadline Cloud By default, users and roles don't have permission to create or modify Deadline Cloud resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*. For details about actions and resource types defined by Deadline Cloud, including the format of the ARNs for each of the resource types, see [Actions, resources, and condition keys for AWS Deadline Cloud](https://docs.aws.amazon.com/service-authorization/latest/reference/list_deadline.html) in the *Service Authorization Reference*. **Topics** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Using the Deadline Cloud console](#security_iam_id-based-policy-examples-console) + [Policy to access the console](#security_iam_id-based-policy-console-access) + [Policy to submit jobs to a queue](#security_iam_id-based-policy-examples-submit-jobs) + [Policy to allow creating a license endpoint](#security_iam-id-based-policy-examples-create-endpoint) + [Policy to allow monitoring a specific farm queue](#security_iam-id-based-policy-examples-monitor-queue) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete Deadline Cloud resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: + **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## Using the Deadline Cloud console To access the AWS Deadline Cloud console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Deadline Cloud resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform. To ensure that users and roles can still use the Deadline Cloud console, also attach the Deadline Cloud `ConsoleAccess` or `ReadOnly` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*. ## Policy to access the console To grant access to all functionality in the Deadline Cloud console, attach this identity policy to a user or role you want to have full access. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Sid": "EC2InstanceTypeSelection", "Effect": "Allow", "Action": [ "ec2:DescribeInstanceTypeOfferings", "ec2:DescribeInstanceTypes", "ec2:GetInstanceTypesFromInstanceRequirements", "pricing:GetProducts" ], "Resource": ["*"] }, { "Sid": "VPCResourceSelection", "Effect": "Allow", "Action": [ "ec2:DescribeVpcs", "ec2:DescribeSubnets", "ec2:DescribeSecurityGroups" ], "Resource": ["*"] }, { "Sid": "ViewVpcLatticeResources", "Effect": "Allow", "Action": [ "vpc-lattice:ListResourceConfigurations", "vpc-lattice:GetResourceConfiguration", "vpc-lattice:GetResourceGateway" ], "Resource": ["*"] }, { "Sid": "ManageVpcEndpointsViaDeadline", "Effect": "Allow", "Action": [ "ec2:CreateVpcEndpoint", "ec2:DescribeVpcEndpoints", "ec2:DeleteVpcEndpoints", "ec2:CreateTags" ], "Resource": ["*"], "Condition": { "StringEquals": { "aws:CalledViaFirst": "deadline.amazonaws.com" } } }, { "Sid": "ChooseJobAttachmentsBucket", "Effect": "Allow", "Action": ["s3:GetBucketLocation", "s3:ListAllMyBuckets"], "Resource": "*" }, { "Sid": "CreateDeadlineCloudLogGroups", "Effect": "Allow", "Action": ["logs:CreateLogGroup"], "Resource": "arn:aws:logs:*:*:log-group:/aws/deadline/*", "Condition": { "StringLike": { "aws:CalledViaFirst": "deadline.amazonaws.com" } } }, { "Sid": "ValidateDependencies", "Effect": "Allow", "Action": ["s3:ListBucket"], "Resource": "*", "Condition": { "StringLike": { "aws:CalledViaFirst": "deadline.amazonaws.com" } } }, { "Sid": "RoleSelection", "Effect": "Allow", "Action": ["iam:GetRole", "iam:ListRoles"], "Resource": "*" }, { "Sid": "PassRoleToDeadlineCloud", "Effect": "Allow", "Action": ["iam:PassRole"], "Condition": { "StringLike": { "iam:PassedToService": "deadline.amazonaws.com" } }, "Resource": "*" }, { "Sid": "KMSKeySelection", "Effect": "Allow", "Action": ["kms:ListKeys", "kms:ListAliases"], "Resource": "*" }, { "Sid": "IdentityStoreReadOnly", "Effect": "Allow", "Action": [ "identitystore:DescribeUser", "identitystore:DescribeGroup", "identitystore:ListGroups", "identitystore:ListUsers", "identitystore:IsMemberInGroups", "identitystore:ListGroupMemberships", "identitystore:ListGroupMembershipsForMember", "identitystore:GetGroupMembershipId" ], "Resource": "*" }, { "Sid": "OrganizationAndIdentityCenterIdentification", "Effect": "Allow", "Action": [ "sso:ListDirectoryAssociations", "organizations:DescribeAccount", "organizations:DescribeOrganization", "sso:DescribeRegisteredRegions", "sso:GetManagedApplicationInstance", "sso:GetSharedSsoConfiguration", "sso:ListInstances", "sso:GetApplicationAssignmentConfiguration", "sso:GetSSOStatus", "sso:ListRegions", "sso:DescribeRegion" ], "Resource": "*" }, { "Sid": "ManagedDeadlineCloudIDCApplication", "Effect": "Allow", "Action": [ "sso:CreateApplication", "sso:PutApplicationAssignmentConfiguration", "sso:PutApplicationAuthenticationMethod", "sso:PutApplicationGrant", "sso:DeleteApplication", "sso:UpdateApplication" ], "Resource": "*", "Condition": { "StringLike": { "aws:CalledViaFirst": "deadline.amazonaws.com" } } }, { "Sid": "ChooseSecret", "Effect": "Allow", "Action": ["secretsmanager:ListSecrets"], "Resource": "*" }, { "Sid": "DeadlineMembershipActions", "Effect": "Allow", "Action": [ "deadline:AssociateMemberToFarm", "deadline:AssociateMemberToFleet", "deadline:AssociateMemberToQueue", "deadline:AssociateMemberToJob", "deadline:DisassociateMemberFromFarm", "deadline:DisassociateMemberFromFleet", "deadline:DisassociateMemberFromQueue", "deadline:DisassociateMemberFromJob", "deadline:ListFarmMembers", "deadline:ListFleetMembers", "deadline:ListQueueMembers", "deadline:ListJobMembers" ], "Resource": ["*"] }, { "Sid": "DeadlineControlPlaneActions", "Effect": "Allow", "Action": [ "deadline:CreateMonitor", "deadline:GetMonitor", "deadline:UpdateMonitor", "deadline:DeleteMonitor", "deadline:ListMonitors", "deadline:CreateFarm", "deadline:GetFarm", "deadline:UpdateFarm", "deadline:DeleteFarm", "deadline:ListFarms", "deadline:CreateQueue", "deadline:GetQueue", "deadline:UpdateQueue", "deadline:DeleteQueue", "deadline:ListQueues", "deadline:CreateFleet", "deadline:GetFleet", "deadline:UpdateFleet", "deadline:DeleteFleet", "deadline:ListFleets", "deadline:ListWorkers", "deadline:CreateQueueFleetAssociation", "deadline:GetQueueFleetAssociation", "deadline:UpdateQueueFleetAssociation", "deadline:DeleteQueueFleetAssociation", "deadline:ListQueueFleetAssociations", "deadline:CreateQueueEnvironment", "deadline:GetQueueEnvironment", "deadline:UpdateQueueEnvironment", "deadline:DeleteQueueEnvironment", "deadline:ListQueueEnvironments", "deadline:CreateLimit", "deadline:GetLimit", "deadline:UpdateLimit", "deadline:DeleteLimit", "deadline:ListLimits", "deadline:CreateQueueLimitAssociation", "deadline:GetQueueLimitAssociation", "deadline:DeleteQueueLimitAssociation", "deadline:UpdateQueueLimitAssociation", "deadline:ListQueueLimitAssociations", "deadline:CreateStorageProfile", "deadline:GetStorageProfile", "deadline:UpdateStorageProfile", "deadline:DeleteStorageProfile", "deadline:ListStorageProfiles", "deadline:ListStorageProfilesForQueue", "deadline:ListBudgets", "deadline:TagResource", "deadline:UntagResource", "deadline:ListTagsForResource", "deadline:CreateLicenseEndpoint", "deadline:GetLicenseEndpoint", "deadline:DeleteLicenseEndpoint", "deadline:ListLicenseEndpoints", "deadline:ListAvailableMeteredProducts", "deadline:ListMeteredProducts", "deadline:PutMeteredProduct", "deadline:DeleteMeteredProduct" ], "Resource": ["*"] }] } ``` ------ ## Policy to submit jobs to a queue In this example, you create a scoped-down policy that grants permission to submit jobs to a specific queue in a specific farm. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "SubmitJobsFarmAndQueue", "Effect": "Allow", "Action": "deadline:CreateJob", "Resource": "arn:aws:deadline:us-east-1:111122223333:farm/FARM_A/queue/QUEUE_B/job/*" } ] } ``` ------ ## Policy to allow creating a license endpoint In this example, you create a scoped-down policy that grants the required permissions to create and manage license endpoints. Use this policy to create the license endpoint for the VPC associated with your farm. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Sid": "CreateLicenseEndpoint", "Effect": "Allow", "Action": [ "deadline:CreateLicenseEndpoint", "deadline:DeleteLicenseEndpoint", "deadline:GetLicenseEndpoint", "deadline:ListLicenseEndpoints", "deadline:PutMeteredProduct", "deadline:DeleteMeteredProduct", "deadline:ListMeteredProducts", "deadline:ListAvailableMeteredProducts", "ec2:CreateVpcEndpoint", "ec2:DescribeVpcEndpoints", "ec2:DeleteVpcEndpoints" ], "Resource": [ "arn:aws:deadline:*:111122223333:*", "arn:aws:ec2:*:111122223333:vpc-endpoint/*" ] }] } ``` ------ ## Policy to allow monitoring a specific farm queue In this example, you create a scoped-down policy that grants permission to monitor jobs in a specific queue for a specific farm. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Sid": "MonitorJobsFarmAndQueue", "Effect": "Allow", "Action": [ "deadline:SearchJobs", "deadline:ListJobs", "deadline:GetJob", "deadline:SearchSteps", "deadline:ListSteps", "deadline:ListStepConsumers", "deadline:ListStepDependencies", "deadline:GetStep", "deadline:SearchTasks", "deadline:ListTasks", "deadline:GetTask", "deadline:ListSessions", "deadline:GetSession", "deadline:ListSessionActions", "deadline:GetSessionAction" ], "Resource": [ "arn:aws:deadline:us-east-1:123456789012:farm/FARM_A/queue/QUEUE_B", "arn:aws:deadline:us-east-1:123456789012:farm/FARM_A/queue/QUEUE_B/*" ] }] } ``` ------ # AWS managed policies for Deadline Cloud An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles. Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases. You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*. ## AWS managed policy: AWSDeadlineCloud-FleetWorker You can attach the `AWSDeadlineCloud-FleetWorker` policy to your AWS Identity and Access Management (IAM) identities. This policy grants workers in this fleet the permissions that are needed to connect to and receive tasks from the service. **Permissions details** This policy includes the following permissions: + `deadline` – Allows principals to manage workers in a fleet. For a JSON listing of the policy details, see [AWSDeadlineCloud-FleetWorker](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-FleetWorker.html) in the *AWS Managed Policy reference guide*. ## AWS managed policy: AWSDeadlineCloud-WorkerHost You can attach the `AWSDeadlineCloud-WorkerHost` policy to your IAM identities. This policy grants the permissions that are needed to initially connect to the service. It can be used as an Amazon Elastic Compute Cloud (Amazon EC2) instance profile. **Permissions details** This policy includes the following permissions: + `deadline` – Allows the user to create workers, assume the fleet role for workers, and apply tags to workers For a JSON listing of the policy details, see [AWSDeadlineCloud-WorkerHost](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-WorkerHost.html) in the *AWS Managed Policy reference guide*. ## AWS managed policy: AWSDeadlineCloud-UserAccessFarms You can attach the `AWSDeadlineCloud-UserAccessFarms` policy to your IAM identities. This policy allows users to access farm data based on the farms that they are members of and their membership level. **Permissions details** This policy includes the following permissions: + `deadline` – Allows the user to access farm data. + `ec2` – Allows users to see details about Amazon EC2 instance types. + `identitystore` – Allows users to see user and group names. + `kms` – Allows users to configure AWS Key Management Service (AWS KMS) customer-managed keys for their AWS IAM Identity Center (IAM Identity Center) instance. For a JSON listing of the policy details, see [AWSDeadlineCloud-UserAccessFarms](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessFarms.html) in the *AWS Managed Policy reference guide*. ## AWS managed policy: AWSDeadlineCloud-UserAccessFleets You can attach the `AWSDeadlineCloud-UserAccessFleets` policy to your IAM identities. This policy allows users to access fleet data based on the farms that they are members of and their membership level. **Permissions details** This policy includes the following permissions: + `deadline` – Allows the user to access farm data. + `ec2` – Allows users to see details about Amazon EC2 instance types. + `identitystore` – Allows users to see user and group names. For a JSON listing of the policy details, see [AWSDeadlineCloud-UserAccessFleets](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessFleets.html) in the *AWS Managed Policy reference guide*. ## AWS managed policy: AWSDeadlineCloud-UserAccessJobs You can attach the `AWSDeadlineCloud-UserAccessJobs` policy to your IAM identities. This policy allows users to access job data based on the farms that they are members of and their membership level. **Permissions details** This policy includes the following permissions: + `deadline` – Allows the user to access farm data. + `ec2` – Allows users to see details about Amazon EC2 instance types. + `identitystore` – Allows users to see user and group names. For a JSON listing of the policy details, see [AWSDeadlineCloud-UserAccessJobs](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessJobs.html) in the *AWS Managed Policy reference guide*. ## AWS managed policy: AWSDeadlineCloud-UserAccessQueues You can attach the `AWSDeadlineCloud-UserAccessQueues` policy to your IAM identities. This policy allows users to access queue data based on the farms that they are members of and their membership level. **Permissions details** This policy includes the following permissions: + `deadline` – Allows the user to access farm data. + `ec2` – Allows users to see details about Amazon EC2 instance types. + `identitystore` – Allows users to see user and group names. For a JSON listing of the policy details, see [AWSDeadlineCloud-UserAccessQueues](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessQueues.html) in the *AWS Managed Policy reference guide*. ## Deadline Cloud updates to AWS managed policies View details about updates to AWS managed policies for Deadline Cloud since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the Deadline Cloud Document history page. | Change | Description | Date | | --- | --- | --- | | [AWSDeadlineCloud-UserAccessFarms](#security-iam-awsmanpol-UserAccessFarms) – Change | Deadline Cloud added new action `kms:Decrypt` so you can use an AWS KMS customer-managed key with your IAM Identity Center instance. | December 22, 2025 | | [AWSDeadlineCloud-WorkerHost](#security-iam-awsmanpol-WorkerHost) – Change | Deadline Cloud added new actions `deadline:TagResource` and `deadline:ListTagsForResource` to allow you to add and view tags associated with workers in your fleet. | May 30, 2025 | | [AWSDeadlineCloud-UserAccessFarms](#security-iam-awsmanpol-UserAccessFarms) – Change[AWSDeadlineCloud-UserAccessJobs](#security-iam-awsmanpol-UserAccessJobs) – Change[AWSDeadlineCloud-UserAccessQueues](#security-iam-awsmanpol-UserAccessQueues) – Change | Deadline Cloud added new actions `deadline:GetJobTemplate` and `deadline:ListJobParameterDefinitions` to allow you to resubmit jobs. | October 7, 2024 | | Deadline Cloud started tracking changes | Deadline Cloud started tracking changes to its AWS managed policies. | April 2, 2024 | # Service roles ## How Deadline Cloud uses IAM service roles Deadline Cloud automatically assumes IAM roles and provides temporary credentials to workers, jobs, and the Deadline Cloud monitor. This approach eliminates manual credential management while maintaining security through role-based access control. When you create monitors, fleets, and queues, you specify IAM roles that Deadline Cloud assumes on your behalf. Workers and the Deadline Cloud monitor then receive temporary credentials from these roles to access AWS services. ## Fleet role Configure a fleet role to give Deadline Cloud workers the permissions they need to receive work and report progress on that work. You usually do not have to configure this role yourself. This role can be created for you in the Deadline Cloud console to include the necessary permissions. Use the following guide to understand the specifics of this role for troubleshooting. When creating or updating fleets programmatically, specify the fleet role ARN using the `CreateFleet` or `UpdateFleet` API operations. ### What the fleet role does The fleet role provides workers with permissions to: + Receive new work and report progress on ongoing work to the Deadline Cloud service + Manage worker lifecycle and status + Record log events to Amazon CloudWatch Logs for the worker logs ### Set up the fleet role trust policy Your fleet role must trust the Deadline Cloud service and be scoped to your specific farm. As a best practice, the trust policy should include security conditions for Confused Deputy protection. To learn more about Confused Deputy protection, see [Confused Deputy](cross-service-confused-deputy-prevention.md) in the *Deadline Cloud User Guide*. + `aws:SourceAccount` ensures only resources from the same AWS account can assume this role. + `aws:SourceArn` restricts role assumption to a specific Deadline Cloud farm. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowDeadlineCredentialsService", "Effect": "Allow", "Action": "sts:AssumeRole", "Principal": { "Service": "credentials.deadline.amazonaws.com" }, "Condition": { "StringEquals": { "aws:SourceAccount": "YOUR_ACCOUNT_ID" }, "ArnEquals": { "aws:SourceArn": "arn:aws:deadline:REGION:YOUR_ACCOUNT_ID:farm/YOUR_FARM_ID" } } } ] } ``` ### Attach the Fleet role permissions Attach the following AWS managed policy to your fleet role: [AWSDeadlineCloud-FleetWorker](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-FleetWorker.html) This managed policy provides permissions for: + `deadline:AssumeFleetRoleForWorker` - Allows workers to refresh their credentials. + `deadline:UpdateWorker` - Allows workers to update their status (for example, to STOPPED when exiting). + `deadline:UpdateWorkerSchedule` - For obtaining work and reporting progress. + `deadline:BatchGetJobEntity` - For fetching job information. + `deadline:AssumeQueueRoleForWorker` - For accessing queue role credentials during job execution. ### Add KMS permissions for encrypted farms If your farm was created using a KMS key, add these permissions to your fleet role to ensure the worker can access encrypted data in the farm. The KMS permissions are only necessary if your farm has an associated KMS key. The `kms:ViaService` condition must use the format `deadline.{region}.amazonaws.com`. When creating a fleet, a CloudWatch Logs log group is created for that fleet. The worker's permissions are used by the Deadline Cloud service to create a log stream specifically for that particular worker. After the worker is set up and running, the worker will use these permissions to send log events directly to CloudWatch Logs. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "CreateLogStream", "Effect": "Allow", "Action": [ "logs:CreateLogStream" ], "Resource": "arn:aws:logs:REGION:YOUR_ACCOUNT_ID:log-group:/aws/deadline/YOUR_FARM_ID/*", "Condition": { "ForAnyValue:StringEquals": { "aws:CalledVia": [ "deadline.REGION.amazonaws.com" ] } } }, { "Sid": "ManageLogEvents", "Effect": "Allow", "Action": [ "logs:PutLogEvents", "logs:GetLogEvents" ], "Resource": "arn:aws:logs:REGION:YOUR_ACCOUNT_ID:log-group:/aws/deadline/YOUR_FARM_ID/*" }, { "Sid": "ManageKmsKey", "Effect": "Allow", "Action": [ "kms:Decrypt", "kms:DescribeKey", "kms:GenerateDataKey" ], "Resource": "YOUR_FARM_KMS_KEY_ARN", "Condition": { "StringEquals": { "kms:ViaService": "deadline.REGION.amazonaws.com" } } } ] } ``` ### Modifying the fleet role Permissions for the fleet role are not customizable. The described permissions are always required and adding additional permissions has no effect. ## Customer-managed fleet host role Set up a WorkerHost role if you use customer-managed fleets on Amazon EC2 instances or on-premises hosts. ### What the WorkerHost role does The WorkerHost role bootstraps workers on customer-managed fleet hosts. It provides the minimal permissions needed for a host to: + Create a worker in Deadline Cloud + Assume the fleet role to fetch operational credentials + Tag workers with fleet tags (if tag propagation is enabled) ### Set up WorkerHost role permissions Attach the following AWS managed policy to your WorkerHost role: [AWSDeadlineCloud-WorkerHost](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-WorkerHost.html) This managed policy provides permissions for: + `deadline:CreateWorker` - Allows the host to register a new worker. + `deadline:AssumeFleetRoleForWorker` - Allows the host to assume the fleet role. + `deadline:TagResource` - Allows tagging workers during creation (if enabled). + `deadline:ListTagsForResource` - Allows reading fleet tags for propagation. ### Understand the bootstrap process The WorkerHost role is only used during initial worker startup: 1. The worker agent starts on the host using WorkerHost credentials. 1. It invokes `deadline:CreateWorker` to register with Deadline Cloud. 1. It then invokes `deadline:AssumeFleetRoleForWorker` to fetch fleet role credentials. 1. From this point forward, the worker uses only fleet role credentials for all operations. The WorkerHost role is not used after the worker starts running. This policy is not required for Service-managed fleets. In Service-managed fleets, bootstrapping is performed automatically. ## Queue role The queue role is assumed by the worker when processing a task. This role provides the permissions needed to complete the task. When creating or updating queues programmatically, specify the queue role ARN using the `CreateQueue` or `UpdateQueue` API operations. ### Set up the queue role trust policy Your queue role must trust the Deadline Cloud service. As a best practice, the trust policy should include security conditions for Confused Deputy protection. To learn more about Confused Deputy protection, see [Confused Deputy](cross-service-confused-deputy-prevention.md) in the *Deadline Cloud User Guide*. + `aws:SourceAccount` ensures only resources from the same AWS account can assume this role. + `aws:SourceArn` restricts role assumption to a specific Deadline Cloud farm. ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "credentials.deadline.amazonaws.com", "deadline.amazonaws.com" ] }, "Action": "sts:AssumeRole", "Condition": { "StringEquals": { "aws:SourceAccount": "YOUR_ACCOUNT_ID" }, "ArnEquals": { "aws:SourceArn": "arn:aws:deadline:us-west-2:123456789012:farm/{farm-id}" } } } ] } ``` ### Understand queue role permissions The queue role doesn't use a single managed policy. Instead, when you configure your queue in the console, Deadline Cloud creates a custom policy for your queue based on your configuration. This automatically created policy provides access to: #### Job attachments Read and write access to your specified Amazon S3 bucket for job input and output files: ``` { "Effect": "Allow", "Action": [ "s3:GetObject", "s3:PutObject", "s3:ListBucket", "s3:GetBucketLocation" ], "Resource": [ "arn:aws:s3:::YOUR_JOB_ATTACHMENTS_BUCKET", "arn:aws:s3:::YOUR_JOB_ATTACHMENTS_BUCKET/YOUR_PREFIX/*" ], "Condition": { "StringEquals": { "aws:ResourceAccount": "YOUR_ACCOUNT_ID" } } } ``` #### Job logs Read access to CloudWatch Logs for jobs in this queue. Each queue has its own log group and each session has its own log stream: ``` { "Effect": "Allow", "Action": [ "logs:GetLogEvents" ], "Resource": "arn:aws:logs:REGION:YOUR_ACCOUNT_ID:log-group:/aws/deadline/YOUR_FARM_ID/*" } ``` #### Third-party software Access to download third-party software supported by Deadline Cloud (such as Maya, Blender, and others): ``` { "Effect": "Allow", "Action": [ "s3:ListBucket", "s3:GetObject" ], "Resource": "*", "Condition": { "ArnLike": { "s3:DataAccessPointArn": "arn:aws:s3:*:*:accesspoint/deadline-software-*" }, "StringEquals": { "s3:AccessPointNetworkOrigin": "VPC" } } } ``` ### Add permissions for your jobs Add permissions to your queue role for AWS services that your jobs need to access. When writing OpenJobDescription step scripts, the AWS CLI and SDK will automatically use credentials from your queue role. Use this to access additional services needed to complete your job. Example use cases include: + for fetching custom data + SSM permissions to tunnel to a custom license server + CloudWatch for emitting custom metrics + Deadline Cloud permission to create new jobs for dynamic workflows ### How queue role credentials are used Deadline Cloud provides queue role credentials to: + Workers during job execution + Users via Deadline Cloud CLI and monitor when interacting with job attachments and logs Deadline Cloud creates separate CloudWatch Logs log groups for each queue. Jobs use queue role credentials to write logs to their queue's log group. The Deadline Cloud CLI and monitor use the queue role (through `deadline:AssumeQueueRoleForRead`) to read job logs from the queue's log group. The Deadline Cloud CLI and monitor use the queue role (through `deadline:AssumeQueueRoleForUser`) to upload or download job attachments data. ## Monitor role Configure a monitor role to give the Deadline Cloud monitor web and desktop applications access to your Deadline Cloud resources. When creating or updating monitors programmatically, specify the monitor role ARN using the `CreateMonitor` or `UpdateMonitor` API operations. ### What the monitor role does The monitor role enables Deadline Cloud monitor to provide end users with access to: + Basic functionality required for the Deadline Cloud Integrated Submitters, CLI and monitor + Custom functionality for end users ### Set up the monitor role trust policy Your monitor role must trust the Deadline Cloud service. As a best practice, the trust policy should include security conditions for Confused Deputy protection. To learn more about Confused Deputy protection, see [Confused Deputy](cross-service-confused-deputy-prevention.md) in the *Deadline Cloud User Guide*. `aws:SourceAccount` ensures only resources from the same AWS account can assume this role. ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "credentials.deadline.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "StringEquals": { "aws:SourceAccount": "YOUR_ACCOUNT_ID" } } } ] } ``` ### Attach monitor role permissions Attach all of the following AWS managed policies to your monitor role for basic operation: + [AWSDeadlineCloud-UserAccessFarms](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessFarms.html) + [AWSDeadlineCloud-UserAccessFleets](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessFleets.html) + [AWSDeadlineCloud-UserAccessJobs](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessJobs.html) + [AWSDeadlineCloud-UserAccessQueues](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSDeadlineCloud-UserAccessQueues.html) ### How the monitor role works When using the Deadline Cloud monitor, a service user signs in using AWS IAM Identity Center (IAM Identity Center), and the monitor role is assumed. The assumed role credentials are used by the monitor application to display the monitor UI, including the list of farms, fleets, queues, and other information. When using the Deadline Cloud monitor desktop application, these credentials are additionally made available on the workstation using a named AWS credential profile corresponding to the profile name provided by the end user. Learn more about named profiles in the [AWS SDK and Tools reference guide](https://docs.aws.amazon.com/sdkref/latest/guide/file-format.html). This named profile is how the Deadline CLI and submitters access Deadline Cloud resources. ### Customizing the monitor role for advanced use cases You can customize the monitor role to modify what users can do at each access level (Viewer, Contributor, Manager, Owner) or to add permissions for advanced workflows. #### Customizing access level permissions The four AWS managed policies attached to the monitor role control what each access level can do. You can add custom policies to the monitor role to grant or restrict permissions for specific access levels using the `deadline:MembershipLevel` condition key. For example, to allow Contributors to update and cancel jobs (which is normally restricted to Managers and Owners), add a policy like the following: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "deadline:UpdateJob", "Resource": "*", "Condition": { "StringEquals": { "deadline:MembershipLevel": "CONTRIBUTOR" } } } ] } ``` With this policy, Contributors can update and cancel jobs in addition to submitting them. #### Adding permissions for advanced workflows You can add custom IAM policies to the monitor role to grant additional permissions to all monitor users. This is useful for advanced scripting workflows where users need access to AWS services beyond the standard Deadline Cloud functionality. Follow these guidelines when modifying your monitor role: + Don't remove any of the managed policies. Removing these policies breaks monitor functionality. ### How Deadline Cloud monitor uses monitor role credentials Deadline Cloud monitor automatically obtains monitor role credentials when you authenticate. This capability enables the desktop application to provide enhanced monitoring capabilities beyond what's available in a standard web browser. When you log in with Deadline Cloud monitor, it automatically creates a profile that you can use with the AWS CLI or any other AWS tool. This profile uses the monitor role credentials, giving you programmatic access to AWS services based on the permissions in your monitor role. Deadline Cloud submitters work the same way - they use the profile created by Deadline Cloud monitor to access AWS services with the appropriate role permissions. ## Advanced customization of Deadline Cloud roles You can extend Deadline Cloud roles with additional permissions to enable advanced use cases beyond basic rendering workflows. This approach leverages Deadline Cloud's access management system to control access to additional AWS services based on queue membership. ### Team collaboration with AWS CodeCommit Add AWS CodeCommit permissions to your Queue role to enable team collaboration on project repositories. This approach uses Deadline Cloud's access management system for additional use cases - only users with access to the specific queue will receive these AWS CodeCommit permissions, allowing you to manage per-project repository access through Deadline Cloud queue membership. This is useful for scenarios where artists need to access project-specific assets, scripts, or configuration files stored in AWS CodeCommit repositories as part of their rendering workflow. #### Add AWS CodeCommit permissions to queue role Add the following permissions to your queue role to enable AWS CodeCommit access: ``` { "Effect": "Allow", "Action": [ "codecommit:GitPull", "codecommit:GitPush", "codecommit:GetRepository", "codecommit:ListRepositories" ], "Resource": "arn:aws:codecommit:REGION:YOUR_ACCOUNT_ID:PROJECT_REPOSITORY" } ``` #### Set up credential provider on artist workstations Configure each artist workstation to use Deadline Cloud queue credentials for AWS CodeCommit access. This setup is done once per workstation. **To configure the credential provider** 1. Add a credential provider profile to your AWS config file (`~/.aws/config`): ``` [profile queue-codecommit] credential_process = deadline queue export-credentials --farm-id farm-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --queue-id queue-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ``` 1. Configure Git to use this profile for AWS CodeCommit repositories: ``` git config --global credential.https://git-codecommit---REGION.amazonaws.com.rproxy.goskope.com.helper '!aws codecommit credential-helper --profile queue-codecommit $@' git config --global credential.https://git-codecommit---REGION.amazonaws.com.rproxy.goskope.com.UseHttpPath true ``` Replace *farm-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX* and *queue-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX* with your actual farm and queue IDs. Replace *REGION* with your AWS region (for example, `us-west-2`). #### Using AWS CodeCommit with queue credentials Once configured, Git operations will automatically use the queue role credentials when accessing AWS CodeCommit repositories. The `deadline queue export-credentials` command returns temporary credentials that look like this: ``` { "Version": 1, "AccessKeyId": "ASIA...", "SecretAccessKey": "...", "SessionToken": "...", "Expiration": "2025-11-10T23:02:23+00:00" } ``` These credentials are automatically refreshed as needed, and Git operations will work seamlessly: ``` git clone https://git-codecommit.REGION.amazonaws.com/v1/repos/PROJECT_REPOSITORY git pull git push ``` Artists can now access project repositories using their queue permissions without needing separate AWS CodeCommit credentials. Only users with access to the specific queue will be able to access the associated repository, enabling fine-grained access control through Deadline Cloud's queue membership system. # Troubleshooting AWS Deadline Cloud identity and access Use the following information to help you diagnose and fix common issues that you might encounter when working with Deadline Cloud and IAM. **Topics** + [I am not authorized to perform an action in Deadline Cloud](#security_iam_troubleshoot-no-permissions) + [I am not authorized to perform iam:PassRole](#security_iam_troubleshoot-passrole) + [I want to allow people outside of my AWS account to access my Deadline Cloud resources](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in Deadline Cloud If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-example-widget` resource but doesn't have the fictional `deadline:GetWidget` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: deadline:GetWidget on resource: my-example-widget ``` In this case, the policy for the `mateojackson` user must be updated to allow access to the `my-example-widget` resource by using the `deadline:GetWidget` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to Deadline Cloud. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in Deadline Cloud. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. ``` User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole ``` In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I want to allow people outside of my AWS account to access my Deadline Cloud resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether Deadline Cloud supports these features, see [How Deadline Cloud works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.