Is it possible to use Tridion 2013 to publish static content (jpg, xml, json) to an Amazon S3 bucket?

Anyone have any idea how this can be accomplished?


  • 2
    You are going to need to write either a storage extension or custom deployer I think. You could look at github.com/SI4T for reference. It stores content in the Broker DB and SOLR Nov 13, 2013 at 5:33
  • 2
    @ChrisMorgan that would have been a valid answer, no need to only comment it. Nov 13, 2013 at 9:44

2 Answers 2


As you are using Tridion 2013, I would suggest that you also look at doing this using External Content Libraries (ECL), rather than through publishing.

Here are some advantage and disadvantages of this approach:


  • Reduced CM database size (especially if you are storing large binaries or videos)
  • Faster publishing (well, actually no publishing of the binaries!)
  • Works better with outscaled publishing (You do not have to pick a Deployer to do the Custom Storage and have this slower than that others OR have the redundancy of every Deployer storing it)
  • A single point of truth (the document is only in one place)
  • You can still add metadata and Component Link to the document using the ECL stub Component
  • Access to the content can be closely controlled within Tridion


  • Editors will need a mechanism for accessing the Amazon S3 bucket to manage the documents. This could be handled through the ECL provider.
  • Additional Content Editor training (for both Tridion and Amazon S3)
  • The document will not be versioned within Tridion (This may also complicate Workflow)
  • You may need to configure Security with Amazon S3 AND Tridion
  • Am I correct in assuming that you mean that through the ECL provider you upload the items in the Amazon S3 bucket (using the Create option in the CMS for a new ECL item) and then at publish time you utilize the direct link to the ECL item? I could see that working, sounds like a better solution than a storage extension in my opinion indeed. Nov 13, 2013 at 9:42
  • @BartKoopman, yes, that is what I was thinking. Nov 13, 2013 at 10:19
  • Very nice option indeed, I would suggest to make that a little more clear in your answer. Specifically, faster publishing will be no publishing of the item by Tridion, but just supplying a link. And the disadvantage of the editors needing a mechanism for accessing Amazon, is actually solved by the ECL provider if you make sure that the provider has the code to upload items to S3. Nov 13, 2013 at 10:52
  • Thanks Bart. I have added some tweaks to my answer. Please feel free to amend with anything that you think I've missed. Nov 13, 2013 at 11:12

You should be writing a Storage Extension and custom Java code to publish to a custom data storage.

You may want to get an idea with this post from architectural perspective as how publishing process works with Custom Data Storage:



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.