Skip to content

SFTP Backend

The SFTP backend stores files on any SSH/SFTP server using paramiko. Unlike fsspec's SFTPFileSystem, it gives you explicit control over host key verification and handles Azure Key Vault PEM quirks out of the box.

Installation

pip install "remote-store[sftp]"

This pulls in paramiko and tenacity (for automatic retry on transient SSH errors).

Usage

from remote_store import BackendConfig, RegistryConfig, Registry, StoreProfile

config = RegistryConfig(
    backends={
        "my-sftp": BackendConfig(
            type="sftp",
            options={
                "host": "files.example.com",
                "username": "deploy",
                "password": "secret",
                "base_path": "/srv/data",
            },
        ),
    },
    stores={"uploads": StoreProfile(backend="my-sftp", root_path="uploads")},
)

with Registry(config) as registry:
    store = registry.get_store("uploads")
    store.write("report.csv", b"col1,col2\n1,2\n")
    data = store.read_bytes("report.csv")

Key-based authentication

from remote_store.backends import SFTPBackend, SFTPUtils

pkey = SFTPUtils.load_private_key("/path/to/id_rsa", from_file=True)

backend = SFTPBackend(
    host="files.example.com",
    username="deploy",
    pkey=pkey,
)

Or load a PEM string directly (useful for secrets managers like Azure Key Vault):

pkey = SFTPUtils.load_private_key(pem_string)

Options

Option Type Default Description
host str (required) SFTP server hostname
port int 22 SSH port
username str None SSH username
password str None SSH password
pkey paramiko.PKey None Private key for key-based auth
base_path str "/" Root path on the remote server
host_key_policy HostKeyPolicy STRICT Host key verification mode (see below)
known_host_keys str None Known-hosts string (code-level override)
host_keys_path str ~/.ssh/known_hosts Path to known_hosts file
config dict None Config dict (may contain known_host_keys)
timeout int 10 SSH connection timeout in seconds
connect_kwargs dict None Extra kwargs passed to SSHClient.connect()

Preflight host-key discovery

To populate a committed host.keys file without going through a TOFU connect first, use SFTPUtils.scan_host_keys(host, port=22). It opens a transport, captures the server's negotiated host key (no authentication), and returns a single known_hosts-formatted line ready to commit:

from pathlib import Path
from remote_store.backends import SFTPUtils

entry = SFTPUtils.scan_host_keys("sftp.example.com")
Path("host.keys").write_text(entry + "\n")

For non-default ports the entry uses the OpenSSH [host]:port form. Network failures (host unreachable, port refused, DNS error) raise OSError; KEX failures (legacy server offering only ssh-rsa) raise paramiko.SSHException — call enable_ssh_rsa_compat() first in that case.

scan_host_keys() returns the negotiated key for one handshake, not every key type the server offers. If the server publishes multiple key types and paramiko later negotiates a type other than the pinned line, the connection fails with BadHostKeyException. Call the helper multiple times under different disabled_algorithms settings if you need full-type coverage.

Host Key Verification

The HostKeyPolicy enum controls how unknown host keys are handled:

Policy Behaviour Use case
STRICT Reject unknown hosts. Key must be in known_hosts. Production (default)
TRUST_ON_FIRST_USE Accept and save on first connect, verify after. First-time server setup
AUTO_ADD Accept any key silently. Dev / testing only

Known host keys are resolved in order (first match wins):

  1. known_host_keys constructor parameter
  2. config["known_host_keys"] dict value
  3. SFTP_KNOWN_HOST_KEYS environment variable
  4. host_keys_path file on disk (default: ~/.ssh/known_hosts)
from remote_store.backends import SFTPBackend, SFTPUtils

# Development / testing
backend = SFTPBackend(
    host="localhost",
    port=2222,
    username="test",
    password="test",
    host_key_policy=SFTPUtils.HostKeyPolicy.AUTO_ADD,
)

Legacy Servers (ssh-rsa / SHA-1)

What changed. Paramiko 5.0 removed ssh-rsa from its host-key defaults — empirically verified, see the research note for the version matrix.

  • paramiko < 5 ships ssh-rsa in defaults at all four negotiation sites. A freshly-imported paramiko already negotiates against an ssh-rsa-only server out of the box.
  • paramiko >= 5 has ssh-rsa removed from all four sites. Connecting to an ssh-rsa-only server raises IncompatiblePeer: Incompatible ssh peer (no acceptable host key) during KEX, before authentication is attempted.

The [sftp] extra has no upper bound on paramiko, so current resolvers pick paramiko 5+ by default. New installs hit the failure unless they call the helper described below.

Diagnose first

