Skip to content

Commit cc8fbcd

Browse files
eedugoneedugon
committed
all urls and ips updated
1 parent ab05281 commit cc8fbcd

File tree

7 files changed

+32
-32
lines changed

7 files changed

+32
-32
lines changed

‎deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet-self.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ PUT /_cluster/settings
2727
"remote": {
2828
"alias-for-my-remote-cluster": { // Align the alias with the remote cluster name used when adding the API key.
2929
"mode":"proxy",
30-
"proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io:9400",
31-
"server_name": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io"
30+
"proxy_address": "<REMOTE_CLUSTER_ADDRESS>:9443",
31+
"server_name": "<REMOTE_CLUSTER_SERVER_NAME>"
3232
}
3333
}
3434
}

‎deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,8 @@ PUT /_cluster/settings
3535
"remote": {
3636
"alias-for-my-remote-cluster": { // Remote cluster alias
3737
"mode":"proxy",
38-
"proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io:9400",
39-
"server_name": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io"
38+
"proxy_address": "<REMOTE_CLUSTER_ADDRESS>:9443",
39+
"server_name": "<REMOTE_CLUSTER_SERVER_NAME>"
4040
}
4141
}
4242
}

‎deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -161,15 +161,15 @@ A deployment can be configured to trust all or specific deployments in any envir
161161

162162
* two specific clusters with the cluster IDs `aaaabbbbaaaabbbb`<1> and `xxxxyyyyxxxxyyyy`<2> from an organization with organization ID `1053523734`
163163
* <3> any cluster from an organization with organization ID `83988631`
164-
* <4> The nodes from its own cluster (whose certificates follow a different convention: `CN = node1.example.com`, `CN = node2.example.com` and `CN = node3.example.com`)
164+
* <4> The nodes from its own cluster (whose certificates follow a different convention: `CN = node1.<CLUSTER_FQDN>`, `CN = node2.<CLUSTER_FQDN>` and `CN = node3.<CLUSTER_FQDN>`)
165165

166166

167167
```
168168
trust.subject_name:
169169
- *.node.aaaabbbbaaaabbbb.cluster.1053523734.account
170170
- *.node.xxxxyyyyxxxxyyyy.cluster.1053523734.account
171171
- *.node.*.cluster.83988631.account
172-
- node*.example.com
172+
- node*.<CLUSTER_FQDN>
173173
```
174174
175175
::::{tip}
@@ -180,7 +180,7 @@ Generate new node certificates for an entire cluster using the file input mode o
180180
::::{dropdown} Using the API
181181
You can update a deployment using the appropriate trust settings for the {{es}} payload.
182182
183-
In order to trust a cluster whose nodes present certificates with the subject names: "CN = node1.example.com", "CN = node2.example.com" and "CN = node3.example.com" in a self-managed environment, you could update the trust settings with an additional direct trust relationship like this:
183+
In order to trust a cluster whose nodes present certificates with the subject names: "CN = node1.<CLUSTER_FQDN>", "CN = node2.<CLUSTER_FQDN>" and "CN = node3.<CLUSTER_FQDN>" in a self-managed environment, you could update the trust settings with an additional direct trust relationship like this:
184184
185185
```json
186186
{
@@ -195,7 +195,7 @@ In order to trust a cluster whose nodes present certificates with the subject na
195195
{
196196
"type" : "generic",
197197
"name" : "My Self-managed environment",
198-
"additional_node_names" : ["node1.example.com", "node2.example.com", "node3.example.com",],
198+
"additional_node_names" : ["node1.<CLUSTER_FQDN>", "node2.<CLUSTER_FQDN>", "node3.<CLUSTER_FQDN>",],
199199
"certificates" : [
200200
{
201201
"pem" : "-----BEGIN CERTIFICATE-----\nMIIDTzCCA...H0=\n-----END CERTIFICATE-----"

‎deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,12 +164,12 @@ A deployment can be configured to trust all or specific deployments in any envir
164164
- *.node.aaaabbbbaaaabbbb.cluster.1053523734.account <1>
165165
- *.node.xxxxyyyyxxxxyyyy.cluster.1053523734.account <1>
166166
- *.node.*.cluster.83988631.account <2>
167-
- node*.example.com <4>
167+
- node*.<CLUSTER_FQDN> <4>
168168
```
169169

