Skip to content

AWS CloudFormation integration deployment method — known issue for 9.2.x and serverless #3947

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 17, 2025
Merged

AWS CloudFormation integration deployment method — known issue for 9.2.x and serverless #3947

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
689fe98
Adds known issues for 9.2.x and serverless
benironside Nov 14, 2025
59c4591
typo fix
benironside Nov 14, 2025
9fcf5da
Incorporates Brandon's review
benironside Nov 17, 2025
8eb351f
Merge branch 'main' into 3946-known-issue
benironside Nov 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions release-notes/elastic-cloud-serverless/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,17 @@ 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.

For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).


**Workaround**<br>

To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` parameter with a `+`.

:::


::::{dropdown} Alerts aren't generated for rules with alert flapping off and an alert delay higher than 1
Expand Down
19 changes: 19 additions & 0 deletions release-notes/elastic-security/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,25 @@ Known issues are significant defects or limitations that may impact your impleme

% :::

:::{dropdown} Deploying integrations using AWS CloudFormation doesn't work
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.

For more information, check [#14627](https://github.com/elastic/security-team/issues/14627).


**Workaround**<br>

To work around this issue, update the default CloudFormation template by replacing the `space` in the `ElasticAgentVersion` parameter with a `+`.

**Resolved**<br>

Resolved in {{stack}} 9.2.2.

:::

:::{dropdown} Entity store transform is unavailable

Applies to: 9.2.0
Expand Down
Loading