2. Before you start — checklist

Tick every line before you begin. The installation cannot succeed without them.

✓

You need

Why

How to get it

☐

An AWS account and a sign-in with administrator rights (or the IAM permissions in Appendix A)

The stack creates security roles. A PowerUserAccess login alone cannot — it fails with “not authorized to perform iam:GetRole”.

Ask your AWS account administrator.

☐

The AWS region you will use (for example US East (N. Virginia))

Everything — certificate, network, stack — must be in the same region.

Choose once and keep it.

☐

A VPC with 2 public and 2 private subnets in different Availability Zones

The load balancer goes in the public subnets; the servers and database go in the private ones.

The default VPC has only public subnets. Create one in about 5 minutes: Step 1 walks through every click.

☐

DNS hostnames and DNS resolution turned on for that VPC

The services find each other by internal DNS names. With either one off, the stack still completes but every page shows an error (502).

The “VPC and more” wizard turns both on. For an existing VPC: Your VPCs → select it → Actions → Edit VPC settings → tick Enable DNS resolution and Enable DNS hostnames → Save.

☐

Internet access from the private subnets (a NAT gateway)

The servers download the QuantaCloud images from Docker Hub when they start. Without it, nothing starts.

Created with the VPC in Step 1.

☐

A domain name you control (for example drive.<your-domain>)

Users open QuantaCloud on it, and sign-in providers return users to it.

Use a domain your company owns. No domain yet? See Getting a domain just below.

☐

An SSL certificate for that exact domain in AWS Certificate Manager (ACM), in the same region

The load balancer serves HTTPS with it.

See Step 2.

Getting a domain

QuantaCloud needs an address such as drive.<your-domain>. Follow A if your company already has a domain, B if it has none.

A. You already have a domain

  1. Choose the address for QuantaCloud: a new name under your domain, e.g. drive.<your-domain>. Do not use a name that already runs another website.

  2. Find out where the domain’s DNS is managed: open Route 53 → Hosted zones.

    • Your domain is in the list → its DNS is in Route 53 in this account. In Step 2 and Step 13 you only click buttons in Route 53.

    • It is not in the list → its DNS is at another provider (GoDaddy, Cloudflare, Namecheap, your IT team…). Ask whoever manages it for access, or send them the records. You add two records there:

      • in Step 2, one CNAME that proves to AWS you own the domain;

      • in Step 13, one CNAME that points drive.<your-domain> at QuantaCloud.

      Both steps say exactly what to type.

  3. Write the address (drive.<your-domain>) in your notes. Nothing to buy.

B. You do not have a domain

Register one in Route 53 (about 10 minutes of clicks, then usually under an hour for AWS to finish):

  1. Open Route 53 → left menu Domains → Registered domains → click Register domains.

  2. Type the name you want (e.g. yourcompany-files), click Search, pick an available one (for example ending in .com) → Select → Proceed to checkout.

  3. Duration: 1 year. Leave Auto-renew on so the domain does not lapse. Next.

  4. Contact information: your company’s name, address, phone and an email you read. Leave Privacy protection on. Next.

  5. Tick the terms → Submit. The cost (about $15 per year for a .com) is added to your AWS bill.

  6. Check that email inbox and click the verification link AWS sends. ⚠️ If the email is not verified within 15 days, the domain is suspended and the site stops working.

  7. Wait until Route 53 → Domains → Requests shows the registration as Successful. Route 53 creates the hosted zone for the domain by itself, so in Step 2 and Step 13 you only click buttons in Route 53.

  8. Write your QuantaCloud address in your notes: e.g. drive. followed by the domain you registered.

Next → Step 1 — create the network (VPC).