1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
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.
respondido hace 3 años
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 2 años