Public Cloud Marketplaces

What is the SUSE SUSE® Security Prime listing on the Cloud Marketplace?

By selecting the SUSE® Security listing from the public cloud marketplace, customers can deploy SUSE® Security to their Kubernetes environment with the advantage of having monthly billing via that cloud provider.

Where do I find SUSE® Security Prime in the Cloud Marketplace?

The listings can be found in the AWS and Azure Marketplace, there are two listings:

Why are there 2 listings, which one should I use?

We have 2 listings for SUSE® Security Prime, in AWS "EU and UK only" and "non-EU and non-UK only" and in Azure "24x7 Support" and "24x7 Support (EMEA Orders Only)", you should pick the listing that reflects where your cloud account gets billed.

Are these listings available in all countries?

The SUSE® Security Prime listing on the public cloud is not available to purchase in all countries. Your billing country is based on the cloud Account ID used to do the deployment. Please read the addendum at the end of this FAQ for a list of countries that can and cannot transact SUSE® Security Prime,via the marketplace.

My cloud account is in the USA, but I want to deploy SUSE® Security in another region, a region that is in a country where I currently cannot transact SUSE® Security, is this possible?

Yes. As long as your cloud account is billed to one of the allowed countries, it is possible to deploy SUSE® Security in any region.

Is this listing available in China?

Whilst it is not possible to transact/bill SUSE® Security Prime in China, it is possible to deploy into regions in China. Please read the addendum at the end of this FAQ for a list of countries that can and cannot transact SUSE® Security via the cloud marketplace.

I have an existing SUSE® Security subscription; can I use this on the public cloud?

BYOS (Bring Your Own Subscription) SUSE® Security Prime deployments are supported on the public cloud, but billing would be through your normal software purchase channels and not through the cloud provider marketplace. Once the existing subscription term ends, you can purchase SUSE® Security Prime via the cloud marketplace and reconfigure your cluster to support monthly billing through the cloud provider.

I have an existing deployment covered by a SUSE® Security subscription; can I use this new listing in the cloud marketplace for new deployments?

Yes, the marketplace listing works independently from your existing SUSE® Security Prime subscriptions. Please remember that support processes may be different for deployments using your existing subscription and those billed via the cloud Marketplace.

Tell me more about how the billing for SUSE® Security Prime works via the cloud?

When purchasing SUSE® Security Prime through the cloud provider marketplace, the billing is as follows:

What are the pricing tiers?

SUSE® Security Prime has different pricing tiers when purchasing via the cloud marketplace. This is based on the number of nodes on which SUSE® Security is deployed. Details of the tiers are below, please check the listing for further pricing information.

Table 1. Pricing tiers | Tier | Nodes (from) | Nodes (to) | |:---:|:--------:|:-------:| | 1 | 5 | 15 | | 2 | 16 | 50 | | 3 | 51 | 100 | | 4 | 101 | 250 | | 5 | 251 | 1000 | | 6 | 1000 | 15 |

Is there a way to try SUSE® Security Prime before purchasing?

If using the SUSE® Security Prime listing in the cloud provider marketplace, billing commences from the time of deployment. SUSE® Security can also be deployed manually using the standard documentation and repositories. When ready to add support to your SUSE® Security deployment and have this billed via the cloud marketplace, follow the available documentation.

How does SUSE calculate the ‘average number of nodes’ to bill for?

The average node count is calculated by adding the number of active nodes (counted hourly) and dividing by the number of hours SUSE® Security has been active in the billing cycle.

Below are 3 examples of how the average node count is calculated.

Table 2. Usage calculations for different scenarios | | Hours Active | Nodes | Usage Total | Average Node count | Node billed | |-------------|:--------:|:---------------------:|:--------:|:------------:|:--------------------:| | Static Usage | 730 | 10 | 7300 | 10 | 10 @Tier 1 | | Bursting Model | 730 | 10 (562 Hours) & 20 (168 Hours) | 10660 | 15 | 15 @Tier 1 (Rounded from 14.6) | | Transient Cluster | 336 | 20 | 6720 | 20 | 20 @Tier 2 |

Are special commercial terms available?

Depending on the deployment, it may be possible to secure special commercial terms. e.g. An annual subscription would be handled via an AWS private offer. Please contact SUSE for more information.

Can my spend on SUSE® Security Prime count towards my cloud discount program such as AWS EDP or Azure’s MACC?

How do I purchase SUSE® Security Prime for additional nodes?

Once SUSE® Security has been deployed from the listing on the cloud marketplace and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes where SUSE® Security is deployed. Just add SUSE® Security to additional nodes in federated clusters as needed.

Is this an annual commitment, will it auto-renew?

By default, the SUSE® Security Prime listing in the cloud provider marketplace is billed on a monthly cycle, based on usage. Billing is on-going for as long as SUSE® Security is deployed.

Depending on the deployment, custom monthly pricing may be available. This applies to AWS and Azure deployments.

Do I need a managed Kubernetes cluster running in my cloud provide to install SUSE® Security Prime and be billed via the marketplace?

Yes. For AWS, to benefit from monthly billing via the AWS Marketplace, the primary cluster must be an EKS Cluster running in your AWS Account. For Azure, to benefit from monthly billing via the Azure Marketplace, the primary cluster must be an AKS Cluster running in your Azure Account.

On which Kubernetes distributions can the SUSE® Security Prime Cloud Marketplace listing be deployed?

