Data Residency for Document Management on AWS

Verify where your document platform stores and processes data across AWS resources, delivery, AI inference, and integrations.

FormKiQ combines packaged Business Solutions with an API-first document platform. Choose customer-managed AWS deployment, dedicated vendor-managed Enterprise, or a hybrid operating model.

RGF Staffing
Pollard Banknote
Smart
UQAM
Esurance
Contruent
OakNorth
FormKiQ on AWS Marketplace Open-source Core and license Inspect applications, APIs, and deployment controls

AWS publishes ISO 27001 and SOC assurance information for its in-scope services. These infrastructure assurances do not certify a FormKiQ application or customer deployment.

Verify Where Your Documents Are Stored and Processed

Data residency sets geographic conditions on storing or processing specific data. Laws, contracts, and internal policies can set different conditions. Identify the records and operations covered, where transfers are permitted, and what evidence the organisation must keep.

The challenge with data residency in document management is that documents are the most common container for regulated personal data — and most document management platforms don't give organisations the ability to verify where their documents actually reside. Vendor-hosted SaaS platforms store your documents in the vendor's infrastructure, in regions the vendor chooses, under data movement policies the vendor defines. The vendor may provide a residency attestation, but the organisation cannot independently verify that documents, metadata, search indexes, and processing outputs all remain within the required boundary.

A FormKiQ deployment gives you regional resources in an AWS account you control. Verify the resource locations and review data paths such as backup, delivery, AI inference, and integrations against the workload's requirements.

FormKiQ document console and AWS CloudFormation deployment — deployments and data under your control

What Is Data Residency?

Data residency and related concepts are often conflated. Understanding the distinctions matters because they drive different architectural decisions:

ConceptDefinitionArchitectural Implication
Data residencyThe requirement that data be stored within a specific geographic boundary — typically a country or economic regionDeploy to an AWS region within the required boundary; ensure all data components (storage, metadata, indexes) are in-region
Data localisationA stronger form of residency — data must not only be stored within the boundary but may not be transferred outside it under any circumstancesSingle-region deployment with no cross-region replication; restrict all processing to in-region services
Data sovereigntyLegal authority over data, which can depend on its location, the entities that control it, and their obligationsAccount-level controls; encryption with customer-managed keys; legal and contractual protections beyond technical architecture
Data protectionThe broader legal framework governing how personal data is collected, processed, stored, and shared — data residency is one element of data protectionResidency controls combined with access controls, retention policies, consent management, and processing records

Data residency is the foundation. Without knowing where your data physically resides, you cannot assess whether sovereignty, localisation, or protection requirements are met. See the companion guide: Data Sovereignty for Document Management on AWS.

How to Verify Residency in a FormKiQ Deployment

Region selection governs where regional resources are created. Service and integration settings determine where copies, requests, and outputs can go. Review both as part of the deployment.

Regional Resources and Connected Services

FormKiQ creates regional resources through CloudFormation. Review those resources alongside global services, configured search endpoints, and external integrations:

ComponentAWS ServiceResidency Enforcement
Document storageAmazon S3S3 bucket created in the selected region. Check replication, backup destinations, and access or export paths.
MetadataAmazon DynamoDBDynamoDB table created in the selected region; data does not replicate outside the region unless explicitly configured
Search indexesConfigured search backendWhen the OpenSearch module is deployed, confirm the domain region and snapshot destinations. For Typesense, check the configured endpoint and backups.
Audit logsAWS CloudTrail + FormKiQ audit logAudit data stored in S3 and DynamoDB within the selected region
Encryption keysAWS KMSKMS keys created in the selected region; keys do not replicate across regions
ComputeAWS LambdaLambda functions execute in the selected region; document content processed in-region
IdentityAmazon CognitoVerify the user pool region and the separate data paths used by federated identity providers
AI processingAmazon BedrockCheck the invoking region and the selected model or inference profile. Verify all allowed processing destinations.

For a Frankfurt deployment, verify the locations of the domain, buckets, tables, keys, and logs that are in scope. CloudFront edge locations can serve requests outside the origin's region. Bedrock inference profiles can route processing beyond the invoking region. Check what data each path handles, including cached objects and inference logs.

Verifiable Residency

