Skip to main content

Setup Zuora Connector for Aurora MySQL

Zuora

Setup Zuora Connector for Aurora MySQL

  1. Last updated
  2. Save as PDF
Provides detailed instructions for setting up the Zuora Connector for Aurora MySQL.

Configuring your Aurora MySQL destination within the Zuora Connector includes steps for setting up Aurora MySQL database credentials, managing permissions, configuring access to the database, and other necessary configurations to facilitate a smooth data transfer process from Zuora to Aurora MySQL.

  •  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. Navigate to Amazon RDS > Databases list. Click the MySQL instance you want to send data to.
  2. On the database page, in the Connectivity & security tab, note the Endpoint and the Port number. You may need to select the Writer instance in the DB identifier list to reveal the endpoint.

    1- aws-mysql-endpoint-port.png
     
  3. To ensure that the destination is accessible from outside your VPC, click Modify at the top right, and in the Connectivity section, within the Additional configuration dropdown, confirm the Publicly accessible setting is set to Yes . Note that it is still only accessible through whitelisted IPs at this point.

    2 - aws-mysql-publicly-accessible.png
     
  4. 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.

    3 -aws-mysql-default-security-group.png
     
  5. In the Security Groups section, select the Inbound rules tab.
  6. Click Edit inbound rules and then click Add rule.
  7. 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).
  8. Click Save rules.

    4 -postgres-add-rule.png

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.

    5 -postgres-vpc-id.png
     
  4. In the Details section, click on the link under Main network ACL.

    6- postgres-main-network-acl-id.png
     
  5. Click on the network ACL ID.

    7 -postgres-network-acl-id.png
     
  6. 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.

      8-postgres-inbound-rules.png
       
    2. Create the inbound rule (if it does not 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 Prequel static IP. Click Save changes.

  7. 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.)


      9-postgres-outbound-rules.png

    2. 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.

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. CREATE USER <username>@'%' IDENTIFIED BY '<some-password>';
  3.  Grant user required privileges on the database. 
    1. GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, CREATE TEMPORARY TABLES, CREATE VIEW ON *.* TO <username>@'%';

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 .* TO @'%';

Step 3: Add Your Destination

  1. After completing the initial setup, provide the host address of your Aurora MySQL database to a Zuora representative. They will use this information to create a connection link for you. 
  2. Using the provided link, you can securely input your Aurora MySQL details, including the port, database name, schema, and authentication credentials. 
  3. Once you fill in these details and test the connection, saving the destination will initiate the onboarding process and begin transferring data from Zuora to your Aurora MySQL database.

Verification and Data Transfer

Once data synchronization is configured with the Aurora MySQL connector, the data is automatically transferred to the specified Aurora MySQL database. This enables direct access and querying of the data within your Aurora MySQL environment or through compatible data analysis tools. You can seamlessly manage and analyze this data within your Aurora MySQL ecosystem.

Format of Transferred Data

For Aurora MySQL, the transferred data will be loaded as properly typed tables within a single schema in the database. Additionally, a special _transfer_status table will be created within the schema to record transfer metadata, specifically including a transfer_last_updated_at timestamp for each table. This table helps track the last update time for the transferred data, facilitating data management and synchronization processes.