FTP endpoint

Not applicable

If i have FTP endpoint and want my users to start using the gateway what are the possible designs. Is streaming the file over the cloud infra a good choice ?

1 8 2,068
8 REPLIES 8

Can you please elaborate on your requirement? By default an API proxy in Apigee Edge can only work with HTTP/HTTP(s) backend services. However you could use node.js or Java callouts to talk to a non-HTTP end-point. You could stream APIs for large payloads.

If you want to use Apigee Edge as an HTTP facade on an FTP PUT operation, you can do it with this callout. It is a custom policy that can be run in any Apigee Edge installation.

You need to configure it to specify the FTP endpoint and port, the credentials, the directory... and then it should just work. There is an example API Proxy bundle in that github repo showing how to use it.

Good luck!

Cool callout! For uploading or downloading files greater than 10mb, does the callout still work with streaming? Or is meant to work with files under the limit?

Is there a way to configure the above callout example to use SFTP? I poked around in the codebase but didn't see anything.

Not applicable

Storage based use cases are interesting to me. I would like to know more about the content accessible via FTP. Is it general information or specific to the consumer? Are there significant security requirements? Is the API proxy intended to provide analytics about the consumption of the content? The more information you can provide the more the community can share their thinking.

Yes security is paramount, governance, analytics, user administration etc is what i need the proxy for. I am specifically concernd about the data flow DMZ-- CLOUD -- User , this will make it slow and add another tool to manage with our MFT solution

Not applicable

My use case :- Users use our secure file storage to upload and download files. We have another tool - a Managed File Transfer tool which provides both SFTP and HTTPS end points to serve files in a secure manner..

Hence while i can configure my proxies on edge running on cloud to the https end point of the mft, how can i route traffic of customers doing sftp through the proxies ? as i would want analytics and governance around the sftp flow too.

If i stream large file (>>2gb) using the https endpoint- the stream flows from our data center to cloud and then to end customer- this increases complexity and time. What are some solutions to improve this situation- or is it even right to do so ?

Has any one seen the architecture of ebay or amazon wrt to large file transfer ?

Not applicable

My use case :- Users use our secure file storage to upload and download files. We have another tool - a Managed File Transfer tool which provides both SFTP and HTTPS end points to serve files in a secure manner..

Hence while i can configure my proxies on edge running on cloud to the https end point of the mft, how can i route traffic of customers doing sftp through the proxies ? as i would want analytics and governance around the sftp flow too.

If i stream large file (>>2gb) using the https endpoint- the stream flows from our data center to cloud and then to end customer- this increases complexity and time. What are some solutions to improve this situation- or is it even right to do so ?

Has any one seen the architecture of ebay or amazon wrt to large file transfer ?