HomeBig DataIntroducing AWS Glue interactive periods for Jupyter

Introducing AWS Glue interactive periods for Jupyter

Interactive Periods for Jupyter is a brand new pocket book interface within the AWS Glue serverless Spark atmosphere. Beginning in seconds and mechanically stopping compute when idle, interactive periods present an on-demand, highly-scalable, serverless Spark backend to Jupyter notebooks and Jupyter-based IDEs resembling Jupyter Lab, Microsoft Visible Studio Code, JetBrains PyCharm, and extra. Interactive periods change AWS Glue growth endpoints for interactive job growth with AWS Glue and affords the next advantages:

  • No clusters to provision or handle
  • No idle clusters to pay for
  • No up-front configuration required
  • No useful resource rivalry for a similar growth atmosphere
  • Simple set up and utilization
  • The very same serverless Spark runtime and platform as AWS Glue extract, remodel, and cargo (ETL) jobs

Getting began with interactive periods for Jupyter

Putting in interactive periods is easy and solely takes just a few terminal instructions. After you put in it, you possibly can run interactive periods anytime inside seconds of deciding to run. Within the following sections, we stroll you thru set up on macOS and getting began in Jupyter.

To get began with interactive periods for Jupyter on Home windows, observe the directions in Getting began with AWS Glue interactive periods.


These directions assume you’re working Python 3.6 or later and have the AWS Command Line Interface (AWS CLI) correctly working and configured. You utilize the AWS CLI to make API calls to AWS Glue. For extra data on putting in the AWS CLI, consult with Putting in or updating the newest model of the AWS CLI.

Set up AWS Glue interactive periods on macOS and Linux

To put in AWS Glue interactive periods, full the next steps:

  1. Open a terminal and run the next to put in and improve Jupyter, Boto3, and AWS Glue interactive periods from PyPi. If desired, you possibly can set up Jupyter Lab as a substitute of Jupyter.
    pip3 set up --user --upgrade jupyter boto3 aws-glue-sessions

  2. Run the next instructions to determine the package deal set up location and set up the AWS Glue PySpark and AWS Glue Spark Jupyter kernels with Jupyter:
    SITE_PACKAGES=$(pip3 present aws-glue-sessions | grep Location | awk '{print $2}')
    jupyter kernelspec set up $SITE_PACKAGES/aws_glue_interactive_sessions_kernel/glue_pyspark
    jupyter kernelspec set up $SITE_PACKAGES/aws_glue_interactive_sessions_kernel/glue_spark

  3. To validate your set up, run the next command:

Within the output, it’s best to see each the AWS Glue PySpark and the AWS Glue Spark kernels listed alongside the default Python3 kernel. It ought to look one thing like the next:

Accessible kernels:
  Python3		~/.venv/share/jupyter/kernels/python3
  glue_pyspark    /usr/native/share/jupyter/kernels/glue_pyspark
  glue_spark      /usr/native/share/jupyter/kernels/glue_spark

Select and put together IAM principals

Interactive periods use two AWS Identification and Entry Administration (IAM) principals (consumer or position) to operate. The primary is used to name the interactive periods APIs and is probably going the identical consumer or position that you simply use with the AWS CLI. The second is GlueServiceRole, the position that AWS Glue assumes to run your session. This is identical position as AWS Glue jobs; if you happen to’re growing a job along with your pocket book, it’s best to use the identical position for each interactive periods and the job you create.

Put together the consumer consumer or position

