EverSQL supports AWS PrivateLink endpoint connections, allowing you to connect your CI/CD workflows directly to EverSQL's Amazon VPC service, so that traffic is transferred over AWS's backbone without leaving the AWS cloud.
This architecture can be used by customers hosting their source control software without public access to the internet (for example, Github Enterprise hosted on a private AWS VPC).
Integrating with EverSQL via AWS PrivateLink
Please follow these steps to create an endpoint in your AWS account, which will allow you to directly connect with EverSQL's API server over an AWS PrivateLink connection.
- As PrivateLink connections require pre-approval, please reach out to our support team at [email protected] and let us know your AWS account id. Once approved, please continue with the steps below.
- Navigate to the VPC dashboard on your AWS management console and choose the VPC you're hosting your source control application on.
- Choose Endpoints from the left-side menu and click Create Endpoint. Please make sure you do not accidentally navigate to the Endpoint Services, but rather to the Endpoints page.
- Choose Find service by name, paste the following service name and click Verify: com.amazonaws.vpce.us-east-1.vpce-svc-019311960f2daf908
- Choose the VPC you're hosting your source control application on, and choose the relevant private subnets.
- Create a security group allowing HTTPS access to the endpoint and associate it with the endpoint.
- Click Create Endpoint. Once the endpoint was created successfully, please reach out to our support team to get the endpoint approved.
- You've now created an endpoint which is directly connected to EverSQL's AWS VPC. The endpoint's DNS name is https://privatelink.eversql.com, which will be used during the GitHub integration.
- Once the endpoint is approved by the EverSQL team, you can integrate GitHub Actions with EverSQL to get your SQL queries scanned and optimized automatically as part of your CI/CD workflows.