Skip to main content

​
Introduction

In this page we’ll explore how to configure a Cosmos cloud environment to connect to resources (ex: a local .html file) on a remote Linux VM via Twingate.

​
Prerequisites

To configure the connectivity between Cosmos and ADO:
  • Cosmos
    • you must have edit access to the cloud env that will connect to a Twingate-protected resource
  • Twingate
    • you need a Twingate paid account (or active free trial)
    • you must have permissions to create a service account
    • you must have permissions to add a new connector: set of access token + refresh token to deploy a connector on the resource/network that will later be accessed by the Cosmos cloud env
  • AWS/GCP/Azure/on-prem
    • you must have SSH access to the Linux VM - this is where the Twingate connector will be deployed

​
Step 1 - Twingate Connector configuration

Go to your Twingate admin console > Network > Overview > Deploy connector > Cloud & Infrastructure > Linux. You should see “Install and Launch Connector Service”: Click on ‘Copy Command’, then ssh into your Linux VM and run the command copied above. You should see this: Then go back to Twingate > Networks > Connectors and observe that your connector has connected: Now let’s create a test python server on that VM (that we’ll later allow-list as Resource in Twingate). First, get the private IP of that VM. From that VM run:
You’ll get something like: 172.31.28.194 From that VM:
  • Create a test html file:
  • Start a test python server (which will be serving the html file):
You should see this:

​
Step 2 - Twingate Service Account configuration

Go to your Twingate admin console > Team > Services > Click on “+ Service” > Service Name = Cosmos > Create Service Account: You should see this: Click on the service account name, the click on “+Service Key”: Keep expiration = 365 days, then Generate: You’ll be offered to rename your key and download the service key token (ex: twingate-cosmos01.json). Then click on “Save & Close”

​
Step 3 - Twingate Resource configuration

Now we’ll add the Linux VM as “Resource” in Twingate. Go to your Twingate admin console > Network > Resources > “+Resource” > Select your network, enter as name “Linux VM”, enter the private IP of your Linux VM > click on Create Resource: Then select your Cosmos service account > Grant Access: You should see this: If you now go to your Cosmos service account view (Twingate admin console > Team > Services > Cosmos) you should see the granted resource:

​
Step 4 - Cosmos cloud env configuration

Go to your Cosmos cloud env from where you’d like to access your Twingate-protected resource. If you don’t have any, create a brand new env: cosmos.augmentcode.com > Settings > Environments > Create an environment > Cloud Machine:
  • Name: Test-Twingate
  • Base image: keep the Cosmos default
  • Repositories: select your repos
  • Refresh: toggle on
  • Click on Create Environment
If you reopen your env, top right click on the 3 dots > Terminal: Install Twingate by running:
Now we’ll bring over the twingate-cosmos01.json key. Run:
Then paste the content of your key, then CTRL-O to save the file, and CTRL-X to exit the file Make sure twingate-cosmos01.json has been created: Move up 1 folder:
Now authenticate to Twingate by running:
You should see: Let’s start Twingate in that terminal session:
Then check that this process is running, paste and enter this:
You should see this: Now let’s try to reach the index.html page:
And should see your Hello World!: Now click on “Update environment” to save your cloud env config, One more step: earlier Twingate was started only in that terminal session. Now we’ll ask Cosmos Advisor to update the cloud env’s startup script so it always starts Twingate upon booting the cloud env across all future sessions. Open a new Cosmos https://cosmos.augmentcode.com > New session > select Cosmos Advisor > select the Test-Twingate cloud env, prompt with
You should see: Any new session stemmed from that Test-Twingate cloud env will now have a Twingate tunnel running.

​
Step 5 - Final Test

Final check, start a brand new session without any expert and prompt execute curl --proxy http://127.0.0.1:9999 http://172.31.28.194:8000, you should see this: Congrats, you’ve configured Twingate with your Cosmos cloud env! You’re now able to leverage Cosmos experts to orchestrate Twingate-protected resources 🎉