170170
1. two specific clusters with cluster ids `aaaabbbbaaaabbbb` and `xxxxyyyyxxxxyyyy` in an ECE environment with Environment ID `1053523734`
171171
2. any cluster from an ECE environment with Environment ID `83988631`
172-
3. the nodes from its own cluster (whose certificates follow a different convention: `CN = node1.example.com`, `CN = node2.example.com` and `CN = node3.example.com`)
172+
3. the nodes from its own cluster (whose certificates follow a different convention: `CN = node1.<CLUSTER_FQDN>`, `CN = node2.<CLUSTER_FQDN>` and `CN = node3.<CLUSTER_FQDN>`)
173173

174174
::::{tip}
175175
Generate new node certificates for an entire cluster using the file input mode of the certutil.
@@ -179,7 +179,7 @@ Generate new node certificates for an entire cluster using the file input mode o
179179
::::{dropdown} Using the API
180180
You can update a deployment using the appropriate trust settings for the {{es}} payload.
181181

182-
In order to trust a cluster whose nodes present certificates with the subject names: "CN = node1.example.com", "CN = node2.example.com" and "CN = node3.example.com" in a self-managed environment, you could update the trust settings with an additional direct trust relationship like this:
182+
In order to trust a cluster whose nodes present certificates with the subject names: "CN = node1.<CLUSTER_FQDN>", "CN = node2.<CLUSTER_FQDN>" and "CN = node3.<CLUSTER_FQDN>" in a self-managed environment, you could update the trust settings with an additional direct trust relationship like this:
183183

184184
```json
185185
{
@@ -194,7 +194,7 @@ In order to trust a cluster whose nodes present certificates with the subject na
194194
{
195195
"type" : "generic",
196196
"name" : "My Self-managed environment",
197-
"additional_node_names" : ["node1.example.com", "node2.example.com", "node3.example.com",],
197+
"additional_node_names" : ["node1.<CLUSTER_FQDN>", "node2.<CLUSTER_FQDN>", "node3.<CLUSTER_FQDN>",],
198198
"certificates" : [
199199
{
200200
"pem" : "-----BEGIN CERTIFICATE-----\nMIIDTzCCA...H0=\n-----END CERTIFICATE-----"

‎deploy-manage/remote-clusters/remote-clusters-api-key.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ If a remote cluster is part of an {{ech}} (ECH) deployment, the remote cluster s
7676
3. Generate a certificate and private key pair for the nodes in the remote cluster:
7777

7878
```sh
79-
./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=192.0.2.1
79+
./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=<CLUSTER_FQDN> --ip=192.0.2.1
8080
```
8181

8282
* Replace `CA_PASSWORD` with the CA password from the previous step.
@@ -180,7 +180,7 @@ PUT /_cluster/settings
180180
"remote" : {
181181
"cluster_one" : { <1>
182182
"seeds" : [
183-
"my.remote.cluster.com:9443" <2>
183+
"<MY_REMOTE_CLUSTER_ADDRESS>:9443" <2>
184184
]
185185
}
186186
}
@@ -205,7 +205,7 @@ The API response indicates that the local cluster is connected to the remote clu
205205
{
206206
"cluster_one" : {
207207
"seeds" : [
208-
"my.remote.cluster.com:9443"
208+
"<MY_REMOTE_CLUSTER_ADDRESS>:9443"
209209
],
210210
"connected" : true,
211211
"num_nodes_connected" : 1, <1>
@@ -239,20 +239,20 @@ PUT _cluster/settings
239239
"remote": {
240240
"cluster_one": {
241241
"seeds": [
242-
"my.remote.cluster.com:9443"
242+
"<MY_REMOTE_CLUSTER_ADDRESS>:9443"
243243
]
244244
},
245245
"cluster_two": {
246246
"mode": "sniff",
247247
"seeds": [
248-
"my.second.remote.cluster.com:9443"
248+
"<MY_SECOND_REMOTE_CLUSTER_ADDRESS>:9443"
249249
],
250250
"transport.compress": true,
251251
"skip_unavailable": true
252252
},
253253
"cluster_three": {
254254
"mode": "proxy",
255-
"proxy_address": "my.third.remote.cluster.com:9443"
255+
"proxy_address": "<MY_THIRD_REMOTE_CLUSTER_ADDRESS>:9443"
256256
}
257257
}
258258
}
@@ -322,15 +322,15 @@ In the following example, `cluster_one`, `cluster_two`, and `cluster_three` are
322322
cluster:
323323
remote:
324324
cluster_one:
325-
seeds: my.remote.cluster.com:9443
325+
seeds: <MY_REMOTE_CLUSTER_ADDRESS>:9443
326326
cluster_two:
327327
mode: sniff
328-
seeds: my.second.remote.cluster.com:9443
328+
seeds: <MY_SECOND_REMOTE_CLUSTER_ADDRESS>:9443
329329
transport.compress: true <1>
330330
skip_unavailable: true <2>
331331
cluster_three:
332332
mode: proxy
333-
proxy_address: my.third.remote.cluster.com:9443 <3>
333+
proxy_address: <MY_THIRD_REMOTE_CLUSTER_ADDRESS>:9443 <3>
334334
```
335335

