You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
CDF creates a Neptune database using a specific engine version. Upgrading the Neptune engine version is a one-way process. In case of failures, roll back requires restoring from a backup as a new cluster. Also If attempting to upgrade the Neptune engine version using a aws recommended Blue/Green solution, the newly created green Neptune cluster (which will soon be promoted as a production cluster after testing) cannot be imported into the existing CloudFormation stack (cfn-neptune.yaml).
Could someone please share insights on this situation or experiences with performing a Neptune upgrade?
Current behavior:
Upgrading neptune cluster to a specific version directly.
Expected behavior:
Upgrade the Neptune database using a Blue/Green strategy to test and promote the updated cluster.
The text was updated successfully, but these errors were encountered:
Aws Connected Device Framework Affected Module(s):
I'm submitting a feature request
Description:
CDF creates a Neptune database using a specific engine version. Upgrading the Neptune engine version is a one-way process. In case of failures, roll back requires restoring from a backup as a new cluster. Also If attempting to upgrade the Neptune engine version using a aws recommended Blue/Green solution, the newly created green Neptune cluster (which will soon be promoted as a production cluster after testing) cannot be imported into the existing CloudFormation stack (cfn-neptune.yaml).
Could someone please share insights on this situation or experiences with performing a Neptune upgrade?
Current behavior:
Upgrading neptune cluster to a specific version directly.
Expected behavior:
Upgrade the Neptune database using a Blue/Green strategy to test and promote the updated cluster.
The text was updated successfully, but these errors were encountered: