Cloud Product Licensing (AWS) with Monthly Licensing
We have licensed software. We would like to use on AWS and provide it to customers. For licensing, we use the MAC address as a unique key, while in a cloud environment like AWS.
1. Because end users on AWS can delete instances and recreate it with ease steps
2. How to licensing with monthly or yearly basis on AWS.
How can I approach? Request through some lights about this.
source to share
Seems like the best solution for you is AWS Marketplace:
https://aws.amazon.com/marketplace/management/tour/#
Simplified payment and payments
Customers pay for AWS Marketplace software as part of their regular AWS billing cycle. AWS manages the complexity of metering, billing, collection, and financial reporting so that sellers can focus on building and selling core products.
source to share
You will need to use Dedicated Hosts or Dedicated Instances on AWS to install the license keys that you bring yourself. Amazon calls this license BYOL (Bring Your Own License). Another option is to buy a license sold by Amazon and use an instance configured to only use AWS.
You can read about BYOL policy here: https://aws.amazon.com/windows/faq/#own-license
Amazon EC2 offers two purchase options that give you dedicated infrastructure: Dedicated Hosts and Dedicated Instances. It is important to note that all BYOL scripts are supported using Dedicated Hosts, and only certain scripts are supported by Dedicated Instances. In addition, if you bring existing Dedicated Hosts or Dedicated Instances licenses, then you are using hardware that is entirely dedicated to your use and the outsourcing language is used within the Microsoft product terms.
For server-specific BYOL license scenarios (e.g. Windows Server, SQL Server) and requiring a license for the number of sockets or physical cores on a dedicated server, you must use dedicated hosts.
For licensing scenarios that are virtual machines, CALs, or user licenses and do not require a license for the number of sockets or physical cores on a dedicated server, but you need to run a dedicated infrastructure (e.g. Windows Desktop, SQL Server, Remote Desktop Services, Microsoft Office and MSDN), you can use dedicated instances.
source to share
I am the founder of a software licensing API called Keygen . I've seen clients use environment variables to license in-place software that runs in the cloud, short servers (like lambda functions), virtual machines, or CI / CD envs. These environments are less likely to have a MAC address or hard drive ID that is actually used for licensing purposes.)
For example, you can require them to install PRODUCT_LICENSE_KEY=B8A5-91D7-CB9A-DAE4-4F6E-1128
, then you can check the license key for each instance using your configured key. If the instance does not have a license key set in their env, then your product fails to load with an error.
For example, with Keygen, validation can be as simple as one request:
curl -X POST https://api.keygen.sh/v1/accounts/demo/licenses/actions/validate-key \
-H 'Content-Type: application/vnd.api+json' \
-H 'Accept: application/vnd.api+json' \
-d '{
"meta": {
"key": "B8A5-91D7-CB9A-DAE4-4F6E-1128"
}
}'
Payment for each license will be handled separately, for example. on a regular basis or whatever you require. You can use a payment processor like Stripe , which works great with most services (including Keygen) through their webhook system.
I think this will be the simplest approach.
source to share