Manage private pricing offers for Amazon Bedrock with managed entitlements

Amazon offers two methods for activating private pricing offers (MPPOs) for Amazon Bedrock across multiple AWS accounts, aiming to streamline the management process and reduce operational friction.

The first method involves a lightweight script designed for one-time activation. This approach is suitable for users who trust each received license without the need for additional infrastructure. The script lists all received licenses within the management account, allowing users to review and confirm that the issuer and account scope align with the expected private offer.

Once reviewed, the script can apply the changes, activating the distributed grants in the AWS Organizations management account. This method requires the user to confirm the account ID and can be executed with a single command.

In contrast, the second method utilizes AWS Cloud Development Kit (CDK) to automate ongoing grant activation. This path is more suited for organizations that require continuous handling of new private pricing agreements. The CDK stack is programmed to listen for specific AWS Marketplace agreement events, verify sellers against a predefined allowlist, and manage the creation and activation of distributed grants dynamically.

The stack comprises an Amazon EventBridge rule to trigger on agreement events, an AWS Lambda function to process the event, and AWS License Manager entitlements to apply the negotiated pricing. This method ensures consistent handling across all accounts, provides an audit trail for each activation attempt, and logs outcomes for review.

Both methods offer distinct advantages. The lightweight script is ideal for quick, one-time operations where trust in all received licenses is assured. Conversely, the CDK automation provides a more scalable solution, automating the grant activation process for ongoing agreements, reducing manual checks, and offering comprehensive logging for auditing. Users should consider their specific needs and operational workflows when choosing between the two methods.