Skip to main content

Deploying CloudCADI from AWS Marketplace on EKS

CloudCADI is deployed into the customer’s AWS account using an AWS CloudFormation template, which provisions the required infrastructure, including an Amazon EKS cluster and Amazon RDS for PostgreSQL. The CloudCADI application is then configured and deployed to the EKS cluster using Helm.

CloudFormation Stack Deployment Walkthrough​

This document describes the step-by-step procedure to deploy the CloudCADI application on Amazon Elastic Kubernetes Service (EKS) using an AWS CloudFormation stack.

Step 1 - Specify Stack Details​

  1. Under Provide a stack name, enter a Stack name (e.g. Multicloud-cloudcadi).

  2. Under EKS cluster, provide the following details:

    ClusterName: Enter the EKS cluster name (unique per account/region).

    KubernetesVersion: Enter the EKS control plane version (e.g. 1.36).

    NodeInstanceType: Enter the node instance type (e.g. t3.large).

    NodeDesiredSize, NodeMinSize, NodeMaxSize: Enter the desired, minimum, and maximum node group size.

    Specify stack details

  3. Under Security configuration, provide the following detail:

    HTTPCIDR: Enter your public IP, or 0.0.0.0/0 to access the CloudCADI UI from anywhere.

  4. Under Network, the VpcCidr and public subnet CIDRs (PublicSubnet1Cidr, PublicSubnet2Cidr) can be left at their default values.

    Security configuration & Network

  5. Under S3 CUR, provide the following details:

    S3BucketName: Enter the bucket name. (Refer to Cost & Usage Data Export (FOCUS))

  6. Under RDS PostgreSQL, provide the following details:

    DBName: Enter the database name.

    DBUsername: Enter the RDS master username.

    DBPassword: Enter the database password.

    DBInstanceClass: Enter the RDS instance class (e.g. db.t3.small).

    Security configuration, Network, S3 CUR, RDS PostgreSQL parameters

  7. Under Cross-Account Configuration and Cross-platform Configuration, leave the default Cross-account ExternalId (or provide your own) and optional AwsTokenIssuerUrl. Cross-Account and Cross-platform Configuration

    Enable Outbound Identity Federation

    Follow these steps to obtain the Token Issuer URL used for AwsTokenIssuerUrl:

    1. Sign in to the AWS account and open IAM → Account settings.

    2. Under Security Token Service (STS), find Outbound Identity Federation and click Enable.

      Outbound Identity Federation - disabled

    3. Once enabled, copy the Token Issuer URL shown under Outbound Identity Federation and use it as the AwsTokenIssuerUrl value.

      Outbound Identity Federation - enabled

  8. Click Next.

Step 2 - IAM Access Configuration​

  1. Under Capabilities, check I acknowledge that AWS CloudFormation might create IAM resources with custom names, then click Create stack. Acknowledge IAM capabilities
Note

Resource creation may take up to 15 minutes.

Step 3 - Accessing CloudCADI​

  1. Once the stack creation is complete, navigate to CloudFormation → Stacks.
  2. Select the newly created CloudCADI stack (e.g. Multicloud-CloudCADI). Stack
  3. Access the CloudCADI application URL from the stack outputs.
  4. You will be redirected to the CloudCADI login page.

Architecture​

CloudCADI on AWS Marketplace — Architecture & Flow
Enterprise FinOps Platform — EKS Deployment (AWS Marketplace CloudFormation flow)
Cluster: Amazon EKS | Database: RDS for PostgreSQL | Storage: Amazon S3 (CUR) | IaC: CloudFormation + Helm | Source: AWS Marketplace
1
Launch the Stack
Launch the CloudCADI CloudFormation stack from AWS Marketplace into the customer's AWS account
→
2
Specify Stack Details
Provide the stack name and parameters for the EKS cluster, VPC/network, S3 CUR bucket, RDS PostgreSQL, and cross-account configuration
→
3
IAM Access Configuration
Acknowledge that CloudFormation may create IAM resources with custom names, then create the stack
→
4
Access CloudCADI
Once stack creation completes, open the application URL from the stack outputs
1
VPC & Networking
Public subnets and security rules restricting UI access to the configured HTTPCIDR
→
2
EKS Cluster
Managed node group sized by the node instance type and min/desired/max parameters
→
3
RDS PostgreSQL
The CloudCADI application connects to RDS for PostgreSQL for application data and database operations
→
4
Helm Deployment
The Helm chart deploys CloudCADI workloads into the provisioned EKS cluster
→
5
Pods Running
CloudCADI containers running inside the customer's EKS cluster
Stack Parameters
  • EKS cluster — ClusterName, KubernetesVersion, NodeInstanceType, node scaling sizes
  • Security — HTTPCIDR
  • Network — VpcCidr, PublicSubnet1Cidr, PublicSubnet2Cidr
  • S3 CUR — S3BucketName for Cost & Usage Report access
  • RDS PostgreSQL — DBName, DBUsername, DBPassword, DBInstanceClass
  • Cross-account / Cross-platform — ExternalId, AwsTokenIssuerUrl
Deployment Model
  • AWS Marketplace — CloudFormation stack, customer-run
Tech Stack
  • Amazon EKS (Kubernetes)
  • RDS for PostgreSQL
  • Amazon S3 (CUR)
  • AWS CloudFormation + Helm
CloudCADI deploys into the customer's own AWS account — the EKS cluster, RDS database, and S3 buckets all stay within their account.