topic Re: clusterXL @AWS on 2 cores in Cloud Firewall

clusterXL @AWS on 2 cores

Daniel_Kavan — Tue, 22 Jun 2021 16:47:30 GMT

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.

Re: clusterXL @AWS on 2 cores

PhoneBoy — Tue, 22 Jun 2021 19:12:24 GMT

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.

Re: clusterXL @AWS on 2 cores

Nir_Shamir — Wed, 23 Jun 2021 05:23:37 GMT

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.

Re: clusterXL @AWS on 2 cores

Timothy_Hall — Wed, 23 Jun 2021 13:25:51 GMT

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.

Re: clusterXL @AWS on 2 cores

Daniel_Kavan — Fri, 25 Jun 2021 15:57:06 GMT

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.

Re: clusterXL @AWS on 2 cores

PhoneBoy — Wed, 23 Jun 2021 14:18:30 GMT

The number of cores is typically a power (or at least a multiple) of 2.
Never seen physical hardware with just 3 cores.

Re: clusterXL @AWS on 2 cores

Daniel_Kavan — Wed, 23 Jun 2021 19:26:06 GMT

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.

Re: clusterXL @AWS on 2 cores

Nir_Shamir — Thu, 24 Jun 2021 06:45:27 GMT

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"