Introducing ability to connect to EMR clusters in different subnets in EMR Studio
Amazon EMR Studio is an integrated development environment (IDE) that makes it easy for data scientists and data engineers to develop, visualize, and debug big data and analytics applications written in R, Python, Scala, and PySpark. Today, we are excited to announce that EMR Studio Workspaces now support connecting to EMR clusters in different subnets that are associated with EMR Studio.
Amazon EMR Studio is an integrated development environment (IDE) that makes it easy for data scientists and data engineers to develop, visualize, and debug big data and analytics applications written in R, Python, Scala, and PySpark. Today, we are excited to announce that EMR Studio Workspaces now support connecting to EMR clusters in different subnets that are associated with EMR Studio.
Previously, you had to select a subnet while creating a Workspace. This meant that the Workspace could access EMR clusters only within that subnet. With this feature, you no longer have to select a subnet for your Workspace. This gives you the flexibility to attach your Workspace to EMR clusters in any of the subnets specified for your Studio. We recommend that during EMR Studio creation, you provide multiple subnets in different Availability Zones to give EMR Studio users access to clusters in different Availability Zones.
EMR Studio is available in US East (Ohio), US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Ireland), Europe (Frankfurt), Europe (London), Europe (Stockholm), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney) , and Asia Pacific (Tokyo) regions.
To learn more about best practices on setting up subnets for EMR Studio, see our documentation here. To learn more about EMR Studio Workspaces, see out documentation here.