← Back to Help & Guides

01 Deploy·02 Open·03 Kiro·04 Connect AWS·05 Start

1. 01

   Deploy the Runtime

   From your CloudOpsGPT Dashboard, choose your Runtime domain (managed or custom), then launch the AWS CloudFormation deployment. Create the stack and wait until AWS shows CREATE_COMPLETE.

   When launched from the Dashboard, CloudOpsGPT passes your activation token and Runtime version to the deployment automatically.

   Your 7-day trial starts when your Runtime successfully registers and connects — not when you create your workspace.

   Go to Dashboard

   CloudFormation details

   Sign in to the Portal, open Dashboard, and choose Launch CloudFormation. Portal Launch CloudFormation is the supported customer Runtime deployment flow. Portal supplies CloudOpsGPT-specific deployment parameters automatically. The customer reviews and creates the CloudFormation stack in their AWS account.

   Launch CloudFormation (from Dashboard): CloudOpsGPT prefills your ActivationToken, sets RuntimeVersion=version42, and uses NetworkMode=Managed (CloudOpsGPT creates the VPC — you do not select VPC/subnets).

   AWS cost note: Runtime infrastructure is deployed into your AWS account. AWS bills those charges directly to your AWS account. Managed deployment creates networking/runtime resources such as VPC/subnets, ALB, EC2, EBS, public IPv4, and supporting resources. Those AWS charges are not included in the CloudOpsGPT subscription.

   1. Stack name: CloudOpsGPT-Runtime in your chosen region.
   2. Acknowledge IAM capabilities if prompted.
   3. Wait for CREATE_COMPLETE (typically 10–15 minutes).

   Parameter	When	Description
   ActivationToken	Managed hostname	Portal activation token. Required when RuntimeDomainName is empty.
   RuntimeDomainName	Customer domain	Your FQDN. Leave empty when using managed hostname with ActivationToken.
   NetworkMode	Default Managed	Managed creates a CloudOpsGPT VPC (default). Existing uses your VPC (advanced).
   VpcId	Existing network only	Required only when NetworkMode=Existing.
   PublicSubnetIds	Existing network only	Exactly two public subnet IDs in different AZs when NetworkMode=Existing.

   Custom domain: Route53HostedZoneId is optional when your customer-owned domain uses Route53 in this AWS account. Supply ActivationToken with empty RuntimeDomainName, or a non-empty RuntimeDomainName.

   Parameter	Default	Notes
   RuntimeVersion	version42	Container image tag in your account ECR. Dashboard Launch sets this automatically.
   ManagedVpcCidr	10.200.0.0/24	Used only when NetworkMode=Managed.
   InstanceType	t3.medium	t3.small, t3.medium, or t3.large.
   KeyName	empty	Optional. SSM is preferred over SSH.
   RuntimeApiUrl	provided	Leave unchanged unless Portal directs otherwise.
   DeploymentBucket	provided	Bootstrap artifact bucket.
   RuntimeDnsServiceToken	provided	Managed hostname DNS custom resource.

   After stack creation, bootstrap installs Docker and starts Runtime services. If the Runtime URL does not respond, wait several minutes, then check stack Events. For persistent issues, connect with AWS Systems Manager Session Manager (InstanceId output) and review /var/log/cloudopsgpt-install.log.

   Required after CREATE_COMPLETE — Termination protection: As the AWS account administrator, enable CloudFormation Termination Protection on the CloudOpsGPT stack (Console → Stack → Stack actions → Edit termination protection, or aws cloudformation update-termination-protection --enable-termination-protection --stack-name <StackName>). Verify with aws cloudformation describe-stacks --stack-name <StackName> --query "Stacks[0].EnableTerminationProtection" (must return True), then confirm in the Portal Dashboard. CloudOpsGPT does not enable this automatically and does not claim protection until you verify it.

   Intentional uninstall: (1) AWS administrator deliberately disables termination protection; (2) AWS administrator deliberately deletes the CloudOpsGPT stack. The 100 GB data volume may be retained — delete it manually in EC2 if no longer needed.

   Bootstrap pulls container images from ECR repositories cloudopsgpt/runtime-backend and cloudopsgpt/runtime-frontend in your deployment AWS account. If Docker pull fails, contact support@cloudopsgpt.com.

   For customer-owned domains, follow the AcmDnsValidationNote output until DNS and the certificate are valid.

   What the template creates (Managed network):

   • CloudOpsGPT Managed VPC with Internet Gateway and exactly two public subnets (no NAT Gateway)
   • Application Load Balancer with HTTPS and HTTP→HTTPS redirect across two AZs
   • EC2 instance (Amazon Linux 2023) behind the ALB with public IPv4 for outbound access
   • Security groups — public HTTPS to ALB; EC2 reachable from ALB only; SSM for administration
   • EBS root (30 GB) and data volume (100 GB, retained on instance terminate)
   • IAM role — SSM, S3 artifacts, same-account ECR pull
   • Managed hostname or customer domain certificate path
   • Runtime services (Docker) started on first boot

   Stack outputs

   Output	Description
   RuntimeUrl	HTTPS URL for Runtime.
   RuntimeDomainName	Hostname on the certificate.
   AlbDnsName	ALB DNS name.
   CertificateArn	ACM certificate ARN.
   AcmDnsValidationNote	DNS/certificate instructions.
   InstanceId	EC2 instance for SSM access.
   ActivateRuntimeCommand	Advanced CLI activation hint.
   AdminPasswordCommand	Support use only.
   PortalUrl	Commercial Portal.
   RuntimeVersion	Deployed release tag.

   Cleanup / intentional uninstall: First disable termination protection, then delete the CloudFormation stack to remove ALB, EC2, and most resources. The 100 GB data volume may be retained — delete it manually in EC2 if no longer needed.

2. 02

   Open your Runtime

   After the stack reaches CREATE_COMPLETE, open the Runtime URL created by the deployment. CloudOpsGPT activation runs automatically during Runtime startup.

   When Runtime is ready, you'll see the CloudOpsGPT sign-in page. Sign in with your Runtime user account to continue.

   Where do I find RuntimeUrl?

   In the AWS Console, open your CloudOpsGPT stack → Outputs → copy RuntimeUrl. After CREATE_COMPLETE, wait a few minutes for Runtime to finish starting, then open the URL.

   See stack outputs in CloudFormation details for the full output list.

3. 03

   Set Up Kiro

   Complete the one-time Kiro setup for your organisation. Organisation administrators perform this step before your team uses CloudOpsGPT with Kiro.

   Open Kiro Setup

4. 04

   Connect an AWS Account

   From Runtime, connect the AWS account you want CloudOpsGPT to work with. Follow the account connection flow shown in Runtime.

   Connection help

   Deploy the cross-account IAM role in each managed AWS account, register the role ARN in Runtime, and wait for Connected. Ensure ExternalId and trust policy match Runtime instructions. If connection fails, redeploy or update the role stack and re-register.

5. 05

   Start Using CloudOpsGPT

   You're ready. Open CloudOpsGPT and run your first AWS task — for example, ask what the most important resources are in your connected account.

   Go to Dashboard