[
https://issues.apache.org/jira/browse/CAMEL-25980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-25980 started by shashank.
----------------------------------------
> camel-aws-secrets-manager - the CloudTrail refresh task misses a secret
> update that CloudTrail makes visible after a newer event was already seen
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25980
> URL: https://issues.apache.org/jira/browse/CAMEL-25980
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
> Reporter: shashank
> Assignee: shashank
> Priority: Minor
>
> {{CloudTrailReloadTriggerTask}} starts each check at the newest event time it
> has seen ({{lastTime}}). CloudTrail makes events visible with a delay that
> differs per event (typically minutes), so an {{UpdateSecret}} or
> {{PutSecretValue}} event with an earlier time can become visible after a
> check already saw a newer event. The next lookup starts at the newer time, so
> the late event is never read and the secret's change does not trigger a
> reload (until another update of that secret).
> CAMEL-25727 fixed the same problem in the aws-cloudtrail consumer with an
> extra lookup over a look-back window and de-duplication by event id. The
> refresh task can do the same: look back over a fixed window (for example 15
> minutes) from the newest time seen, and skip the event ids it already handled
> in that window.
> h3. Proposed fix
> Bring the late-event lookup of CAMEL-25727 over to
> {{CloudTrailReloadTriggerTask}}: an inclusive lookup from {{lastTime -
> lookBack}}, de-duplicated by event id (bounded to the window), at the cost of
> reading the window again on each check (state the extra requests per check
> against the {{LookupEvents}} limit of 2 requests per second).
> Affected: main.
> _Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
