Simplify real-time analytics with zero-ETL from Amazon DynamoDB to Amazon SageMaker Lakehouse

{
    "Model": "2012-10-17",
    "Assertion": [
        {
            "Sid": "TablePolicy01",
            "Effect": "Allow",
            "Principal": {
                "Service": "glue.amazonaws.com"
            },
            "Action": [
                "dynamodb:ExportTableToPointInTime",
                "dynamodb:DescribeExport",
                "dynamodb:DescribeTable"
            ],
            "Useful resource": "*"
        }
    ]
}

{
    "Model": "2012-10-17",
    "Assertion": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam:::root"
            },
            "Action": "glue:CreateInboundIntegration",
            "Resource": "arn:aws:glue:::database/salesmarketing_XXX"
        },
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "glue.amazonaws.com"
            },
            "Action": "glue:AuthorizeInboundIntegration",
            "Resource": "arn:aws:glue:::database/salesmarketing_XXX"
        }
    ]
}

Now you’re able to create your zero-ETL integration.

Create a zero-ETL integration

Full the next steps to create a zero-ETL integration:

1. On the AWS Glue console, choose Zero-ETL integrations within the navigation pane.

2. Choose “Create zero-ETL integration” to create a brand new configuration.

3. Choose Amazon DynamoDB because the supply sort.

4. Beneath Supply particulars, choose ecommerce_customer_behavior for DynamoDB desk.

5. Beneath Goal particulars, present the next data:
   1. For AWS account, choose Use the present account.
   2. For Information warehouse or catalog, enter the account ID of your default catalog.
   3. For Goal database, enter salesmarketing_XXX.
   4. For Goal IAM function, enter datazone_usr_role_XXX.

6. Beneath Output settings, choose Unnest all fields and Use major keys from DynamoDB tables, go away Configure goal desk identify because the default worth (ecommerce_customer_behavior), then choose Subsequent.

7. Enter zetl-ecommerce-customer-behavior for Title beneath Integration particulars, then choose Subsequent.

8. Choose Create and launch integration to launch the combination.

The standing needs to be Creating after the combination is efficiently initiated.
The standing will change to Energetic in roughly a minute.

Confirm that the SageMaker Lakehouse desk exists. This course of may take as much as quarter-hour to finish, as a result of the default refresh interval from DynamoDB is about to fifteen minutes.

Validate the SageMaker Lakehouse desk

Now you can question your SageMaker Lakehouse desk, created by way of zero-ETL integration, utilizing numerous question engines. Full the next steps to confirm you’ll be able to you see the desk in SageMaker Unified Studio:

1. Log in to the SageMaker Unified Studio portal utilizing the only sign-on (SSO) possibility.

2. Choose your challenge to view its particulars web page.

3. Choose Information within the navigation pane.

4. Confirm you could see the Iceberg desk within the SageMaker Lakehouse catalog.

Question with Athena

On this part, we present tips on how to use Athena to question the SageMaker Lakehouse desk from SageMaker Unified Studio. On the challenge web page, find the ecommerce_customer_behavior desk within the catalog, and on the choices menu (three dots), choose Question with Athena.

This creates a SELECT question towards the SageMaker Lakehouse desk in a brand new window, and you must see the question outcomes as proven within the following screenshot.

Question with Amazon Redshift

You may as well question the SageMaker Lakehouse desk from SageMaker Unified Studio utilizing Amazon Redshift. Full the next steps:

1. Choose the connection on the highest proper.
2. Choose Redshift (Lakehouse) from the listing of connections.
3. Choose the awsdatacatalog database.
4. Choose the salesmarketing schema.
5. Choose Select button.

The outcomes will probably be proven within the Amazon Redshift Question Editor.

Question with Amazon EMR Serverless

You may question the Lakehouse desk utilizing Amazon EMR Serverless, which makes use of Apache Spark’s processing capabilities. Full the next steps:

1. On the challenge web page, choose Compute within the navigation pane.
2. Choose Add compute on the Information processing tab to create an EMR Serverless compute related to the challenge.

3. You may create new compute sources or hook up with current sources. For this instance, choose Create new compute sources.

4. Choose EMR Serverless.

