I have a template which creates an ELB and attaches an existing subnet within a VPC. This creates just fine but when I then update my stack and add a security group with a VpcId property with a value equal to the existing VPC ID in which my attached subnet belongs the stack fails with the following error:
"You have specified two resources that belong to different networks"
If I remove the VpcId property from my security group it creates it in my default VPC and the stack creation works. I cannot understand why this can be because the security group has a relationship to the ELB in the specified ingress rules -
"IpProtocol": "tcp",
"FromPort": "8000",
"ToPort": "8010",
"SourceSecurityGroupOwnerId": {
"Fn::GetAtt": [
"ElasticLoadBalancer",
"SourceSecurityGroup.OwnerAlias"
]
},
I cannot explicitly state the VPC ID on the ELB as it has no such property, only Subnet or AZ.
SourceSecurityGroupOwnerId
and notSourceSecurityGroupId
with theRef
to your ELB security group. Did you try removing thisIpProtocol
property and keeping theVpcId
? – Céline Aussourd