What might account for this?
(Choose two.)
The new minor version has not yet been designated as preferred and requires a manual upgrade.
Configuring automatic upgrades using the AWS CLI is not supported. This must be enabled expressly using the AWS Management Console.
Applying minor version upgrades requires sufficient free space.
The AWS CLI command did not include an apply-immediately parameter.
Aurora has detected a breaking change in the new minor version and has automatically rejected the upgrade.
Explanations:
A new minor version must be designated as preferred before it can be applied. If it hasn’t been set as preferred, the update won’t occur automatically.
The AWS CLI supports enabling automatic minor version upgrades, so this is not the reason the update didn’t happen.
Sufficient free space is not required to apply minor version upgrades in Aurora. This is typically not an issue for minor version upgrades.
Without theapply-immediatelyparameter, changes won’t be applied right away, so the update will only happen during the next maintenance window.
Aurora would not automatically reject the upgrade due to a breaking change unless explicitly configured to do so. Minor version updates generally don’t introduce breaking changes.
I infer that the answer is:
The new minor version has not yet been designated as preferred and requires a manual upgrade.
I assess that the answer is:
The new minor version has not yet been designated as preferred and requires a manual upgrade.