> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/vault/batch-file-transmission/sftp-proxy/ftps-over-sftp.md).
# FTPS over SFTP
VGS allows to connect to FTPS upstream using SFTP as the connection interface. Since this is not a native protocol implementation, it has some requirements and limitations.
## Upstream requirements
To establish such connections, your server must support:
* Passive connection mode
* TLS encryption
* User/Pass auth
* UTF8 encoding
* Binary transfer mode
## FTP commands
For proper cross-protocol work, each of those commands must be enabled on your server:
* Get current path: `PWD`
* Get file stats: `MLST`
* Upload file: `STOR`
* Download file: `RETR`
* List directory: `LIST`
* Create directory: `MKD`
* Remove file or directory: `DELE` `RMD`
* Rename file or directory: `RNFR` `RNTO`
> If the described above mapping schema doesn’t work for your case or you need a specific commands behavior, please contact our [Support](mailto:support@vgs.io). VGS can provide a flexible configuration for any custom scenario.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.verygoodsecurity.com/vault/batch-file-transmission/sftp-proxy/ftps-over-sftp.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
