Skip to main content

​
Prerequisites

  • If your MySQL database is protected by security groups or other firewall settings, you will need to have the data-syncing service’s static IP available to complete Step 1.

​
Step 1: Allow access

Allow write access to a portion of your Aurora MySQL database.

​
Configure the Security Group

  1. In your Amazon RDS > Databases list, click the MySQL instance you want to send data to.
  2. In the database page, in the Connectivity & security tab, make note of the Endpoint and the Port number. Note that you may need to select the “Writer instance” in the DB identifier list to reveal the endpoint.
  1. To ensure that the destination is accessible from outside your VPC, click “Modify” in the top right, and in the “Connectivity” section, within the Additional configuration dropdown, confirm the Publicly accessible setting is set to Yes (or No if you plan to connect through a bastion host via SSH tunneling instead). Note that it is still only accessible through whitelisted IPs at this point.
  1. Returning to the database page, within the “Writer instance” details, click one of the VPC security groups (usually default). Note: VPC groups are permissive (vs. restrictive) and for instances with multiple VPC security groups, only one needs to be configured with the new inbound rule.
  1. In the Security Groups section, select the Inbound rules tab.
  2. Click Edit inbound rules and then click Add rule.
  3. Edit the newly created rule of type Custom TCP with the Port range noted in the first step (usually 5432) and a Custom Source value that includes all of the service IPs. Note: you will need to add /32 to the end of each IP (CIDR notation).
  4. Click Save rules.

​
Configure network ACLs (access control list)

For database instances in a VCP
  1. In your RDS dashboard, select the MySQL instance.
  2. Click the link to the instance’s VPC.
  3. Click the VPC ID.
  1. In the Details section, click on the link under Main network ACL.
  1. Click on the network ACL ID.

​
Edit the inbound rules

  1. Click on the Inbound rules tab, and check if there is an existing rule with a Source of 0.0.0.0/0 set to Allow. (This is a default rule created by AWS. If this rule already exists, skip to Edit outbound rules.)
  1. Create the inbound rule (if it doesn’t exist). Click Edit inbound rules and either Add new rule or edit an existing rule to allow access to the port number of your database instance (usually 5432) from the data-syncing service’s static IP. Click Save changes.

​
Edit the outbound rules

  1. In the ACL menu, select the Outbound rules tab, and check if there is an existing rule with a Destination of 0.0.0.0/0 set to Allow. (This is a default rule created by AWS. If this rule already exists, skip to the next step.)
  1. Create the outbound rule (if it doesn’t exist). Click Edit outbound rules and edit the rules to allow outbound traffic to ports 1024-65535 for Destination 0.0.0.0/0.
Connecting through a bastion hostIf you prefer not to make the database publicly accessible, SSH tunneling through a bastion host is supported instead. Allow inbound SSH (port 22) on the bastion host’s security group, create an SSH user and add the data-syncing service’s public key to ~/.ssh/authorized_keys, and add the bastion host’s security group to the database’s inbound rules. You will provide the bastion address, port, and username when configuring the destination.

​
Step 2: Create writer user

Create a database user to perform the writing of the source data.
  1. Open a connection to your Aurora MySQL database.
  2. Create a user for the data transfer by executing the following SQL command.
  1. Grant user required privileges on the database.
If the schema/database already exists:By default, the service creates a new schema (in MySQL, schema is synonymous with database). If you prefer to create the schema yourself before connecting the destination, you must ensure that the writer user has the proper permissions on the schema, using GRANT ALL PRIVILEGES ON <database_name>.* TO <username>@'%';

​
Step 3: Add your destination

Securely share your host name, database name, port, your chosen schema name, username, and password with us to complete the connection.