5. Enter a compute identify (for instance, Gross sales-Advertising and marketing), choose the newest launch of EMR Serverless, and choose Add compute.

It’ll take a while to create the compute.

It’s best to see the standing as Began for the compute. Now it’s prepared for use as your compute possibility for querying by way of a Jupyter pocket book.

6. Choose the Construct menu and choose JupyterLab.

It’ll take a while to arrange the workspace for operating JupyterLab.

After the Jupyter Lab area is about up, you must see a web page much like the next screenshot.

7. Choose the brand new folder icon to create a brand new folder.

8. Title the folder lakehouse_zetl_lab.

9. Navigate to the folder you simply created and create a pocket book beneath this folder.

10. Choose the pocket book Python3 (ipykernel) on the Launcher tab, and rename the pocket book to query_lakehouse_table.

You may observe that the pocket book is exhibiting native Python as default language and compute. The 2 drop down menus present the connection sort and compute for the chosen connection sort, simply above the primary cell inside the Jupyter pocket book.

11. Choose PySpark because the connection, and choose the EMR Serverless software as compute.

12. Enter the next pattern code to question the desk utilizing Spark SQL:

import sys
from pyspark.sql import SparkSession
from pyspark.sql.features import *

# Set the present database
spark.catalog.setCurrentDatabase("salesmarketing_XXX")

# Execute SQL question and retailer leads to DataFrame
df = spark.sql("choose * from ecommerce_customer_behavior restrict 10")

# Show the outcomes
df.present()

You may see the Spark DataFrame outcomes.

Clear up

To keep away from incurring future prices, delete the SageMaker area, DynamoDB desk, AWS Glue sources, and different objects created from this publish.

Conclusion

This publish demonstrated how one can set up a zero-ETL connection from DynamoDB to SageMaker Lakehouse, making your information accessible in Iceberg format with out constructing customized information pipelines. We confirmed how one can analyze this DynamoDB information by way of numerous compute engines inside SageMaker Unified Studio. This streamlined method alleviates conventional information motion complexities, and allows extra environment friendly information evaluation workflows instantly out of your DynamoDB tables.

Check out this answer in your personal use case, and share your suggestions within the feedback.

In regards to the authors

Narayani Ambashta is an Analytics Specialist Options Architect at AWS, specializing in the automotive and manufacturing sector, the place she guides strategic prospects in growing trendy information and AI methods. With over 15 years of cross-industry expertise, she makes a speciality of massive information structure, real-time analytics, and AI/ML applied sciences, serving to organizations implement trendy information architectures. Her experience spans throughout lakehouse, generative AI, and IoT platforms, enabling prospects to drive digital transformation initiatives. When not architecting trendy options, she enjoys staying lively by way of sports activities and yoga.

Raj Ramasubbu is a Senior Analytics Specialist Options Architect centered on massive information and analytics and AI/ML with AWS. He helps prospects architect and construct extremely scalable, performant, and safe cloud-based options on AWS. Raj offered technical experience and management in constructing information engineering, massive information analytics, enterprise intelligence, and information science options for over 18 years previous to becoming a member of AWS. He helped prospects in numerous {industry} verticals like healthcare, medical units, life sciences, retail, asset administration, automobile insurance coverage, residential REIT, agriculture, title insurance coverage, provide chain, doc administration, and actual property.

Yadgiri Pottabhathini is a Senior Analytics Specialist Options Architect within the media and leisure sector. He makes a speciality of helping enterprise prospects with their information and analytics cloud transformation initiatives, whereas offering steerage on accelerating their Generative AI adoption by way of the event of knowledge foundations and trendy information methods that leverage open-source frameworks and applied sciences.

Junpei Ozono is a Sr. Go-to-market (GTM) Information & AI options architect at AWS in Japan. He drives technical market creation for information and AI options whereas collaborating with international groups to develop scalable GTM motions. He guides organizations in designing and implementing progressive data-driven architectures powered by AWS providers, serving to prospects speed up their cloud transformation journey by way of trendy information and AI options. His experience spans throughout trendy information architectures together with Information Mesh, Information Lakehouse, and Generative AI, enabling prospects to construct scalable and progressive options on AWS.