Data Feed SFTP Export Failed | Community
Skip to main content
F
fer2209
Level 2
July 31, 2026
Solved

Data Feed SFTP Export Failed

  • July 31, 2026
  • 5 replies
  • 88 views

Hi Adobe Community,

I already have a location configured to export a Data Feed. When I process it, the feed fails with Error 300 (Delivery Error).

My setup:

  • Destination is an SFTP account that should automatically ingest the data into an S3 bucket.

  • I can see the .tsv.gz files on the SFTP server.

  • However, when I check the S3 bucket, the files are not there.

Questions:

  • Does Adobe deliver only to the SFTP endpoint, and the sync to S3 must be handled separately (e.g., AWS Transfer Family)?

  • Has anyone successfully configured Data Feeds to land directly in S3 via SFTP integration?

  • Any guidance on resolving Error 300 in this scenario would be greatly appreciated.

Thanks in advance for your help!

 

Best answer by parthGupta

Hi ​@fer2209 -
 

Adobe actually supports two distinct delivery mechanisms, and it's worth knowing the difference:

  • Direct S3 delivery — Adobe Data Feeds can deliver straight to an S3 bucket as a destination type, using an access key/secret key and bucket/prefix configuration (not SFTP at all). Adobe's own Data Feeds documentation covers Amazon S3 as a supported destination directly.
  • SFTP delivery — a completely separate destination type where Adobe pushes files to your SFTP endpoint. Adobe has no visibility into, or involvement with, whatever happens to the file after it lands on your SFTP server. Any SFTP→S3 sync is entirely your own infrastructure's responsibility — Adobe isn't aware of it and can't guarantee compatibility with it.

    if you're routing through SFTP, sync to S3 has to be handled separately. Given your use case, it may honestly be simpler to just configure the Data Feed with S3 as the direct destination type rather than going through SFTP + AWS Transfer Family — that removes an entire layer of moving parts and potential failure points.

5 replies

parthGupta
parthGuptaAccepted solution
Level 2
August 1, 2026

Hi ​@fer2209 -
 

Adobe actually supports two distinct delivery mechanisms, and it's worth knowing the difference:

  • Direct S3 delivery — Adobe Data Feeds can deliver straight to an S3 bucket as a destination type, using an access key/secret key and bucket/prefix configuration (not SFTP at all). Adobe's own Data Feeds documentation covers Amazon S3 as a supported destination directly.
  • SFTP delivery — a completely separate destination type where Adobe pushes files to your SFTP endpoint. Adobe has no visibility into, or involvement with, whatever happens to the file after it lands on your SFTP server. Any SFTP→S3 sync is entirely your own infrastructure's responsibility — Adobe isn't aware of it and can't guarantee compatibility with it.

    if you're routing through SFTP, sync to S3 has to be handled separately. Given your use case, it may honestly be simpler to just configure the Data Feed with S3 as the direct destination type rather than going through SFTP + AWS Transfer Family — that removes an entire layer of moving parts and potential failure points.
    F
    fer2209Author
    Level 2
    August 3, 2026

    Thanks!!

    F
    fer2209Author
    Level 2
    August 3, 2026

    Do you know what is the common file inside of zip? Is it .tab? Do you know if exist a different way to export this data? The reason is because by company policies data transfer is  SFTP + AWS Transfer Family and if the default file is .tab is not allow it

    parthGupta
    parthGupta
    Level 2
    August 3, 2026

    It’s .tsv (tab-separated values)

    Terms & ConditionsAccessibility statement

    Loading footer...