Guides
Start typing to search…

VPC peering

This section explains how VPC peering enables account-to-account connectivity between your VPC and Quickwork’s VPC allowing Quickwork journeys to securely access private resources over the cloud provider’s internal network, without public IP whitelisting.

Enterprises often need Quickwork to connect with databases, APIs, and internal applications that sit inside private subnets.

VPC peering is the preferred and most secure connectivity option for enterprises using Quickwork. It enables a private, direct network connection between your cloud environment (for example, AWS or Azure) and Quickwork’s infrastructure, without exposing any systems to the public internet.

Through VPC peering, Quickwork establishes account-to-account connectivity between two Virtual Private Clouds (VPCs), allowing seamless and secure data flow between Quickwork journeys and your private resources such as databases, APIs, or internal applications.

Benefits

  • No public exposure: Your infrastructure remains in a private subnet, with no need to whitelist public IPs.
  • Enhanced security: Data never leaves the cloud provider’s internal network.
  • Low latency: Direct routing between subnets ensures faster communication than internet-based connections.
  • Enterprise-ready: Trusted and deployed with leading enterprises and financial institutions.

How it works

  1. Quickwork creates a private subnet within its infrastructure dedicated to your account.
  2. Your cloud team creates a subnet dedicated to Quickwork connectivity within your VPC.
  3. Quickwork and your cloud team exchange VPC peering details (VPC ID, Account ID, and CIDR block).
  4. Quickwork sends a VPC peering request to your cloud account.
  5. Your team accepts the request from the cloud console.
  6. Once approved, traffic between the two VPCs is routed privately through the peering connection.

Customer scope

  • Provide the following details to Quickwork:
    • Cloud Account ID (For example, AWS Account ID).
    • VPC ID and CIDR block.
  • Accept the VPC peering request initiated by Quickwork.
  • Update routing tables in your VPC to allow communication with Quickwork’s private subnet.

Quickwork scope

  • Initiate and manage the VPC peering request from Quickwork’s private VPC.
  • Configure private routing and network rules for your specific workflow requirements.
  • Ensure secure data exchange and transaction flow as defined in your automation setup.

Example: Connecting to a private RDS via VPC peering

If your AWS environment hosts an RDS database (For example, PostgreSQL, MySQL) in a private subnet, Quickwork can access it securely via VPC peering:

  1. Your AWS team provides: AWS Account ID, Target VPC ID, CIDR block for the private subnet
  2. Quickwork sends a VPC peering request using these details.
  3. Your AWS administrator accepts the request in the AWS Management Console.
  4. Both sides update route tables to establish two-way communication.
  5. Quickwork journeys can now securely query or insert data into your RDS instance without using public endpoints.

Contact for setup

To initiate a VPC peering setup, please write to [email protected]

Include the following details in your request:

  • Your Quickwork account email address.
  • Your AWS Account ID, VPC ID, and CIDR block for which VPC peering needs to be performed.

Quickwork’s infrastructure team will validate the details, share the required Quickwork-side AWS Account ID, VPC/CIDR information via support, and initiate the VPC peering request from Quickwork’s environment.

📚 Additional resources

https://docs.aws.amazon.com/vpc/latest/peering/create-vpc-peering-connection.html


Updated 28 days ago