Deliver data to TheyDo via SFTP
Overview
This article is for enterprise IT teams that deliver data to TheyDo but do not use a direct AWS S3 connection. SFTP gives you a second way to get data in, using the managed file transfer (MFT) tooling you already run, over a secure connection.
When to use SFTP
TheyDo can receive data through a cross-account Amazon S3 connection. That works well for teams already set up on AWS, but not every team wants to stand up an AWS account just to send data. SFTP covers that case: if your data delivery is standardized on an MFT tool, you can send the same data over SFTP instead. It is a different transport for the same pipeline, so the data lands in TheyDo the same way once it arrives.
Note: SFTP setup is handled together with your CSM. The steps below outline what to expect; your CSM will help you complete them.
How SFTP delivery is set up
- Ask your CSM to set up SFTP data delivery for your workspace.
- Generate SSH keys for the secure connection.
- Share the public key with TheyDo, and receive an SFTP endpoint in return.
- Configure your MFT tool to deliver files to that endpoint.
- Send a test delivery and confirm the data arrives as expected.
Once delivery is working, your files flow to TheyDo on the same schedule and in the same format your pipeline already uses.
Tip: SFTP changes only how data reaches TheyDo, not what happens next. Once the data is in, it is processed the same way as data delivered over S3. Reviewer note: SFTP is not documented in the product glossary. Confirm the full setup flow with product before publishing, specifically: exact SSH key format, who generates the endpoint, supported file formats, and delivery frequency options. Treat the numbered steps as a draft outline until confirmed. Cross-links to add: "How to import data", "Amazon S3 integration".