Serverless Containers — Domain & Access Management

This guide explains how network access, domains, and HTTPS work for Serverless Container applications in CloudRaya.

It focuses on the platform networking model behind the UI, so you understand not just what to click, but how traffic flows from the public internet to your application.

How Traffic Reaches Your App

Every Serverless Container application is exposed through a CloudRaya-managed load balancer.

The high-level flow is:

User Browser
   ↓
Public DNS (Your Domain or Default Domain)
   ↓
CloudRaya Load Balancer
   ↓
Application Containers

CloudRaya handles:

• Public IP and routing
• TLS/HTTPS termination
• Traffic distribution to running containers

You control:

• Which domains point to your app
• When and how custom domains are added or removed
• DNS records in your domain provider

Default Domain vs Custom Domain

Default Domain

When you deploy an app, CloudRaya automatically assigns a system domain:

<app-id>.cloudraya.app

Characteristics:

• HTTPS is enabled automatically
• DNS is fully managed by CloudRaya
• Cannot be removed
• Intended for testing, staging, and initial validation

This domain always points to the CloudRaya load balancer for your app.

Custom Domain (Domain Alias)

A custom domain allows you to expose your app using a domain you own, such as:

www.example.com
app.company.com

In CloudRaya, this is called a domain alias.

Key concept:

CloudRaya does not manage your domain registrar or DNS provider. You create a DNS record that points your domain to CloudRaya’s load balancer.

How CNAME Mapping Works

CloudRaya uses a CNAME-based routing model for custom domains.

What You Create in Your DNS Provider

You will add a record like this:

What This Means

• Your domain becomes an alias for the CloudRaya load balancer
• All traffic to your domain is routed to CloudRaya’s platform
• CloudRaya then forwards the traffic to the correct application based on the domain name

Adding a Custom Domain (Domain Alias)

Step 1 — Open Your Application

1. Go to Marketplace → My Apps
2. Click your application name
3. Open the General tab

Step 2 — Add Domain Alias

1. In the Domain Aliases section, click + Add Domain
2. Enter your domain name (for example: www.example.com)
3. Leave HTTPS enabled
4. Click Save

CloudRaya will now:

• Register the domain internally
• Prepare HTTPS certificate provisioning
• Show you the required DNS record

DNS Configuration Required

After adding a domain alias, you will see a DNS Configuration panel showing:

• Record Type: CNAME
• Name / Host: Your domain
• Value / Points to: CloudRaya load balancer domain

You must create this record in your DNS provider before the domain becomes active.

HTTPS Lifecycle

Automatic Certificate Provisioning

Once the CNAME record is detected, CloudRaya will:

1. Verify that your domain points to the platform
2. Request an HTTPS certificate
3. Attach the certificate to the load balancer

This process is automatic and may take several minutes.

Delete & Recreate Model

Why Domains Cannot Be Edited

A domain alias is tightly bound to:

• Certificate issuance
• Load balancer routing
• Internal application mapping

Because of this, domain aliases cannot be edited once created.

How to Change a Domain

1. Delete the existing domain alias
2. Add a new domain alias with the correct name
3. Update the CNAME record in your DNS provider

This ensures clean certificate and routing state on the platform.

Multiple Domains per Application

You can attach more than one domain alias to a single application.

Example:

www.example.com
app.example.com

Both domains will:

• Point to the same load balancer
• Serve the same application
• Receive individual HTTPS certificates

Production Best Practices

• Use the default domain for testing and validation
• Add custom domains only when the app is stable
• Keep a record of DNS changes for audit and rollback
• Use separate domains for staging and production
• Avoid reusing the same domain across multiple platforms

Summary

CloudRaya uses a load balancer–centric domain model:

• All domains, default or custom, route to the CloudRaya platform
• DNS CNAME records link your domain to the platform
• HTTPS is automatically provisioned and managed
• Domains follow a delete and recreate lifecycle for consistency and security

This design allows you to scale applications, rotate containers, and update infrastructure without changing public endpoints.

Next Guide

Learn how application and database containers use environment variables, how updates trigger redeploys, and how to manage sensitive values securely.

📄 Serverless Containers — Configuration & Environment Variables