Before mutating paramiko's defaults, confirm the failure shape. An IncompatiblePeer error from paramiko wraps four distinct negotiation failures — host key, KEX, cipher, or MAC — and only the first is fixed by enable_ssh_rsa_compat(). The other three need connect_kwargs={"disabled_algorithms": ...} instead. SFTPUtils.scan_host_algorithms() parses the server's SSH_MSG_KEXINIT advertisement (RFC 4253 § 7.1) over a raw socket — no paramiko, no authentication, so the result reflects exactly what the server advertises:

from remote_store.backends import SFTPUtils

info = SFTPUtils.scan_host_algorithms("legacy.example.com")
print("host-key algos:", info["server_host_key_algorithms"])
print("kex algos:     ", info["kex_algorithms"])

If server_host_key_algorithms == ["ssh-rsa"], this guide applies and the next subsection is the fix. If it's kex_algorithms that's narrow (e.g. only diffie-hellman-group14-sha1), enable_ssh_rsa_compat() will not help; widen the relevant list via SFTPBackend(connect_kwargs={"disabled_algorithms": ...}).

Fix: re-enable ssh-rsa at process startup

SFTPUtils.enable_ssh_rsa_compat() adds ssh-rsa to all four paramiko host-key sites in one call. It is a no-op on paramiko < 5 (all four guards short-circuit) and the required recovery path on paramiko >= 5:

from remote_store.backends import SFTPUtils

# Call once, before any SFTPBackend connect to a legacy server.
SFTPUtils.enable_ssh_rsa_compat()

If you observe IncompatiblePeer: no acceptable kex algorithm

KEX / cipher / MAC negotiation failures are a separate problem; enable_ssh_rsa_compat() does not help. Widen the relevant algorithm list via the connect_kwargs={"disabled_algorithms": ...} SFTP constructor argument instead.

Security tradeoff

This is process-global: every paramiko transport in the process will then accept SHA-1 host keys. Only enable this if every server your process connects to is under your operational control, and push server operators to upgrade to rsa-sha2-256/rsa-sha2-512 so the shim can be removed.

Alternative: pin paramiko<5

Pinning paramiko<5 keeps the consumer on the empirically-verified compatible range (>= 3.0,< 5) and avoids the helper entirely. The tradeoff is freezing on paramiko 4.x while upstream moves on:

Approach Loses
paramiko<5 pin Future paramiko 5+ improvements (perf, protocol features, CVE fixes once 4.x EOLs)
enable_ssh_rsa_compat() Process-wide SHA-1 host-key acceptance only

Either composes cleanly with the library's [sftp] floor of paramiko>=3.0. To pin the consumer must override at their own dependency layer (e.g. requirements.txt line paramiko>=3.0,<5).

Connection Behaviour

  • Lazy connect — no network call happens during construction. The SSH/SFTP connection is established on the first operation.
  • Auto-reconnect — if the connection goes stale between operations, the backend reconnects transparently.
  • Retry — transient SSH errors (SSHException, OSError, EOFError) are retried up to 3 times with exponential backoff (2 s min, 10 s max).
  • Single connection, not thread-safe — each SFTPBackend instance holds one paramiko SFTPClient. Calling it from multiple threads simultaneously (e.g. via SyncBackendAdapter + asyncio.gather) races on the shared socket. Create one SFTPBackend per thread for parallel workloads.

Capabilities

The SFTP backend supports all capabilities except GLOB and ATOMIC_MOVE. See the capabilities matrix for full details.

Atomic write caveat

Atomic writes use a temp file (.~tmp.<name>.<uuid>) and rename. If the connection drops between write and rename, the orphan temp file will remain on the server.

Move fallback

move() tries posix_rename (atomic), then standard rename(), then copy + delete as a last resort. Most servers support at least rename().

TOCTOU on overwrite=False

Like most backends, the exists-check and write are separate operations. Concurrent writers can both pass the check.

See the Concurrency and Atomicity Guarantees guide for details and workarounds.

Escape Hatch

Access the underlying paramiko.SFTPClient when you need protocol-level features:

import paramiko

sftp_client = backend.unwrap(paramiko.SFTPClient)
sftp_client.listdir_attr("/custom/path")

See also

API Reference

SFTPBackend

SFTPBackend(
    host: str,
    *,
    port: int = 22,
    username: str | None = None,
    password: str | Secret | None = None,
    pkey: Any = None,
    base_path: str = "/",
    host_key_policy: HostKeyPolicy | str = STRICT,
    known_host_keys: str | None = None,
    host_keys_path: str | None = None,
    config: dict[str, Any] | None = None,
    timeout: int = 10,
    connect_kwargs: dict[str, Any] | None = None,
    retry: RetryPolicy | None = None,
)

