1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Turns out since Graviton instances for Elasticache was just recently released (<2 months), there was limited capacity within the AZs that the clusters were running in. The API checks if there is capacity within each subnet/AZ included in the subnet group, and if at least one of the AZs doesn't have capacity it will not apply the modification or even show it as an available option.
répondu il y a 3 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans