Visualize information lineage utilizing Amazon SageMaker Catalog for Amazon EMR, AWS Glue, and Amazon Redshift

Amazon SageMaker gives a complete hub that integrates information, analytics, and AI capabilities, offering a unified expertise for customers to entry and work with their information. By way of Amazon SageMaker Unified Studio, a single and unified surroundings, you should use a variety of instruments and options to help your information and AI improvement wants, together with information processing, SQL analytics, mannequin improvement, coaching, inference, and generative AI improvement. This providing is additional enhanced by the combination of Amazon Q and Amazon SageMaker Catalog, which offer an embedded generative AI and governance expertise, serving to customers work effectively and successfully throughout the complete information and AI lifecycle, from information preparation to mannequin deployment and monitoring.

With the SageMaker Catalog information lineage function, you may visually observe and perceive the move of your information throughout completely different methods and groups, gaining a whole image of your information property and the way they’re related. As an OpenLineage-compatible function, it helps you hint information origins, observe transformations, and think about cross-organizational information consumption, supplying you with insights into cataloged property, subscribers, and exterior actions. By capturing lineage occasions from OpenLineage-enabled methods or via APIs, you may achieve a deeper understanding of your information’s journey, together with actions inside SageMaker Catalog and past, finally driving higher information governance, high quality, and collaboration throughout your group.

Moreover, the SageMaker Catalog information lineage function variations every occasion, so you may observe adjustments, visualize historic lineage, and evaluate transformations over time. This supplies worthwhile insights into information evolution, facilitating troubleshooting, auditing, and information integrity by exhibiting precisely how information property have developed, and generates belief in information.

On this publish, we focus on the visualization of knowledge lineage in SageMaker Catalog and the way seize lineage from completely different AWS analytics companies comparable to AWS Glue, Amazon Redshift, and Amazon EMR Serverless robotically, and visualize it with SageMaker Unified Studio.

Resolution overview

The era of knowledge lineage in SageMaker Catalog operates via an automatic system that captures metadata and relationships between completely different information artifacts for AWS Glue, Amazon EMR, and Amazon Redshift. When information strikes via varied AWS companies, SageMaker robotically tracks these actions, transformations, and dependencies, creating an in depth map of the information’s journey. This monitoring consists of details about information sources, transformations, processing steps, and ultimate outputs, offering a whole audit path of knowledge motion and transformation.

The implementation of knowledge lineage in SageMaker Catalog gives a number of key advantages:

• Compliance and audit help – Organizations can reveal compliance with regulatory necessities by exhibiting full information provenance and transformation historical past
• Influence evaluation – Groups can assess the potential influence of adjustments to information sources or transformations by understanding dependencies and relationships within the information pipeline
• Troubleshooting and debugging – When points come up, the lineage system helps establish the basis trigger by exhibiting the whole path of knowledge transformation and processing
• Knowledge high quality administration – By monitoring transformations and dependencies, organizations can higher keep information high quality and perceive how information high quality points may propagate via their methods

Lineage seize is automated utilizing a number of instruments in SageMaker Unified Studio. To be taught extra, check with Knowledge lineage help matrix.

Within the following sections, we present you how one can configure your assets and implement the answer. For this publish, we create the answer assets within the us-west-2 AWS Area utilizing an AWS CloudFormation template.

Stipulations

Earlier than getting began, be sure to have the next:

Configure SageMaker Unified Studio with AWS CloudFormation

The vpc-analytics-lineage-sus.yaml stack creates a VPC, subnet, safety group, IAM roles, NAT gateway, web gateway, Amazon Elastic Compute Cloud (Amazon EC2) shopper, S3 buckets, SageMaker Unified Studio area, and SageMaker Unified Studio venture. To create the answer assets, full the next steps:

1. Launch the stack vpc-analytics-lineage-sus utilizing the CloudFormation template:
   
