Load AWS Lookoutequipment data in Python using dltHub

Build a AWS Lookoutequipment-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete AWS Lookoutequipment data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def aws_lookoutequipment_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://amazonaws.com/",
            "auth": {
                "type": "aws4",
                "accessKeyId": "AWS_ACCESS_KEY_ID",
                "secretAccessKey": "AWS_SECRET_ACCESS_KEY",
                "service": "lookoutequipment",
                "region": "region"
            },
        },
        "resources": [
            data-ingestion-job, dataset
        ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='aws_lookoutequipment_pipeline',
        destination='duckdb',
        dataset_name='aws_lookoutequipment_data', 
    )
    # Load the data
    load_info = pipeline.run(aws_lookoutequipment_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from aws_lookoutequipment’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Dataset Management: Create, retrieve, and delete datasets for training Lookout for Equipment models
  • Model Management: Train, retrieve, and delete machine learning models for equipment anomaly detection
  • Inference Scheduling: Create, manage, and delete scheduled inference jobs to monitor equipment in real-time
  • Data Ingestion: Monitor and retrieve status of data ingestion jobs that populate datasets

You will then debug the AWS Lookoutequipment pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install dlt[workspace]

    Initialize a dlt pipeline with AWS Lookoutequipment support.

    dlt init dlthub:aws_lookoutequipment duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for AWS Lookoutequipment API, as specified in @aws_lookoutequipment-docs.yaml 
Start with endpoint(s) data-ingestion-job and dataset and skip incremental loading for now. 
Place the code in aws_lookoutequipment_pipeline.py and name the pipeline aws_lookoutequipment_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python aws_lookoutequipment_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    AWS Signature Version 4 signing is required for all requests. Use AWS access key ID and secret access key to sign requests with the Authorization header, or provide credentials through environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. The service name for signing is lookoutequipment and the region must be specified in the request.

    To get the appropriate API keys, please visit the original source at redocly.github.io. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python aws_lookoutequipment_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline aws_lookoutequipment load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset aws_lookoutequipment_data
The duckdb destination used duckdb:/aws_lookoutequipment.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline aws_lookoutequipment_pipeline show

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("aws_lookoutequipment_pipeline").dataset()
# get ["data-ingestion-job"] table as Pandas frame
data.["data-ingestion-job"].df().head()

Extra resources:

Next steps