A critical advantage of deploying FormKiQ in your own AWS account: residency is verifiable, not attested. Your infrastructure team can confirm residency by examining:

  • S3 bucket region — visible in the AWS console and API; the bucket physically resides in the specified region
  • DynamoDB table region — visible in the console; the table and its data reside in the specified region
  • OpenSearch domain region — visible in the console; the search domain resides in the specified region
  • KMS key region — visible in the console; the key exists only in the specified region
  • CloudTrail configuration — visible in the console; audit logs are delivered to S3 in the specified region
  • Lambda function region — visible in the console; functions execute in the specified region

This is fundamentally different from vendor residency attestations, where the organisation trusts the vendor's claim without the ability to verify it independently.

Supported AWS Regions

FormKiQ supports deployment across 20 AWS regions, providing residency options across six continents:

RegionAWS Region CodeKey Data Residency Frameworks
Frankfurt, Germanyeu-central-1GDPR, German BDSG, German banking regulations
Irelandeu-west-1GDPR
London, UKeu-west-2UK GDPR post-Brexit, UK FCA requirements
Paris, Franceeu-west-3GDPR, French CNIL requirements
Stockholm, Swedeneu-north-1GDPR, Nordic data protection legislation
Milan, Italyeu-south-1GDPR, Italian healthcare and financial services
N. Virginia, USus-east-1US state privacy laws, HIPAA, federal workloads
Ohio, USus-east-2US state privacy laws, HIPAA
Oregon, USus-west-2US state privacy laws, HIPAA
Montreal, Canadaca-central-1PIPEDA, Quebec Law 25, provincial privacy legislation
Calgary, Canadaca-west-1PIPEDA, Alberta PIPA
Mumbai, Indiaap-south-1India DPDP Act, RBI data localisation
Singaporeap-southeast-1Singapore PDPA
Sydney, Australiaap-southeast-2Australian Privacy Act, APRA CPS 234
Tokyo, Japanap-northeast-1Japan APPI, financial data localisation
Seoul, South Koreaap-northeast-2South Korea PIPA, financial data localisation
Cape Town, South Africaaf-south-1South Africa POPIA
São Paulo, Brazilsa-east-1Brazil LGPD
UAEme-central-1UAE PDPL, DIFC/ADGM data protection
Bahrainme-south-1GCC data localisation, Saudi Arabia PDPL-adjacent

FormKiQ Core also supports AWS GovCloud (US West) for US federal workloads requiring FedRAMP High-authorised infrastructure. For unlisted regions, SAM CLI installation is available. AWS China regions are not currently supported.

Multi-Jurisdiction Residency

Organisations operating across multiple jurisdictions often need documents from different regions to remain in their respective geographic boundaries. The typical pattern is separate FormKiQ instances per region, with regional storage and a separate review of shared services such as centralised identity:

                     ┌──────────────────────────┐
                     │   Central Identity (SSO)  │
                     │   Microsoft Entra / Google │
                     └──────┬─────────┬──────────┘
                            │         │
              ┌─────────────┘         └──────────────┐
              ▼                                      ▼
┌──────────────────────────┐          ┌──────────────────────────┐
│  FormKiQ Instance — EU   │          │  FormKiQ Instance — CA   │
│  Region: eu-central-1    │          │  Region: ca-central-1    │
│  (Frankfurt)             │          │  (Montreal)              │
│                          │          │                          │
│  EU documents            │          │  Canadian documents      │
│  EU metadata             │          │  Canadian metadata       │
│  EU search indexes       │          │  Canadian search indexes │
│  EU audit logs           │          │  Canadian audit logs     │
│  EU encryption keys      │          │  Canadian encryption keys│
│                          │          │                          │
│  GDPR-governed           │          │  PIPEDA/Law 25-governed  │
└──────────────────────────┘          └──────────────────────────┘

This architecture provides:

  • Regional separation — each instance has its own regional stores; verify any shared identity, delivery, and integration paths
  • Centralised authentication — users authenticate through a single SSO provider, with access to the appropriate regional instance based on their role and jurisdiction
  • Independent governance — each instance has its own retention policies, access controls, and compliance configuration appropriate to the jurisdiction
  • Independent audit — each instance produces its own audit trail, enabling jurisdiction-specific audit responses

