Add support to configure port in cloud_id #7794
Labels
Comments
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 6, 2018
Make it possible for the host section from the cloud.id to contain a port. If the port is not specified, 443 is used, like before. This is proposed fix for elastic#7794.
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 8, 2018
Make it possible for the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before. The custom port can be specified in multiple ways. The cloudid is formed like this: `<host>:<es-id>:<kb-id>`. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host). Examples: ``` 'us-central1.gcp.cloud.es.io:9243$ac31ebb90241773157043c34fd26fd46$a4c06230e48c8fce7be88a074a3bb3e0' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9243 ``` Or: ``` 'us-central1.gcp.cloud.es.io$ac31ebb90241773157043c34fd26fd46:9243$a4c06230e48c8fce7be88a074a3bb3e0:9244' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9244 ``` Closes: elastic#7794. (cherry picked from commit daaca33)
tsg
added a commit
to tsg/beats
that referenced
this issue
Aug 8, 2018
Make it possible for the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before. The custom port can be specified in multiple ways. The cloudid is formed like this: `<host>:<es-id>:<kb-id>`. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host). Examples: ``` 'us-central1.gcp.cloud.es.io:9243$ac31ebb90241773157043c34fd26fd46$a4c06230e48c8fce7be88a074a3bb3e0' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9243 ``` Or: ``` 'us-central1.gcp.cloud.es.io$ac31ebb90241773157043c34fd26fd46:9243$a4c06230e48c8fce7be88a074a3bb3e0:9244' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9244 ``` Closes: elastic#7794. (cherry picked from commit daaca33)
kvch
pushed a commit
that referenced
this issue
Aug 8, 2018
Make it possible for the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before. The custom port can be specified in multiple ways. The cloudid is formed like this: `<host>:<es-id>:<kb-id>`. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host). Examples: ``` 'us-central1.gcp.cloud.es.io:9243$ac31ebb90241773157043c34fd26fd46$a4c06230e48c8fce7be88a074a3bb3e0' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9243 ``` Or: ``` 'us-central1.gcp.cloud.es.io$ac31ebb90241773157043c34fd26fd46:9243$a4c06230e48c8fce7be88a074a3bb3e0:9244' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9244 ``` Closes: #7794. (cherry picked from commit daaca33)
kvch
pushed a commit
that referenced
this issue
Aug 8, 2018
Make it possible for the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before. The custom port can be specified in multiple ways. The cloudid is formed like this: `<host>:<es-id>:<kb-id>`. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host). Examples: ``` 'us-central1.gcp.cloud.es.io:9243$ac31ebb90241773157043c34fd26fd46$a4c06230e48c8fce7be88a074a3bb3e0' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9243 ``` Or: ``` 'us-central1.gcp.cloud.es.io$ac31ebb90241773157043c34fd26fd46:9243$a4c06230e48c8fce7be88a074a3bb3e0:9244' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9244 ``` Closes: #7794. (cherry picked from commit daaca33)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Make it possible for the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before. The custom port can be specified in multiple ways. The cloudid is formed like this: `<host>:<es-id>:<kb-id>`. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host). Examples: ``` 'us-central1.gcp.cloud.es.io:9243$ac31ebb90241773157043c34fd26fd46$a4c06230e48c8fce7be88a074a3bb3e0' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9243 ``` Or: ``` 'us-central1.gcp.cloud.es.io$ac31ebb90241773157043c34fd26fd46:9243$a4c06230e48c8fce7be88a074a3bb3e0:9244' ``` Results in: ``` ES: https://ac31ebb90241773157043c34fd26fd46.us-central1.gcp.cloud.es.io:9243 KB: https://a4c06230e48c8fce7be88a074a3bb3e0.us-central1.gcp.cloud.es.io:9244 ``` Closes: elastic#7794. (cherry picked from commit 8d8ac27)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using cloud_id beats (and logstash) when connecting to an ECE hosted deployment will require users to add a redirect rule to their reverse proxy, or load balancer since beats will default to 443 if no port is specified. This is fine for ESS (where we do forward these requests to the correct port), but will break in case of ECE that listens on a different port by default.
Including the relevant port in the cloud_id will allow this integration to work seamlessly without a need to configure any redirect rules.
// cc @tsg @AlexP-Elastic
The text was updated successfully, but these errors were encountered: