Other considerations and known issues - Amazon EMR

Other considerations and known issues

The following list contains other considerations and known issues of EMR Serverless.

  • EMR Serverless is available in the following AWS Regions: Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), South America (São Paulo), US East (N. Virginia), US East (Ohio), US West (N. California), and US West (Oregon). For a list of endpoints associated with these Regions, see Service endpoints.

  • EMR Serverless only supports batch workloads that use job run APIs. EMR Serverless doesn't support interactive workloads from EMR Studio or other notebook services. You can run interactive workloads with EMR on EC2, or EMR on EKS. To learn more on how to enable EMR Studio for interactive workloads with EMR on EC2 or EMR on EKS, see Enable interactive workloads with EMR Studio.

  • The default timeout for a job run is 12 hours. You can change this setting with the executionTimeoutMinutes property in the startJobRun API or the AWS. You can set executionTimeoutMinutes to 0 if you want your job run to never time out. For example, if you have a streaming application, setting executionTimeoutMinutes to 0 will allow the streaming job to run continuously.

  • Without VPC connectivity, a job can access some AWS service endpoints in the same AWS Region. These services include Amazon S3, AWS Glue, Amazon CloudWatch Logs, AWS KMS, AWS Security Token Service, Amazon DynamoDB, and AWS Secrets Manager. You can enable VPC connectivity to access other AWS services through AWS PrivateLink, but you aren't required to do this. To access external services, you can create your application with a VPC.

  • EMR Serverless doesn't support HDFS. The local disks on workers are temporal storage that EMR Serverless uses to shuffle and process data during job runs.

  • EMR Serverless doesn't support the existing emr-dynamodb-connector.