Enable IPv6 support for SSM Client #4623
Merged
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.
Summary
Enable SSM client to automatically use dualstack endpoints when running on IPv6-only instances.
Ref PR: #4580
Implementation details
i. Modified
NewSSMClient
to acceptIPCompatibility
parameterii. Set
useDualStackEndpoint
based on IPv6 compatibility statusTaskResources
such asFSxWindowsFileServer
,SSMSecret
, andCredentialSpecs
.ipCompatibility
field to each task resource.New*
constructors to accept an additionalipCompatibility
parameter.New*
is invoked when there's a new incoming task that requires task resources.Initialize()
is invoked when Agent restarts and reinitialize task resources. Updated such that theipCompatibility
field is populated.Config.InstanceIPCompatibility
is the source of value. Updated call chains so that theipCompatibility
is passed down correctlyTesting
Setups done:
Executed functional test suite on dualstack subnet. Verified all tests passed and pre-prod endpoint usage through docker container logs.
New tests cover the changes: no
Description for the changelog
Enhancement: SSM Client resolves to dualstack endpoint on IPV6-only instances
Additional Information
Does this PR include breaking model changes? If so, Have you added transformation functions?
Does this PR include the addition of new environment variables in the README?
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.