1 個回答
- 最新
- 最多得票
- 最多評論
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.
已回答 3 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前