[SFN] Fix optimised integrations clients leading to timeouts and retries #9732
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.
Motivation
Invocations of service integrations in SFN v2 currently trigger the default behaviour of boto for connection and read timeouts, as well as the retry strategy. This could potentially disrupt the State Machine's behaviour related to timeout and retry declarations.
Closes #9731
Changes
This pull request deactivates the mentioned boto behaviour to guarantee that timeout issues are passed upstream to the interpreter as intended.