Documentation Index
Fetch the complete documentation index at: https://www.latitude.sh/docs/llms.txt
Use this file to discover all available pages before exploring further.
Cloud Gateway establishes a private, secure, and direct connection between your Latitude.sh servers and major cloud providers.
To connect Latitude.sh’s infrastructure to your cloud provider’s resources, log in to the dashboard, select a project, then navigate to Interconnection > Cloud Gateway in the sidebar.
Complete the required fields to submit your request. Once submitted, the team will handle the configurations.
Connecting to AWS
Connecting to GCP
Connecting to Azure
Configure connection details
Choose the location of your Latitude.sh server from which you want to establish the connection to AWS. Optionally, select a private network if one is configured.Enter the IP address range in CIDR format. The IP prefix is associated with your on-premises network and needs to be routable to AWS. Complete the request
Choose the desired port speed for your connection from the available options. Once all fields are completed, click Request.
Cancel AWS connection
Log in to your AWS account and remove the connection associated with Cloud Gateway. Next, go to Support in the dashboard and create a New ticket to request service cancellation.The connection will be terminated once both steps are completed and the team processes your request. Choose the location of your Latitude.sh server from which you want to establish the connection to GCP.
Enter the IP address range in CIDR format. The IP prefix is associated with
your on-premises network and needs to be routable to GCP.
Select GCP as the destination cloud provider.
Enter the GCP region where your resources are hosted.
From the main menu in the Google Cloud Console, select Hybrid Connectivity > Interconnect.
Select Partner Interconnect and click Continue.
Click I already have a service provider.
Configure your attachment.
Provide the following details:
Redundancy: Review the options for redundancy and select. You can create redundant Attachments or a single Attachment.
Network: Select the VPC network you want your VPC to connect to.
Region: Select the region where your attachment will connect.
Cloud Router: A Cloud Router to associate with this attachment. You can only choose a Cloud Router in the VPC network and region that you selected with an ASN of 16550. If you don’t have an existing Cloud Router, create one with an ASN of 16550. For redundancy, each VLAN attachment must be associated with a unique Cloud Router. Google automatically adds an interface and a BGP peer on the Cloud Router.
VLAN attachment name: Lowercase letters only.
Description (optional).
Maximum Transmission Unit (MTU): To use the 1500-byte MTU, the VPC network using the attachment must have an MTU set to 1500. In addition, the on-premises VMs and routers must have an MTU set to 1500. If your network has the default MTU of 1460, leave the field at 1440.
Copy the pairing key and click OK.
Go back to the Cloud Gateway form and paste the copied pairing key into the
Pairing Key field.
Choose the desired port speed for your connection from the available options.
Once all fields are completed, click Request.
Choose the location of your Latitude.sh server from which you want to establish the connection to Azure.
Enter the IP address range in CIDR format. The IP prefix is associated with
your on-premises network and needs to be routable to Azure.
Select Azure as the destination cloud provider.
Enter the service key from your ExpressRoute
circuit.
To generate one, create an ExpressRoute connection in the Azure Portal and
deploy the circuit. Choose the desired port speed for your connection from the available options.
Once all fields are completed, click Request.
