search

F5Networks / f5-aws-cloudformation-v2

AWS Cloudformation Templates for quickly deploying BIG-IP services in AWS
13 stars 22 forks source link

standalone 2nic instance doesn't associate Public IP #49

Closed vchepkov closed 11 months ago

vchepkov commented 11 months ago

I am trying to deploy 2-nic configuration F5 DNS server using bigip-standalone.yaml the goal is to have mgmt/private interface in private subnet and public interface in public subnet

The following attributes are used:

    mgmtSubnetId: subnet-xxx
    mgmtAddress: 10.x.x.x
    mgmtSecurityGroupId: !Ref DNSSecurityGroup
    externalSubnetId: subnet-xxx
    externalSelfIp: 10.x.x.x
    externalSecurityGroupId: !Ref DNSExternalSecurityGroup
    externalServicePublicIpIds: !Ref DNS1EIP
    numExternalPublicIpAddresses: 1
    numSecondaryPrivateIpAddresses: 0

There is no association being made with AWS::EC2::EIP, so not sure what's missing

vchepkov commented 11 months ago

Never mined, I was almost there Instead of externalServicePublicIpIds, it should be

externalSelfPublicIpId: !GetAtt DNS1EIP.AllocationId