Multi-instance and multi-region licensing is available on FormKiQ Advanced and Enterprise.

Data Residency for AI Processing

AI processing creates a specific residency concern: when a document is sent to an AI service for classification, extraction, or analysis, the document content must be processed within the residency boundary — not just stored within it. FormKiQ addresses this through Amazon Bedrock's inference region controls:

Residency ConcernHow FormKiQ Addresses It
Processing locationCheck the model or inference profile and every allowed destination against the required processing boundary
Data in transitVerify the service endpoint and routing. Cross-region inference can process a request outside the invoking region
Processing outputVerify the destinations for returned outputs, application storage, and any enabled invocation logs
No external sharingReview AWS and model data-handling terms and the configured processing, logging, and integration paths

This is a critical distinction from third-party AI services, where documents may be processed in any region the service provider chooses — and where the processing location may change without notice.

Data Residency and Related Governance Controls

Data residency doesn't operate in isolation. It intersects with other governance controls that together form a complete data protection posture:

Governance ControlHow It Relates to Residency
EncryptionVerify key location, key policies, grants, and encryption settings. A regional key does not establish the location of every caller or decrypted copy
Access controlABAC policies can include jurisdiction as an access attribute — EU documents accessible only to EU-authorised users
RetentionJurisdiction-specific retention policies applied to documents within each regional instance — ensuring retention compliance aligns with residency compliance
Audit trailVerify regional log destinations, central collectors, archives, and any cross-region copies
Data subject rightsCoordinate requests across the stores and processors in scope while respecting each applicable access and transfer boundary

Regulatory Frameworks Requiring Data Residency

FrameworkResidency RequirementFormKiQ Support
GDPR / UK GDPRPersonal data of EU/UK residents must be protected regardless of processing location; many organisations implement EU-only storage as a compliance measureEU region deployment (six regions); UK region (London)
PIPEDA / Quebec Law 25Canadian personal information subject to Canadian jurisdiction; Quebec Law 25 imposes additional notification requirements for out-of-province transfersCanadian deployment (Montreal, Calgary)
Australia Privacy Act / APRA CPS 234Financial sector data localisation requirements; general privacy obligations with cross-border transfer restrictionsAustralian deployment (Sydney)
India DPDP Act / RBI guidelinesRBI mandates that payment data be stored within India; DPDP Act introduces broader data localisation provisionsIndian deployment (Mumbai)
Brazil LGPDPersonal data protection with cross-border transfer restrictionsBrazilian deployment (São Paulo)
South Korea PIPAPersonal information localisation requirements with consent-based transfer mechanismsSouth Korean deployment (Seoul)
Japan APPICross-border transfer restrictions with adequacy-based exceptionsJapanese deployment (Tokyo)
South Africa POPIAPersonal information must be processed in accordance with South African law; cross-border transfer conditionsSouth African deployment (Cape Town)
UAE PDPL / DIFC / ADGMData localisation requirements for certain data categories; free zone-specific data protection frameworksUAE deployment (Dubai region)
Saudi Arabia PDPLData localisation requirements for certain categories of personal dataBahrain deployment (regionally proximate)

Who Needs Data Residency Document Management

Organisation TypeResidency ChallengeKey Drivers
Multi-national corporationsEmployee, customer, and vendor data across jurisdictions — each jurisdiction with different residency requirementsGDPR, PIPEDA, LGPD, APPI, PIPA, PDPA — simultaneous compliance across regions
Financial servicesClient data subject to both privacy residency and financial regulatory localisationAPRA CPS 234, RBI data localisation, FCA, OSFI, MAS — financial regulators increasingly require in-country processing
HealthcarePatient data subject to health-specific residency requirements alongside general privacy frameworksHIPAA (US region), GDPR (EU region), provincial health privacy legislation (Canadian regions)
Government and public sectorCitizen data subject to government data sovereignty requirements; some governments mandate domestic processingNational security frameworks, government cloud requirements, citizen data protection mandates
Technology and SaaSCustomer data from multiple jurisdictions requiring per-customer or per-region residency guaranteesCustomer DPA requirements, GDPR, SOC 2, customer security assessments
Legal and professional servicesClient data subject to professional confidentiality obligations and client-specified residency requirementsBar association requirements, client security requirements, engagement-specific residency commitments
Research institutionsResearch data subject to funder-specified residency, ethics board requirements, and data protection legislationResearch ethics frameworks, funder data management requirements, international collaboration protocols

