Skip to main content
This entry uses the gateway mapping described in Transfer Family SFTP coverage and limitations. Infrastructure only: SFTP with SERVICE_MANAGED users and startup SSH keys. Cluster deployments use a single-writer server; user changes are not a live Transfer management API. Approved no-cluster designs use mounted object storage on Google Cloud and OCI; Azure Container Apps uses Azure Files rather than Blob storage. Capacity, private client routing and host-key trust require configuration; custom identity providers, multiple home-directory mappings and AWS IAM path-policy enforcement are not reproduced. AWS Transfer management APIs, managed workflows, FTPS, FTP and AS2 are not provided by this mapping.

​
Coverage by target cloud

​
Mapping and limitations

Transfer Family’s SFTP configuration moves to an SFTP gateway in the target environment. The registered gateway runs atmoz/sftp and serves the SFTP wire protocol. Users, SSH keys, home directories and storage mounts are gateway configuration. AWS Transfer management APIs, managed workflows, FTP, FTPS and AS2 are not provided by this SFTP mapping. These target services provide the mapping described above, within its stated limits.

​
Debug this service

For requests through a service adapter, use Explain and request diagnostics to investigate the selected mapping. Follow the BYOC service-adapter debugging runbook to capture and interpret the diagnostic evidence. Service Catalog.