Yeah, it was always a tech preview kind of thing. The basic operations used to work, but since most of the available client tools (s3cmd/boto/etc) had special workarounds for odd AWS behaviors (in the return behavior), they would have a hard time working with the S3 implementation in CloudStack which was based entirely on the WSDL.
On 10/21/13 10:16 PM, "Darren S" <darren.s.sheph...@gmail.com> wrote: >I didn't even know this feature existed until yesterday, so I thought I'd >try it out, but it seems that the S3 API in CloudStack completely doesn't >work in 4.2. Is it supposed to? Is this an official feature or some >tech preview type thing? > >Darren
