You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/auth/auth.rst
+1-7Lines changed: 1 addition & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1059,20 +1059,14 @@ be used in lieu of manual caching.
1059
1059
1060
1060
If using manual caching, the "Expiration" field MUST be stored
1061
1061
and used to determine when to clear the cache. Credentials are considered
1062
-
valid if they are more than one minute away from expiring, to the reduce the
1062
+
valid if they are more than five minutes away from expiring, to the reduce the
1063
1063
chance of expiration before they are validated by the server.
1064
1064
1065
1065
If there are no current valid cached credentials, the driver MUST initiate a
1066
1066
credential request. To avoid adding a bottleneck that would override the
1067
1067
``maxConnecting`` setting, the driver MUST not place a lock on making a
1068
1068
request. The cache MUST be written atomically.
1069
1069
1070
-
Once valid credentials are received, the driver SHOULD schedule an update of
1071
-
the cache within five minutes of the expiration time, unless the driver does not have the ability to schedule background tasks. The background task MUST
1072
-
handle timeouts or errors and retry appropriately. The purpose of the
1073
-
background task is to limit the chance of needing to initiate multiple
1074
-
simultaneous requests.
1075
-
1076
1070
If AWS authentication fails for any reason, the cache MUST be cleared.
0 commit comments