BYOC is available on the Enterprise plan. Contact the Paradime team at support@paradime.io for details.
Prerequisites
The bulk of the provisioning work is done remotely by Paradime automation. However, to get started, you need to provide Paradime with the necessary access along with some additional information:- AWS Account ID: The AWS account ID of the target deployment account, available in the AWS Console.
- AWS Region: The AWS region where the BYOC resources should be deployed.
- Route53 hosted zone: A public Route53 hosted zone for the DNS name your Paradime deployment will live under (for example
paradime.example.com). Paradime creates DNS records for the application endpoints in this zone and uses it for TLS certificate validation. Pass the Hosted Zone ID to your Paradime contact.
ParadimeBYOC IAM role that allows Paradime to:
- Create and manage a VPC
- Create one or more EKS clusters
- Create and maintain 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
- Create and manage ElastiCache Redis instances
- Create and manage FSx for OpenZFS file systems
- Create and manage a DynamoDB table
- Request and validate ACM certificates
- Create DNS records in your Route53 hosted zone
- Create and manage Lambda functions, EventBridge rules, and SNS topics used for operational automation
Provisioning access
Create a ParadimeBYOC policy
Navigate to IAM -> Policies and create a new policy calledParadimeBYOC with the following JSON content. Substitute {AWS_ACCOUNT_ID} with your actual account ID and {HOSTED_ZONE_ID} with the ID of the Route53 hosted zone from the prerequisites.
Created-By: Paradime resource tag, a paradime- name prefix, or both. DNS access is limited to the single hosted zone you nominate. This follows the principle of least privilege and creates a clear boundary between Paradime-managed and customer-managed infrastructure within the same account.
Create a ParadimeBYOC role
Reach out to the Paradime team at support@paradime.io to get the Paradime BYOC provisioner account ID and the external ID used below.
ParadimeBYOC. Select AWS Account as the trusted entity type and enter arn:aws:iam::{PARADIME_PROVISIONER_ACCOUNT_ID}:root, which is the Paradime BYOC provisioner account. On the Add permissions page, find and select the ParadimeBYOC policy you created earlier. On the final Review and create page, edit the Trust Policy to make it look like this:
sts:ExternalId condition. The external ID acts as an additional authentication factor that prevents unauthorized parties from asking Paradime to assume your role.
Deployment
The actual deployment is done by Paradime automation. It provisions the VPC and networking, EKS clusters and node groups, IAM roles and instance profiles, RDS PostgreSQL instances, ElastiCache Redis, FSx for OpenZFS, a DynamoDB table, S3 buckets, CloudWatch Logs delivery, KMS keys, ACM certificates, and DNS records in your hosted zone, all tagged withCreated-By: Paradime.
All that’s left to do is notify your Paradime contact at support@paradime.io that access has been granted, and pass along your AWS Account ID, Region, and Route53 Hosted Zone ID.