Within the case of native growth, the primary position is already configured if you happen to can run the AWS CLI. For those who can’t run the AWS CLI, observe these steps for organising. For those who typically use the AWS CLI or Boto3 to work together with AWS Glue and have full AWS Glue permissions, you possibly can probably skip this step.

  1. To validate this primary consumer or position is about up, open a brand new terminal window and run the next code:
    aws sts get-caller-identity

    You need to see a response like the next. If not, it’s possible you’ll not have permissions to name AWS Safety Token Service (AWS STS), otherwise you don’t have the AWS CLI arrange correctly. For those who merely get entry denied calling AWS STS, it’s possible you’ll proceed if you already know your consumer or position and its wanted permissions.

        "Account": "123456789123",
        "Arn": "arn:aws:iam::123456789123:consumer/MyIAMUser"
        "Account": "123456789123",
        "Arn": "arn:aws:iam::123456789123:position/myIAMRole"

  2. Guarantee your IAM consumer or position can name the AWS Glue interactive periods APIs by attaching the AWSGlueConsoleFullAccess managed IAM coverage to your position.

In case your caller identification returned a consumer, run the next:

aws iam attach-user-policy --role-name <myIAMUser> --policy-arn arn:aws:iam::aws:coverage/AWSGlueConsoleFullAccess

In case your caller identification returned a task, run the next:

aws iam attach-role-policy --role-name, --policy-arn arn:aws:iam::aws:coverage/AWSGlueConsoleFullAccess

Put together the AWS Glue service position for interactive periods

You’ll be able to specify the second principal, GlueServiceRole, both within the pocket book itself by utilizing the %iam_role magic or saved alongside the AWS CLI config. You probably have a task that you simply sometimes use with AWS Glue jobs, this will likely be that position. For those who don’t have a task you utilize for AWS Glue jobs, consult with Establishing IAM permissions for AWS Glue to set one up.

To set this position because the default position for interactive periods, edit the AWS CLI credentials file and add glue_role_arn to the profile you plan to make use of.

  1. With a textual content editor, open ~/.aws/credentials.
    On Home windows, use C:Usersusername.awscredentials.
  2. Search for the profile you utilize for AWS Glue; if you happen to don’t use a profile, you’re in search of [Default].
  3. Add a line within the profile for the position you plan to make use of like, glue_role_arn=<AWSGlueServiceRole>.
  4. I like to recommend including a default Area to your profile if one will not be specified already. You are able to do so by including the road area=us-east-1, changing us-east-1 along with your desired Area.
    For those who don’t add a Area to your profile, you’re required to specify the Area on the prime of every pocket book with the %area magic.When completed, your config ought to look one thing like the next:

  5. Save the config.

Begin Jupyter and an AWS Glue PySpark pocket book

To start out Jupyter and your pocket book, full the next steps:

  1. Run the next command in your terminal to open the Jupyter pocket book in your browser:

    Your browser ought to open and also you’re introduced with a web page that appears like the next screenshot.

  2. On the New menu, select Glue PySpark.

A brand new tab opens with a clean Jupyter pocket book utilizing the AWS Glue PySpark kernel.

Configure your pocket book with magics

AWS Glue interactive periods are configured with Jupyter magics. Magics are small instructions prefixed with % firstly of Jupyter cells that present shortcuts to regulate the atmosphere. In AWS Glue interactive periods, magics are used for all configuration wants, together with:

  • %area – Area
  • %profile – AWS CLI profile
  • %iam_role – IAM position for the AWS Glue service position
  • %worker_type – Employee kind
  • %number_of_workers – Variety of employees
  • %idle_timeout – How lengthy to permit a session to idle earlier than stopping it
  • %additional_python_modules – Python libraries to put in from pip

Magics are positioned at first of your first cell, earlier than your code, to configure AWS Glue. To find all of the magics of interactive periods, run %assist in a cell and a full listing is printed. Except for %%sql, working a cell of solely magics doesn’t begin a session, however units the configuration for the session that begins subsequent if you run your first cell of code. For this publish, we use three magics to configure AWS Glue with model 2.0 and two G.2X employees. Let’s enter the next magics into our first cell and run it:

%glue_version 2.0
%number_of_workers 2
%worker_type G.2X
%idle_tiemout 60

Welcome to the Glue Interactive Periods Kernel
For extra data on obtainable magic instructions, please kind %assist in any new cell.

