[JCR-3732] Externalize S3 endpoints

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.4
• Fix Version/s: 2.7.5
• Component/s: jackrabbit-core
• Assignee: Dominique Pfister
• Reporter: Shashank Gupta
• Created: 20/Feb/14 10:54
• Updated: 08/Oct/19 15:21
• Resolved: 13/Mar/14 12:29

Description

Currently S3 connector uses S3 region ( already externalized via aws.properties) to configure S3 endpoint as per the mapping [1].
There are cases where single S3 region may contains multiple endpoints. for e. US Standard region has two endpoints:
s3.amazonaws.com (Northern Virginia or Pacific Northwest)
s3-external-1.amazonaws.com (Northern Virginia only)
To handle these cases, S3 connector should externalize endpoint configuration (as optional) and has higher precedence over endpoint derived via S3 region.
[1]
http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region