-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: support dual stack requests for aws clients #52
Conversation
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.
there might be some unintended sbc state things in this pr, but otherwise looks good imo
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.
Great work sorry for taking so long to review. I left one minor comment. Otherwise we have been using the readme's in the services as a source of truth for valid attribute and secret fields in conversations recently. We should therefore add dual_stack
to those two readmes until we have a better option for documenting this.
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.
👍
1c9d6f1
to
8ab07c3
Compare
8ab07c3
to
97aae6e
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
This reverts commit 899c62c.
Summary
Dual stack access for ipv4/ipv6 is by default disabled in aws clients. This PR allows users to enable dual stack access using the attributes field. The new field
dual_stack
is a boolean type.Concerns
Updating the aws dependencies have caused the memory usage in boundary to spike. Before updating the aws dependencies, boundary was utilizing ~460MB while idling. With the updates, boundary is utilizing ~720MB while idling. I think this is concerning, but I'm not sure how to proceed.