[DOCS-16103] [Server]Add configurable retry count in AWS IAM code Created: 09/May/23  Updated: 13/Nov/23  Resolved: 01/Aug/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 5.0.18, 4.4.22, 7.0.0-rc1, 6.0.7, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Corry Root
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-76699 Add configurable retry count in AWS I... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-16288 [Server] Backport DOCS-16103 to v6.3 Backport Sub-Task Closed Corry Root  
DOCS-16289 [Server] Backport DOCS-16103 to v6.0 Backport Sub-Task Closed Corry Root  
DOCS-16290 [Server] Backport DOCS-16103 to v5.0 Backport Sub-Task Closed Corry Root  
DOCS-16291 [Server] Backport DOCS-16103 to v4.4 Backport Sub-Task Closed Corry Root  
Participants:
Days since reply: 39 weeks ago
Story Points: 2

 Description   
Original Downstream Change Summary

setParameter awsSTSRetryCount now retries for all errors, not just HTTP 5xx errors.

Description of Linked Ticket

Currently, the AWS STS code will fail without retrying on connection failures. Now connection failures can be difficult to differentiate from misconfiguration in some cases but we should add a configurable retry count. This is in addition to SERVER-62053 which only retries if a connection can be made to the server and the server returns HTTP 500.



 Comments   
Comment by Ashley Brown [ 10/May/23 ]

Please backport through v4.4.

Generated at Thu Feb 08 08:14:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.