3. Step 1 — Prepare your values

Write these down; you will type them into the form in Step 3.

3.1 Create the network (VPC)

Skip this if your company already gave you a VPC that meets the checklist. It takes about 5 minutes and is done once.

  1. In the AWS console, check the region at the top right is the one you chose (for example US East (N. Virginia) us-east-1).

  2. Search for VPC in the top search bar and open it.

  3. Click Create VPC (orange button).

  4. Under Resources to create, choose VPC and more. The preview on the right then draws the whole network.

  5. Fill in the form:

    Field

    Set it to

    Name tag auto-generation

    ticked, name quantacloud

    IPv4 CIDR block

    leave 10.0.0.0/16

    IPv6 CIDR block

    No IPv6 CIDR block

    Tenancy

    Default

    Number of Availability Zones (AZs)

    2

    Number of public subnets

    2

    Number of private subnets

    2

    NAT gateways

    click Zonal (not None — with None nothing can start). A second choice then appears: 1 per AZ for real use, or In 1 AZ to save about $1/day (a zone failure then cuts the servers off the internet)

    VPC endpoints

    leave S3 Gateway (free)

    DNS options

    tick both Enable DNS hostnames and Enable DNS resolution

  6. Click Create VPC. AWS shows each step with a green tick; the NAT gateway takes 2–3 minutes. Wait until the page says Success, then click View VPC.

The NAT gateway is billed by the hour from now on (about $1/day each), whether or not the stack exists yet. If you stop here for a while, delete the VPC and recreate it later.

Next → 3.2 — request the certificate.

3.2 Request the SSL certificate

  1. In the top search bar type Certificate Manager and open it (check the region at the top right is the one you chose).

  2. Click Request (orange, top right) → Request a public certificate → Next.

  3. Fully qualified domain name: click the box, delete anything already in it (the browser may refill an old entry), and type your own address, e.g. drive. followed by your company’s domain. Wherever this guide writes <your-domain>, put your real domain instead; a certificate for the placeholder can never be issued.

  4. Leave the rest as it is: Allow export = Disable export, Validation method = DNS validation, Key algorithm = RSA 2048. Look at the domain box once more, then click Request (bottom right).

  5. The certificate’s page opens, status Pending validation. In the Domains box check the domain is yours, then:

    • your domain is in Route 53 in this account: click Create records in Route 53 → Create records;

    • your DNS is elsewhere: copy the CNAME name and CNAME value shown and create that CNAME record at your DNS provider.

  6. Wait until Status shows Issued (usually 5–30 minutes; click the refresh button now and then).

  7. At the top of the same page, under ARN (it starts with arn:aws:acm:), click the copy icon and paste it into your notes.

Note

The certificate must name the domain you will actually use. A certificate for a different name makes the website show a warning and makes the Qdrive desktop app refuse to connect.

Next → 3.3 — note your network IDs.

3.3 Find your network IDs

Open VPC in the AWS console:

Value

Where to find it

VPC ID (vpc-…)

Your VPCs → the row whose Name is the one from 3.1 (e.g. quantacloud-vpc) → the VPC ID column

2 public subnet IDs (subnet-…)

Subnets → filter by your VPC → the two whose name contains public (e.g. quantacloud-subnet-public1-us-east-1a)

2 private subnet IDs (subnet-…)

Subnets → the two whose name contains private (e.g. quantacloud-subnet-private1-us-east-1a)

Next → 3.4 — create the encryption key.

3.4 Create the credential encryption key

This key protects every cloud credential your users save inside QuantaCloud.

  1. Open AWS CloudShell: the >_ icon in the top bar of the AWS console (a terminal opens at the bottom of the page after a few seconds). A Mac or Linux terminal, or Git Bash on Windows, works too.

  2. Type this and press Enter:

    openssl rand -hex 32
    
  3. It prints one line of exactly 64 characters (0–9 and a–f). Select it, copy it, and paste it into your notes. If you ran the command more than once, use only the last line.

Warning

Save this key in your password manager now. If it is ever lost, the cloud credentials stored in QuantaCloud can never be read again. There is no recovery.

Next → 3.5 — choose the first administrator.

3.5 Choose the first administrator

There is nothing to click here: decide these three values and write them in your notes. You type them into the stack form in Step 3, Section 4 — Sign-in (FirstAdminUsername, FirstAdminEmail, FirstAdminPassword), and sign in with them once the stack is ready.

Value

Rules

Example

Username

3–15 characters, starts with a letter, only letters, digits and _

admin

Email

a real address you can read

it@<your-domain>

Initial password

at least 8 characters

(choose one)

You will be asked to change the password the first time you sign in.

Next → 3.6 — note the product version.

3.6 Choose the product version

Value

What to use

Image repository

cloudstier

Image tag

2026.10.26.1 — a fixed, tested release. (latest also works, but a fixed version means an accidental stack update never changes your software.)

Next → 3.7 — check your notes against the list.

3.7 Your notes now hold everything the form asks for

Step 2 uploads the YAML; after Next the console shows the form, and Step 3 is where each value goes:

From

Value

Form field in Step 3

3.6

image repository, image tag

ImageRepositoryPrefix, ImageTag

3.3

VPC ID

VpcId

3.3

2 public subnet IDs

PublicSubnetIds

3.3

2 private subnet IDs

PrivateSubnetIds

3.2

certificate ARN

CertificateArn

3.2

your domain with https://

PublicBaseUrl

3.5

username, email, initial password

FirstAdminUsername, FirstAdminEmail, FirstAdminPassword

3.4

64-character key

CredentialEncryptionKey

Next → Step 2 — open CloudFormation and upload the YAML.