Repository navigation
[aws] Add processor tags to ingest pipelines - #19824
Conversation
550a1be to
0c07b52
Compare
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
💔 Build Failed
Failed CI StepsHistory |
|
👀 I have started reviewing the PR |
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
Vera Review BotFor the current commit state, I did not find any issues. 🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills
|
Add `tag` fields to every processor in all AWS ingest pipelines using `elastic-package modify --modifiers pipeline-tag`. Also update `on_failure` error messages to include `_ingest.pipeline` per the SVR00009 linter rule. Both are requirements that will be enforced when the AWS package format_version is bumped to 3.6.0. Also fix two pre-existing duplicate processors exposed by the tagging: - cloudfront_logs/default.yml: duplicate x-edge-response-result-type rename - rds/default.yml: duplicate FreeStorageSpace rename Fixes cloudfront_logs/pipeline_process_ip.yml which was missing a pipeline-level on_failure block (SVR00008/SVR00009).
0c07b52 to
1541dd3
Compare
|
✅ All changelog entries have the correct PR link. |
|
👀 I have started reviewing the PR |
Vera Review BotFor the current commit state, I did not find any issues. 🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills
|
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
guardduty |
1893.94 | 1408.45 | -485.49 (-25.63%) | 💔 |
inspector |
1308.9 | 1026.69 | -282.21 (-21.56%) | 💔 |
securityhub_findings |
2087.68 | 1709.4 | -378.28 (-18.12%) | 💔 |
securityhub_findings_full_posture |
2178.65 | 1795.33 | -383.32 (-17.59%) | 💔 |
securityhub_insights |
1709.4 | 1443 | -266.4 (-15.58%) | 💔 |
cloudwatch_logs |
200000 | 142857.14 | -57142.86 (-28.57%) | 💔 |
To see the full report comment with /test benchmark fullreport
💚 Build Succeeded
History
|
| field: json.resource.containerDetails.name | ||
| target_field: aws.guardduty.resource.container_details.name | ||
| ignore_missing: true | ||
| - convert: | ||
| tag: convert_json_resource_containerDetails_securityContext_privileged_to_aws_guardduty_resource_container_details_security_context_privileged_8d0f193a |
There was a problem hiding this comment.
These auto-generated tags can be lengthy.
| target_field: aws.apigateway.connection_id | ||
| ignore_missing: true | ||
| - rename: | ||
| tag: rename_aws_apigateway_eventType_to_aws_apigateway_event_type_2a463e2f |
There was a problem hiding this comment.
@andrewkroh : Do these numbers 2a463e2f have any relevance here ?
There was a problem hiding this comment.
Based on the source code for the elastic-package modify --modifiers pipeline-tag command, it looks like its an additional hash of the processor config to help make the ID distinct or unique.
|
Tick the box to add this pull request to the merge queue (same as
|
Add tag fields to every processor in all aws_securityhub ingest pipelines using elastic-package modify --modifiers pipeline-tag, and update pipeline-level on_failure error messages to include _ingest.pipeline per the SVR00009 linter rule. Both are requirements that will be enforced when the package format_version is bumped to 3.6.x for Identity Federation support. Also fix a pre-existing copy-paste bug surfaced by the tagging: the pipeline_object_evidence pipeline processor in default.yml was tagged pipeline_object_device, duplicating the device processor's tag. Landing these changes separately keeps the upcoming format_version bump PR small, following the precedent of elastic#19824 for the aws package. No functional effect at format_version 3.5.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Proposed commit message
Created with Claude Code using Sonnet 4.6.
Background
This PR pre-lands the ingest pipeline changes required by the
elastic-packagelinter whenformat_versionis bumped to 3.6.0:tagfieldon_failuremust setevent.kind: pipeline_erroron_failureerror message must include_ingest.pipelineBy landing these changes separately, the upcoming format_version bump PR
will be smaller and easier to review. These changes are also safe to
backport since they have no functional effect at format_version 3.4.0.
The changes were generated with:
followed by manual fixes for the on_failure message template updates
and two duplicate processor removals that were surfaced by the tagging.
Checklist
changelog.ymlfile.Related