v1.6.2

What's Changed

⚠️ This is a patch for V1.6.1. If you are upgrading from a previous version of data.all, please have a look at the "Manual actions required" section. Fresh deployments are unaffected.

• Add missing KMS keys for canaries by @dlpzx in #619
• Allow restricted nacls backend VPC by @noah-paige in #626
• Fix cloudfront stack in case custom domain is given by @dbalintx in #607
• resolve unnecessary dependency in git_release role by @dlpzx in #623
• get prefix list ids for dbmigration for infra region by @dlpzx in #624
• Handle External ID SSM v1.6.1> by @noah-paige in #630

Upgrading from <v1.6.0 to v1.6.2

The externalID used to secure the pivotRole(s) in linked environments will be moved from AWS Secrets Manager to AWS Systems Manger Parameter Store as part of this upgrade.

⚠️ NOTE: If you have deployed data.all with enable_pivot_role_auto_create set to true in your cdk.json then you will not have to perform the manual steps listed below and can simply upgrade to v1.6.2. If not please continue with the manual steps below:

In order to retain the same externalID and not have to update the pivotRole(s) of each linked environment, follow the below steps:

1. In your data.all deployment account, Navigate to AWS Secrets Manager and retrieve the secret value of the external ID (named dataall-externalId-{envname}) --> keep this value somewhere for later reference
   

2. Upgrade code from existing version to v1.6.2 and commit latest code changes to deploy via CodePipeline

3. Once the CodePipeline execution is complete, Navigate to SSM Parameter Store in Deployment Account and find externalID Parameter (named /dataall/{envname}/pivotRole/externalId) --> edit the existing value with the one retained from Step 1
   

Full Changelog: v1.6.1...v1.6.2