Cloud Deployment Guide for RLC¶

This guide covers deploying Rocky Linux from CIQ (RLC) in various cloud environments.

Supported Cloud Platforms¶

RLC is available across major cloud platforms:

Amazon Web Services (AWS)
Microsoft Azure
Google Cloud Platform (GCP)
Oracle Cloud Infrastructure (OCI)

AWS Deployment¶

From AWS Marketplace¶

Navigate to AWS Marketplace
Search for "Rocky Linux from CIQ"
Select the appropriate instance type
Configure networking and security
Launch instance

Command Line Deployment¶

# Launch RLC instance
aws ec2 run-instances \
  --image-id ami-rlc-latest \
  --instance-type t3.medium \
  --key-name my-key-pair \
  --security-group-ids sg-12345678 \
  --subnet-id subnet-12345678

Azure Deployment¶

From Azure Marketplace¶

Access Azure Marketplace
Find "Rocky Linux from CIQ"
Configure resource group and networking
Deploy virtual machine

PowerShell Deployment¶

# Create RLC VM
New-AzVM `
  -ResourceGroupName "myResourceGroup" `
  -Name "rlc-vm" `
  -Location "East US" `
  -ImageName "RLC-Publisher:RLC-Offer:RLC-SKU:latest" `
  -Size "Standard_B2s"

Google Cloud Platform¶

From GCP Marketplace¶

Visit GCP Marketplace
Locate "Rocky Linux from CIQ"
Configure project and networking
Create instance

gcloud CLI Deployment¶

# Create RLC instance
gcloud compute instances create rlc-instance \
  --image-family=rlc-family \
  --image-project=ciq-public \
  --machine-type=e2-medium \
  --zone=us-central1-a

Oracle Cloud Infrastructure¶

From OCI Marketplace¶

Navigate to OCI Marketplace
Search for "Rocky Linux from CIQ"
Configure compartment and networking
Launch compute instance

Post-Deployment Configuration¶

Initial Setup¶

# Connect to instance
ssh -i your-key.pem ec2-user@instance-ip

# Update system
sudo dnf update

# Configure repositories (if needed)
sudo dnf config-manager --enable rlc-extras

Security Configuration¶

# Configure firewall
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --reload

# Update SSH configuration
sudo vim /etc/ssh/sshd_config
sudo systemctl restart sshd

Cost Optimization¶

Instance Sizing¶

Development: t3.micro, B1s, e2-micro
Production: t3.medium+, Standard_B2s+, e2-standard-2+
High Performance: c5.xlarge+, Standard_F4s+, c2-standard-4+

Reserved Instances¶

Consider reserved instances for long-term deployments to reduce costs.

Monitoring and Management¶

Cloud-Native Monitoring¶

Each cloud platform provides native monitoring:

AWS: CloudWatch
Azure: Azure Monitor
GCP: Cloud Monitoring
OCI: Monitoring Service

RLC-Specific Monitoring¶

# Install monitoring tools
sudo dnf install htop iotop nethogs

# Configure system monitoring
sudo systemctl enable --now cockpit.socket

Backup and Recovery¶

Cloud Snapshots¶

Use cloud-native snapshot services for backup:

# AWS
aws ec2 create-snapshot --volume-id vol-12345678

# Azure
az snapshot create --resource-group myRG --source myVM

# GCP
gcloud compute disks snapshot my-disk --snapshot-names=my-snapshot

Networking¶

Security Groups / Firewall Rules¶

Configure appropriate security groups for your RLC instances:

# Common ports to consider:
# 22 - SSH
# 80 - HTTP
# 443 - HTTPS
# 9090 - Cockpit (if used)

Troubleshooting¶

Common Cloud Issues¶

Instance not accessible: - Check security groups/firewall rules - Verify SSH key configuration - Confirm public IP assignment

Repository access issues: - Verify outbound internet connectivity - Check DNS resolution - Confirm RLC subscription status

For detailed troubleshooting, see the main Troubleshooting Guide.