5. Step 3 — Fill in the form (every field explained)¶
The form is grouped in sections. Fields marked ★ must be filled in. Leave every other field at its default unless the “When to change” column applies to you.
The console shows some fields under a descriptive title instead of their name
(for example PublicBaseUrl appears as Public address of this deployment -
optional). The tables give both.
How the form works:
Text fields: click and type (or paste) the value.
VpcId: a drop-down, choose the VPC from step 3.1 (its name starts withquantacloud).PublicSubnetIdsandPrivateSubnetIds: drop-downs that accept several values. Click the field and pick both public subnets; click again and pick both private subnets. Each chosen subnet appears as a small box below.Hidden fields (passwords, keys) show dots as you type. Paste carefully.
If a value is wrong, the console shows the rule in red under the field when you click Next. Fix it and click Next again.
Section 1 — Product¶
Field |
★ |
What to enter |
When to change |
|---|---|---|---|
|
choose |
|
|
|
★ |
type
|
Only if your vendor gave you another registry path |
|
replace
|
When upgrading (see section 13) |
|
the five … image
override boxes
( |
leave all five empty |
Only when support asks you to run one specific image |
Section 2 — Network¶
Field |
★ |
What to enter |
|---|---|---|
|
★ |
Click the box: a list of the account’s VPCs opens. Choose
the one with the name from step 3.1, e.g.
|
|
★ |
Click the box and choose |
|
★ |
The same, with |
|
★ |
Paste the ARN from step 3.2. It looks like
|
|
★ in practice |
|
Section 3 — Database¶
Field |
What to enter |
Notes |
|---|---|---|
|
(leave empty) |
Empty = the stack creates its own database. Only fill in to use an existing MySQL 8 server. |
|
(leave the defaults) |
|
|
(default
|
|
|
(leave empty) |
Only needed with your
own
|
|
(default |
Keep 8.4. MySQL 8.0 is past AWS standard support and is billed extra (RDS Extended Support). |
|
(default
|
Raise for many users. |
|
(default |
GiB. |
|
|
|
Section 4 — Sign-in¶
Field |
★ |
What to enter |
|---|---|---|
|
★ |
type the username from
step 3.5 (e.g.
|
|
★ |
type the email from step 3.5 |
|
★ |
type the initial password from step 3.5 (shown as dots) |
|
Only for Amazon Cognito sign-in — see section 10 |
|
|
Only if that Cognito app client has a secret (hidden as you type) |
|
|
Only for “Continue with Google” — see section 10 |
The first administrator is created once, when the database is set up. On later updates these three fields are ignored, so they can never reset or replace an existing administrator.
Section 4b — Optional features¶
For the install, leave every field in this section empty — empty means the
product’s normal behaviour, and each one can be changed later with a stack
update. Do not pick a value from the list just because one is offered: for
example AdminCertificatesPage = off locks the page you need to switch mTLS
on.
Field |
What it does |
Leave empty unless… |
|---|---|---|
|
Lets users connect a Box account in QuantaDrive |
you have a Box app (section 10) |
|
|
never set it to |
|
|
support asks you |
|
|
you want ports editable in the console |
|
Largest single upload, in bytes (default 1 GB, maximum 10 GB) |
you need larger
uploads, e.g.
|
|
Largest multi-file upload, in bytes (default 1 GB) |
as above |
|
Largest request body
(default |
support asks you, e.g.
|
|
|
you want full API logging |
Section 5 — Secrets¶
Field |
★ |
What to enter |
|---|---|---|
|
★ |
paste the 64 characters from step 3.4 (shown as dots; paste, do not type) |
Section 6 — Internal mTLS (optional)¶
Field |
What to enter |
|---|---|
|
Leave |
|
Leave empty. |
Note
mTLS means the services inside QuantaCloud also use HTTPS, with
certificates, when they talk to each other. You switch it on after the
install, from the Admin Console: no certificates to prepare, nothing to type
(see Appendix B). With off, users
still reach the site over HTTPS; only the traffic between the services
inside your private network is plain HTTP.
When the form is filled in — the last three pages¶
Click Next at the bottom of the form. The Configure stack options page opens — change nothing except the tick box at the bottom:
On the page
Leave it as
Tags - optional
no tags
Permissions → IAM role - optional
empty (do not choose or create a role)
Express mode
Enable not ticked
Behavior on provisioning failure
Roll back all resources
Additional settings (Stack policy, Rollback configuration, Notification options, Stack creation options)
closed, unchanged
Capabilities (at the very bottom)
tick “I acknowledge that AWS CloudFormation might create IAM resources.” — without it you cannot go on
Then click Next.
The Review and create page opens — a summary in four boxes, top to bottom:
Box
What to do
Step 1: Create stack
nothing (shows the template)
Step 2: Specify stack details
check the Stack name and every Parameter against your notes — a wrong value here is the most common cause of a failed install. To fix one, click Edit on this box.
Step 3: Configure stack options
nothing
Capabilities (if shown again at the bottom)
the box must be ticked; tick it if it is not
Click Submit (orange, bottom right). You land on your stack’s page (CloudFormation → Stacks →
<stack name>), Events tab, status CREATE_IN_PROGRESS — continue with Step 4.
Next → Step 4 — wait for CREATE_COMPLETE.