2. Present the parameter values as listed within the following desk.
   

   Parameters	Pattern worth
   DatazoneS3Bucket	s3://datazone-{account_id}/
   DomainName	dz-studio
   EnvironmentName	sm-unifiedstudio
   PrivateSubnet1CIDR	10.192.20.0/24
   PrivateSubnet2CIDR	10.192.21.0/24
   PrivateSubnet3CIDR	10.192.22.0/24
   ProjectName	sidproject
   PublicSubnet1CIDR	10.192.10.0/24
   PublicSubnet2CIDR	10.192.11.0/24
   PublicSubnet3CIDR	10.192.12.0/24
   UsersList	analyst
   VpcCIDR	10.192.0.0/16

The stack creation course of can take roughly 20 minutes to finish. You’ll be able to examine the Outputs tab for the stack after the stack is created.

Subsequent, we put together supply information, setup the AWS Glue ETL Job, Amazon EMR Serverless Spark Job and Amazon Redshift Job to generate the lineage and seize lineage from Amazon SageMaker Unified Studio

Put together information

The next is instance information from our CSV information:

attendance.csv

EmployeeID,Date,ShiftStart,ShiftEnd,Absent,OvertimeHours
E1000,2024-01-01,2024-01-01 08:00:00,2024-01-01 16:22:00,False,3
E1001,2024-01-08,2024-01-08 08:00:00,2024-01-08 16:38:00,False,2
E1002,2024-01-23,2024-01-23 08:00:00,2024-01-23 16:24:00,False,3
E1003,2024-01-09,2024-01-09 10:00:00,2024-01-09 18:31:00,False,0
E1004,2024-01-15,2024-01-15 09:00:00,2024-01-15 17:48:00,False,1

staff.csv

EmployeeID,Title,Division,Position,HireDate,Wage,PerformanceRating,Shift,Location
E1000,Employee_0,High quality Management,Operator,2021-08-08,33002.0,1,Night time,Plant C
E1001,Employee_1,Upkeep,Supervisor,2015-12-31,69813.76,5,Night,Plant B
E1002,Employee_2,Manufacturing,Technician,2015-06-18,46753.32,1,Night,Plant A
E1003,Employee_3,Admin,Supervisor,2020-10-13,52853.4,5,Night time,Plant A
E1004,Employee_4,High quality Management,Supervisor,2023-09-21,55645.27,5,Night,Plant A

