Incorporates Brandon's review

Author: benironside

release-notes/elastic-cloud-serverless/known-issues.md

@@ -17,14 +17,14 @@ Known issues are significant defects or limitations that may impact your impleme
 ## Active
 
 :::{dropdown} Deploying integrations using AWS CloudFormation doesn't work
-On November 10, 2025 it was discovered that new deployments of integrations such as Asset Discovery and Cloud Security Posture Management that collect data from cloud service providers do not work when deployed to AWS using the AWS CloudFormation deployment option. The problem results from a malformed CloudFormation parameter: `ElasticAgentVersion`. The default value for `ElasticAgentVersion` has a `space` instead of a `+`. This produces an invalid agent version value.
+New deployments of integrations that collect data from cloud service providers, such as Asset Discovery and Cloud Security Posture Management, do not work when deployed to AWS using agent-based deployment and the AWS CloudFormation deployment option. The problem results from a malformed CloudFormation parameter: `ElasticAgentVersion`. The default value for `ElasticAgentVersion` has a space instead of a `+`. This produces an invalid agent version value.
 
-For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).
+For more information, check [#14627](https://github.com/elastic/kibana/pull/242365).
 
 
 **Workaround**<br> 
 
-To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` parameter with a `+`.
+To work around this issue, update the default CloudFormation template by replacing the space in the `ElasticAgentVersion` parameter with a `+`.
 
 :::
 

release-notes/elastic-security/known-issues.md

@@ -20,14 +20,14 @@ Known issues are significant defects or limitations that may impact your impleme
 Applies to: 9.2.0 and 9.2.1
 
 **Impact**<br> 
-New deployments of integrations such as Asset Discovery and Cloud Security Posture Management that collect data from cloud service providers do not work when deployed to AWS using the AWS CloudFormation deployment option. The problem results from a malformed CloudFormation parameter: `ElasticAgentVersion`. The default value for `ElasticAgentVersion` has a `space` instead of a `+`. This produces an invalid agent version value.
+New deployments of integrations that collect data from cloud service providers, such as Asset Discovery and Cloud Security Posture Management, do not work when deployed to AWS using agent-based deployment and the AWS CloudFormation deployment option. The problem results from a malformed CloudFormation parameter: `ElasticAgentVersion`. The default value for `ElasticAgentVersion` has a space instead of a `+`. This produces an invalid agent version value.
 
-For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).
+For more information, check [#14627](https://github.com/elastic/kibana/pull/242365).
 
 
 **Workaround**<br> 
 
-To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` parameter with a `+`.
+To work around this issue, update the default CloudFormation template by replacing the space in the `ElasticAgentVersion` parameter with a `+`.
 
 **Resolved**<br>