[
https://issues.apache.org/jira/browse/IGNITE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193906#comment-15193906
]
Valentin Kulichenko commented on IGNITE-2831:
---------------------------------------------
This can be achieved by implementing {{AddressResolver}} interface. I think we
should provide implementations for clouds out of the box. E.g., for EC2 this
can be done using metadata URLs:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
> Support advertised address for use with EC2 service discovery
> -------------------------------------------------------------
>
> Key: IGNITE-2831
> URL: https://issues.apache.org/jira/browse/IGNITE-2831
> Project: Ignite
> Issue Type: Improvement
> Reporter: Cory Parent
> Priority: Blocker
>
> Currently it is not possible to connect to an Ignite cluster as a client from
> a non-AWS environment (e.g. local development machine) due to the manner in
> which Ignite registers instance addresses. I propose that the default
> behavior (registering the private IP address) should remain, however, the
> ability to mitigate this issue should be provided via a method to use an
> advertised address instead. Such a solution is provided by Kafka
> configuration to resolve this very issue. This would allow us to override the
> private IP address with a public or Elastic IP, thus allowing connection from
> non-AWS environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
