How to Create a Dedicated Deployment in AceCloud?

Overview

A Dedicated Deployment in AceCloud allows you to run applications on exclusive infrastructure resources allocated specifically to your project.

This option provides:

• Better performance

• Resource isolation

• Ability to access deployments privately within your VPC

Prerequisites

Before creating a deployment, ensure:

• You are logged in to the AceCloud portal

• A Project and Region are selected

• You have a valid container image (Public or Private)

• A VPC network is available

Note: Ensure that the VPC has an active router configured. VPCs provisioned via firewall configurations are not eligible for selection.

Step 1: Navigate to Deployment Creation

1. Go to Deployments from the left menu, then click Overview

1. Click Create Deployment

Step 2: Configure Deployment Details

2.1 Deployment Name

• Enter a unique name

• Example: my-app

2.2 Deployment Type

• Select Dedicated

Step 3: Select Image Type

Option A: Public Image

3A.1 Select Public Image

• Choose Public Image

3A.2 Image URL / Tag

• Enter image URL

Examples:

nginx

3A.3 Command (Optional)

• Override the default container command if required

Option B: Private Image

3B.1 Select Private Image

• Choose Private Image

Note: Support for Private Images in Dedicated Deployments is currently under development and will be available in an upcoming release.

3B.2 Registry Secret

• Select an existing Registry Secret

OR

• Click Create new registry secret

• Add registry credentials

• Save and select the secret

Note: If registry credentials are regenerated using Generate Credentials, the previously saved credentials are invalidated. Ensure that you update the Registry Secret and restart your deployment.

3B.3 Image URL / Tag

• Enter the full image name and tag

Example:

myapp:latest

ubuntu:latest

Note: The registry URL is automatically prefixed. You only need to enter the image in the format image:tag.

Only images hosted in the AceCloud registry are supported. To use images from other private registries, first migrate them to the AceCloud registry using ACR Source Registry + Replication.

3B.4 Command (Optional)

• Enter a custom startup command if required. If not specified, the default command defined in the container image will be used.

Step 4: Configure Resources

4.1 Resource Flavor

• Select a predefined resource configuration

4.2 Replicas

• Define the number of instances

4.3 Autoscaling (Optional)

Enable autoscaling to automatically scale based on usage.

If enabled, configure:

• Minimum Replicas

• Maximum Replicas

• CPU Target (%)

• Memory Target (%)

Step 5: Configure Networking

5.1 Network Configuration

• Choose a VPC from the dropdown

Deployment will run inside the selected VPC.

Note:

• The selected VPC must have a router configured and must not be a firewall-created VPC.

• If you do not have an existing VPC, select Create VPC to create a new VPC for the deployment.

Step 6: External Access

6.1 Enable External Access

• Toggle ON to make the application accessible externally

6.2 Endpoint Access Type

Public

• Accessible from anywhere

Protected

• Restricted access

When selected:

• You must provide Allowed IP CIDR(s)

6.3 Allowed IP CIDR(s)

• Define allowed IP ranges

Example:

192.168.1.0/24

10.0.0.0/16

6.4 Ports Configuration

Click Add Port and configure:

• Name → Port name

• Protocol → HTTP / HTTPS / TCP / UDP

• Exposed Port → Client-facing port of the deployment; can be public or private depending on External Access

• Container Port → Internal container port

Step 7: Configure Volumes (Optional)

• Click Add Volume

• Attach persistent storage

Step 8: Configure Environment Variables

8.1 Environment Secrets

• Select an existing secret OR

• Click Create new secret

8.2 Environment Variables

Click Add Environment Variables

• Add key-value pairs

Example:

NODE=production

PORT=3000

Step 9: Review Deployment Summary

Verify on the right panel:

• Deployment Type → Dedicated

• Image Type

• Resource Flavor

• Replicas & Autoscaling

• Network configuration

• External access

• Ports

Step 10: Create Deployment

• Click Create Deployment

The platform will:

• Provision dedicated resources

• Pull image and start container(s)

• Apply scaling and access settings

Post Deployment

After successful deployment:

• Access via endpoint

• Monitor under Insights

• Scale or update anytime

• If the deployment remains in the Provisioning state for an extended period, open the deployment and review the container logs to identify any errors or issues preventing the deployment from becoming active.

• Dedicated deployments may take approximately 20–30 minutes to become active, as dedicated infrastructure resources are provisioned within your project during the deployment process.