Please view our Getting Began web page to entry probably the most up-to-date data on the Interactive Periods kernel: https://docs.aws.amazon.com/glue/newest/dg/interactive-sessions.html
Setting Glue model to: 2.0
Earlier variety of employees: 5
Setting new variety of employees to: 2
Earlier employee kind: G.1X
Setting new employee kind to: G.2X

Whenever you run magics, the output lets us know the values we’re altering together with their earlier settings. Explicitly setting all of your configuration in magics helps guarantee constant runs of your pocket book each time and is advisable for manufacturing workloads.

Run your first code cell and creator your AWS Glue pocket book

Subsequent, we run our first code cell. That is when a session is provisioned to be used with this pocket book. When interactive periods are correctly configured inside an account, the session is totally remoted to this pocket book. For those who open one other pocket book in a brand new tab, it will get its personal session by itself remoted compute. Run your code cell as follows:

from awsglue.context import GlueContext
from awsglue.job import Job
from awsglue.transforms import *
from awsglue.utils import getResolvedOptions
from pyspark.context import SparkContext

sc = SparkContext.getOrCreate()
glueContext = GlueContext(sc)
spark = glueContext.spark_session
job = Job(glueContext)

Authenticating with profile=default
glue_role_arn outlined by consumer: arn:aws:iam::123456789123:position/AWSGlueServiceRoleForSessions
Making an attempt to make use of current AssumeRole session credentials.
Attempting to create a Glue session for the kernel.
Employee Sort: G.2X
Variety of Employees: 2
Session ID: 12345678-12fa-5315-a234-567890abcdef
Making use of the next default arguments:
--glue_kernel_version 0.31
--enable-glue-datacatalog true
Ready for session 12345678-12fa-5315-a234-567890abcdef to get into prepared standing...
Session 12345678-12fa-5315-a234-567890abcdef has been created

Whenever you ran the primary cell containing code, Jupyter invoked interactive periods, provisioned an AWS Glue cluster, and despatched the code to AWS Glue Spark. The pocket book was given a session ID, as proven within the previous code. We will additionally see the properties used to provision AWS Glue, together with the IAM position that AWS Glue used to create the session, the variety of employees and their kind, and every other choices that have been handed as a part of the creation.

Interactive periods mechanically initialize a Spark session as spark and SparkContext as sc; having Spark able to go saves loads of boilerplate code. Nonetheless, if you wish to convert your pocket book to a job, spark and sc should be initialized and declared explicitly.

Work within the pocket book

Now that we’ve a session up, let’s do some work. On this train, we take a look at inhabitants estimates from the AWS COVID-19 dataset, clear them up, and write the outcomes a desk.

This walkthrough makes use of knowledge from the COVID-19 knowledge lake.

To make the information from the AWS COVID-19 knowledge lake obtainable within the Information Catalog in your AWS account, create an AWS CloudFormation stack utilizing the next template.

For those who’re signed in to your AWS account, deploy the CloudFormation stack by clicking the next Launch stack button:


It fills out many of the stack creation kind for you. All you should do is select Create stack. For directions on making a CloudFormation stack, see Get began.

After I’m engaged on a brand new knowledge integration course of, the very first thing I typically do is determine and preview the datasets I’m going to work on. If I don’t recall the precise location or desk title, I sometimes open the AWS Glue console and search or browse for the desk then return to my pocket book to preview it. With interactive periods, there’s a faster approach to browse the Information Catalog. We will use the %%sql magic to indicate databases and tables with out leaving the pocket book. For this instance, the inhabitants desk I would like in is the COVID-19 dataset however I don’t recall its actual title, so I take advantage of the %%sql magic to look it up:

present tables in `covid-19`  # Bear in mind, dashes in names should be escaped with backticks.

