Concurrent Agreements: is LicenseArn kept or replaced on renewal?

When a SaaS contract with Concurrent Agreements enabled renews through auto-renewal, a new agreement ID is created for each renewal cycle. The LicenseArn represents the actual authorization or right to use the software and is tied to a specific agreement, while the agreement ID represents the commercial or legal arrangement between parties.

To track the relationship between renewals across the chain of agreements, you should use the Renewal History feature available in the Manage Subscriptions interface. This shows all past and upcoming offers and agreements in the renewal chain in order, which is specifically designed to help you see every offer and agreement across the chain since a new agreement ID is created each time an agreement renews.

For future-dated agreements, it's worth noting that the LicenseArn is generated on the agreement start date, which might occur months after the agreement ID is created. This timing consideration may be relevant when tracking renewals.

Regarding your specific question about real-world renewal behavior and the linkage mechanism between old and new licenses beyond what's documented - the available documentation focuses on the Renewal History as the primary mechanism for tracking agreement chains, but doesn't explicitly detail whether the LicenseArn itself changes or persists through renewal, or provide alternative linking mechanisms in the event payload structure you mentioned.
Sources
Complete guide to upgrading your SaaS product to AWS Marketplace Concurrent Agreements | AWS Marketplace
Managing subscriptions with auto-renewal - AWS Marketplace