Prerequisites and considerations - 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 (PDF).

Prerequisites and considerations


EMR Notebooks are available as EMR Studio Workspaces in the console. The Create Workspace button in the console lets you create new notebooks. To access or create Workspaces, EMR Notebooks users need additional IAM role permissions. For more information, see Amazon EMR Notebooks are Amazon EMR Studio Workspaces in the console and Amazon EMR console.

Consider the following when planning to integrate a Git-based repository with EMR Notebooks.

Amazon CodeCommit

If you use a CodeCommit repository, you must use Git credentials and HTTPS with CodeCommit. SSH Keys, and HTTPS with the Amazon CLI credential helper are not supported. CodeCommit does not support personal access tokens (PATs). For more information, see Using IAM with CodeCommit: Git credentials, SSH keys, and Amazon access keys in the IAM User Guide and Setup for HTTPS users using Git credentials in the Amazon CodeCommit User Guide.

Access and permission considerations

Before associating a repository with your notebook, make sure that your cluster, IAM role for EMR Notebooks, and security groups have the correct settings and permissions. You can also configure Git-based repositories that you host in a private network by following the instructions in Configure a privately-hosted Git repository for EMR Notebooks.

  • Cluster internet access – The network interface that is launched has only a private IP address. This means that the cluster that your notebook connects to must be in a private subnet with a network address translation (NAT) gateway or must be able to access the internet through a virtual private gateway. For more information, see Amazon VPC options.

    The security groups for your notebook must include an outbound rule that allows the notebook to route traffic to the internet from the cluster. We recommend that you create your own security groups. For more information, see Specifying EC2 security groups for EMR Notebooks.


    If the network interface is launched into a public subnet, it won't be able to communicate with the internet through an internet gateway (IGW).

  • Permissions for Amazon Secrets Manager – If you use Secrets Manager to store secrets that you use to access a repository, the Service role for EMR Notebooks must have a permissions policy attached that allows the secretsmanager:GetSecretValue action.

Configure a privately-hosted Git repository for EMR Notebooks

Use the following instructions to configure privately-hosted repositories for EMR Notebooks. You must provide a configuration file with information about your DNS and Git servers. Amazon EMR uses this information to configure EMR notebooks that can route traffic to your privately-hosted repositories.


Before you configure a privately-hosted Git repository for EMR Notebooks, you must have the following:

  • An Amazon S3 Control location where files for your EMR notebook will be saved.

To configure one or more privately-hosted Git repositories for EMR Notebooks
  1. Create a configuration file using the provided template. Include the following values for each Git server that you want to specify in your configuration:

    • DnsServerIpV4- The IPv4 address of your DNS server. If you provide values for both DnsServerIpV4 and GitServerIpV4List, the value for DnsServerIpV4 takes precedence and will be used to resolve your GitServerDnsName.


      To use privately-hosted Git repositories, your DNS server must allow inbound access from EMR Notebooks. We strongly recommend that you secure your DNS server against other, unauthorized access.

    • GitServerDnsName - The DNS name of your Git server. For example "".

    • GitServerIpV4List - A list of IPv4 addresses that belong to your Git server(s).

    [ { "Type": "PrivatelyHostedGitConfig", "Value": [ { "DnsServerIpV4": "<>", "GitServerDnsName": "<>", "GitServerIpV4List": [ "<>", "<>" ] }, { "DnsServerIpV4": "<>", "GitServerDnsName": "<>", "GitServerIpV4List": [ "<>", "<>" ] } ] } ]
  2. Save your configuration file as configuration.json.

  3. Upload the configuration file into your designated Amazon S3 storage location in a folder called life-cycle-configuration. For example, if your default S3 location is s3://DOC-EXAMPLE-BUCKET/notebooks, your configuration file should be located at s3://DOC-EXAMPLE-BUCKET/notebooks/life-cycle-configuration/configuration.json.


    We strongly recommend that you restrict access to your life-cycle-configuration folder to only your EMR Notebooks administrators, and to the service role for EMR Notebooks. You should also secure configuration.json against unauthorized access. For instructions, see Controlling access to a bucket with user policies or Security Best Practices for Amazon S3.

    For upload instructions, see Creating a folder and Uploading objects in the Amazon Simple Storage Service User Guide.