AWS

Deploy and manage your infrastructure on AWS using Ryvn’s automated provisioning system.

​

Prerequisites

Before you begin, make sure you have:

• An AWS account
• Access to the AWS Console

​

Configure Your Environment

1. Go to the Environments tab in the Ryvn Dashboard
2. Click Create Environment in the top-right corner
3. Give your environment a name (e.g. production)
4. Select a release channel (e.g. production)
   Release channels link services to environments. When you push code changes, services publish releases to release channels. Environments subscribed to those channels automatically deploy new releases.

5. Click Create Environment

​

Provisioning Steps

1. From your environment in the Ryvn Dashboard, click View Environment
2. Click Self Setup
3. Click Start Provisioning
4. Select AWS as your cloud provider
5. Fill out the form with your AWS credentials
6. Click Continue
7. Click Create Permissions
8. Follow the AWS-specific instructions shown in the dashboard
9. Return to Ryvn and wait for provisioning to complete

​

Provisioning Methods

Ryvn offers two methods for provisioning AWS infrastructure:

​

BYOC (Bring Your Own Cloud)

With BYOC, Ryvn creates a new VPC in your AWS account with the specified CIDR block.

​

Configuration Interface

BYOC provisioning offers two configuration modes:

Basic Mode A user-friendly form interface with the following options:

• Region: Select your AWS region (e.g., US East, EU West)
• VPC CIDR Block: Specify the IP range for your VPC (default: 10.42.0.0/16)
• Application Node Group Configuration:
  • Instance Type: Choose from t3.medium (2 CPU, 4GB RAM), t3.large (2 CPU, 8GB RAM), or t3.xlarge (4 CPU, 16GB RAM)
  • Min Size: Minimum number of nodes (recommended: 2)
  • Max Size: Maximum number of nodes for scaling

Advanced Mode A YAML editor for more detailed configuration:

Configuration Requirements:

• You must specify a vpc_cidr value in the standard CIDR notation format (e.g., 10.0.0.0/16)
• The CIDR block must be a valid IPv4 address range with a subnet mask between /0 and /32

Example configuration:

region: us-east-1
vpc_cidr: 10.42.0.0/16
eks_managed_node_groups:
  application:
    instance_types: ["t3.large"]
    min_size: 2
    max_size: 2
    desired_size: 2
  system:
    instance_types: ["t3.large"]

​

Custom Terraform Executor Policies

For cases where you need to deploy Terraform services with specific permissions, you can add custom IAM policy statements to the Ryvn Agent role by adding a terraform_executor_policies block to your configuration:

terraform_executor_policies:
  - effect: Allow
    actions:
      - "*"
    resource: "*"

This configuration grants full access permissions to Terraform services running in your environment, allowing you to deploy any Terraform resources without restriction. You can also specify more granular permissions if needed.

​

BYOVPC (Bring Your Own VPC)

With BYOVPC, Ryvn uses an existing VPC in your AWS account.

Configuration Requirements:

• You must specify a vpc_id that starts with “vpc-”
• You must provide at least 3 unique private subnet IDs, each starting with “subnet-”
• All subnet IDs must be unique

Example configuration:

vpc_id: vpc-0123456789abcdef0
private_subnet_ids:
  - subnet-0123456789abcdef1
  - subnet-0123456789abcdef2
  - subnet-0123456789abcdef3

​

What Gets Created

Ryvn provisions a production-ready EKS cluster in your AWS account, complete with secure networking and IAM configuration. This includes a VPC with private subnets, load balancers for service exposure, and all necessary security groups and IAM roles.