- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1/"Which pieces of information are we required to display? Start date, expiration date, entitlement level?" -- Yes, but it depends on the product that you are selling. In general information related to the product purchase such as how long that specific contract dimension purchase will be and whether there will be a usage based charge.
2/"What does it mean to "correctly handle" notifications around entitlements and subscriptions? Are we required to quickly reflect back to the customer any changes within the product? Are we required to make behavioral access changes to the product, depending on the kind of notification?" -- This is more about our two SaaS APIs (entitlements and subscriptions ) handling depending on the SaaS pricing models. The SaaS pricing model determines which APIs should be called:
- SaaS contracts – GetEntitlements in the AWS Marketplace Entitlement Service.
- SaaS contracts with consumption – GetEntitlements in the AWS Marketplace Entitlement Service and BatchMeterUsage in the AWS Marketplace Metering Service.
- SaaS subscriptions – BatchMeterUsage in the AWS Marketplace Metering Service.
Contenuto pertinente
- Come posso risolvere gli errori di connessione di Marketplace AWS nei miei processi ETL in AWS Glue?AWS UFFICIALEAggiornata 3 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for your answer. It sounds like there are no requirements to do anything with the information in the notifications other than call the APIs, just prove that we're calling the APIs?