5. Steps 9–11 — Fill in the form, then submit¶
Step 9 — 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 - REQUIRED if you use
your own domain). 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 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 1, e.g.
|
|
★ |
Click the box and choose |
|
★ |
The same, with |
|
★ |
Paste the ARN from Step 2. It looks like
|
|
★ do not leave empty |
|
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 5 (e.g. |
|
★ |
type the email from Step 5 |
|
★ |
type the initial password from Step 5 (shown as dots) |
|
the User pool ID from Step 6b — only for SSO / SaaS users |
|
|
the Client ID from Step 6b |
|
|
the Client secret from Step 6b (hidden as you type) |
|
|
the Google values from Step 6b — only for “Continue with Google” |
Note
Filled now, SSO and Google need no stack update after the install. Left empty, the SaaS (Cognito) users tab shows “Cognito is not configured on this server” and SSO cannot sign in until you add them with an update (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 renew the
internal certificates.
Field |
What it does |
Leave empty unless… |
|---|---|---|
|
Lets users connect a Box account in QuantaDrive |
you prepared Box OAuth in Step 6b |
|
|
never set it to
|
|
|
support asks you |
|
|
never on AWS: each service has its own network address, so ports cannot clash, and the stack fixes them - a port saved on that page never takes effect |
|
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 4 (shown as dots; paste, do not type) |
Section 6 — Internal mTLS¶
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. The stack creates those certificates itself during the install, in your own account, before any service starts: nothing to prepare, nothing to type. The Admin Console shows and renews them (see Appendix B).
Section 7 — Power schedule (optional)¶
Switches QuantaCloud off outside working hours to save cost, and on again in
the morning. While it is off nobody can use QuantaCloud. Leave
PowerSchedule at none if people use it at night or at weekends.
Field |
What to enter |
|---|---|
|
|
|
When it switches off, 24-hour
|
|
When it switches on, 24-hour
|
|
Your time zone, e.g.
|
Whatever you choose, you can always switch it on or off by hand — see section 14, Switching QuantaCloud off and on. You can change the schedule later with an update of the stack.
Next → Step 10 — configure stack options.
Step 10 — Configure stack options: tick the IAM box¶
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.
Next → Step 11 — review and submit.
Step 11 — Review and submit¶
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 |
Then click Submit (orange, bottom right). You land on your stack’s page
(CloudFormation → Stacks → <stack name>), Events tab, status
CREATE_IN_PROGRESS.
Next → Step 12 — wait for CREATE_COMPLETE.