search

rabbitmq / rabbitmq-peer-discovery-aws

AWS-based peer discovery backend for RabbitMQ 3.7.0+
Other
24 stars 11 forks source link

no_proxy configuration is required for rabbitmq-peer-discovery-aws in rabbitmq.conf #28

Closed amir-git closed 5 years ago

amir-git commented 5 years ago

I am getting following error when I use "cluster_formation.proxy.http_proxy"

Failed to fetch EC2 instance ID from "http://169.254.169.254/latest/meta-data/instance-id"

Access control configuration prevents your request from being allowed at this time. Please contact your service provider if you feel this is incorrect.

I have setup proxy and can successfully load the required plugins, I need to configure no_proxy somewhere to be able to retrieve instance-id

michaelklishin commented 5 years ago

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).

We get at least a dozen of questions through various venues every single day, often light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.

Please post this to rabbitmq-users.

Thank you.

michaelklishin commented 5 years ago

This plugin assumes that http://169.254.169.254/latest/meta-data/instance-id is accessible for instance metadata retrieval.

Access control configuration prevents your request from being allowed at this time

contains a hint.

michaelklishin commented 5 years ago

Perhaps proxy exclusions would help but I don't know why would it make sense to access 169.254.169.254 over a proxy on AWS.

amir-git commented 5 years ago

to be able to use the plugin I need to use corp proxy so rabbitmq.conf file set as below: cluster_formation.proxy.http_proxy = {{ proxy_address }} cluster_formation.proxy.https_proxy = {{ proxy_address }} however when I set proxy_exclusions, the rabbitmq-server service fails to restart : cluster_formation.proxy.proxy_exclusions = localhost, 169.254.169.254

amir-git commented 5 years ago

Perhaps proxy exclusions would help but I don't know why would it make sense to access 169.254.169.254 over a proxy on AWS.

I reached to this point that I need to bypass 169.254.169.254 , now I am struggling how

michaelklishin commented 5 years ago

@amir-git please post your questions to the mailing list in the future.

Proxy exclusions are configured like so

cluster_formation.proxy.proxy_exclusions.1 = a-host
cluster_formation.proxy.proxy_exclusions.2 = 169.254.169.254

(very much like all list-like things, e.g. listeners, are configured in rabbitmq.conf).

michaelklishin commented 5 years ago

Cluster Formation documentation guide was updated to cover this. Thank you for bringing this up.