336336
1. Compression is explicitly enabled for requests to `cluster_two`.

‎deploy-manage/remote-clusters/remote-clusters-cert.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ PUT /_cluster/settings
8686
"remote" : {
8787
"cluster_one" : { <1>
8888
"seeds" : [
89-
"my.remote.cluster.com:9300" <2>
89+
"<MY_REMOTE_CLUSTER_ADDRESS>:9300" <2>
9090
]
9191
}
9292
}
@@ -111,7 +111,7 @@ The API response indicates that the local cluster is connected to the remote clu
111111
{
112112
"cluster_one" : {
113113
"seeds" : [
114-
"my.remote.cluster.com:9300"
114+
"<MY_REMOTE_CLUSTER_ADDRESS>:9300"
115115
],
116116
"connected" : true,
117117
"num_nodes_connected" : 1, <1>
@@ -143,20 +143,20 @@ PUT _cluster/settings
143143
"remote": {
144144
"cluster_one": {
145145
"seeds": [
146-
"my.remote.cluster.com:9300"
146+
"<MY_REMOTE_CLUSTER_ADDRESS>:9300"
147147
]
148148
},
149149
"cluster_two": {
150150
"mode": "sniff",
151151
"seeds": [
152-
"my.second.remote.cluster.com:9300"
152+
"<MY_SECOND_REMOTE_CLUSTER_ADDRESS>:9300"
153153
],
154154
"transport.compress": true,
155155
"skip_unavailable": true
156156
},
157157
"cluster_three": {
158158
"mode": "proxy",
159-
"proxy_address": "my.third.remote.cluster.com:9302"
159+
"proxy_address": "<MY_THIRD_REMOTE_CLUSTER_ADDRESS>:9300"
160160
}
161161
}
162162
}
@@ -226,15 +226,15 @@ In the following example, `cluster_one`, `cluster_two`, and `cluster_three` are
226226
cluster:
227227
remote:
228228
cluster_one:
229-
seeds: my.remote.cluster.com:9300
229+
seeds: <MY_REMOTE_CLUSTER_ADDRESS>:9300
230230
cluster_two:
231231
mode: sniff
232-
seeds: my.second.remote.cluster.com:9300
232+
seeds: <MY_SECOND_REMOTE_CLUSTER_ADDRESS>:9300
233233
transport.compress: true <1>
234234
skip_unavailable: true <2>
235235
cluster_three:
236236
mode: proxy
237-
proxy_address: my.third.remote.cluster.com:9302 <3>
237+
proxy_address: <MY_THIRD_REMOTE_CLUSTER_ADDRESS>:9300 <3>
238238
```
239239
240240
1. Compression is explicitly enabled for requests to `cluster_two`.

‎deploy-manage/remote-clusters/remote-clusters-migrate.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ On the remote cluster:
6969
3. Generate a certificate and private key pair for the nodes in the remote cluster:
7070

7171
```sh
72-
./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=192.0.2.1
72+
./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=<CLUSTER_FQDN> --ip=192.0.2.1
7373
```
7474

7575
* Replace `CA_PASSWORD` with the CA password from the previous step.
@@ -169,7 +169,7 @@ On the local cluster:
169169
"remote" : {
170170
"my_remote" : { <1>
171171
"mode": "proxy",
172-
"proxy_address": "my.remote.cluster.com:9443" <2>
172+
"proxy_address": "<MY_REMOTE_CLUSTER_ADDRESS>:9443" <2>
173173
}
174174
}
175175
}
@@ -198,7 +198,7 @@ On the local cluster:
198198
"my_remote": {
199199
"connected": true, <1>
200200
"mode": "proxy",
201-
"proxy_address": "my.remote.cluster.com:9443",
201+
"proxy_address": "<MY_REMOTE_CLUSTER_ADDRESS>:9443",
202202
"server_name": "",
203203
"num_proxy_sockets_connected": 0,
204204
"max_proxy_socket_connections": 18,

0 commit comments

Comments
 (0)