For AWS, the SUSE® Security Prime AWS Marketplace listing must be deployed on an Amazon EKS. For Azure, the SUSE® Security Prime Azure Marketplace listing must be deployed on AKS via the marketplace offering.

What is the deployment mechanism?

For AWS, the Marketplace listing for SUSE® Security Prime is deployed using Helm. For Azure, the SUSE® Security Prime Azure Marketplace listing is deployed using the Azure Portal (and the deployment is CNAB based).

What is the easiest way to get started?

The way to get started is to add the cloud marketplace listing for SUSE® Security Prime to a managed cubernetes cluster, such as as EKS or AKS. Follow the instructions in the usage section, a Helm chart in AWS and the Azure Portal for Azure, takes care of the application installation and setting up billing.

What version of SUSE® Security is installed when using the marketplace listing?

The marketplace listing for SUSE® Security Prime is tied to a specific version of SUSE® Security, typically the latest version available at the time of the listing update. Please check the listing for further information.

I need a prior version of SUSE® Security installed, can I still use the listing?

No. There is no choice of SUSE® Security version when deploying using the marketplace listing. If a prior version of SUSE® Security is required, must be installed manually using the standard documentation.

How often is the listing updated (including the version of SUSE® Security)?

The marketplace listing is tied to a specific version of SUSE® Security, usually the latest version available at the time the listing was last updated.

Typically, the marketplace listing is updated quarterly, or more frequently if there are security issues. SUSE® Security itself is updated with major, minor, or patch versions every 6-8 weeks.

To update the SUSE® Security product to a current version before the marketplace listing is updated, please see Updating SUSE® Security.

I have many Kubernetes clusters across multiple cloud accounts, does the SUSE® Security billing still work and enable tiered pricing?

Yes. Downstream (federated) clusters running SUSE® Security can be deployed across single or multiple cloud accounts, on-premises or even across diffferent public clouds. Downstream nodes report up to the primary SUSE® Security deployment. This process is called federation and is needed to enable tiered pricing for your SUSE® Security deployments.

Billing is routed to the cloud provider account in which the primary cluster is running.

I have multiple independent clusters, each running a separate installation of the SUSE® Security Prime marketplace listing, how is this billed?

As the SUSE® Security deployments are independent, each cluster is billed separately from the others. It is not possible to benefit from tiered pricing across clusters unless the SUSE® Security deployments are federated. Federation requires that only the primary cluster (not downstream remotes) be installed with the SUSE® Security Prime marketplace listing. Learn more about federation in Enterprise Multi-Cluster Management.

If Federation is not possible, consider custom terms from SUSE.

How can I federate SUSE® Security to benefit from tiered pricing across all deployments?

The primary cluster must be running on a managed kubernetes cluster. This is EKS in the AWS Cloud, or AKS in Azure. The cluster must be running the SUSE® Security Prime marketplace listing.

I have purchased multiple SUSE products from the public cloud marketplace (e.g., Rancher Prime and SUSE® Security Prime), does the marketplace billing method still work?

Yes. The billing mechanisms for the two deployments are independent and will be billed separately via the marketplace.

I already have an existing cluster in place and want to add SUSE® Security Prime and have this billed via the marketplace. Is this possible?

Yes, providing it is an EKS cluster in AWS, or AKS in Azure. Simply deploy the AWS Marketplace listing for SUSE® Security Prime to your EKS or AKS cluster.

I already have an existing cluster with SUSE® Security deployed, can I just install the SUSE® Security Prime marketplace listing and have support billed via the cloud marketplace?

Yes. This is possible by redeploying the SUSE® Security Prime from the cloud provider marketplace listing. Please follow the documentation to back up the existing SUSE® Security configuration, as it may be necessary to restore the configuration into the new deployment.

How do I get support?

It is very simple to open a support case with SUSE for SUSE® Security. Create a ‘supportconfig’ via the NewVector UI and upload the output to the SUSE Customer Center. The support config bundle can be exported from the SUSE® Security console under Settings > Configuration.

Is there any difference between the SUSE® Security Prime product on the cloud marketplace compared to the versions I can run in my own data center or install manually in the cloud?

The SUSE® Security Prime product in the cloud marketplace is the same product with the same functionality as what you would install manually in the cloud or run on-premises. The only difference is the billing route.

Does the primary cluster (responsible for billing) need to run 24/7?

To ensure continuity with support, it is recommended that the primary SUSE® Security Prime cluster always remains active.

What if the primary cluster responsible for billing is unable to connect to the cloud provider billing framework?

There may be multiple reasons why the primary cluster is unable to connect to the billing framework, but it is the customer’s responsibility to ensure that the primary cluster is active and connected. While the cluster is not connected to the billing framework, it is not possible to raise a support request.

My primary cluster has been offline, what happens with billing when it reconnects?

If the primary cluster is offline or disconnected from the cloud provider billing framework for a period of time, when it reconnects, the stored usage data will be uploaded and will appear on your next marketplace bill.

How do I get fixes and updates to SUSE® Security?

SUSE® Security is updated with major, minor, or patch versions every 6-8 weeks. To update SUSE® Security to a current version before the SUSE® Security Prime marketplace listing is updated, please see Updating SUSE® Security.

Where can I find out more about the SUSE® Security Prime Marketplace listing?

Where can I find out more about SUSE® Security?

Learn more about SUSE® Security and SUSE® Security Prime with:

Countries that can transact SUSE® Security Prime through the cloud marketplace Please see the Geographical Availability of SUSE® Security Prime and other SUSE Marketplace products at this link.