Merge branch 'main' into gm/updatesnowflakeimportantchanges

gerardma77 · web-flow · commit 96255e7ba3fb · 2025-08-25T14:26:44.000+02:00
diff --git a/content/terraform-docs-agents/v1.15.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.15.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -43,8 +43,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.16.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.16.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -42,8 +42,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.17.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.17.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.18.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.18.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.19.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.19.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.20.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.20.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.21.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.21.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.22.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.22.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -40,8 +40,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-docs-agents/v1.23.x/docs/cloud-docs/agents/request-forwarding.mdx b/content/terraform-docs-agents/v1.23.x/docs/cloud-docs/agents/request-forwarding.mdx
@@ -42,8 +42,12 @@ flag, or set the environment variable `TFC_AGENT_REQUEST_FORWARDING=true`. When
 the agent starts, you will see the following log messages:
 
 ```
-[INFO]  core: Request forwarding is enabled
-[INFO]  grpc_connector: Connected to broker, awaiting requests
+[INFO]  core: Broker connection is enabled
+[INFO]  grpc_connector: Connecting to broker: host=agents.terraform.io:7146
+[INFO]  grpc_connector: agent grpc server serving...
+[INFO]  grpc_connector: Keep alive is enabled: host=agents.terraform.io:7146
+[DEBUG] rpc_server: Handling broker authorization challenge
+[DEBUG] rpc_server: status-event: successful connection
 ```
 
 These log messages indicate that the agent has successfully connected to HCP Terraform
diff --git a/content/terraform-enterprise/v202506-1/docs/enterprise/deploy/configuration/network.mdx b/content/terraform-enterprise/v202506-1/docs/enterprise/deploy/configuration/network.mdx
@@ -110,6 +110,8 @@ To run Terraform Enterprise in an airgapped environment, you must also whitelist
 - `s3-r-w.us-west-2.amazonaws.com`
 - `s3-r-w.eu-central-1.amazonaws.com`
 - `s3-r-w.eu-west-1.amazonaws.com`
+- `prod-us-east-1-starport-layer-bucket.s3.dualstack.us-east-1.amazonaws.com`
+- `prod-us-west-1-starport-layer-bucket.s3.dualstack.us-west-1.amazonaws.com`
 
 Note that the domains are owned by Amazon, not HashiCorp, and may change at any time. Refer to this documentation to verify the domains each time you run the deployment configuration.  
 
diff --git a/content/vault/global/partials/important-changes/summary-tables/1_19.mdx b/content/vault/global/partials/important-changes/summary-tables/1_19.mdx
@@ -29,6 +29,7 @@ Introduced | Recommendations | Edition    | Change
 Found  | Fixed  | Workaround | Edition    | Issue
 ------ |------- | ---------- | ---------- | -----
 1.19.0 | No     | **Yes**    | Enterprise | [Duplicate unseal/seal wrap HSM keys](/vault/docs/v1.19.x/updates/important-changes#hsm-keys)
+1.19.6 | No     | No.        | All.       | [AWS auto join fails on startup](/vault/docs/v1.20.x/updates/important-changes#aws-auto-join)
 1.19.0 | 1.19.3 | **Yes**    | All        | [Login/token renewal failures after group changes](/vault/docs/v1.19.x/updates/important-changes#group-writes)
 1.19.0 | 1.19.3 | Upgrade    | All        | [Unexpected DB static role rotations on upgrade](/vault/docs/v1.19.x/updates/important-changes#db-static-role-rotations)
 1.19.0 | 1.19.3 | Upgrade    | All        | [Unexpected LDAP static role rotations on upgrade](/vault/docs/v1.19.x/updates/important-changes#ldap-static-role-rotations)
diff --git a/content/vault/global/partials/important-changes/summary-tables/1_20.mdx b/content/vault/global/partials/important-changes/summary-tables/1_20.mdx
@@ -21,6 +21,7 @@ Introduced | Recommendations | Edition    | Change
 Found  | Fixed  | Workaround | Edition    | Issue
 ------ |--------| ---------- | ---------- | -----
 1.20.0 | No     | **Yes**    | Enterprise | [Duplicate unseal/seal wrap HSM keys](/vault/docs/v1.20.x/updates/important-changes#hsm-keys)
+1.20.0 | No     | No.        | All.       | [AWS auto join fails on startup](/vault/docs/v1.20.x/updates/important-changes#aws-auto-join)
 1.20.0 | 1.20.1 | **Yes**    | Enterprise | [Secondary cluster reload overwrites development cluster setting](/vault/docs/v1.20.x/updates/important-changes#development-cluster-reload)
 1.20.0 | 1.20.1 | **Yes**    | All        | [UI login fails for auth mounts with underscores and unauthenticated listing](/vault/docs/v1.20.x/updates/important-changes#ui-login-underscore)
 1.20.0 | 1.20.1 | **Yes**    | All        | [GUI navigation error for KV v2 secret paths containing underscores](/vault/docs/v1.20.x/updates/important-changes#ui-kvv2-underscore-secrets)
diff --git a/content/vault/v1.19.x/content/docs/updates/important-changes.mdx b/content/vault/v1.19.x/content/docs/updates/important-changes.mdx
@@ -309,6 +309,19 @@ Explicitly set the default endpoint and region when configuring sts:
 
 ## Known issues
 
+### AWS auto join fails on startup ((#aws-auto-join)).
+
+| Change      | Status | Affected version               | Fixed version
+| ----------- | ------ | ------------------------------ | --------------------
+| Known issue | Open   | 1.19.5 to 1.19.8, 1.20.x       | None
+
+After unsealing Vault and attempting to autojoin nodes to the cluster, if Dual Stack endpoints are not enabled in that region.
+
+#### Workaround
+
+Auto join will not work with this issue existing. If you need to rely on auto join for your nodes, do not upgrade. 
+
+
 ### Duplicate unseal/seal wrap HSM keys ((#hsm-keys)) <EnterpriseAlert inline="true" />
 
 | Change      | Status | Affected version               | Fixed version
diff --git a/content/vault/v1.20.x/content/docs/updates/important-changes.mdx b/content/vault/v1.20.x/content/docs/updates/important-changes.mdx
@@ -187,6 +187,18 @@ $ vault write auth/kubernetes/role/demo      \
 
 ## Known issues
 
+### AWS auto join fails on startup ((#aws-auto-join)).
+
+| Change      | Status | Affected version               | Fixed version
+| ----------- | ------ | ------------------------------ | --------------------
+| Known issue | Open   | 1.19.5 to 1.19.8, 1.20.x       | None
+
+After unsealing Vault and attempting to autojoin nodes to the cluster, if Dual Stack endpoints are not enabled in that region.
+
+#### Workaround
+
+Auto join will not work with this issue existing. If you need to rely on auto join for your nodes, do not upgrade. 
+
 ### Duplicate unseal/seal wrap HSM keys ((#hsm-keys)) <EnterpriseAlert inline="true" />
 
 | Change      | Status | Affected version                       | Fixed version
diff --git a/content/vault/v1.20.x/content/partials/global-settings/both/client-cert.mdx b/content/vault/v1.20.x/content/partials/global-settings/both/client-cert.mdx
@@ -4,7 +4,7 @@
 
 Path to a PEM-encoded CA certificate file on the local disk. Used for TLS
 communication with the server. **The specified certificate must match to the
-private key specified with `-client-cert`**.
+private key specified with `-client-key`**.
 
 **Examples**:
 
