3. Steps 1–7 — Prepare your values¶
Steps 1–7 create the network and the certificate and collect the values the form needs; you type them in at Step 9.
Step 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.
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).
Search for VPC in the top search bar and open it.
Click Create VPC (orange button).
Under Resources to create, choose VPC and more. The preview on the right then draws the whole network.
Fill in the form:
Field
Set it to
Name tag auto-generation
ticked, name
quantacloudIPv4 CIDR block
leave
10.0.0.0/16IPv6 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
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 → Step 2 — request the certificate.
Step 2 — Request the SSL certificate¶
In the top search bar type Certificate Manager and open it (check the region at the top right is the one you chose).
Click Request (orange, top right) → Request a public certificate → Next.
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.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).
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.
Wait until Status shows Issued (usually 5–30 minutes; click the refresh button now and then).
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 → Step 3 — note your network IDs.
Step 3 — Note your network IDs¶
Open VPC in the AWS console:
Value |
Where to find it |
|---|---|
VPC ID ( |
Your VPCs → the row whose Name is
the one from Step 1 (e.g.
|
2 public subnet IDs
( |
Subnets → filter by your VPC → the two
whose name contains public (e.g.
|
2 private subnet IDs
( |
Subnets → the two whose name contains
private (e.g.
|
Next → Step 4 — create the encryption key.
Step 4 — Create the encryption key¶
This key protects every cloud credential your users save inside QuantaCloud.
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.Type this and press Enter:
openssl rand -hex 32
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 → Step 5 — choose the first administrator.
Step 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 9, 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
|
|
a real address you can read |
|
|
Initial password |
at least 8 characters |
(choose one) |
You will be asked to change the password the first time you sign in.
Next → Step 6 — note the product version and sign-in details.
Step 6 — Note the product version and sign-in details¶
6a. Product version (everyone):
Value |
What to use |
|---|---|
Image repository |
|
Image tag |
|
6b. Features that live in other consoles (only those you will use):
Sign-in with SSO (Cognito), Google sign-in, QuantaGrid on Azure and the Box connector are set up partly in another company’s console. Prepare them now, before the upload: almost every error seen in real installs came from doing this afterwards, in a hurry, with a value in the wrong box or the new domain’s address missing. Skip any part you do not use.
Feature |
Prepare now |
The values go into |
|---|---|---|
Sign in with SSO / SaaS users |
Cognito below |
install form, Step 9 Section 4 |
Continue with Google |
Google below |
Admin Console after install (10.2), or install form Section 4 |
Box, each user’s own account (OAuth) |
Box OAuth below |
install form, Step 9 Section 4b |
Box, one shared account (JWT) |
Box JWT below |
Admin Console after install (10.6) |
QuantaGrid on Azure Blob |
Azure below |
Admin Console after install (10.5) |
Three rules prevent almost every error:
Every address you register is
https://<your-domain>/…, the domain from Step 2, written in full.A secret is copied once, at once, into your notes, and pasted only into the place this guide names.
In Azure, copy a secret’s Value (it contains
~), never its Secret ID (a code with dashes).
First open Cognito: AWS console → top search bar Cognito → Amazon Cognito → left menu User pools (check the region at the top right is the one you chose). Then follow A or B.
A. A user pool is listed — you already have Cognito
Click your user pool. On its overview, copy the User pool ID (e.g.
us-east-1_AbCdEf123).Left menu Applications → App clients → click your app client.
No app client, or none with a secret: click Create app client → Traditional web application → a name (e.g.
quantacloud) → Create app client.
In App client information, copy the Client ID, then click Show client secret and copy the Client secret.
Edit (App client information) → Authentication flows: tick ALLOW_ADMIN_USER_PASSWORD_AUTH → Save changes.
Login pages tab → Edit → Allowed callback URLs → Add another URL →
https://<your-domain>/admin-api/auth/oidc/callback(your domain from Step 2) → Save changes.
B. The list is empty — you do not have Cognito yet
Click Create user pool.
Define your application: choose Traditional web application; Name your application: e.g.
quantacloud.Options for sign-in identifiers: tick Email.
Required attributes for sign-up: leave email.
Add a return URL:
https://<your-domain>/admin-api/auth/oidc/callback(your domain from Step 2).Click Create user directory. AWS creates the user pool and an app client with a secret.
Click Go to overview, then do A, steps 1–4 (copy the User pool ID, Client ID and Client secret; tick ALLOW_ADMIN_USER_PASSWORD_AUTH). The return URL from step 5 is already the callback URL.
Google (“Continue with Google”): do step 1 of section 10.2 now and copy the Client ID and Client secret.
Box OAuth (each user connects their own Box account):
Box Developer Console (developer.box.com) → My Apps → Create New App → Custom App → User Authentication (OAuth 2.0) → a name → Create App.
Configuration → OAuth 2.0 Redirect URIs: add
https://<your-domain>/api/v1/connectors/box/callback→ Save Changes.Copy the Client ID and Client Secret from the same page.
Box JWT (one shared Box account, needs a Box Enterprise account):
Create New App → Custom App → Server Authentication (with JWT) → a name → Create App.
Configuration → Add and Manage Public Keys → Generate a Public/Private Keypair. Keep the JSON file Box downloads: it is the only copy of the private key.
Ask your Box administrator to authorize the app: Box Admin Console → Apps → Custom Apps Manager → Add App → the app’s Client ID.
Azure (QuantaGrid on Azure Blob):
Azure portal → App registrations → New registration → a name → Register. Copy the Application (client) ID and Directory (tenant) ID.
Certificates & secrets → Client secrets → New client secret → Add. Copy the Value at once (Azure never shows it again).
Your storage account → Access control (IAM) → Add role assignment → Storage Blob Data Contributor → assign it to the app.
For Step-up SSO as well: the app → Authentication → Add a platform → Web → Redirect URIs:
https://<your-domain>/grid/sso/azure/callback.Note the storage account name.
Warning
Keep the secrets in your notes only. Cognito, Google and Box OAuth go into the form fields in Step 9; Azure and the Box JWT file go into the Admin Console after the install. None of them ever goes into Client secret reference in Product login.
Next → Step 7 — check your notes.
Step 7 — Check your notes¶
Step 8 uploads the YAML; after Next the console shows the form, and Step 9 is where each value goes:
From step |
Value |
Form field in Step 9 |
|---|---|---|
6 |
image repository, image tag |
|
3 |
VPC ID |
|
3 |
2 public subnet IDs |
|
3 |
2 private subnet IDs |
|
2 |
certificate ARN |
|
2 |
your domain with
|
|
5 |
username, email, initial password |
|
4 |
64-character key |
|
6b (optional) |
Cognito user pool ID, client ID, client secret |
|
6b (optional) |
Google client ID, client secret |
|
6b (optional) |
Box OAuth client ID, client secret |
|
6b (optional) |
Azure tenant ID, client ID, secret Value, storage account; Box JWT file |
not in the form: Admin Console after install (10.5, 10.6) |
Next → Step 8 — open CloudFormation and upload the YAML.