Troubleshooting EMR Serverless identity and access - Amazon EMR
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Troubleshooting EMR Serverless identity and access

Use the following information to help you diagnose and fix common issues that you might encounter when working with Amazon EMR Serverless and IAM.

I am not authorized to perform an action in EMR Serverless

If the error message indicates you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password.

The following example error occurs when the mateojackson IAM user tries to use the console to view details about a fictional list-applications resource but does not have the emr-serverless:ListApplications permissions.

An error occurred (AccessDeniedException) when calling the ListApplications operation: User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: emr-serverless:ListApplications on resource: arn:aws:emr-serverless:us-east-1:123456789012:/*

In this case, Mateo asks his administrator to update his policies to allow him to access the list-applications operation using the emr-serverless:ListApplications action. For more information, see Job runtime roles.

I am not able to invoke StartJobRun

If the Amazon Web Services Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password.

The following example error occurs when the mateojackson IAM user tries to invoke StartJobRun resource but does not have the iam:PassRole permissions.

arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: iam:PassRole on resource: arn:aws:iam::123456789012:role/JobExecutionRole

In this case, Mateo asks his administrator to update his policies to allow him to pass the arn:aws:iam::123456789012:role/JobExecutionRole role for the iam:PassRole action and attach it to mateojackson IAM user. For more information, see Job runtime roles

My job fails with error could not assume execution role

The following is an example error message that you'd see when the job execution role passed to the StartJobRun API is not set up properly.

Could not assume execution role arn:aws:iam::123456789012:user/JobExecutionRole because it does not exist or is not set up with the required trust relationship

If this happens, validate that the IAM Role specified by the executionRoleArn parameter passed to the StartJobRun API call exists in the account which is invoking the StartJobRun API. If the IAM Role exists, validate that the role’s trust policy has been set up properly by following instructions in Job runtime roles.

I want to view my access keys

After you create your IAM user access keys, you can view your access key ID at any time. However, you can't view your secret access key again. If you lose your secret key, you must create a new access key pair.

Access keys consist of two parts: an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access key (for example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY). Like a user name and password, you must use both the access key ID and secret access key together to authenticate your requests. Manage your access keys as securely as you do your user name and password.

Important

Do not provide your access keys to a third party, even to help find your canonical user ID. By doing this, you might give someone permanent access to your account.

When you create an access key pair, you are prompted to save the access key ID and secret access key in a secure location. The secret access key is available only at the time you create it. If you lose your secret access key, you must add new access keys to your IAM user. You can have a maximum of two access keys. If you already have two, you must delete one key pair before creating a new one. To view instructions, see Managing access keys in the IAM User Guide.

I'm an administrator and want to allow others to access EMR Serverless

To allow others to access Amazon EMR Serverless, you must create an IAM entity (user or role) for the person or application that needs access. They will use the credentials for that entity to access Amazon. You must then attach a policy to the entity that grants them the correct permissions in Amazon EMR Serverless.

To get started right away, see Creating your first IAM delegated user and group in the IAM User Guide.

I want to allow people outside of my Amazon account to access my EMR Serverless 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: