MySQL on Amazon RDS to Snowflake: 3 Proven Methods to Integrate Data

Migrate MySQL on Amazon RDS to Snowflake using Snowflake Native Connectors, AWS Managed Services, or Hevo’s no-code ELT. Get real-time pipelines running in minutes.

Hevo automates your data migration from MySQL on Amazon RDS to Snowflake with real-time, reliable pipelines and visibility of the full process. With Hevo’s intuitive pipeline setup, data flows in real-time. Check out our 1-minute demo below to see the seamless integration in action!

Organizations rely on multiple databases and cloud-based solutions for their ever-expanding data storage needs. However, for in-depth analysis of organizational data, it is essential to perform seamless integrations between different platforms.

Centralizing data in a data warehouse like Snowflake can help you obtain valuable insights for enhancing decision-making. You can connect any database, including MySQL on Amazon RDS, with Snowflake to create a single source of truth for in-depth analysis of business operations. Connecting MySQL on Amazon RDS to Snowflake can also help you leverage the advanced analytics capabilities of Snowflake, a unified platform with cross-cloud, storage-decoupling, and data cloning capabilities.

According to Snowflake Summit 2025 announcements, Snowflake’s Standard Warehouse Generation 2 delivers 2.1x faster analytics performance over its previous generation. Organizations that centralize their operational data in Snowflake are already getting significantly faster query results without changing their workloads. That’s a compelling reason to bridge your Amazon RDS MySQL instance with Snowflake. 

This article discusses three methods for connecting MySQL on Amazon RDS to Snowflake, covering Snowflake Native Connectors, AWS Managed Services, and third-party ETL/ELT tools. Based on your requirements, you can determine which method is best suited for your workflow.

Teams evaluating Snowflake ETL tools often compare native Snowflake loading methods, AWS-managed replication services, and modern ELT platforms based on factors like CDC support, transformation flexibility, infrastructure overhead, and real-time performance. 

Prerequisites to Connect MySQL on Amazon RDS to Snowflake

Before starting the migration, ensure the following are in place:

Prerequisite	Details
Active Amazon RDS MySQL instance	Your source database must be running and accessible. Refer to Amazon RDS Read Replicas to offload replication traffic from your primary instance.
Active Snowflake account	A target Snowflake account with the necessary compute warehouse and database set up.
Snowflake user permissions	The user account used for data loading must have CREATE TABLE, INSERT, and COPY INTO privileges on the target schema.
Network/VPC configuration	Your RDS instance’s security group must allow outbound traffic to the migration tool or intermediate staging location (e.g., S3 bucket).
IAM roles and policies	AWS IAM role with read permissions on the RDS instance and read/write access to the S3 staging bucket (required for Methods 1 and 2).
MySQL binary logging enabled	Required if you need Change Data Capture (CDC) for ongoing sync. Set binlog_format=ROW in your RDS parameter group.
Staging S3 bucket (Methods 1 & 2)	An S3 bucket in the same region as your RDS instance to act as an intermediate data staging area.

How to Connect MySQL on Amazon RDS to Snowflake?

There are three reliable methods to migrate data from MySQL on Amazon RDS to Snowflake. Here’s a quick comparison before we get to the details:

Method Comparison Table

Feature	Method 1: Snowflake Native Connectors	Method 2: AWS Managed Services (DMS)	Method 3: Third-Party ETL/ELT (Hevo)
Setup complexity	Medium	Medium–High	Low (no-code)
Real-time/CDC support	Limited (batch-oriented)	Yes (via DMS CDC)	Yes (near real-time)
Transformations	Manual (SQL)	Limited	Built-in (drag-and-drop + Python)
Maintenance overhead	Medium	High	Low
Best for	Batch loads from S3	AWS-native CDC pipelines	Fast, automated pipelines
Cost model	Snowflake compute + S3	AWS DMS + S3 + Snowflake	Hevo subscription + Snowflake
Technical expertise needed	SQL + Snowflake	AWS DMS + SQL	Minimal

Method 1: Using Snowflake Native Connectors

Snowflake provides native support for loading data from Amazon S3 using external stages and the COPY INTO command. This approach uses S3 as an intermediate staging layer between your RDS MySQL instance and Snowflake.

Step 1: Export MySQL Data from Amazon RDS to S3

Use the MySQL SELECT INTO OUTFILE S3 command to export your table data directly to an S3 bucket:

SELECT * INTO OUTFILE S3 ‘s3://your-bucket/exports/table_name.csv’   FIELDS TERMINATED BY ‘,’   ENCLOSED BY ‘”‘   LINES TERMINATED BY ‘\n’ FROM your_table_name;

Alternatively, use AWS Data Pipeline or a scheduled Lambda function to automate this export.

Step 2: Create a Snowflake External Stage Pointing to S3

In your Snowflake worksheet, create an external stage that references your S3 bucket:

CREATE OR REPLACE STAGE my_s3_stage   URL = ‘s3://your-bucket/exports/’   CREDENTIALS = (     AWS_KEY_ID = ‘<your_aws_access_key>’     AWS_SECRET_KEY = ‘<your_aws_secret_key>’   );

For production use, configure the stage with an IAM role instead of access keys for enhanced security.

Step 3: Define the File Format

CREATE OR REPLACE FILE FORMAT my_csv_format   TYPE = ‘CSV’   FIELD_DELIMITER = ‘,’   SKIP_HEADER = 1   NULL_IF = (‘NULL’, ‘null’)   EMPTY_FIELD_AS_NULL = TRUE;

Step 4: Create the Target Table in Snowflake

CREATE OR REPLACE TABLE your_schema.your_table (   id INTEGER,   name VARCHAR(100),   location VARCHAR(100),   created_at TIMESTAMP );

Step 5: Load Data Using COPY INTO

COPY INTO your_schema.your_table FROM @my_s3_stage/table_name.csv FILE_FORMAT = (FORMAT_NAME = ‘my_csv_format’) ON_ERROR = ‘CONTINUE’;

Verify the load:

SELECT * FROM your_schema.your_table LIMIT 100;

Limitations

• Not real-time: This method is batch-oriented. For frequent syncs, you need to automate the export-stage-copy pipeline on a schedule.
• Schema drift: Any DDL changes on the RDS side (new columns, type changes) require manual schema updates in Snowflake.
• S3 management overhead: You are responsible for managing the lifecycle, costs, and permissions of the S3 staging bucket.

Method 2: Using AWS Managed Services (AWS DMS + S3)

AWS Database Migration Service (DMS) provides a managed approach to replicate data from MySQL on Amazon RDS to Snowflake. It supports both full-load and ongoing CDC replication, which makes it suitable for near-continuous sync scenarios.

Step 1: Set Up Source and Target Endpoints in AWS DMS

1. Navigate to AWS DMS in the AWS Management Console.
2. Create a Source Endpoint for your RDS MySQL instance, providing the endpoint URL, port (default: 3306), database name, username, and password.
3. Create a Target Endpoint for Snowflake, DMS writes to an intermediate S3 bucket, which Snowflake then ingests. Configure an S3 endpoint as the DMS target.

Step 2: Enable Binary Logging on RDS MySQL

For CDC, binary logging must be enabled on your RDS parameter group:

binlog_format = ROW binlog_checksum = NONE

Apply the parameter group change and reboot your RDS instance.

Step 3: Create a DMS Replication Instance

• Choose an instance class appropriate for your data volume (e.g., dms.t3.medium for moderate workloads).
• Place the replication instance in the same VPC as your RDS MySQL instance.
• Enable Multi-AZ for production workloads.

Step 4: Create and Run a Migration Task

1. Create a Database Migration Task with the source and target endpoints.
2. Select Full load + CDC for ongoing replication, or Full load only for a one-time migration.
3. Configure table mappings to specify which schemas and tables to migrate.
4. Start the task and monitor progress in the DMS console.

Step 5: Load S3 Output into Snowflake

Once DMS writes to S3, set up a Snowpipe or a scheduled COPY INTO task in Snowflake to ingest the files automatically:

CREATE OR REPLACE PIPE my_dms_pipe   AUTO_INGEST = TRUE AS   COPY INTO your_schema.your_table   FROM @my_s3_stage/dms-output/   FILE_FORMAT = (FORMAT_NAME = ‘my_csv_format’);

Limitations

