Update to v1.5.0 from 1.4.3 have significant issues.

[DonthineniSagar]

Describe the bug
We would like update LZA version to 1.5.0

To Reproduce
Update to LZA 1.5.0 from 1.4.3

Expected behavior
A complete update without issues
Please complete the following information about the solution:

• Version: [e.g. v1.4.3]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0021) - Video On Demand workflow with AWS Step Functions, MediaConvert, MediaPackage, S3, CloudFront and DynamoDB. Version v5.0.0". If the description does not contain the version information, you can look at the mappings section of the template:

Mappings:
  SourceCode:
    General:
      S3Bucket: "solutions"
      KeyPrefix: "video-on-demand-on-aws/v5.0.0"

• Region: ap-southeast-2
• Was the solution modified from the version published on this repository?N
• If the answer to the previous question was yes, are the changes available on GitHub?NA
• Have you checked your service quotas for the sevices this solution uses? NA
• Were there any errors in the CloudWatch Logs? NA

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
We have Custom NACLs created in Network Config file and attached to VPCs, during the update process. The pipeline was failing due to the NACL association was already existing, deleting the custom NACL and running the pipeline worked for NACLs. However it became inconsistent with TGW attachement and failed. is this expected?

Thanks,
Sagar

[padebnat]

Hello @DonthineniSagar ,
Thank you for reaching out to the Landing Zone Accelerator team!
I wanted to let you know that we have added an item in our backlog to look into this issue.

Thank you for your support and interest of the LZA solution! I will leave this issue open should you have any follow-ups for the team, and we will update you when the issue is fixed.

[bo1984]

@DonthineniSagar can you provide the error that you're getting and in which Network stack you're getting this error? NACLs should not have any effect on the TGW attachments.

[awsclemj]

The NACL issue appears to be related to an upstream issue in the CDK library. Relating that bug report here for reference — aws/aws-cdk#27476

[DonthineniSagar]

Thanks for the response, @awsclemj @bo1984 since it was test LZA, i tried removing NACL and LZA proceeded without an issue creating the NACL again, however this is not going to be a valid work around in Production LZA.

Can we safely roll back to 1.4.3 on test? as we need to have the test LZA on same as prod, test platform related changes.

Thank you! appreciate your help.

[richardkeit]

Hi @awsclemj , I reckon close this one out 🎉