* Credentials providers in async mode require clusters to be created so that they can use the async
* - For ContainerCredentialsProvider (including ECS and EKS), a cluster is created with the uri of
* configured. There may be many WebIdentityCredentialsProvider instances instances configured, each
* with their own region, or their own role ARN or role session name. The aws cluster manager will
* maintain only a single cluster per region, and notify all relevant WebIdentityCredentialsProvider
* - For IAMRolesAnywhere, this behaves similarly to WebIdentityCredentialsProvider, where there may
* be many instantiations of the credential provider for different roles, regions and profiles. The
* Create all queued clusters, if we were unable to create them in real time due to envoy cluster
absl::flat_hash_map<std::string, std::unique_ptr<CredentialsProviderCluster>> managed_clusters_;