Skip to content
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

Merged
merged 3 commits into from
Apr 24, 2024

Conversation

Neurostep
Copy link
Contributor

@Neurostep Neurostep commented Apr 22, 2024

Description

In this PR we introduce a new AWS instrumentation function InstrumentAWSClient. It uses aws-sdk-go-v2. The usage of the InstrumentAWSSession 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 authentication

Screenshot 2024-04-23 at 18 18 16

Checklist

  • Prefixed the PR title with the JIRA ticket code
  • Performed simple, atomic commits with good commit messages
  • Verified that the commit history is linear and commits are squashed as necessary
  • Thoroughly tested the changes in development and/or staging
  • Updated the README.md as necessary

Related links

@Neurostep Neurostep requested a review from a team as a code owner April 22, 2024 15:13
@Neurostep Neurostep requested review from fotos and laynax April 22, 2024 15:13
@Neurostep Neurostep force-pushed the maksimt/SERF-2971/aws-sdk-go-v2 branch 2 times, most recently from bec91fe to 74bf117 Compare April 22, 2024 15:25
fotos
fotos previously approved these changes Apr 22, 2024
Copy link
Contributor

@fotos fotos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 LGTM 🚀

README.md Outdated Show resolved Hide resolved
laynax
laynax previously approved these changes Apr 23, 2024
Copy link
Contributor

@laynax laynax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Neurostep Neurostep dismissed stale reviews from laynax and fotos via 4ae9688 April 23, 2024 12:33
@Neurostep Neurostep force-pushed the maksimt/SERF-2971/aws-sdk-go-v2 branch from 74bf117 to 4ae9688 Compare April 23, 2024 12:33
@Neurostep Neurostep requested review from fotos and laynax April 23, 2024 12:33
@Neurostep Neurostep force-pushed the maksimt/SERF-2971/aws-sdk-go-v2 branch from 4ae9688 to 3dd4aba Compare April 23, 2024 12:34
@Neurostep Neurostep force-pushed the maksimt/SERF-2971/aws-sdk-go-v2 branch from 3dd4aba to 7b1f61b Compare April 23, 2024 12:45
fotos
fotos previously approved these changes Apr 23, 2024
Copy link
Contributor

@fotos fotos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 LGTM 🚀

laynax
laynax previously approved these changes Apr 23, 2024
@Neurostep Neurostep dismissed stale reviews from laynax and fotos via 4d2597a April 23, 2024 15:54
@Neurostep Neurostep force-pushed the maksimt/SERF-2971/aws-sdk-go-v2 branch from 7b1f61b to 4d2597a Compare April 23, 2024 15:54
@Neurostep Neurostep requested review from fotos and laynax April 23, 2024 16:18
Copy link
Contributor

@fotos fotos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 LGTM 🚀

@Neurostep Neurostep merged commit cdb60e5 into main Apr 24, 2024
7 checks passed
@Neurostep Neurostep deleted the maksimt/SERF-2971/aws-sdk-go-v2 branch April 24, 2024 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants