Use AWS Glue Network Connection to call APIs in Glue Jobs

   Go back to the Task List

  [« 1. Pre-requisite ]    [3. Create IAM Role »]

2. Create the VPC

You first create a VPC with a private and a public subnet. You need a VPC because the AWS Glue Job needs an Amazon Elastic network interfaces (ENI) to call the REST API over internet. The ENI is created in the private subnet with NAT Gateway using AWS Glue connection. NAT Gateway will enable outbound call to the REST API.

  1. Login to the AWS Console. Select an AWS Region of your choice where AWS Glue is available as a service. You will see the exercise instructions using the Paris region. Go to the VPC Management Console. Click on the Elastic IPs menu item in the left and then click on the Allocate Elastic IP address button.

    Elastic IPs Menu

  2. On the next screen, click on the Allocate button. An Elastic IP address is created which you will use for the NAT Gateway when creating the VPC.

    Allocate IP

  3. On the VPC Management Console and click on the Launch VPC Wizard button.

    VPC Wizard

  4. On the next screen, select VPC with Public and Private Subnets choice and click on the Select button.

    VPC Choice

  5. On the next screen, enter GlueVPC as the VPC Name and select the Elastic IP address (created in the previous steps) for the Elastic IP Allocation ID field. Keep rest of the values as default and click on the Create VPC button.

    Create VPC

  6. The VPC will be created in couple of minutes. Please wait for it to finish. You will use VPC private subnet and the default security group later to create ENI to call the REST API using AWS Glue Connection.

  7. The next task is to create an IAM Role which is used by the Glue Job and Connection.