Reintroduce Amazon web services module

[gonzaarancibia]

Description

Reintroduce a functional Amazon web services module adapting the visualizations to the available fields in Wazuh 5.0.0

Issues Resolved

#8055

Evidence

Screenshot

Test

• Verify that the aws section render correctly

Check List

• All tests pass
  • yarn test:jest
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[rodrigofez]

🟢 LGTM

Test	Chrome	Firefox	Safari
Verify that the aws section render correctly	🟢	⚫	🟢

Chrome

Safari

[rodrigofez]

LGTM

It only looks like you need to run prettier in plugins/main/public/utils/applications.ts

[Ripdiegozz]

CR 🟢
Tests 🟢

[FernandoCastilla]

LGTM

[Ripdiegozz]

🔴 Tests

1. When sorting the aws.cloudtrail_event_source field in the events table, it throws the following error.

2026-02-11.10-47-12.mp4

[Desvelao]

Test

🔴 Tests

1. When sorting the aws.cloudtrail_event_source field in the events table, it throws the following error.

2026-02-11.10-47-12.mp4

Sorting works for me, maybe this could be fixed in a recent version of indexer or you need to update the resource files of indexer.

[Desvelao]

LGTM!

[Desvelao]

I just replicated the commented problem by @Ripdiegozz with other table columns:

[github-actions]

Wazuh Check Updates plugin code coverage (Jest) test	%	values
Statements	78.72%	( 185 / 235 )
Branches	62.72%	( 69 / 110 )
Functions	61.7%	( 29 / 47 )
Lines	78.72%	( 185 / 235 )

[github-actions]

Wazuh Core plugin code coverage (Jest) test	%	values
Statements	29.82%	( 190 / 637 )
Branches	14.78%	( 42 / 284 )
Functions	19.65%	( 34 / 173 )
Lines	30%	( 189 / 630 )

[Desvelao]

I just replicated the commented problem by @Ripdiegozz with other table columns:

I just started a new environment and this seems to work again the first times I tried.

Yesterday we saw if changing the order of the columns in the sort, the problem could not appear or filtering by the document where the aws.cloudtrail_event_source field exist.

I think we could continue with the revision and merging the PR due to the error is not consistent, this could be reviewed in a future issue if this happens again.

EDIT: after a time with the environment, I experienced the problem.

Response of the request

``` { "error": { "root_cause": [], "type": "search_phase_execution_exception", "reason": "", "phase": "fetch", "grouped": true, "failed_shards": [], "caused_by": { "type": "unsupported_operation_exception", "reason": null } } } ```

The error happens on Discover app if using the Time and the aws.cloudtrail_event_source field as sorting order.

[github-actions]

Main plugin code coverage (Jest) test	%	values
Statements	20.42%	( 5496 / 26914 )
Branches	15.65%	( 2597 / 16590 )
Functions	17.51%	( 1174 / 6704 )
Lines	20.66%	( 5347 / 25878 )

We will not block the pull request due to the error found related to sorting, this seems that happens sometimes.