[
https://issues.apache.org/jira/browse/IGNITE-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283259#comment-16283259
]
Alexey Popov commented on IGNITE-7052:
--------------------------------------
A scope of changes:
1. added {{bucketEndpoint}} configuration property to {{TcpDiscoveryS3IpFinder}}
2. added {{bucketEndpoint}} configuration property to {{S3CheckpointSpi}}
3. added tests for new property
4. updated existent tests to avoid bucket name conflicts
[~ntikho...@apache.org], please review
TC run:
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F3179%2Fhead
> S3 IP finder: add an ability to provide endpoint address
> --------------------------------------------------------
>
> Key: IGNITE-7052
> URL: https://issues.apache.org/jira/browse/IGNITE-7052
> Project: Ignite
> Issue Type: Improvement
> Components: s3
> Affects Versions: 2.3
> Reporter: Valentin Kulichenko
> Fix For: 2.4
>
>
> By default S3 client detects region automatically by sending special request
> to {{us-west-1}}. In case environment is restricted to some other region,
> this leads to connection timeout exception.
> The issue can be solved by providing a specific region endpoint via
> {{AmazonS3Client#setEndpoint}} method. To support this we need to add
> {{endpoint}} configuration property to the IP finder.
> List of S3 region endpoints:
> http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
