AWS Marketplace is enhancing its offerings by introducing Concurrent Agreements for SaaS and professional services products. This feature allows multiple active purchases for the same product within a single AWS account, effective from June 1, 2026, when all new SaaS products must comply with the updated integration requirements.
This guide outlines the necessary technical steps for migrating to Concurrent Agreements, focusing on the shift from Amazon Simple Notification Service (SNS) to Amazon EventBridge, along with API updates and strategies for managing multiple licenses.
Understanding Concurrent Agreements
With Concurrent Agreements, sellers can opt to enable this feature on existing listings or create new ones. The integration must be updated to support multiple active agreements per customer, requiring adjustments to APIs, event schemas, and license management logic.
Alternatively, a new listing can be created with Concurrent Agreements enabled, allowing for a gradual migration of customers from a legacy listing as contracts renew.
Key Changes to Expect
Previously, sellers faced limitations with a single agreement per account, often resorting to workarounds. Now, buyers can accept multiple offers for the same product, each with distinct terms and pricing.
The introduction of the LicenseArn parameter is significant. This new identifier will replace product IDs and customer identifiers, uniquely identifying each software license purchased through AWS Marketplace.
Migration Steps
To successfully transition to Concurrent Agreements, sellers should follow these high-level steps:
- Opt in to Concurrent Agreements via the AWS Marketplace Management Portal for existing listings.
- For new listings created after June 1, 2026, Concurrent Agreements will be enabled by default.
- Transition notifications from Amazon SNS to Amazon EventBridge, as EventBridge supports the
LicenseArnparameter.
API Updates
Three core APIs will now support LicenseArn:
ResolveCustomer- ReturnsLicenseArnalongside buyer AWS account ID and product code.GetEntitlements- AcceptsLicenseArnas a filter, allowing retrieval of specific agreement entitlements.BatchMeterUsage- RequiresLicenseArnin usage records for products that have opted in.
Data Schema Redesign
To facilitate the new licensing structure, sellers need to redesign their data schemas, making LicenseArn the primary identifier. This change simplifies provisioning and billing, linking usage directly to specific licenses rather than customer identifiers.
Considerations for Application Design
When adapting to Concurrent Agreements, sellers should consider tenant provisioning strategies and how to manage multiple licenses effectively. Starting June 1, 2026, new SaaS products will need to utilize CustomerAWSAccountId and LicenseArn in place of the previous identifiers.
Final Thoughts
For existing sellers, the migration to support Concurrent Agreements involves updating APIs, redesigning data schemas, and enhancing customer experiences. This transition is crucial for leveraging improved licensing capabilities while ensuring continuity of service.
