Default ec2 endpoint is ec2.us-east-1.amazonaws.com#30323
Default ec2 endpoint is ec2.us-east-1.amazonaws.com#30323DaveCTurner merged 4 commits intoelastic:masterfrom
Conversation
I split elastic#27925 in two parts: * The documentation fix (this PR) * The code fix (still in elastic#27925) Closes elastic#27464.
|
Hi @dadoonet, what do you think about changing the statement below?
|
|
Pinging @elastic/es-distributed |
|
Thanks for the feedback @wedneyyuri! I updated the PR. |
|
Any update on this PR? |
|
Does it normally take this long to fix a documentation bug? I just spent a good chunk of my weekend trying to figure out why my new cluster in EU wasn't working when I had everything configured according to the documentation which incorrectly says the endpoint is auto detected. Wish I found this PR earlier. |
|
Unfortunately there was a typo in the earlier ping for a review. It should have notified @tlrx. |
|
@elastic/es-distributed Can we merge this documentation PR? People are still suffering from that because our documentation is not accurate. See https://discuss.elastic.co/t/discovery-ec2-plugin-always-tries-to-ping-localhost-never-finds-the-nodes-that-it-should/160433/8 |
Today our docs claim that the `discovery-ec2` plugin auto-detects the EC2 endpoint, but this is not the case. This fixes these docs. Closes #27464.
Today our docs claim that the `discovery-ec2` plugin auto-detects the EC2 endpoint, but this is not the case. This fixes these docs. Closes #27464.
I split #27925 in two parts:
Closes #27464.