[
https://issues.apache.org/jira/browse/IGNITE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194013#comment-15194013
]
Cory Parent commented on IGNITE-2831:
-------------------------------------
I agree with this solution as it doesn't require any additional information and
would remain platform agnostic. A simple call to
`http://169.254.169.254/latest/meta-data/public-ipv4` should solve the issue.
In lieu of out of the box support for the time being, could you provide any
guidance on the interim solution? Perhaps an example of implementing the
`AddressResolver`?
> 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)
