You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My best guess as to the root cause is that this statement should only be executed if the IPAM pool has shareTargets assigned, which the sandbox pool in the TSE-SE reference architecture does not. I cannot speak to any of the implications beyond that.
privatecreateIpamPoolMap(ipamAllocations: IpamAllocationConfig[],poolMap: Map<string,string>,props: AcceleratorStackProps,){constdelegatedAdminAccountId=props.accountsConfig.getAccountId(props.networkConfig.centralNetworkServices!.delegatedAdminAccount,);for(constallocofipamAllocations){constipamPool=props.networkConfig.centralNetworkServices!.ipams?.find(item=>item.pools?.find(item=>item.name===alloc.ipamPoolName),);if(ipamPool===undefined){this.logger.error(`Specified Ipam Pool not defined`);thrownewError(`Configuration validation failed at runtime.`);}if(!poolMap.has(alloc.ipamPoolName)){letpoolId: string;if(delegatedAdminAccountId===cdk.Stack.of(this).account&&ipamPool.region===cdk.Stack.of(this).region){poolId=cdk.aws_ssm.StringParameter.valueForStringParameter(this,this.getSsmPath(SsmResourceType.IPAM_POOL,[alloc.ipamPoolName]),);}elseif(ipamPool.region!==cdk.Stack.of(this).region){poolId=this.getCrossRegionPoolId(delegatedAdminAccountId,alloc.ipamPoolName,ipamPool.region);}else{poolId=this.getResourceShare(`${alloc.ipamPoolName}_IpamPoolShare`,'ec2:IpamPool',delegatedAdminAccountId,this.cloudwatchKey,).resourceShareItemId;}poolMap.set(alloc.ipamPoolName,poolId);}}}
centralNetworkServices:
...ipams:
- name: "{{ AcceleratorPrefix }}-ipam"...pools:
### Global Ipam Pools ###
- name: "{{ AcceleratorPrefix }}-sandbox-pool"description: "Sandbox networks are isolated to the local sandbox account they are created for, and never connected to other networks in the accelerator, therefore overlapping ranges are by design."provisionedCidrs:
- "{{ sandboxCidr }}"
To Reproduce
Steps to reproduce the behavior.
Use a minimally customized TSE-SE reference architecture configuration, replacing network-config.yaml with network-config.yaml.ipam
Expected behavior
A clear and concise description of what you expected to happen.
Please complete the following information about the solution:
Version: v1.10.0
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.
Region: us-east-1
Was the solution modified from the version published on this repository? yes, it's a slight variant of the TSE-SE reference architecture
If the answer to the previous question was yes, are the changes available on GitHub? no
Have you checked your service quotas for the services this solution uses? yes
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.
The text was updated successfully, but these errors were encountered:
Describe the bug
I encountered the following error while deploying TSE-SE v1.10.0-a with the IPAM network-config.yaml.
My best guess as to the root cause is that this statement should only be executed if the IPAM pool has
shareTargets
assigned, which the sandbox pool in the TSE-SE reference architecture does not. I cannot speak to any of the implications beyond that.To Reproduce
Steps to reproduce the behavior.
Use a minimally customized TSE-SE reference architecture configuration, replacing
network-config.yaml
withnetwork-config.yaml.ipam
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.
The text was updated successfully, but these errors were encountered: