To Reproduce
Use a minimally customized TSE-SE reference architecture configuration, with more than the default share of VPC endpoints exposed.
Expected behavior
A clear and concise description of what you expected to happen.
Please complete the following information about the solution:
[x] Version: v1.10.1
To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.
[x] Region: us-east-1
[x] Was the solution modified from the version published on this repository? yes, it's a slight variant of the TSE-SE reference architecture
[x] If the answer to the previous question was yes, are the changes available on GitHub? no
[x] Have you checked your service quotas for the services this solution uses? yes
[x] Were there any errors in the CloudWatch Logs? yes, I've attached the relevant snippet
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
Describe the bug
I encountered the following error in the Network account while deploying TSE-SE v1.10.0-a with LZA v1.10.1:
Prior to this failure I see these Route53 resource creation requests in progress:
To Reproduce Use a minimally customized TSE-SE reference architecture configuration, with more than the default share of VPC endpoints exposed.
Expected behavior A clear and concise description of what you expected to happen.
Please complete the following information about the solution:
Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context Add any other context about the problem here.