View a markdown version of this page

Migrate the hub stack (optional) - Network Orchestration for AWS Transit Gateway

Migrate the hub stack (optional)

Follow the step-by-step instructions in this section to migrate the hub stack from earlier versions to the latest version.

Migrate from v1 to v3

Important

You cannot directly update solution v1 to latest due to breaking changes in latest, including UserPoolAddOns which is not supported under the Essential pricing tier.

Hub template

  1. Download the latest version of the hub template from the link of the network-orchestration-hub.template CloudFormation template.

  2. Make the following change in UserPool Attribute Name in the hub template by removing custom: from the attribute name. Cognito is adding custom to the attribute so we don’t need to put it in our configuration. For more information, see SchemaAttribute in the AWS CloudFormation User Guide.

    Edit the template to remove the custom: prefix from the Cognito User Pool attribute:

    # Change from: Name: custom:CognitoUserGr # To: Name: CognitoUserGr
  3. Save the changes to the hub template.

  4. Sign in to the Amazon Cognito console, select your user pool created by v1 hub, and navigate to Feature plan under settings. Select Plus plan instead of Essential plan.

  5. Follow the steps provided in Hub stack to update the hub stack using the modified hub template.

Spoke template

For spoke template, follow the steps provided in Spoke stack.

Migrate from v2 to v3

Hub template

  1. Download the latest version of the hub template from the link of the network-orchestration-hub.template CloudFormation template.

  2. Make the following change in UserPool Attribute Name in the hub template by removing custom: from the attribute name. Cognito is adding custom to the attribute so we don’t need to put it in our configuration.

    Edit the template to remove the custom: prefix from the Cognito User Pool attribute:

    # Change from: Name: custom:CognitoUserGr # To: Name: CognitoUserGr
  3. Save the changes to the hub template.

  4. Follow the steps provided in Hub stack to update the hub stack using the modified hub template.

Spoke template

For spoke template, follow the steps provided in Spoke stack.

Note

If you created peering attachments using solution versions before v3.0.0 and then upgraded to v3.0.0 or later, those attachments cannot be deleted by updating the tag value on the transit gateway. You will need to delete them manually.