- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Migrate from AWS vSEC R80.10 to R80.30
- 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
Migrate from AWS vSEC R80.10 to R80.30
We have been using vSEC R80.10 succesfully in AWS. One instance with both gateway and management.
We got a notice that it will no longer be supported so we got the new R80.30 AMI from the AWS Marketplace.
We activated our licenses but it seems the new AMI does not include the management server. It says in the marketplace description:
"This BYOL distributed security gateway is managed from a central Security Management Server, which provides consistent security policy management, enforcement, and reporting AWS and hybrid deployments within a single pane of glass. The Security Management Server is not included in this offering. Please choose one of the CloudGuard IaaS Security Management offerings in AWS Marketplace."
Does this mean we now have to runt TWO EC2 instances instead of one? This would double operating costs.
Any help to clarify this will be greatly appreciated.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The R80.20 and R80.30 AMIs are either management OR gateway images that don’t support standalone installation.
We plan to support this again in R80.40.
In the meantime, you can continue to use your R80.10 instance.
We are removing it from the marketplace for new installs, but you can continue to use your existing instances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The R80.20 and R80.30 AMIs are either management OR gateway images that don’t support standalone installation.
We plan to support this again in R80.40.
In the meantime, you can continue to use your R80.10 instance.
We are removing it from the marketplace for new installs, but you can continue to use your existing instances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tech support could not figure this one out for about 10 days.
It is a change which is somewhat difficult to understand as it doubles the operating cost for clouds which only require a single firewall. Even if one operates different sites or clouds, as in our case, we try to avoid dependencies between sites and therefore prefer that each site have its own manager.
So we will now have to deal with R80.30 in physical sites, where we use Open Server, and with R80.10 in AWS...
Not a huge deal, but an unwelcome mix.
Thanks very much and best regards!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why? Its “transition” ...
more explanations: In the past we supported AWS w regular Gaia but there are many limitations (all resolved w new linux 3.10 Gaia). So as of R80.20 the AWS is based on the 3.10 kernel which is GW (the management support of new gaia exist for a while but not integrated w this special gw branch). As of R80.40, the new 3.10 gaia is the only version and supports all modes and that ends the transition period.
Solution: R80.40 is in early availability now and if you are interested, we can add you to the program. So if you do not want to change your configuration (split mgmt and gw), you should use R80.40 in EA or wait for GA... The GA, it is expected around the new year of 2020 so its not far off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Dorit.
Thanks for the explanation and suggestions.
To avoid multiple transitions, I think it will be best to allow the short wait until GA of R80.40 to make the transition in AWS (if hopefully it will also allow importing the R80.10 configuration as R80.30 does).
When this is done and stable we will upgrade our R80.30 open server environment to R80.40 as well.
Regards from Madrid!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi.
Is there any update as to when R80.40 will be available for VSEC in the AWS Marketplace.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R80.40 is in final release days.... We hope to release it any day (next week probably).
As of R80.40, the vSec version is now part of the main release so after we GA the main release, we are ready for vSec and we will quickly start publishing in market places. The process of publishing also depend on the public cloud provider so it may take a week or two.
To sum up: i hope to see it available in market place in January but if not then by the first week of February.
To set the expectation the above is our current plan and the actual delivery may get delayed if we find new blocking issues
You are also welcome to use the EA (release candidate now and give us feedback)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great Dorit. Thanks.
We have no problem with waiting 2 or 3 weeks to move our Vsec standalone from R80.10 to R80.40.
We will be on the lookout.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any news about Vsec R80.40?
I don't find it available in the AWS Marketplace cloud.
I only see a trial version "CloudGuard IaaS All-In-One R80.40 (Free Trial)"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please contact me directly if there is an issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your answer,
I will contact you directly.