• Complex setup: DMS configuration with CDC, VPC peering, and Snowpipe requires significant AWS expertise.
• Latency: Data passes through S3 before reaching Snowflake, adding inherent latency even for CDC pipelines.
• Cost unpredictability: DMS instance costs, S3 storage costs, and Snowflake ingest costs all stack up and can be difficult to estimate upfront.
• Limited transformation support: DMS performs minimal data transformations; complex business logic must be applied post-load in Snowflake.

Method 3: Using a Third-Party ETL/ELT Tool (Hevo)

Hevo is one of the leading ELT tools on the market, and its purpose-built pipeline architecture takes care of schema mapping, error handling, and real-time sync out of the box.

Here are the steps for MySQL on Amazon RDS to Snowflake integration with Hevo Data:

Step 1: Configure MySQL on Amazon RDS as the Source

• Log in to your Hevo account and navigate to Pipelines > Create Pipeline.
• Select MySQL on Amazon RDS as the source connector.
• Enter your RDS endpoint, port, database name, username, and password.
• Choose your replication mode: Full Load for a one-time sync or CDC for ongoing real-time replication.
• Test the connection and save the source configuration.

Step 2: Configure Snowflake as the Destination

• Select Snowflake as the destination.
• Provide your Snowflake account identifier, warehouse name, database, schema, username, and password.
• Test the connection and save the destination configuration.

It will take a few minutes only to complete these steps and automate the data migration process from MySQL on Amazon RDS to Snowflake. Hevo handles schema creation, data type mapping, and incremental updates automatically, with no custom scripts required.

For best practices and advanced pipeline configurations tailored to Snowflake’s architecture, Hevo’s documentation on Snowflake ETL provides detailed guidance worth exploring.

What Can You Achieve by Migrating Data from MySQL on Amazon RDS to Snowflake?

Here’s what you can expect to achieve by migrating data from Amazon RDS MySQL to Snowflake:

• Centralize your data from websites and mobile applications to support better analysis.
• Track the response of customers towards specific marketing campaigns and improve future strategies.
• Identify any possible patterns in the collected data, which can help uncover any events or discrepancies in business workflows.
• Determine the most popular content that is driving sales.

Here are some other migrations that you may need:

• MySQL on Amazon RDS to BigQuery
• MySQL on Amazon RDS to Databricks
• MySQL on Amazon RDS to Redshift
• MySQL on Amazon RDS to PostgreSQL
• Amazon RDS to Firebolt
• Oracle to Snowflake ETL
• MongoDB to Snowflake ETL

Choose the Right Method to Move MySQL on Amazon RDS to Snowflake 

Migrating MySQL on Amazon RDS to Snowflake unlocks powerful analytics capabilities that go far beyond what a transactional database can offer. The right method depends on your specific requirements:

• Snowflake Native Connectors are a cost-effective starting point for teams comfortable with SQL and batch pipelines.
• AWS Managed Services (DMS) work well for organizations already invested in the AWS ecosystem and needing CDC support without third-party tools.
• Third-party ETL/ELT tools like Hevo deliver the fastest time-to-value with no-code pipelines, built-in transformations, and near real-time sync, ideal for teams that want to focus on insights rather than infrastructure.

As a fully managed, no-code ELT platform, Hevo is built for teams that need data movement to be simple, reliable, and transparent without requiring engineering effort or ongoing maintenance:

• Simple: Guided, no-code setup gets your pipeline running in minutes, no scripting, no infrastructure management.
• Reliable: Auto-healing pipelines, intelligent retries, and automatic schema handling keep data flowing even when sources change.
• Transparent: Unified dashboards, detailed logs, and data lineage views give you complete end-to-end visibility at every stage.
• Secure: Fully compliant with SOC II, HIPAA, and GDPR, enterprise-grade protection built in.

See how connecting AWS RDS MSSQL to Snowflake can optimize your data workflows. Explore our guide for straightforward instructions on the migration.Unlike tools with opaque usage-based billing, Hevo’s event-based pricing model offers complete cost transparency, no hidden fees, no surprise overages, just clear and consistent billing as your data scales. Schedule a demo today to see if Hevo would be a good fit for you!

If you don’t want SaaS tools with unclear pricing that burn a hole in your pocket, opt for a tool that offers a simple, transparent pricing model. Schedule a demo today to see if Hevo would be a good fit for you!

FAQs