Infrastructure Setup

​

Overview

This section guides you through creating the cloud infrastructure for Relvy self-hosting using AWS as an example. The core self-hosting setup requires an application server and database.

​

Routing Options

If you have a way to route a subdomain to your Relvy server (e.g., through your existing load balancer, reverse proxy, or direct DNS), you can skip the load balancer and SSL certificate setup. Otherwise, you’ll need to deploy an Application Load Balancer and obtain an SSL certificate for secure access.

​

Core Components (Required)

​

Optional Components (Production)

​

Step 1: Create Security Groups

Security groups act as virtual firewalls to control network access. We’ll create security groups for the required components, with optional groups for the load balancer setup.

​

1.1 ALB Security Group (Optional)

Navigate to EC2 Console → Security Groups → Create Security Group

​

Inbound Rules

​

Outbound Rules

​

1.2 App Security Group

Navigate to EC2 Console → Security Groups → Create Security Group

​

Inbound Rules

​

Outbound Rules

​

1.3 Database Security Group

Navigate to EC2 Console → Security Groups → Create Security Group

​

Inbound Rules

​

Outbound Rules

• None (databases don’t need outbound access)

​

1.4 Update ALB Security Group

Now update the ALB security group’s outbound rule:

1. Navigate to EC2 Console → Security Groups
2. Select relvy-alb-sg
3. Click Edit outbound rules
4. Update the HTTP rule destination to relvy-app-sg

​

Step 2: Create Application Load Balancer (Optional)

If you have a way to route a subdomain to your Relvy server (as mentioned in the Routing Options above), you can skip this step. Otherwise, create a load balancer for production use.

Navigate to EC2 Console → Load Balancers → Create Load Balancer

​

2.1 Basic Configuration

​

2.2 Network Configuration

​

2.3 Create Target Group

1. Click “Create target group” (opens in new tab)
2. Configure as follows:

​

2.4 Configure Listener

​

2.5 Review and Create

Review the configuration and create the ALB. Note down the ALB DNS name: relvy-app-alb-xxxxxxxxx.us-west-2.elb.amazonaws.com

​

Step 3: Create EC2 Instance (Core Component)

This is the main application server. You can access Relvy directly through this instance if you don’t need a load balancer.

Navigate to AWS Console → EC2 → Instances → Launch Instance

​

3.1 Basic Configuration

​

3.2 Instance Type

​

3.3 Key Pair

Option A: Create new key pair

1. Click Create new key pair
2. Name: relvy-app-key
3. Key pair type: RSA
4. Private key format: .pem
5. Click Create key pair and download

Option B: Use existing key pair

• Select from dropdown if you already have one

​

3.4 Network Settings

​

3.5 Storage Configuration

​

3.6 Launch Instance

Review and launch the instance. Wait for it to reach the “Running” state.

​

3.7 Register with Load Balancer (Optional)

If you created a load balancer in Step 2:

1. Navigate to EC2 → Target Groups
2. Select your target group (relvy-app-tg)
3. Click Register targets
4. Select your new instance
5. Port: 80
6. Click Include as pending below → Register pending targets

If you’re not using a load balancer, you can access Relvy directly via the EC2 instance’s public IP address.

​

Step 4: Create RDS Instance

​

4.1 Create Database Instance

Navigate to RDS Console → Databases → Create database

​

4.1.1 Database Creation Method

• Standard create (not Easy create)

​

4.1.2 Engine Options

​

4.1.3 Templates

• Production (for best practices)

​

4.1.4 Settings

​

4.1.5 Instance Configuration

​

4.1.6 Connectivity

​

4.1.7 Database Authentication

• Database authentication: Password authentication

​

4.1.8 Additional Configuration

Wait for DB creation and note the endpoint.

​

4.2 Update App Security Group

Navigate to EC2 Console → Security Groups → relvy-app-sg

Add outbound rule:

• Type: PostgreSQL, Port: 5432, Destination: relvy-db-sg, Description: Database access

​

Step 5: Verify Infrastructure

​

5.1 Check All Components

Verify all components are created and running:

​

5.2 Test Connectivity

# Test SSH access to EC2
ssh -i relvy-app-key.pem ec2-user@<EC2_PUBLIC_IP>

# Test database connectivity (from EC2)
sudo yum install -y postgresql17
psql -h <RDS_ENDPOINT> -U postgres -d relvydb

​

Important Notes

​

Next Steps

Your cloud infrastructure is now ready! The next steps are:

1. Configure Domain - Set up DNS records and SSL certificate in Domain Configuration
2. Setup Slack Integration - Create Slack app (optional) in Slack Setup
3. Deploy Application - Install Docker and deploy Relvy in Application Deployment