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
In #1155 we settled on a temporary solution of using a FetchToBuffer call inside of the platform Init function for AWS to handle waiting for networking to come up before attempting to fetch the region hint from the metadata service. See this comment for more information about why the decision was chosen.
Some alternative potential solutions:
Adding a Retryer to the aws.Config so the AWS API handles retrying (by default it seems that there would only ever be a single retry)
Fetching the region hint from an HTTP URL instead of the AWS API
Putting the API call inside a retry loop (we need to test out the different failure states to make sure that we're only retrying in the case of network/platform errors)
We also need to note the fact that if we do indeed move away from using a FetchToBuffer call we'll need to handle checking the Offline state inside of the Init function.
The text was updated successfully, but these errors were encountered:
Feature Request
In #1155 we settled on a temporary solution of using a
FetchToBuffer
call inside of the platformInit
function for AWS to handle waiting for networking to come up before attempting to fetch the region hint from the metadata service. See this comment for more information about why the decision was chosen.Some alternative potential solutions:
Retryer
to theaws.Config
so the AWS API handles retrying (by default it seems that there would only ever be a single retry)We also need to note the fact that if we do indeed move away from using a
FetchToBuffer
call we'll need to handle checking theOffline
state inside of theInit
function.The text was updated successfully, but these errors were encountered: