AWS marketplace documentation change
Summary
Removed note about Concurrent Agreements limitation, clarified vendor-metered tag format, simplified reference to seller experience, and added detailed buyer instructions for activating vendor-metered tags with backfill option and timing notes.
Security assessment
Changes are documentation improvements focused on cost allocation tagging procedures and user experience. No security vulnerabilities, incidents, or security-specific features are mentioned or addressed. The modifications clarify tag formats and provide operational guidance without introducing security controls or addressing security weaknesses.
Diff
diff --git a/marketplace/latest/userguide/metering-for-usage.md b/marketplace/latest/userguide/metering-for-usage.md index 25bb63379..8f3540017 100644 --- a//marketplace/latest/userguide/metering-for-usage.md +++ b//marketplace/latest/userguide/metering-for-usage.md @@ -100,4 +99,0 @@ There are many ways to tag a buyer's software usage. One way is to first ask you -###### Note - -Concurrent Agreements license-level metering is not currently supported for vendor-metered tagging (VMT) products. If your product uses VMT, continue using standard `ProductCode`-based metering. - @@ -152 +148 @@ The following table shows an example of the buyer experience after a buyer activ -In this example, the buyer can see allocated usage in their **Cost Usage Report**. The vendor-metered tags use the prefix `“aws:marketplace:isv”`. Buyers can activate them in the Billing and Cost Management, under **Cost Allocation Tags** , **AWS-generated cost allocation tags**. +In this example, the buyer can see allocated usage in their **Cost Usage Report**. The vendor-metered tags use the prefix `aws:marketplace:isv:` followed by the tag key name. For example, a tag with the key `BusinessUnit` appears as `aws:marketplace:isv:BusinessUnit`. Buyers can activate these tags in the Billing and Cost Management, under **Cost Allocation Tags** , **AWS-generated cost allocation tags**. @@ -154 +150 @@ In this example, the buyer can see allocated usage in their **Cost Usage Report* -The first and last rows of the **Cost Usage Report** are relevant to what the Seller sends to the Metering Service (as shown in the [Seller experience](./container-metering-meterusage.html#container-vendor-metered-tag-seller) example). +The first and last rows of the **Cost Usage Report** are relevant to what the seller sends to the Metering Service (as shown in the Seller experience example). @@ -163,0 +160,25 @@ xyz | 111122223333 | Network: per (GB) inspected | 30 | 1111 | Marketing +The following screenshot shows an example of the AWS Cost Explorer Service view after a buyer activates vendor-metered tags and groups costs by the `user` tag. + + + +In this example, the seller defines a $0.00 dimension to report credit consumption and a $0.01 dimension for overage charges. Each unit represents $0.01. Cost allocation tags allow the buyer to interactively slice costs by any tag in [AWS Cost Explorer Service](https://aws.amazon.com/aws-cost-management/aws-cost-explorer/), showing that `john` totals 8,500 units ($85.00) and `jane` totals 3,500 units ($35.00) across both dimensions. + +###### To activate vendor-metered tags in the buyer account + + 1. Sign in to the AWS Management Console and open the [AWS Billing console](https://console.aws.amazon.com/billing/). Then choose **Cost allocation tags** from the left navigation pane. + + 2. Choose the **AWS-generated cost allocation tags** tab. + + 3. Search for `aws:marketplace:isv:` to find tags for all products that support vendor-metered tagging. + + 4. Select the check boxes for the tags you want to activate, and then choose **Activate**. + + 5. (Optional) To backfill tags for metering records that were reported before activation, choose **Backfill tags**. Select the month when the metering records were reported, and then choose **Confirm**. + + + + +###### Note + +After activation, vendor-metered tags take up to 24 hours to appear in the Billing and Cost Management console and AWS Cost Explorer Service. If you choose to backfill tags, the backfill process also takes approximately 24 hours to complete. +