- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Re: Failure to deploy cluster template in AWS
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Failure to deploy cluster template in AWS
Template keeps rolling back with this message:
Embedded stack arn:aws:cloudformation:us-east-1:256456036607:stack/Check-Point-Cluster-ClusterStack-Z9KT09CQRK20/9edef850-aa14-11e7-836b-503f23fb5536 was not successfully created: The following resource(s) failed to create: [ClusterRole, ClusterPublicAddress, AMI, InternalRoutingTable, MemberAPublicAddress, InstanceSecurityGroup, MemberBPublicAddress].
Parameters supplied were:
AllowUploadDownload true
AvailabilityZone us-east-1a
ClusterExternalAddr 10.50.50.10
ClusterInternalAddr 10.50.50.200
ExternalSubnetCidr 10.50.50.0/26
InstanceType c4.large
InternalSubnetCidr 10.50.50.192/26
KeyName blablabla
MemberAExternalAddr 10.50.50.11
MemberAInternalAddr 10.50.50.201
MemberBExternalAddr 10.50.50.12
MemberBInternalAddr 10.50.50.202
NTPPrimary 0.pool.ntp.org
NTPSecondary 1.pool.ntp.org
PasswordHash blablabla
Shell /bin/bash
SICKey ****
Version R80.10-BYOL
VpcCidr 10.50.50.0/24
Are there any limitations that i am not aware of, (i.e. minimum subnet size, etc.), or am I missing something?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for repeatedly answering my own questions, but it may come handy for someone bumping into same issues.
The problem was caused by the AWS EIP limit of 5 per region.
If you are experiencing it in the lab environment, chose another region.
In production, contact AWS and request the limit increase.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for repeatedly answering my own questions, but it may come handy for someone bumping into same issues.
The problem was caused by the AWS EIP limit of 5 per region.
If you are experiencing it in the lab environment, chose another region.
In production, contact AWS and request the limit increase.
![](/skins/images/A53DAF99EDBAFE11A1FC6E62F510C235/responsive_peak/images/icon_anonymous_message.png)