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

A Transfer server becomes an atmoz/sftp gateway hosted in the target environment. SFTP clients connect to that server using its endpoint and SSH host key. Configure user keys and storage mounts on the gateway, and distribute the replacement host key to clients. This mapping does not reproduce AWS Transfer’s management API or add managed workflows, FTP, FTPS or AS2 support. These target services provide the mapping described above, within its stated limits. Service Catalog.