This guide outlines the process for deploying Devin in your AWS Virtual Private Cloud (VPC) environment, providing access to resources within your corporate firewall.
Terraform deployment is our recommended approach for setting up Devin in your AWS VPC. This automated method ensures consistent, repeatable infrastructure provisioning with minimal manual configuration.
Gather the following information which will be required for the Terraform configuration:
AWS Account Number (12-digit number)
VPC ID (vpc-xxxxxxxxxxxxxxxxx)
Two Subnet IDs:
subnet-xxxxxxxxxxxxxxxxx
subnet-xxxxxxxxxxxxxxxxx
Helpful AWS CLI commands:
Copy
Ask AI
# List your VPCsaws ec2 describe-vpcs# List subnets in a specific VPCaws ec2 describe-subnets --filters "Name=vpc-id,Values=<your-vpc-id>"
2
Configure Firewall Access
Ensure your endpoint security systems (user devices that will access Devin) allow access to:
*.devin.ai
*.devinenterprise.com
*.devinapps.com
3
Obtain Terraform Configuration and Auth Token
Contact Cognition to receive:
An authentication token for pulling the hypervisor image
The Terraform configuration files customized for your environment
Once you share your environment information (from Step 1), we will provide these resources to you.
4
Execute Terraform Script
We can schedule a call to execute this step together. The process involves:
Extract the Terraform configuration files to a directory on your local machine:
Copy
Ask AI
mkdir -p ~/devin-terraform && cd ~/devin-terraform# Extract files received from Cognition
Initialize the Terraform environment:
Copy
Ask AI
terraform init
Review the planned infrastructure changes:
Copy
Ask AI
terraform plan
Apply the configuration to provision the infrastructure:
Copy
Ask AI
terraform apply
Confirm the changes when prompted.
The Terraform scripts will set up all necessary components including EC2 instances, S3 buckets, security groups, IAM roles, and the hypervisor registration.
5
Run First Devin Session
After the Terraform script completes successfully, we will work together to:
Verify that the resources have been created in your AWS console
Run a first Devin session to ensure connectivity to the required services
Debug any issues that arise with the support of Cognition team