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

[aws-cpp-sdk-core]: increase STS reliability and retries #2611

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

grrtrr
Copy link
Contributor

@grrtrr grrtrr commented Aug 2, 2023

This fixes issues we have repeatedly experienced when using STS for authentication in a large Kubernetes cluster, with heavy load on STS:

  1. The default connect timeout of 1s is too low. It happens that connections slow down. One case is very high load on kube DNS. A value of 30 seconds has proven to be robust.
  2. The retry parameters are too short, authentication would frequently fail whenever STS was under higher load. The retry settings have worked in production for about 2 years.

Check all that applies:

  • Did a review by yourself.
  • Added proper tests to cover this PR. (If tests are not applicable, explain.)
    We have before/after experience. Without these settings, calls to STS would frequently time out whenever STS was under higher load.
    Within the close to 2 years after making this change, we no longer experienced authentication failures when STS was under load.
  • Checked if this PR is a breaking (APIs have been changed) change.
  • Checked if this PR will not introduce cross-platform inconsistent behavior.
  • [X]] Checked if this PR would require a ReadMe/Wiki update.

Check which platforms you have built SDK on to verify the correctness of this PR.

  • Linux
  • Windows
  • Android
  • MacOS
  • IOS
  • Other Platforms

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This fixes issues we have repeatedly experienced when using STS for authentication
in a large Kubernetes cluster, with heavy load on STS:
1. The default connect timeout of 1s is too low. It happens that
   connections slow down. One case is very high load on kube DNS.
   A value of 30 seconds has proven to be robust.
2. The retry parameters are too short, authentication would frequently
   fail whenever STS was under higher load. The retry settings have
   worked in production for about 2 years.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant