ContentsTap to jump to a section+
- The October 16 documentation history adds Singapore specifically for VMware agents.
- Do not extend that support to every Transform agent or feature.
- The workspace region and eventual workload destination can differ.
A regional addition with a narrow scope
AWS Transform’s documentation history records Singapore, ap-southeast-1, support for VMware agents on October 16, 2026. The current supported-regions page explicitly qualifies Singapore as VMware-agents-only.
This October 18 report covers the dated documentation addition, not an expansion of every Transform capability. Friday Works has not run a customer migration to establish costs, duration or result quality.
Workspace and workload destination are different
AWS explains that the workspace determines the job’s region. For VMware projects, that region supports discovery; a different migration target can be selected for the resulting workloads.
Friday Works recommends documenting job-management location, relevant data-processing scope and eventual deployment destination separately. Selecting a Singapore workspace alone does not prove that every workload or processing operation stays there.
Review processing as well as storage
The supported-regions guide warns that data can be processed outside the region where Transform is used and links to cross-region guidance. Regional availability is not a substitute for understanding the service’s processing path.
For residency-sensitive projects, check the exact agent and feature against current provider guidance. Do not extend one region table entry to every AI call. Obtain clarification before submitting actual system information if the approved scope remains uncertain.
Start with an owned, limited discovery scope
Friday Works recommends a controlled evaluation on organization-owned machines with approved access and collection scope. Compare discovered assets and dependencies with existing records and identify missing information.
A tool-generated recommendation is not an approved migration decision. Validate recovery, business applications, external connections and destination ownership before moving critical services.

Assess project-specific benefits
Singapore availability may interest regional infrastructure teams, but it does not itself establish lower latency, lower cost or faster migration. Those outcomes depend on the project and implementation.
Record the agent type, workspace region, destination, collection permissions and acceptance criteria before expansion. Follow AWS’s current region and cross-region pages alongside its change history. The event date remains October 16 rather than being relabeled as an October 18 launch.
References
Sources used in this guide
We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.
- Transform document history — VMware agents Singapore addition, 16 October 2026AWS ↗︎
- Supported Regions — Singapore VMware-agents-only; checked 18 October 2026AWS ↗︎
- Cross-region processing — check the current feature-specific scopeAWS ↗︎
- Original screenshot of the vendor-published interactive VMware migration demo; captured 18 October 2026; proportional resize and neutral cover margin, no UI reconstruction; interface copyright AWS retainedAmazon Web Services / screenshot capture Friday Works ↗︎
- Official AWS Transform for migrations product page linking to the interactive demoAmazon Web Services ↗︎