Bases: Backend

SFTP backend using pure paramiko.

move() attempts posix_rename (atomic on POSIX-compliant servers), then falls back to rename, and finally to a stream copy followed by a delete. Because atomicity cannot be guaranteed across all servers, ATOMIC_MOVE is not declared.

Warning

Not thread-safe for concurrent access. This backend maintains a single SSH/SFTP connection (paramiko SFTPClient), which is not safe to call from multiple threads simultaneously. Concurrent calls via SyncBackendAdapter and asyncio.gather will race on the shared socket and may hang or corrupt responses. Create one SFTPBackend instance per thread if you need parallel operations.

Parameters:

  • host (str) –

    SFTP server hostname (required, non-empty).

  • port (int, default: 22 ) –

    SSH port (default: 22).

  • username (str | None, default: None ) –

    SSH username.

  • password (str | Secret | None, default: None ) –

    SSH password.

  • pkey (Any, default: None ) –

    paramiko.PKey instance for key-based auth.

  • base_path (str, default: '/' ) –

    Root path on the remote server (default: /).

  • host_key_policy (HostKeyPolicy | str, default: STRICT ) –

    Host key verification policy (see SFTPUtils.HostKeyPolicy). Accepts enum value or string.

  • known_host_keys (str | None, default: None ) –

    Known hosts string (code-level override).

  • host_keys_path (str | None, default: None ) –

    Path to known_hosts file (default: ~/.ssh/known_hosts).

  • config (dict[str, Any] | None, default: None ) –

    Optional config dict (may contain known_host_keys).

  • timeout (int, default: 10 ) –

    SSH connection timeout in seconds.

  • connect_kwargs (dict[str, Any] | None, default: None ) –

    Extra kwargs passed to SSHClient.connect().

check_health

check_health() -> None

Confirm the SFTP connection works by stat-ing the base path.

Establishes the SSH/SFTP connection lazily if needed (retried at connection scope) and issues one stat round-trip.

Raises:

resolve

resolve(path: str) -> ResolutionPlan

Return a ResolutionPlan with SFTP-specific details.

Parameters:

  • path (str) –

    Backend-relative key.

Returns:

exists

exists(path: str) -> bool

Return True if a file or folder exists at path; never NotFound.

Issues one stat round-trip; a missing path returns False.

Raises:

is_file

is_file(path: str) -> bool

Return True if path is an existing regular file (False if absent or a folder).

Raises:

is_folder

is_folder(path: str) -> bool

Return True if path is an existing directory (False if absent or a file).

Raises:

read

read(path: str) -> BinaryIO

Open path for reading and return a buffered, streaming handle.

Reads lazily over the SFTP channel (wrapped in a BufferedReader), so memory stays constant regardless of file size. Because the read is deferred, path being a directory must be rejected before the handle is returned — a real OpenSSH server opens a directory for reading without error and only fails on the first read, which this streaming path never issues itself. So this one read path keeps an eager type check, unlike read_bytes (which reads immediately and classifies on failure).

Raises:

  • NotFound

    If the file does not exist, or a path component is itself a file.

  • InvalidPath

    If path names a directory.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails mid-read.

read_bytes

read_bytes(path: str) -> bytes

Read and return the full file content as bytes.

Prefetches and materialises the whole file in memory (unlike the lazy read stream).

Directory rejection is lazy (unlike read, which stats eagerly): a directory target raises InvalidPath only because the read of it fails. This assumes the server either refuses to open a directory for reading or reports a non-zero directory st_size — both hold on OpenSSH, where a directory reports st_size == 4096. A non-standard server that opens a directory for reading and reports st_size == 0 would make this return empty bytes rather than raising InvalidPath.

Raises:

  • NotFound

    If the file does not exist, or a path component is itself a file.

  • InvalidPath

    If path names a directory (subject to the server assumption above).

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails mid-read.

write

write(
    path: str,
    content: WritableContent,
    *,
    overwrite: bool = False,
    metadata: Mapping[str, str] | None = None,
) -> WriteResult

Write content to path, streaming it over the SFTP channel.

The bytes are streamed straight to the destination file (no temp-and-rename), so a dropped connection mid-write can leave a partial or truncated file there — use write_atomic when readers must never see a half-written file. Missing parent directories are created first (one stat per ancestor).

The returned WriteResult carries size (counted during upload) and source="native", but every rich field — last_modified, etag, version_id, digest — is None: SFTP's write response carries no metadata at all, and the backend does not stat afterwards to fetch any. Call get_file_info when the metadata is needed.

Raises:

  • AlreadyExists

    If the file exists and overwrite is False.

  • InvalidPath

    If path names a directory, or an ancestor of path exists as a regular file.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails mid-write.