FormKiQ Editions for Data Residency

Capability
Core
Foundation
Essentials
Operational
Advanced
AI + Automation
Enterprise
Full platform
Foundation
Single-Region Deployment (20 regions)
Support
GovCloud Deployment (US West)✓
Foundation
Document Storage (S3) & API
Tagging, Search & Classification
Essentials and above
Encryption (KMS — in-transit & at-rest)—
Workflows, Queues & Rulesets—
Document Control & Versioning—
Advanced and Enterprise
AI Processing with Inference Region Controls——
Multi-Instance & Multi-Region Licensing——
Document Gateway Modules——
Integration Framework Modules——
Enterprise only
Vendor-Managed & Hybrid Deployment———
Compliance Consulting———
Support
SupportCommunity2-business-day SLAPrivate Slack + 40 hrs onboarding8-business-hour SLA + strategic support

Getting Started

FormKiQ Core can be deployed to any of 20 supported AWS regions in fifteen to twenty minutes. Multi-instance and multi-region licensing for organisations with residency requirements across multiple jurisdictions is available on Advanced and Enterprise.

Start a Proof-of-Value deployment

Frequently Asked Questions

What is data residency?

Data residency is the requirement that certain categories of data — typically personal data — be stored within a specific geographic boundary, usually a country or economic region. Data residency requirements arise from privacy legislation (GDPR, PIPEDA, LGPD), sector-specific regulations (financial data localisation, health data requirements), and contractual obligations (customer DPAs, government procurement requirements).

How is data residency different from data sovereignty?

Data residency addresses where data is physically stored. Data sovereignty addresses whose laws govern the data and who can compel access to it. You can satisfy data residency (store data in Germany) while failing data sovereignty (if a foreign government can compel your vendor to produce the data under its own laws). FormKiQ supports both — residency through regional deployment, and sovereignty through customer-account ownership and customer-managed encryption keys.

How do I verify that my documents are stored in the correct region?

Because FormKiQ deploys into your own AWS account, you can verify residency directly through the AWS console — checking the region of your S3 buckets, DynamoDB tables, OpenSearch domains, KMS keys, and Lambda functions. This is a verifiable confirmation, not a vendor attestation.

Can I deploy FormKiQ in multiple regions simultaneously?

Yes. Multi-instance and multi-region licensing on Advanced and Enterprise allows separate FormKiQ deployments in different regions — each containing only the documents appropriate for that region. Centralised authentication through SSO provides a single identity plane across regional instances.

What about data that needs to be accessed from multiple regions?

Separate regional instances can keep their primary data stores independent while sharing authentication. Assess who can open, download, or export records from another jurisdiction and where those activities are processed and logged.

Does AI processing respect data residency?

Select an in-region model and invocation path if the workload requires one region. With a geographic profile, requests may be processed in multiple regions in the specified geography. Check the Bedrock inference profiles, including the possible destinations, before enabling document AI.

Guide follow-up

Talk through data residency and customer control

Bring your region requirements, document storage and processing boundaries, audit expectations, and governance model. We will map how FormKiQ can support customer-controlled deployment.

  • Review required AWS regions, accounts, and data boundaries
  • Identify storage, metadata, search, processing, backup, and logging requirements
  • Discuss access controls, encryption, monitoring, and audit evidence
  • Decide whether an architecture review or proof-of-value makes sense
Regan Wolfrom, FormKiQ Co-Founder and Chief Technology Officer

Hosted by Regan Wolfrom

Co-Founder and Chief Technology Officer

Regan is a platform engineering specialist with experience in cloud architecture, site reliability, high-traffic production systems, and long-term platform stability.

Trusted migration experience: Read RGF Staffing Belgium’s account of migrating 20M+ documents from Alfresco.

Not ready to book? Get a data residency recommendation.

Share your region, sovereignty, or customer-control requirement, and we will suggest a practical next step.

No calendar booking required.

Start with FormKiQ Core

The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

Get Started Free

Deploy FormKiQ Essentials or Advanced

Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

Explore Options

Plan an Enterprise Rollout

For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

Book a Call