License Deprovisioned vs Purchase Agreement Ended — which starts the 1-hour final-usage window?"
I'm implementing usage metering for a consumption-based SaaS product under the Concurrent Agreements model, and I've found two AWS sources that appear to contradict each other on when the 1-hour window for final BatchMeterUsage submissions begins.
The Concurrent Agreements upgrade blog (updated 6/12/2026) states:
Purchase agreement ended – This event is sent to the manufacturer or proposer when an agreement expires. It provides a 1-hour window for final usage submissions.
and elaborates in the "Usage metering changes" section that the Purchase Agreement Ended event is the window start and License Deprovisioned is the window close (usage no longer accepted).
But the SaaS EventBridge integration guide states:
AWS Marketplace sends the License Deprovisioned - Manufacturer event to signal the start of the final reporting window.
These give opposite answers, and the distinction is load-bearing: the two events can arrive at different times, so subscribing to the wrong one risks submitting final records after the window has closed and losing billable usage.
Questions:
- Which event marks the start of the 1-hour final-usage window — Purchase Agreement Ended or License Deprovisioned - Manufacturer?
- If it's Purchase Agreement Ended: since that event does not include a LicenseArn (which BatchMeterUsage requires), is the intended approach to maintain a LicenseArn ↔ agreementId mapping captured from License Updated events? Is there any other supported way to resolve the license for final metering?
- Topics
- AWS Marketplace
- Tags
- AWS Marketplace
- Language
- English
asked a month ago64 views
- Newest
- Most votes
- Most comments
A similar question was found.
AWS Marketplace SaaS subscription "License Deprovisioned - Manufacturer" event order | AWS re:Post
On the other hand, the statements "Window start – Purchase agreement ended" and "Window close – License Deprovisioned" in the blog post you cited contradict the latest documentation and official AWS responses. It is highly likely that the information in the blog is inaccurate. The author may have conflated the strict one-hour window during which BatchMeterUsage is accepted with the (potentially variable-length) grace period between agreement termination and license expiration, while attempting to describe the entire span—from agreement termination to license expiration—broadly as a "grace period."
In conclusion, the approach you are envisioning—maintaining a mapping between LicenseArn and agreementId derived from "License Updated" events—is the intended approach explicitly recommended by AWS. The blog states the following:
The "Purchase Agreement Ended" event does not include the
license.arn. SinceBatchMeterUsagerequires aLicenseArn, you must maintain an accurate mapping between theLicenseArnand the activeagreement IDthroughout the subscription's lifecycle. This mapping is obtained from "License Updated" events (which contain both identifiers).
Based on the current guidance for Concurrent Agreements, the Purchase Agreement Ended event marks the start of the 1-hour final-usage window for consumption-based products. The License Deprovisioned event marks the end of that window—after which usage reporting will no longer be accepted.
This means you have approximately 1 hour between when the Purchase Agreement Ended event is sent (at agreement expiration) and when the License Deprovisioned event is sent (when entitlements are fully revoked) to submit your final usage records.
Regarding your second question: Yes, you are correct. Since the Purchase Agreement Ended event does not include the LicenseArn, and BatchMeterUsage requires LicenseArn, you must maintain an accurate mapping between LicenseArn and active agreement IDs throughout the subscription lifecycle. You should capture this mapping from License Updated events, which include both identifiers. This is the supported approach for resolving the license for final metering when you receive the Purchase Agreement Ended event.
This mapping strategy is essential for correctly attributing usage when customers have multiple active subscriptions under the Concurrent Agreements model.
Sources
Complete guide to upgrading your SaaS product to AWS Marketplace Concurrent Agreements | AWS Marketplace
answered a month ago
this directly contradicts an answer related to this question https://repost.aws/questions/QUXW1blxT9Tz-hLad9RntzWw/aws-marketplace-saas-subscription-license-deprovisioned-manufacturer-event-order , hopefully a human checks this
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
if the blog is inaccurate, the start window is the License Deprovisioned, and then the mapping is not needed. But we are just speculating here. I don't see an official answer to this yet. I guess I'll just wait to experience it. Thanks anyway