-
Notifications
You must be signed in to change notification settings - Fork 0
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
[SERF-2971] Instrument AWS clients using aws-sdk-go
version 2
#105
Conversation
bec91fe
to
74bf117
Compare
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 🚀
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
74bf117
to
4ae9688
Compare
4ae9688
to
3dd4aba
Compare
3dd4aba
to
7b1f61b
Compare
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 🚀
7b1f61b
to
4d2597a
Compare
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 🚀
Description
In this PR we introduce a new AWS instrumentation function
InstrumentAWSClient
. It uses aws-sdk-go-v2. The usage of theInstrumentAWSSession
marked is deprecated.Additionally, we updated the
PubSub
configuration to use AWS Config instead of the AWS session to support the migration to AWS SDK Go version 2.In this PR we keep AWS version 1 SDK to have a smooth transition to a AWS SDK Go version 2.
The usage of the AWS SDK Go version 1 will be cleaned up when we migrate all services.
Testing considerations
Tested these changes in
user-notifications-ingestion
to confirm the AWS MSK authenticationChecklist
development
and/orstaging
README.md
as necessaryRelated links