write_atomic

write_atomic(
    path: str,
    content: WritableContent,
    *,
    overwrite: bool = False,
    metadata: Mapping[str, str] | None = None,
) -> WriteResult

Write content to path atomically via a temp file plus server rename.

Readers never observe a partial file: the body is streamed to a hidden temp file in the destination directory, then promoted with posix_rename (atomic on POSIX-compliant servers). Servers without posix_rename fall back to a plain rename (non-atomic overwrite: the target is removed first), and the temp file is cleaned up on failure.

As in write, the returned WriteResult carries size and source="native" but leaves every rich field (last_modified / etag / version_id / digest) None.

Raises:

  • AlreadyExists

    If the file exists and overwrite is False.

  • InvalidPath

    If path names a directory, or an ancestor of path exists as a regular file.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails.

open_atomic

open_atomic(
    path: str, *, overwrite: bool = False
) -> Iterator[BinaryIO]

Yield a writable handle promoted to path atomically on clean exit.

Writes stream to a hidden temp file in the destination directory; on clean exit it is promoted with posix_rename (atomic on POSIX servers, falling back to rename), and on any exception the temp file is removed and path is left untouched.

Raises:

  • AlreadyExists

    If the file exists and overwrite is False.

  • InvalidPath

    If path names a directory, or an ancestor of path exists as a regular file.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails.

delete

delete(path: str, *, missing_ok: bool = False) -> None

Delete the file at path.

Raises:

  • NotFound

    If the file does not exist (or a path component is itself a file) and missing_ok is False.

  • InvalidPath

    If path names a directory (use delete_folder).

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails.

delete_folder

delete_folder(
    path: str,
    *,
    recursive: bool = False,
    missing_ok: bool = False,
) -> None

Delete the folder at path.

recursive=True walks and removes the subtree bottom-up (one round-trip per entry — not atomic; an interruption can leave the tree partially removed). recursive=False removes only an empty folder after checking it has no entries.

Raises:

list_files

list_files(
    path: str,
    *,
    recursive: bool = False,
    max_depth: int | None = None,
) -> Iterator[FileInfo]

Yield files under path, one FileInfo at a time.

Lazily walks the remote directory (listdir_attr); a missing path yields nothing. recursive descends via one directory-listing round-trip per folder (max_depth bounds the descent). Failures other than a missing path surface as RemoteStoreError during iteration.

list_folders

list_folders(path: str) -> Iterator[FolderEntry]

Yield immediate subfolders of path as FolderEntry records.

One directory-listing round-trip; a missing path yields nothing, and other failures surface as RemoteStoreError during iteration.

iter_children

iter_children(
    path: str,
) -> Iterator[FileInfo | FolderEntry]

Yield the immediate files and folders under path in one listing.

Overrides the base two-pass default with a single listdir_attr round-trip, yielding FileInfo for files and FolderEntry for folders. A missing path yields nothing; other failures surface as RemoteStoreError during iteration.

get_file_info

get_file_info(path: str) -> FileInfo

Return metadata for the file at path from a single stat round-trip.

Raises:

get_folder_info

get_folder_info(path: str) -> FolderInfo

Return aggregate metadata for the folder at path.

File count, total size, and latest modification time are gathered by recursively walking the whole subtree (one listing round-trip per folder), so cost scales with the number of descendants.

Raises:

move

move(
    src: str, dst: str, *, overwrite: bool = False
) -> None

Move or rename the file src to dst.

Tries posix_rename first (atomic on POSIX-compliant servers), then a plain rename, and finally a stream copy-then-delete. Because the outcome depends on server support, atomicity is not guaranteed across all servers and ATOMIC_MOVE is not declared. src == dst is a no-op; missing parent directories of dst are created first.

Raises:

  • NotFound

    If src does not exist.

  • InvalidPath

    If src or dst names a directory, or an ancestor of dst exists as a regular file.

  • AlreadyExists

    If dst exists, src != dst, and overwrite is False.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails.

copy

copy(
    src: str, dst: str, *, overwrite: bool = False
) -> None

Copy the file src to dst by streaming through the client.

SFTP has no server-side copy, so the bytes round-trip through the client (download then upload); this is not atomic — an interruption can leave a partial file at dst. src == dst is a no-op; missing parent directories of dst are created first.

Raises:

  • NotFound

    If src does not exist.

  • InvalidPath

    If src or dst names a directory, or an ancestor of dst exists as a regular file.

  • AlreadyExists

    If dst exists, src != dst, and overwrite is False.

  • PermissionDenied

    If the server denies access (EACCES).

  • BackendUnavailable

    If the SSH/SFTP connection cannot be established or fails.