IPAM nested pool

Question

Ran into an issue today with CloudFormation and the new IPAM Pool. Trying to create a nested pool. The Parent pool creates just fine but when the Child pool tries to create it errors out. CloudTrail shows the error as: 'The sourcePoolId ipam-pool-01234567890abcdef has an AddressFamily ipv4 different from input AddressFamily IPv4'

From what I've troubleshoot and tested, CloudFormation only accepts IPv4 or IPv6 for the Address Family. The API only accepts ipv4 or ipv6. It looks like when CloudFormation queries the parent pool for its address family, it returns ipv4 (as expected) but when it compares it to what was provided in the validated template, they are not a match (different case).

Anyone else run into this or had similar results?

Answer

Must have been a bug that is fixed now as I got this Cloudformation deployed fine, creating parent and nested pools.

```
---
AWSTemplateFormatVersion: '2010-09-09'
Description: Nested IPAM pool
Resources:

IPAM:
    Type: AWS::EC2::IPAM
    Properties: 
      Description: Sample IPAM
      OperatingRegions: 
        - RegionName: !Ref AWS::Region

IPAMScope:
    Type: AWS::EC2::IPAMScope
    Properties: 
      Description: Default private scope
      IpamId: !Ref IPAM
      IpamScopeType: private

ParentPool:
    Type: AWS::EC2::IPAMPool
    Properties: 
      AddressFamily: ipv4
      Description: Sample parent pool
      IpamScopeId: !GetAtt IPAM.PrivateDefaultScopeId
      Locale: !Ref AWS::Region
      ProvisionedCidrs: 
        - Cidr: 10.0.0.0/10

NestedPool:
    Type: AWS::EC2::IPAMPool
    Properties: 
      AddressFamily: ipv4
      Description: Sample nested pool
      IpamScopeId: !GetAtt IPAM.PrivateDefaultScopeId
      Locale: !Ref AWS::Region
      ProvisionedCidrs: 
        - Cidr: 10.1.0.0/16
      SourceIpamPoolId: !Ref ParentPool
```

IPAM nested pool

相关内容