Skip to content

Environment Requirements

Applies to: All subscriptions

Purpose

Turn the architecture into something that can be procured and provisioned. Every destination, port, protocol and specification a customer's infrastructure and network teams need is named here, so a change request can be raised without a further conversation.

Audience

Infrastructure engineers, network engineers, database administrators, procurement.

Prerequisites

Steps

Page What it specifies
Sizing and Capacity Compute, memory and storage per tier, and what drives each
Network and Firewall Every inbound and outbound path, as a change-request table
Database Requirements Edition, configuration, maintenance and the feature that isolation depends on

What must be decided before this section is useful

Decision Why it changes the specification
Topology Decides how many hosts and whether the database is separate
Document volume The primary driver of both compute and storage
Retention period Storage grows with it, and it is a statutory question, not a technical one
Non-production environments Each needs its own specification and its own provider credentials
Data residency Constrains hosting location before anything else is chosen

The four constraints that matter most

Row-Level Security must be available in the database edition. Tenant isolation is enforced inside the database engine. An edition without it cannot run Complifly safely, and this has a licensing cost implication that belongs in procurement, not in a later technical conversation.

Outbound HTTPS is mandatory. Complifly cannot function without reaching the GSP. Where an egress proxy intercepts TLS, its certificate must be trusted by the application, and where the provider restricts by source address, that address must be fixed and registered.

PDF rendering is memory-hungry. Document rendering runs a headless browser. Under bulk printing this, rather than the API, is usually the first thing to exhaust memory. Size for peak print, not for average request load.

Storage grows continuously and is not fully discretionary. Compliance evidence — payloads, signed responses, cached documents — accumulates for the statutory retention period. Provision for growth from the start; retrofitting storage under a live compliance system is disruptive.

Validation

The environment is ready when an infrastructure engineer can answer all of these from documentation alone:

Question Source
How many hosts, of what size? Sizing and Capacity plus the chosen topology
How much storage, growing at what rate? Sizing and Capacity
Which database edition and version? Database Requirements
Which firewall rules, in both directions? Network and Firewall
Which certificates, for which hostnames? Domains and URLs
What is monitored, and at what threshold? Monitoring and Health Checks

Troubleshooting

Symptom Cause Action
Infrastructure ordered against the wrong specification Sizing agreed before volumes were known Re-check against Sizing and Capacity; those figures are estimates and must be sanity-checked against your own volumes
Database licensing challenged during procurement The edition requirement was not raised early Row-Level Security is not optional. Raise it as a functional requirement, not a preference
Firewall requests rejected or delayed Submitted as a vague request rather than a specific rule set Use the table in Network and Firewall verbatim
Disk fills within months of go-live Growth rate not modelled, or retention not agreed Measure actual growth over the first month and re-forecast. See Housekeeping
Bulk printing fails while everything else is fine Memory sized for average load, not peak rendering Raise memory on the rendering host or reduce batch size