|database|           tableName|isTemporary|
|covid-19|alleninstitute_co...|      false|
|covid-19|alleninstitute_me...|      false|
|covid-19|aspirevc_crowd_tr...|      false|
|covid-19|aspirevc_crowd_tr...|      false|
|covid-19|cdc_moderna_vacci...|      false|
|covid-19|cdc_pfizer_vaccin...|      false|
|covid-19|       country_codes|      false|
|covid-19|  county_populations|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_knowledge_g...|      false|
|covid-19|covid_testing_sta...|      false|
|covid-19|covid_testing_us_...|      false|
|covid-19|covid_testing_us_...|      false|
|covid-19|      covidcast_data|      false|
|covid-19|  covidcast_metadata|      false|
|covid-19|enigma_aggregatio...|      false|
solely displaying prime 20 rows

Trying via the returned listing, we see a desk named county_populations. Let’s choose from this desk, sorting for the most important counties by inhabitants:

choose * from `covid-19`.county_populations type by `inhabitants estimate 2018` desc restrict 10

|            id|  id2|         county|      state|inhabitants estimate 2018|
|            Id|  Id2|         County|      State|    Inhabitants Estima...|
|0500000US01085| 1085|        Lowndes|    Alabama|                    9974|
|0500000US06057| 6057|         Nevada| California|                   99696|
|0500000US29189|29189|      St. Louis|   Missouri|                  996945|
|0500000US22021|22021|Caldwell Parish|  Louisiana|                    9960|
|0500000US06019| 6019|         Fresno| California|                  994400|
|0500000US28143|28143|         Tunica|Mississippi|                    9944|
|0500000US05051| 5051|        Garland|   Arkansas|                   99154|
|0500000US29079|29079|         Grundy|   Missouri|                    9914|
|0500000US27063|27063|        Jackson|  Minnesota|                    9911|

Our question returned knowledge however in an sudden order. It seems to be like inhabitants estimate 2018 sorted lexicographically if the values have been strings. Let’s use an AWS Glue DynamicFrame to get the schema of the desk and confirm the problem:

