Skip to content

Commit 689fe98

Browse files
committed
Adds known issues for 9.2.x and serverless
1 parent 555ffec commit 689fe98

File tree

2 files changed

+30
-0
lines changed

2 files changed

+30
-0
lines changed

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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,17 @@ Known issues are significant defects or limitations that may impact your impleme
1616

1717
## Active
1818

19+
:::{dropdown} Deploying integrations using AWS CloudFormation doesn't work
20+
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.
21+
22+
For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).
23+
24+
25+
**Workaround**<br>
26+
27+
To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` oarameter with a `+`.
28+
29+
:::
1930

2031

2132
::::{dropdown} Alerts aren't generated for rules with alert flapping off and an alert delay higher than 1

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

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,25 @@ Known issues are significant defects or limitations that may impact your impleme
1616

1717
% :::
1818

19+
:::{dropdown} Deploying integrations using AWS CloudFormation doesn't work
20+
Applies to: 9.2.0 and 9.2.1
21+
22+
**Impact**<br>
23+
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.
24+
25+
For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).
26+
27+
28+
**Workaround**<br>
29+
30+
To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` oarameter with a `+`.
31+
32+
**Resolved**<br>
33+
34+
Resolved in {{stack}} 9.2.2.
35+
36+
:::
37+
1938
:::{dropdown} Entity store transform is unavailable
2039

2140
Applies to: 9.2.0

0 commit comments

Comments
 (0)