Closed jacekhewko closed 1 year ago
Hi @jacekhewko , thank you for your interest in the Landing Zone Accelerator on AWS! I have been able to reproduce this error in my environment, and the team is currently working on a fix.
The root cause of the problem is that SSM Parameters are not created in new AWS Accounts as they should be. In your case, the SSM parameter that was not created was /accelerator/network/vpc/Shared-Network/id
. As an immediate workaround, you can manually create the missing SSM Parameter(s) in the new account. The correct value should be stored at the same path in SSM Parameter Store within a preexisting account.
I will update this issue as the team makes progress on implementing the fix. Thank you again for identifying this bug!
+1
Hi @jacekhewko @FlemmingBehrend , thank you for your patience on this issue. This behavior was fixed in our latest release v1.4.2, please update your LZA deployment to version 1.4.2 in order to resolve the behavior. I'll be closing this issue now that the fix has been released, thank you again for bringing this to our attention.
Hi @erwaxler,
Thanks for the info.
Unfortunately, the error did not disappear after upgrading to v1.4.2 and launching the pipeline again, nor can I find any /accelerator/network/vpc/Shared-Network/id
parameter in the main or the child AWS accounts of the solution. Thus I am unable to get rid of the pipeline failure.
Hi @jacekhewko , you will need to create those parameters manually for this pipeline run only. Please see the v1.4.2 Release Notes for more detailed instructions on which SSM parameters need to be created.
I would recommend the above approach. If this is a development environment that can tolerate downtime, another option would be to unshare then reshare the subnet to have automatically create the parameters. Regardless of the path you take, please let me know if this resolves your error.
Hello,
We haven't heard from you on this issue in a while. If you require any additional assistance, please feel free to reply and/or re-open this issue.
Thank you for your interest in Landing Zone Accelerator on AWS!
Hello,
AWSAccelerator-Pipeline fails on Network_Associations step with the below:
This happened when added 6 new AWS accounts into accounts-config.yaml. Nothing else have changed.
Anyone got an idea why would this happen and how to fix this?
Thanks, Jacek