Overview
Stigg’s integration with Amazon Aurora (MySQL-compatible) allows you to export your product catalog, customer, and subscription data directly to your Aurora cluster for custom reporting and analysis.Stigg’s native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg’s pricing for more details.
View the full entity schema
See every table and column exported to your destination, organized by entity group.
Setting up the integration
Prerequisites
You’ll need an Aurora MySQL cluster with a database and a user that has permission to create tables and write data in the target schema. Aurora MySQL 3.x (MySQL 8.0-compatible) is fully supported; Aurora MySQL 2.x is supported on a best-effort basis.1
Allow access
In the RDS console, go to Databases and select your Aurora MySQL instance. On the Connectivity & security tab, note the Endpoint and Port (usually
3306).Confirm the Publicly accessible setting is set to Yes — it’s still only reachable through whitelisted IPs at this point. If you’re connecting via SSH tunnel instead, this can be left as No.You may need to select the Writer instance in the DB identifier list to reveal its endpoint — this is the endpoint to use, since Stigg needs to write data.Click the VPC security group (usually default) attached to the Writer instance, then click Edit inbound rules > Add rule:Save the rule.
Also check the Network ACL attached to the cluster’s VPC. From the RDS instance’s VPC, open the Main network ACL and confirm there’s an inbound rule allowing traffic on the database port from Stigg’s static IP (most default ACLs already allow this via a
0.0.0.0/0 rule), and an outbound rule allowing ports 1024–65535 to 0.0.0.0/0.If your cluster isn’t accessible from the public internet, SSH tunneling through a bastion host is supported instead: allow inbound SSH (port
22) from Stigg’s static egress IP on the bastion host, create an SSH user with Stigg’s public key in ~/.ssh/authorized_keys (contact Stigg support for the key), and use the bastion host’s security group as the source in the inbound rule above instead of Stigg’s static IP. Provide the bastion host address, port, and username in the connection form.2
Create a writer user
Create the database user Stigg will connect as, and grant it the required privileges:If you’re pre-creating the schema rather than letting Stigg create it on first sync, grant privileges on that schema only instead:
3
Connect Stigg with Aurora (MySQL)
In Stigg, navigate to Integrations > Apps > Amazon Aurora (MySQL).Enter the following information in the connection form:
Click Test & connect.
4
Select entities to export
After entering your connection details, expand the Entities to export section to choose which entity groups to include in the sync. All groups are selected by default.See Exported entities for a description of each group.