fix: resolved issue with fetching agent key from ssm due to missing aws sdk #1402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aryamohanan
force-pushed
the
aws-sdk-ssm
branch
2 times, most recently
from
eca638d to
88ba7d7
Compare
aryamohanan
commented
Oct 24, 2024
aryamohanan
force-pushed
the
aws-sdk-ssm
branch
from
f6d8d9a to
c40e07c
Compare
aryamohanan
force-pushed
the
aws-sdk-ssm
branch
from
c40e07c to
9069d37
Compare
aryamohanan
force-pushed
the
aws-sdk-ssm
branch
from
9069d37 to
eebcd11
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref INSTA-17430
Node.js 18.x is using AWS SDK v3. In our code, we are using AWS SDK v2. The problem is that, NodeJS 18.x runtime does not come with version 2 of the AWS SDK automatically packaged and ready to use. This is the reason we are getting the error for not being able to find aws-sdk.