Developing Scripts Using Development Endpoints

AWS Glue can create an environment—known as a development endpoint—that you can use to iteratively develop and test your extract, transform, and load (ETL) scripts. You can create, edit, and delete development endpoints using the AWS Glue console or API.

Note

Development endpoints are not supported for use with AWS Glue version 2.0 jobs. For more information, see Running Spark ETL Jobs with Reduced Startup Times.

Managing your Development Environment

When you create a development endpoint, you provide configuration values to provision the development environment. These values tell AWS Glue how to set up the network so that you can access the endpoint securely and the endpoint can access your data stores.

You can then create a notebook that connects to the endpoint, and use your notebook to author and test your ETL script. When you're satisfied with the results of your development process, you can create an ETL job that runs your script. With this process, you can add functions and debug your scripts in an interactive manner.

Follow the tutorials in this section to learn how to use your development endpoint with notebooks.

Topics

• Development Endpoint Workflow
• How AWS Glue Development Endpoints Work with SageMaker Notebooks
• Adding a Development Endpoint
• Viewing Development Endpoint Properties
• Accessing Your Development Endpoint
• Creating a Notebook Server Hosted on Amazon EC2
• Tutorial Setup: Prerequisites for the Development Endpoint Tutorials
• Tutorial: Set Up a Local Apache Zeppelin Notebook to Test and Debug ETL Scripts
• Tutorial: Set Up an Apache Zeppelin Notebook Server on Amazon EC2
• Tutorial: Set Up a Jupyter Notebook in JupyterLab to Test and Debug ETL Scripts
• Tutorial: Use an SageMaker Notebook with Your Development Endpoint
• Tutorial: Use a REPL Shell with Your Development Endpoint
• Tutorial: Set Up PyCharm Professional with a Development Endpoint
• Advanced Configuration: Sharing Development Endpoints among Multiple Users