How do I keep documents in a specific country or region for data residency?
Deploy FormKiQ's customer-managed resources in an approved AWS region, then verify the locations of every related data flow. Documents, metadata, indexes, OCR output, AI inference, logs, backups, and external integrations can have different boundaries. A regional storage choice provides control over placement; it does not by itself guarantee that all processing or copies remain there.
Inventory the whole document path
Record the location and owner of primary content, versions, metadata, derived artifacts, search indexes, logs, backups, and exports. Include browser downloads, email attachments, signature providers, support access, and any integration that receives document data.
Select services and models available within the required geography. Review replication and backup policies as well as the source stack region. A cross-region AI inference profile may route requests outside the source region even while documents remain in a regional S3 bucket.
Validate the intended boundary
Deploy a fictional document and trace ingestion, processing, retrieval, backup, and deletion. Inspect actual resource configuration and service destinations. Record approved exceptions and prevent unapproved destinations through the relevant IAM, organization, network, and application controls.
Residency, sovereignty, and regulatory compliance are related but different assessments. Confirm legal and contractual requirements with the responsible organization, and retain evidence of the implemented deployment rather than relying on a general product statement.
Edition and configuration
Customer-managed AWS deployment is available across editions. Multi-region commercial licensing is available with Advanced/Enterprise; service availability and each selected module must be checked in the target region.