> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/workflows/file-transfer/ftp.md).

# FTP

FTP is a low-security, simple file transfer protocol that is easy to set up and widely supported.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FzRBQOrfUDzDi8T4uxw5B%2Fftp1.png?alt=media&amp;token=ce0b28ec-b36c-4214-b566-274fa89339d4" alt=""><figcaption></figcaption></figure>

In the *Security Settings* for FTPS, select Implicit TLS or SSL or Explicit TLS or SSL.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FMj3EsHEKWUsh5FbpMXco%2Fimage.png?alt=media&amp;token=362a5d82-ef87-435b-928e-d185ed8f1c3d" alt=""><figcaption></figcaption></figure>

Implicit TLS or SSL is typically used in legacy or pre-configured environments where security requirements mandate all connections to be encrypted by default. The client and server automatically establish a secure channel without any negotiation, with encryption starting as soon as the connection is established.

Explicit TLS/SSL is Commonly used in modern setups where flexibility and compatibility with non-secure FTP are needed. The connection starts unencrypted, and the client explicitly requests encryption by issuing a STARTTLS command. The server then upgrades the connection to a secure one, allowing mixed use of encrypted and unencrypted sessions based on client-server negotiation.

*Accept Unauthenticated Certificates*: Allows the FTP client to connect even if the server's SSL/TLS certificate cannot be authenticated, useful for testing or non-critical connections.

*Passive Mode*: Enables the client to initiate both control and data connections, useful for navigating firewalls and NAT environments.


---

# 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://documentation.astera.com/astera-data-stack-v10/workflows/file-transfer/ftp.md?ask=<question>&goal=<user_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.
