Skip to main content
Before beginning the technical setup below, two preparatory steps must be completed first.

Technical Setup

Once those steps are complete, Cloud Capital will schedule a meeting to walk you through the setup process if it is unfamiliar to you. You will need to be able to log in to your AWS Organizational Management account with the appropriate role or permissions.
1

Create a New Commitment Account

In your AWS Organization, create a new empty account. This will be the dedicated account into which Cloud Capital purchases commitments — AWS distributes these across your organizational accounts in the most optimized way by design.You can create the account via the AWS Console, Terraform, or CloudFormation. Refer to the AWS documentation for full instructions.
2

Log In to the Cloud Capital Application

Open the Cloud Capital application and log in to your account.
3

Log In to the New Commitment Account

In a second browser tab, log in to the new commitment account you created in Step 1 using an Admin role or login.
Keep both tabs open — you will be switching between them in the steps ahead.
4

Navigate to Cost Optimization Role Setup

Back in the Cloud Capital tab, navigate to the Cost Allocation page using the left-side menu. In the top-right corner, click the Manage Cloud Providers gear icon.On the Cloud Provider Integrations page that opens, click the Manage dropdown and select Cost Optimization Role.
5

Review the Cost Optimization AWS Role Page

You will now be on the Cost Optimization AWS Role page. This is where you will install the role that allows Cloud Capital to purchase commitments into your new account.
Commitments purchased into a dedicated account within your AWS Organization distribute automatically across all member accounts. This is AWS best practice for commitment management and ensures the most optimized coverage across your full organization.
6

Run the CloudFormation Stack

Click Run CloudFormation Stack. This opens an AWS Console page with the CloudFormation stack pre-populated and ready to deploy.
Before proceeding, you can click View Template to inspect the permissions and resources the stack will create. This is recommended if your security team needs to review the role before deployment.
At the bottom of the page, check the acknowledgement box confirming that this stack will create AWS resources, then click the Create Stack button in the bottom-right corner.
7

Copy the Role ARN from Stack Outputs

Stack creation takes approximately 3–4 minutes. Once complete, click on the Outputs tab for the stack and copy the ARN for the role that was created.The ARN will look similar to this:
arn:aws:iam::############:role/CloudCapitalOptimizationRole
8

Paste the Role ARN into Cloud Capital

Return to the Cloud Capital app tab. Paste the Role ARN you copied into the provided field. The Commitment Buying dropdown will update to Enabled.
9

Test the Role

Click Test Role to verify that the role is working correctly with Cloud Capital’s systems. A successful test will be confirmed with a confetti animation on screen.
If the test fails, double-check that the CloudFormation stack completed successfully and that you copied the full ARN from the Outputs tab. Contact support@cloudcapital.co if the issue persists.
10

Save and Complete Onboarding

Click the Save button on the far right of the page to finalise the setup.

What Happens Next

Congratulations — the technical setup is complete. The Cloud Capital Customer Success team will now schedule a series of meetings with you and your team. These sessions begin the process of reviewing your cloud spend forecast, factoring in business initiatives and metrics, and analysing your architecture spend trends. From those discussions, Cloud Capital will propose a structured ladder sequence of savings commitments designed to maximise your cloud savings potential — with Cloud Capital taking on the commitment risk on your behalf.

Learn About the Onboarding & Proposal Process

Understand how Cloud Capital analyses your spend, builds the commitment ladder, and manages the weekly review cadence with your team.