# Create a DynamicFrame of county_populations and print it is schema
dyf = glueContext.create_dynamic_frame.from_catalog(
    database="covid-19", table_name="county_populations"

|-- id: string
|-- id2: string
|-- county: string
|-- state: string
|-- inhabitants estimate 2018: string

The schema exhibits inhabitants estimate 2018 to be a string, which is why our column isn’t sorting correctly. We will use the apply_mapping remodel in our subsequent cell to right the column kind. In the identical remodel, we additionally clear up the column names and different column sorts: clarifying the excellence between id and id2, eradicating areas from inhabitants estimate 2018 (conforming to Hive’s requirements), and casting id2 as an integer for correct sorting. After validating the schema, we present the information with the brand new schema:

# Rename id2 to simple_id and convert to Int
# Take away areas and rename inhabitants est. and convert to Lengthy
mapped = dyf.apply_mapping(
        ("id", "string", "id", "string"),
        ("id2", "string", "simple_id", "int"),
        ("county", "string", "county", "string"),
        ("state", "string", "state", "string"),
        ("population estimate 2018", "string", "population_est_2018", "long"),
|-- id: string
|-- simple_id: int
|-- county: string
|-- state: string
|-- population_est_2018: lengthy

mapped_df = mapped.toDF()

|            id|simple_id|   county|  state|population_est_2018|
|0500000US01001|     1001|  Autauga|Alabama|              55601|
|0500000US01003|     1003|  Baldwin|Alabama|             218022|
|0500000US01005|     1005|  Barbour|Alabama|              24881|
|0500000US01007|     1007|     Bibb|Alabama|              22400|
|0500000US01009|     1009|   Blount|Alabama|              57840|
|0500000US01011|     1011|  Bullock|Alabama|              10138|
|0500000US01013|     1013|   Butler|Alabama|              19680|
|0500000US01015|     1015|  Calhoun|Alabama|             114277|
|0500000US01017|     1017| Chambers|Alabama|              33615|
|0500000US01019|     1019| Cherokee|Alabama|              26032|
|0500000US01021|     1021|  Chilton|Alabama|              44153|
|0500000US01023|     1023|  Choctaw|Alabama|              12841|
|0500000US01025|     1025|   Clarke|Alabama|              23920|
|0500000US01027|     1027|     Clay|Alabama|              13275|
|0500000US01029|     1029| Cleburne|Alabama|              14987|
|0500000US01031|     1031|   Espresso|Alabama|              51909|
|0500000US01033|     1033|  Colbert|Alabama|              54762|
|0500000US01035|     1035|  Conecuh|Alabama|              12277|
|0500000US01037|     1037|    Coosa|Alabama|              10715|
|0500000US01039|     1039|Covington|Alabama|              36986|
solely displaying prime 20 rows

With the information sorting accurately, we will write it to Amazon Easy Storage Service (Amazon S3) as a brand new desk within the AWS Glue Information Catalog. We use the mapped DynamicFrame for this write as a result of we didn’t modify any knowledge previous that remodel:

# Create "demo" Database if none exists
spark.sql("create database if not exists demo")

# Set glueContext sink for writing new desk
s3output = glueContext.getSink(
s3output.setCatalogInfo(catalogDatabase="demo", catalogTableName="populations")

# Write out ‘mapped’ to a desk in Glue Catalog
s3output = glueContext.getSink(
s3output.setCatalogInfo(catalogDatabase="demo", catalogTableName="populations")

Lastly, we run a question towards our new desk to indicate our desk created efficiently and validate our work:

choose * from demo.populations

Convert notebooks to AWS Glue jobs with nbconvert

Jupyter notebooks are saved as .ipynb information. AWS Glue doesn’t presently run .ipynb information immediately, so that they should be transformed to Python scripts earlier than they are often uploaded to Amazon S3 as jobs. Use the jupyter nbconvert command from a terminal to transform the script.

  1. Open a brand new terminal or PowerShell tab or window.
  2. cd to the working listing the place your pocket book is.
    That is probably the identical listing the place you ran jupyter pocket book at first of this publish.
  3. Run the next bash command to transform the pocket book, offering the right file title on your pocket book:
    jupyter nbconvert --to script <Untitled-1>.ipynb

  4. Run cat <Untitled-1>.ipynb to view your new file.
  5. Add the .py file to Amazon S3 utilizing the next command, changing the bucket, path, and file title as wanted:
    aws s3 cp <Untitled-1>.py s3://<bucket>/<path>/<Untitled-1.py>

  6. Create your AWS Glue job with the next command.

Observe that the magics aren’t mechanically transformed to job parameters when changing notebooks domestically. You could put in your job arguments accurately, or import your pocket book to AWS Glue Studio and full the next steps to maintain your magic settings.

aws glue create-job 
    --name is_blog_demo
    --role "<GlueServiceRole>" 
    --command {"Identify": "glueetl", "PythonVersion": "3", "ScriptLocation": "s3://<bucket>/<path>/<Untitled-1.py"} 
    --default-arguments {"--enable-glue-datacatalog": "true"} 
    --number-of-workers 2 
    --worker-type G.2X

Run the job

After you might have authored the pocket book, transformed it to a Python file, uploaded it to Amazon S3, and at last made it into an AWS Glue job, the one factor left to do is run it. Achieve this with the next terminal command:

aws glue start-job-run --job-name is_blog --region us-east-1


AWS Glue interactive periods supply a brand new approach to work together with the AWS Glue serverless Spark atmosphere. Set it up in minutes, begin periods in seconds, and solely pay for what you utilize. You should use interactive periods for AWS Glue job growth, advert hoc knowledge integration and exploration, or for big queries and audits. AWS Glue interactive periods are typically obtainable in all Areas that assist AWS Glue.

To study extra and get began utilizing AWS Glue Interactive Periods go to our developer information and start coding in seconds.

In regards to the creator

Zach Mitchell is a Sr. Huge Information Architect. He works inside the product workforce to boost understanding between product engineers and their clients whereas guiding clients via their journey to develop knowledge lakes and different knowledge options on AWS analytics providers.


Most Popular

Recent Comments