With Bring Your Own Cloud (BYOC) on AWS, all the components interacting with private data are deployed on the customer infrastructure on AWS and managed by the Cube Control Plane via the Cube Operator. This document provides step-by-step instructions for deploying Cube BYOC on AWS.Documentation Index
Fetch the complete documentation index at: https://docs.cube.dev/llms.txt
Use this file to discover all available pages before exploring further.
Available on the Enterprise plan.
Contact us for details. For private API access from your
applications and BI tools, see Private API Connectivity.
Prerequisites
The bulk of provisioning work will be done remotely by Cube automation. However, to get started, you’ll need to provide Cube with the necessary access along with some additional information that includes:- AWS Account ID: The AWS account ID of the target deployment account the AWS Console.
- AWS Region: The AWS region where the BYOC resources should be deployed.
CubeCloudBYOC IAM role that would allow Cube to:
- Create and manage a VPC
- Create one or more EKS clusters
- Create necessary IAM roles and policies
- Configure VPC networking
- Run ec2 instances
- Manage ec2 autoscaling
- Manage S3 buckets
- Manage CloudWatch Logs
- Create and manage RDS PostgreSQL instances
Provisioning access
Create a CubeCloudBYOC policy
Navigate to IAM->Policies and create a new policy calledCubeCloudBYOC
with the following JSON content. Please substitute AWS_ACCOUNT_ID with your
actual account ID.
Creating a role
Navigate to IAM->Roles and create a new Role calledCubeCloudBYOC. Select
AWS Account as the Trusted entity. Type and enter
arn:aws:iam::307491255751:root, which is the Cube BYOC provisioner
account. On the Add permissions page, find and select the CubeCloudBYOC
policy you created earlier. On the final Review and create page, edit the
Trust Policy to make it look like this.
"sts:ExternalId": "cube-cloud-byoc" in the Condition section.