Skip to content
This repository was archived by the owner on Aug 7, 2026. It is now read-only.
This repository was archived by the owner on Aug 7, 2026. It is now read-only.

Upgrade the Neptune cluster version using a Blue/Green solution. #219

Description

@dhinesh-karan

Aws Connected Device Framework Affected Module(s):

I'm submitting a feature request

  • [] bug report
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions