2 Answers
- Newest
- Most votes
- Most comments
1
Hello.
When configuring "NetworkInterfaces", try configuring security groups within "AWS::EC2::NetworkInterface" instead of using "SecurityGroups".
Try modifying your template as follows:
"Node01": {
"Type": "AWS::EC2::Instance",
"Metadata": {
"Comment": "Node01"
},
"Properties": {
"VpcId": {
"Ref": "myVPC"
},
"AvailabilityZone": "us-east-2a",
"DisableApiTermination": false,
"EbsOptimized": false,
"IamInstanceProfile": "",
"ImageId": "ami-001328fb3d9e52497",
"InstanceInitiatedShutdownBehavior": "stop",
"InstanceType": "t3.xlarge",
"KeyName": "mykey",
"Monitoring": true,
"NetworkInterfaces": [
{
"NetworkInterfaceId": {
"Ref": "Node01NetworkInterface"
},
"DeviceIndex": "1"
}
],
"PrivateDnsNameOptions": {
"EnableResourceNameDnsAAAARecord": false,
"EnableResourceNameDnsARecord": false,
"HostnameType": "resource-name"
},
"SourceDestCheck": false,
"Tags": [
{
"Key": "Name",
"Value": "node-01"
}
]
}
},
"ESNode01NetworkInterface": {
"Type": "AWS::EC2::NetworkInterface",
"Properties": {
"VpcId": {
"Ref": "myVPC"
},
"Description": "Node01 Network Network",
"InterfaceType": "interface",
"PrivateIpAddress": "10.69.16.50",
"SourceDestCheck": true,
"GroupSet" : [{ "Ref": "NodeClusterSecurityGroup"},{"Ref": "NodeSecurityGroup"}],
"SubnetId": {
"Ref": "PrivateSubnet2a"
}
}
},
0
Thank you for the help! This resolved the issue. Now to continue down the JSON Cloudformation debug road.
answered a month ago
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago