-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
Compute AAD to encrypty/decrypt SO only if needed #75818
Compute AAD to encrypty/decrypt SO only if needed #75818
Conversation
Pinging @elastic/ingest-management (Team:Ingest Management) |
022b17f
to
e189d1c
Compare
e189d1c
to
1674914
Compare
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This approach seems reasonable to me, I ultimately defer my approval to @elastic/kibana-security as they're more familiar with this code than I.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary
While working on optimizing Fleet performance I noticed we compute the AAD for encrypting saved object even if we do not encrypt any attribute.
In Fleet this mean a lot of AAD get can computed for nothing, for example we are doing a periodical call to do a bulk update on every agent to set a timestamp
last_checkin
a field that is not encrypted.I think we can avoid that call when not needed.
TODO
This change seems to have a limited impact on fleet performance, but it still thinks looks like a small improvment