{"id":5383,"date":"2018-01-05T10:00:34","date_gmt":"2018-01-05T15:00:34","guid":{"rendered":"http:\/\/chriscolotti.us\/?p=5383"},"modified":"2018-01-05T19:16:12","modified_gmt":"2018-01-06T00:16:12","slug":"how-to-use-tintri-cloud-connector-with-other-s3-targets","status":"publish","type":"post","link":"https:\/\/chriscolotti.us\/vmware\/how-to-use-tintri-cloud-connector-with-other-s3-targets\/","title":{"rendered":"How To Use Tintri Cloud Connector With Other S3 Targets"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Happy 2018 everyone!\u00a0 I wanted to share something I have been testing at the request of a few customers that have been interested in using Tintri Cloud Connector.\u00a0 I will preface this with the simple statement that this is currently unsupported<\/strong>, however I am working on that within the Tintri walls.\u00a0 What makes Tintri Cloud Connector unique is that it natively interacts with the S3 API.\u00a0 Therefore, as long as an S3 target is 100% S3 API compliant there is no reason I have found for this not to work.\u00a0 In fact, I have tested with multiple targets as you will see.<\/p>\n

<\/p>\n

When Tintri Cloud Connector was first released last year the integration was for AWS S3 in their public cloud and for IBM Cloud Object Storage which is essentially on premises S3 target.\u00a0 So I got to thinking…..as did a few customers, what about other S3 compliant targets such as:<\/p>\n