The former Porticor support site is now frozen. Please refer to our Intuit page.

Alternative to host name mapping for S3 bucket outside of US Standard

Michael Bertolacci's Avatar

Michael Bertolacci

08 Apr, 2015 02:11 AM

Hi there,

I am very dissatisfied with the idea of using hostname mapping for our s3 bucket outside of the US standard: this means all our s3 traffic will go via Porticor, even if just redirected, which is ridiculous.

I tried using the standard S3 REST API via our Porticor instance, path <instance>.d.porticor.net/<bucketname>/, but the requests just got redirected to the .s3-ap-southeast-2.amazonaws.com subdomain bucket name, and nothing was encrypted.

Is there really no way around this for buckets outside of US standard?

Mike

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac