1. Navigate to the Amazon EMR console:
   • Open the AWS Management Console.
   • Go to the Amazon EMR console by searching for “EMR” in the services search bar.
2. Select the EMR cluster:
   • Select the EMR cluster that is not in a VPC.
3. Update the cluster settings:
   • Click on the “Edit” button or navigate to the “Hardware” tab in the cluster details.
   • Scroll down to the “Network and Security” section.
4. Select VPC and Subnet:
   • Under the “Network and Security” section, choose the VPC where you want to place the EMR cluster.
   • Select a subnet within the chosen VPC.
5. Configure security groups:
   • Review and update the security groups associated with the EMR cluster to ensure proper network access controls.
6. Save the changes:
   • Click on the “Save” or “Update” button to apply the changes to the EMR cluster.
7. Verify the VPC configuration:
   • After saving the changes, verify that the EMR cluster is now running within the specified VPC by checking the cluster details.

​

1. Create a VPC (if not already created): Use the following AWS CLI command to create a VPC:
   aws ec2 create-vpc --cidr-block 10.0.0.0/16
   
2. Create Subnets within the VPC: Create at least two subnets in different Availability Zones within the VPC using the following command:
   aws ec2 create-subnet --vpc-id <your-vpc-id> --cidr-block 10.0.1.0/24 --availability-zone <az1>
   aws ec2 create-subnet --vpc-id <your-vpc-id> --cidr-block 10.0.2.0/24 --availability-zone <az2>
   
3. Create an Internet Gateway (IGW) and attach it to the VPC:
   aws ec2 create-internet-gateway
   aws ec2 attach-internet-gateway --vpc-id <your-vpc-id> --internet-gateway-id <your-igw-id>
   
4. Create Route Tables and associate them with the subnets:
   aws ec2 create-route-table --vpc-id <your-vpc-id>
   aws ec2 associate-route-table --route-table-id <your-route-table-id> --subnet-id <your-subnet-id>
   
5. Create Security Groups for EMR Clusters: Create a security group for EMR clusters that allows necessary inbound and outbound traffic using the following command:
   aws ec2 create-security-group --group-name EMR-SG --description "Security Group for EMR Clusters" --vpc-id <your-vpc-id>
   
6. Launch EMR Cluster within the VPC: Launch the EMR cluster within the VPC and specify the security group and subnets created earlier using the AWS Management Console or AWS CLI.
7. Verify the Configuration: Use the following command to describe the EMR cluster and verify that it is running within the VPC:
   aws emr describe-cluster --cluster-id <your-cluster-id>
   

1. Create a VPC:
   • Use the AWS SDK for Python (Boto3) to create a new Virtual Private Cloud (VPC) in your AWS account.
   • You can use the create_vpc method from the ec2 client in Boto3 to create a VPC.
2. Create Subnets:
   • Create one or more subnets within the VPC. Make sure the subnets are in different availability zones for high availability.
   • Use the create_subnet method from the ec2 client in Boto3 to create subnets.
3. Create an Internet Gateway (IGW):
   • Attach an Internet Gateway to the VPC to allow internet access for resources within the VPC.
   • Use the create_internet_gateway method from the ec2 client in Boto3 to create an Internet Gateway.
4. Create Route Tables:
   • Create route tables for the public and private subnets within the VPC.
   • Use the create_route_table method from the ec2 client in Boto3 to create route tables.
5. Associate Subnets with Route Tables:
   • Associate the subnets with their respective route tables to control the routing of network traffic.
   • Use the associate_route_table method from the ec2 client in Boto3 to associate subnets with route tables.
6. Launch EMR Cluster in VPC:
   • When launching an EMR cluster using Boto3, specify the Ec2SubnetId parameter to launch the cluster within the VPC.
   • Set the Ec2SubnetId parameter to the ID of the subnet where you want to launch the EMR cluster.

import boto3

# Create a VPC
ec2 = boto3.client('ec2')
vpc = ec2.create_vpc(CidrBlock='10.0.0.0/16')

# Create a subnet
subnet = ec2.create_subnet(VpcId=vpc['Vpc']['VpcId'], CidrBlock='10.0.0.0/24', AvailabilityZone='us-east-1a')

# Create an Internet Gateway
igw = ec2.create_internet_gateway()
ec2.attach_internet_gateway(InternetGatewayId=igw['InternetGateway']['InternetGatewayId'], VpcId=vpc['Vpc']['VpcId'])

# Create a route table
route_table = ec2.create_route_table(VpcId=vpc['Vpc']['VpcId'])

# Associate subnet with route table
ec2.associate_route_table(RouteTableId=route_table['RouteTable']['RouteTableId'], SubnetId=subnet['Subnet']['SubnetId'])

# Launch EMR cluster within the VPC
emr = boto3.client('emr')
response = emr.run_job_flow(
    Name='MyEMRCluster',
    ReleaseLabel='emr-6.2.0',
    Instances={
        'Ec2SubnetId': subnet['Subnet']['SubnetId'],
        'EmrManagedMasterSecurityGroup': 'sg-12345678',
        'EmrManagedSlaveSecurityGroup': 'sg-12345678',
        'InstanceGroups': [
            {
                'InstanceRole': 'MASTER',
                'InstanceType': 'm5.xlarge',
                'InstanceCount': 1
            }
        ]
    },
    VisibleToAllUsers=True
)

resource "aws_emr_cluster" "THIS_EMR_CLUSTER" {
  name          = "REPLACE_WITH_CLUSTER_NAME"
  release_label = "REPLACE_WITH_EMR_RELEASE" # e.g. "emr-7.2.0"
  applications  = ["Hadoop"]

  # Ensure the cluster runs in a VPC by assigning a subnet in your VPC
  ec2_attributes {
    subnet_id = aws_subnet.EMR_SUBNET.id
  }

  master_instance_type = "m5.xlarge"
  core_instance_type   = "m5.xlarge"
  core_instance_count  = 2

  service_role = aws_iam_role.EMR_SERVICE_ROLE.arn
  role_arn     = aws_iam_role.EMR_EC2_INSTANCE_PROFILE_ROLE.arn
}

resource "aws_subnet" "EMR_SUBNET" {
  vpc_id                  = aws_vpc.EMR_VPC.id
  cidr_block              = "REPLACE_WITH_SUBNET_CIDR" # e.g. "10.0.1.0/24"
  availability_zone       = "REPLACE_WITH_AZ"          # e.g. "us-east-1a"
  map_public_ip_on_launch = false
}

resource "aws_vpc" "EMR_VPC" {
  cidr_block           = "REPLACE_WITH_VPC_CIDR" # e.g. "10.0.0.0/16"
  enable_dns_support   = true
  enable_dns_hostnames = true
}

• REPLACE_WITH_CLUSTER_NAME with your EMR cluster name.
• REPLACE_WITH_EMR_RELEASE with a supported EMR release label.
• REPLACE_WITH_VPC_CIDR / REPLACE_WITH_SUBNET_CIDR with your network ranges.
• REPLACE_WITH_AZ with an AZ in your region.
• Wire aws_iam_role.EMR_SERVICE_ROLE and aws_iam_role.EMR_EC2_INSTANCE_PROFILE_ROLE to your existing IAM roles or define them separately.