Add the pattern information from attendance.csv and staff.csv to the S3 bucket specified within the earlier CloudFormation stack (s3://datazone-{account_id}/csv/).

Ingest worker information in Amazon Relational Database Dervice (Amazon RDS) for MySQL desk

On the CloudFormation console, open the stack vpc-analytics-lineage-sus and accumulate the Amazon RDS for MySQL database endpoint to make use of within the following instructions to create a default employeedb database.

1. Hook up with Amazon EC2 occasion with mysql package deal set up
2. Run the next command to hook up with the database

   >MySQL -u admin -h database-1.cuqd06l5efvw.us-west-2.rds.amazonaws.com -p

3. Run the next command to create an worker desk

   Use employeedb;
   
   CREATE TABLE worker (
     EmployeeID longtext,
     Title longtext,
     Division longtext,
     Position longtext,
     HireDate longtext,
     Wage longtext,
     PerformanceRating longtext,
     Shift longtext,
     Location longtext
   );

4. Working the next command to insert rows.

   INSERT INTO worker (EmployeeID, Title, Division, Position, HireDate, Wage, PerformanceRating, Shift, Location) VALUES ('E1000', 'Employee_0', 'High quality Management', 'Operator', '2021-08-08', 33002.00, 1, 'Night time', 'Plant C'), ('E1001', 'Employee_1', 'Upkeep', 'Supervisor', '2015-12-31', 69813.76, 5, 'Night', 'Plant B'), ('E1002', 'Employee_2', 'Manufacturing', 'Technician', '2015-06-18', 46753.32, 1, 'Night', 'Plant A'), ('E1003', 'Employee_3', 'Admin', 'Supervisor', '2020-10-13', 52853.40, 5, 'Night time', 'Plant A'), ('E1004', 'Employee_4', 'High quality Management', 'Supervisor', '2023-09-21', 55645.27, 5, 'Night', 'Plant A');

Seize lineage from AWS Glue ETL job and pocket book

To reveal the lineage, we arrange an AWS Glue extract, rework, and cargo (ETL) job to learn the worker information from an Amazon RDS for MySQL desk and the worker attendance information from Amazon S3, and be part of each datasets. Lastly, we write the information to Amazon S3 and create the attendance_with_emp1 desk within the AWS Glue Knowledge Catalog.

Create and configure AWS Glue job for lineage era

Full the next steps to create your AWS Glue ETL job:

1. On the AWS Glue console, create a brand new ETL job with AWS Glue model 5.0.
2. Allow Generate lineage occasions and supply the area ID (retrieve from the CloudFormation template output for DataZoneDomainid; it’ll have the format dzd_xxxxxxxx)
   
3. Use the next code snippet within the AWS Glue ETL job script. Present the S3 bucket (bucketname-{account_id}) used within the previous CloudFormation stack.

   from pyspark.sql import SparkSession
   from pyspark.sql import SparkSession, DataFrame
   from pyspark.sql.features import *
   from pyspark.sql.sorts import *
   from pyspark import SparkContext
   from pyspark.sql import SparkSession
   import sys
   import logging
   
   
   spark = SparkSession.builder.appName("lineageglue").enableHiveSupport().getOrCreate()
    
   connection_details = glueContext.extract_jdbc_conf(connection_name="connectionname")
   
   employee_df = spark.learn.format("jdbc").choice("url", "jdbc:MySQL://dbhost:3306/database_name").choice("dbtable", "worker").choice("person", connection_details['user']).choice("password", connection_details['password']).load()
   
   s3_paths = {
   'absent_data': 's3://bucketname-{account_id}/csv/attendance.csv'
   }
   absent_df = spark.learn.csv(s3_paths['absent_data'], header=True, inferSchema=True)
   
   joined_df = employee_df.be part of(absent_df, on="EmployeeID", how="interior")
   
   joined_df.write.mode("overwrite").format("parquet").choice("path", "s3://datazone-{account_id}/attendanceparquet/").saveAsTable("gluedbname.tablename")

4. Select Run to start out the job.
5. On the Runs tab, verify the job ran with out failure.
   
6. After the job has executed efficiently, navigate to the SageMaker Unified Studio area.
7. Select Challenge and below Overview, select Knowledge Sources.
8. Choose the Knowledge Catalog supply (accountid-AwsDataCatalog-glue_db_suffix-default-datasource).
9. On the Actions dropdown menu, select Edit.
   
10. Beneath Connection, allow Import information lineage.
11. Within the Knowledge Choice part, below Desk Choice Standards, present a desk title or use * to generate lineage.
12. Replace the information supply and select Run to create an asset known as attendance_with_emp1 in SageMaker Catalog.
13. Navigate to Property, select the attendance_with_emp1 asset, and navigate to the LINEAGE part.

The next lineage diagram exhibits an AWS Glue job that integrates information from two sources: worker info saved in Amazon RDS for MySQL and worker absence data saved in Amazon S3. The AWS Glue job combines these datasets via a be part of operation, then creates a desk within the Knowledge Catalog and registers it as an asset in SageMaker Catalog, making the unified information obtainable for additional evaluation or machine studying functions.

Create and configure AWS Glue pocket book for lineage era

Full the next steps to create the AWS Glue pocket book:

1. On the AWS Glue console, select Creator utilizing an interactive code pocket book.
2. Beneath Choices, select Begin contemporary and select Create pocket book.
3. Within the pocket book, use the next code to generate lineage.

   Within the following code, we add the required Spark configuration to generate lineage after which learn CSV information from Amazon S3 and write in Parquet format to the Knowledge Catalog desk. The Spark configuration consists of the next parameters:

   • spark.extraListeners=io.openlineage.spark.agent.OpenLineageSparkListener – Registers the OpenLineage listener to seize Spark job execution occasions and metadata for lineage monitoring
   • spark.openlineage.transport.sort=amazon_datazone_api – Specifies Amazon DataZone because the vacation spot service the place the lineage information shall be despatched and saved
   • spark.openlineage.transport.domainId=dzd_xxxxxxx – Defines the distinctive identifier of your Amazon DataZone area the place the lineage information shall be related
   • spark.glue.accountId={account_id} – Specifies the AWS account ID the place the AWS Glue job is working for correct useful resource identification and entry
   • spark.openlineage.sides.custom_environment_variables – Lists the particular surroundings variables to seize within the lineage information for context in regards to the AWS and AWS Glue surroundings
   • spark.glue.JOB_NAME=lineagenotebook – Units a novel identifier title for the AWS Glue job that may seem in lineage monitoring and logs

   See the next code:

   %%configure —title venture.spark -f
   {
   "—conf":"spark.extraListeners=io.openlineage.spark.agent.OpenLineageSparkListener 
   --conf spark.openlineage.transport.sort=amazon_datazone_api 
   --conf spark.openlineage.transport.domainId=dzd_xxxxxxxx 
   --conf spark.glue.accountId={account_id} 
   --conf spark.openlineage.sides.custom_environment_variables=[AWS_DEFAULT_REGION;GLUE_VERSION;GLUE_COMMAND_CRITERIA;GLUE_PYTHON_VERSION;] 
   --conf spark.glue.JOB_NAME=lineagenotebook"
   }
   
   from pyspark.sql import SparkSession
   from pyspark.sql import SparkSession, DataFrame
   from pyspark.sql.features import *
   from pyspark.sql.sorts import *
   from pyspark import SparkContext
   from pyspark.sql import SparkSession
   import sys
   import logging
   
   
   spark = SparkSession.builder.appName("lineagegluenotebook").enableHiveSupport().getOrCreate()
   
   s3_paths = {
   'absent_data': 's3://datazone-{account_id}/csv/attendance.csv'
   }
   absent_df = spark.learn.csv(s3_paths['absent_data'], header=True, inferSchema=True)
   
   absent_df.write.mode("overwrite").format("parquet").choice("path", "s3://datazone-{account_id}/attendanceparquet2/").saveAsTable("gluedbname.tablename")

4. After the pocket book has executed efficiently, navigate to the SageMaker Unified Studio area.
5. Select Challenge and below Overview, select Knowledge Sources.
6. Select the Knowledge Catalog supply ({account_id}-AwsDataCatalog-glue_db_suffix-default-datasource).
7. Select Run to create the asset attendance_with_empnote in SageMaker Catalog.
8. Navigate to Property, select the attendance_with_empnote asset, and navigate to the LINEAGE part.

The next lineage diagram exhibits an AWS Glue job that reads information from the worker absence data saved in Amazon S3. The AWS Glue job rework CSV information into Parquet format, then creates a desk within the Knowledge Catalog and registers it as an asset in SageMaker Catalog.

Seize lineage from Amazon Redshift

To reveal the lineage, we’re creating an worker desk and an attendance desk and be part of each datasets. Lastly, we create a brand new desk known as employeewithabsent in Amazon Redshift. Full the next steps to create and configure lineage for Amazon Redshift tables:

1. In SageMaker Unified Studio, open your area.
2. Beneath Compute, select Knowledge warehouse.
3. Open venture.redshift and replica the endpoint title (redshift-serverless-workgroup-xxxxxxx).
   
4. On the Amazon Redshift console, open the Question Editor v2, and connect with the Redshift Serverless workgroup with a secret. Use the AWS Secrets and techniques Supervisor choice and select the key redshift-serverless-namespace-xxxxxxxx.
   
5. Use the next code to create tables in Amazon Redshift and cargo information from Amazon S3 utilizing the COPY command. Be sure that the IAM position has GetObject permission on the S3 information attendance.csv and staff.csv.

   Create Redshift desk absent

   CREATE TABLE public.absent (
       employeeid character various(65535),
       date date,
       shiftstart timestamp with out time zone ,
       shiftend timestamp with out time zone,
       absent boolean,
       overtimehours integer
   );

   Load information into absent desk.

   COPY absent
   FROM 's3://datazone-{account_id}/csv/attendance.csv' 
   IAM_ROLE 'arn:aws:iam::accountid:position/RedshiftAdmin'
   csv
   IGNOREHEADER 1;

   Create Redshift desk worker

   CREATE TABLE public.worker (
       employeeid character various(65535),
       title character various(65535),
       division character various(65535),
       position character various(65535),
       hiredate date,
       wage double precision,
       performancerating integer,
       shift character various(65535),
       location character various(65535)
   );

   Load information into worker desk.

   COPY worker
   FROM 's3://datazone-{account_id}/csv/staff.csv' 
   IAM_ROLE 'arn:aws:iam::account-id:position/RedshiftAdmin'
   csv
   IGNOREHEADER 1;

6. After the tables are created and the information is loaded, carry out the be part of between the tables and create a brand new desk with a CTAS question:

   CREATE TABLE public.employeewithabsent AS
   SELECT 
     e.*,
     a.absent,
     a.overtimehours
   FROM public.worker e
   INNER JOIN public.absent a
   ON e.EmployeeID = a.EmployeeID;

7. Navigate to the SageMaker Unified Studio area.
8. Select Challenge and below Overview, select Knowledge Sources.
9. Choose the Amazon Redshift supply (RedshiftServerless-default-redshift-datasource).
10. On the Actions dropdown menu, select Edit.
11. Beneath Connection, Allow Import information lineage.
12. Within the Knowledge Choice part, below Desk Choice Standards, present a desk title or use * to generate lineage.
13. Replace the information supply and select Run to create an asset known as employeewithabsent in SageMaker Catalog.
14. Navigate to Property, select the employeewithabsent asset, and navigate to the LINEAGE part.

The next lineage diagram exhibits becoming a member of two redshift tables and creating a brand new redshift desk and registers it as an asset in SageMaker Catalog.

Seize lineage from EMR Serverless job

To reveal the lineage, we learn worker information from an RDS for MySQL desk and an attendance dataset from Amazon Redshift, and be part of each datasets. Lastly, we write the information to Amazon S3 and create the attendance_with_employee desk within the Knowledge Catalog. Full the next steps:

1. On the Amazon EMR console, select EMR Serverless within the navigation pane.
2. To create or handle EMR Serverless purposes, you want the EMR Studio UI.
   1. If you have already got an EMR Studio within the Area the place you wish to create an utility, select Handle purposes to navigate to your EMR Studio, or choose the EMR Studio that you simply wish to use.
   2. If you happen to don’t have an EMR Studio within the Area the place you wish to create an utility, select Get began after which select Create and launch Studio. EMR Serverless creates an EMR Studio for you so you may create and handle purposes.
3. Within the Create studio UI that opens in a brand new tab, enter the title, sort, and launch model to your utility.
4. Select Create utility.
5. Create an EMR Spark serverless utility with the next configuration:
   1. For Kind, select Spark.
   2. For Launch model, select emr-7.8.0.
   3. For Structure, select x86_64.
   4. For Software setup choices, choose Use customized settings.
   5. For Interactive endpoint, allow the endpoint for EMR Studio.
   6. For Software configuration, use the next configuration:

      [{
          "Classification": "iceberg-defaults",
          "Properties": {
              "iceberg.enabled": "true"
          }
      }]

6. Select Create and Begin utility.
7. After utility has began, submit the Spark utility to generate lineage occasions. Copy the next script and add it to the S3 bucket (s3://datazone-{account_id}/script/). Add the MySQL-connector-java JAR file to the S3 bucket (s3://datazone-{account_id}/jars/) to learn the information from MySQL.

   from pyspark.sql import SparkSession
   from pyspark.sql import SparkSession, DataFrame
   from pyspark.sql.features import *
   from pyspark.sql.sorts import *
   from pyspark import SparkContext
   from pyspark.sql import SparkSession
   import sys
   import logging
   
   
   spark = SparkSession.builder.appName("lineageglue").enableHiveSupport().getOrCreate()
   
   employee_df = spark.learn.format("jdbc").choice("driver","com.MySQL.cj.jdbc.Driver").choice("url", "jdbc:MySQL://dbhostname:3306/databasename").choice("dbtable", "worker").choice("person", "admin").choice("password", "xxxxxxx").load()
   
   absent_df = spark.learn.format("jdbc").choice("url", "jdbc:redshift://redshiftserverlessendpoint:5439/dev").choice("dbtable", "public.absent").choice("person", "admin").choice("password", "xxxxxxxxxx").load()
   
   joined_df = employee_df.be part of(absent_df, on="EmployeeID", how="interior")
   
   joined_df.write.mode("overwrite").format("parquet").choice("path", "s3://datazone-{account_id}/emrparquetnew/").saveAsTable("gluedname.tablename")

8. After you add the script, use the next command to submit the Spark utility. Change the next parameters based on your surroundings particulars:
   1. application-id: Present the Spark utility ID you generated.
   2. execution-role-arn: Present the EMR execution position.
   3. entryPoint: Present the Spark script S3 path.
   4. domainID: Present the area ID (from the CloudFormation template output for DataZoneDomainid: dzd_xxxxxxxx).
   5. accountID: Present your AWS account ID.

      aws emr-serverless start-job-run --application-id 00frv81tsqe0ok0l --execution-role-arn arn:aws:iam::{account_id}:position/service-role/AmazonEMR-ExecutionRole-1717662744320 --name "Spark-Lineage" --job-driver '{
              "sparkSubmit": {
                  "entryPoint": "s3://datazone-{account_id}/script/emrspark2.py",
                  "sparkSubmitParameters": "--conf spark.executor.cores=1 --conf spark.executor.reminiscence=4g --conf spark.driver.cores=1 --conf spark.driver.reminiscence=4g --conf spark.executor.cases=2 --conf spark.hadoop.hive.metastore.shopper.manufacturing facility.class=com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory --conf spark.jars=/usr/share/aws/datazone-openlineage-spark/lib/DataZoneOpenLineageSpark-1.0.jar,s3://datazone-{account_id}/jars/MySQL-connector-java-8.0.20.jar --conf spark.extraListeners=io.openlineage.spark.agent.OpenLineageSparkListener --conf spark.openlineage.transport.sort=amazon_datazone_api --conf spark.openlineage.transport.domainId=dzd_xxxxxxxx --conf spark.glue.accountId={account_id}"
              }
          }'

      

9. After the job has executed efficiently, navigate to the SageMaker Unified Studio area.
10. Select Challenge and below Overview, select Knowledge Sources.
11. Choose the Knowledge Catalog supply ({account_id}-AwsDataCatalog-glue_db_xxxxxxxxxx-default-datasource).
12. On the Actions dropdown menu, select Edit.
13. Beneath Connection, allow Import information lineage.
14. Within the Knowledge Choice part, below Desk Choice Standards, present a desk title or use * to generate lineage.
15. Replace the information supply and select Run to create an asset known as attendancewithempnew in SageMaker Catalog.
16. Navigate to Property, select the attendancewithempnew asset, and navigate to the LINEAGE part.

The next lineage diagram exhibits an AWS Glue job that integrates worker info saved in Amazon RDS for MySQL and worker absence data saved in Amazon Redshift. The AWS Glue job combines these datasets via a be part of operation, then creates a desk within the Knowledge Catalog and registers it as an asset in SageMaker Catalog.

Clear up

To wash up your assets, full the next steps:

1. On the AWS Glue console, delete the AWS Glue job.
2. On the Amazon EMR console, delete the EMR Serverless Spark utility and EMR Studio.
3. On the AWS CloudFormation console, delete the CloudFormation stack vpc-analytics-lineage-sus.

Conclusion

On this publish, we confirmed how information lineage in SageMaker Catalog helps you observe and perceive the whole lifecycle of your information throughout varied AWS analytics companies. This complete monitoring system supplies visibility into how information flows via completely different processing phases, transformations, and analytical workflows, making it a necessary device for information governance, compliance, and operational effectivity.

Check out these lineage visualization strategies to your personal use instances, and share your questions and suggestions within the feedback part.

Concerning the Authors