- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- clusterXL @AWS on 2 cores
- 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
clusterXL @AWS on 2 cores
Is anyone running clusterXL on R80.40 on 2 cores in the cloud as active/active? I'm thinking about setting up an AWS transit gw with clusterXL with 2 cores for each member. Is 2 cores enough? I'm not sure if you can get 6 cores, 3 cores on each.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have installed Regular Clusters in AWS with 2 cores.
This was dictated to me by the customer because of budget issues. They didn't pass a lot of traffic so 2 cores was enough.
Anyway , at any point , they can upgrade to a stronger VM image if they need to.
Of course they will need to purchase more cores to their licenses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The “vendor recommended” size on our marketplace entry is a 4 core instance size.
2 core instances only offer a bare minimum amount of RAM.
The next largest instance is 8 cores.
These choices are dictated by AWS.
Also note it’s not really ClusterXL Active/Active in the traditional sense, but there are various deployment methods that are active/active.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have installed Regular Clusters in AWS with 2 cores.
This was dictated to me by the customer because of budget issues. They didn't pass a lot of traffic so 2 cores was enough.
Anyway , at any point , they can upgrade to a stronger VM image if they need to.
Of course they will need to purchase more cores to their licenses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nir, Can you confirm your gateway cluster was in it's own VPC? In the attached image from sk111013, you can see the cloud formation template creates a new VPC for the gateways. From what I can tell, whether you use clusterXL or an autoscale group, these gateways get deployed to their OWN security VPC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, Best Practice is to put the deployment in its own VPC.
you can create a new one with the Template or build your own and use the template for "existing VPC"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Agree with Phoneboy here, even on a bare metal non-cloud firewall only having 2 cores will work but is not very efficient for traffic inspection and handling.
now available at maxpowerfirewalls.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some times for funding, you have to go thru POC and show it can work though. With active/active, I hope its a little better. If AWS would have an AMI with 3 cores, that would be just right.
Update: we ended up NOT using a clusterXL at AWS because of the limitation of NOT being able to use a VIP over two separate AZs. Using a cluster would have limited us to ONE AZ.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The number of cores is typically a power (or at least a multiple) of 2.
Never seen physical hardware with just 3 cores.
- Tags:
- phoneboy 1 Dan 0