[ https://issues.apache.org/jira/browse/JCLOUDS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ignasi Barrera closed JCLOUDS-385. ---------------------------------- > Allow ability to override AWS S3 US Standard endpoint > ----------------------------------------------------- > > Key: JCLOUDS-385 > URL: https://issues.apache.org/jira/browse/JCLOUDS-385 > Project: jclouds > Issue Type: Improvement > Components: jclouds-blobstore, jclouds-core > Affects Versions: 1.7.0, 1.6.3 > Reporter: Niraj Tolia > Priority: Minor > > Currently, jclouds defines the endpoint for US Standard in > AWSS3ProviderMetadata as https://s3.amazonaws.com. The only way I have > discovered so far to override this is to construct a AWSS3ProviderMetadata > object with tweaked default properties for the US Standard Region > (jclouds.region.us-standard.endpoint). > Our use case for setting the URL is that we sometimes see strange DNS > resolution for US Standard that points clients to the Pacific Northwest > region instead of the Virginia region even though the clients are on the east > coast. The AWS recommendation, both through a private support ticket and > publicly documented at > https://forums.aws.amazon.com/message.jspa?messageID=185820 is to use > http://s3-external-1.amazonaws.com for Northern Virginia and > http://s3-external-2.amazonaws.com for Pacific Northwest if clients need to > be pinned to a region. > Is the above approach (tweaking AWSS3ProviderMetadata) the recommended way to > do this? If not, should an easier way of overriding the endpoint be provided? -- This message was sent by Atlassian JIRA (v6.1#6144)