aws-sdk-marketplacemetering 1.91.0 → 1.92.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a708345315a14af47a9d39f30deae8cae6d88e3a27ed30274a880604db5937ea
-  data.tar.gz: 45af1ac2bd9771eac1da3c9bc5d72eb8b30a226ef3a70ae3fe7d71eb2bb4673d
+  metadata.gz: bc027680612c20455b34c6b2d641aef69f9dc90329b08bbafd472042f2a02529
+  data.tar.gz: 955eb99be2d45b7874bb7583d3fb4303d0ba25798d881d57fef82f8b81fe84dc
 SHA512:
-  metadata.gz: '06659accd952b05e3defb3a19fdef5e7bb6b4a63f491249d3f7ddcf6b4084d91e7f3d44d7fdbca0a81a58dc417db22099a051c8a6e9ac262d1c3d4d9295c965d'
-  data.tar.gz: 5dd1570dc5c151d8f28c41708c7edeede43790a2829cccde91c1850aed2dfe1b60637ef5b40b6136e55c551e1316bd3f1e0531acba4cc313fcd2bae791dd4f46
+  metadata.gz: 4269a445e2416f58dbf978ef09fc7a0a73411b39c749db61a87050eae58421c317f25c4213b6d3a87ba5a63e3d9f04b523826e1af991b2554d8bcc56a033b49c
+  data.tar.gz: f50b57c990c6cb20c2477390eedb60ae8c1d62cbb2d42962111e8e5aaeb1889f7172f5d696f271d7160444b22c0cb2ce95158d7728edd9f297e3baa1c489fee7

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.92.0 (2026-01-22)
+------------------
+
+* Feature - Customer Identifier parameter deprecation date has been removed. For new implementations, we recommend using the CustomerAWSAccountID. Your current integration will continue to work. When updating your implementation, consider migrating to CustomerAWSAccountID for improved integration.
+
 1.91.0 (2026-01-16)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.91.0
+1.92.0

data/lib/aws-sdk-marketplacemetering/client.rb

@@ -483,11 +483,12 @@ module Aws::MarketplaceMetering
 
     # @!group API Operations
 
-    # The `CustomerIdentifier` parameter is scheduled for deprecation on
-    # March 31, 2026. Use `CustomerAWSAccountID` instead.
-    #
-    #  These parameters are mutually exclusive. You can't specify both
-    # `CustomerIdentifier` and `CustomerAWSAccountID` in the same request.
+    # The `CustomerIdentifier` and `CustomerAWSAccountID` are mutually
+    # exclusive parameters. You must use one or the other, but not both in
+    # the same API request. For new implementations, we recommend using the
+    # `CustomerAWSAccountID`. Your current integration will continue to
+    # work. When updating your implementation, consider migrating to
+    # `CustomerAWSAccountID` for improved integration.
     #
     # To post metering records for customers, SaaS applications call
     # `BatchMeterUsage`, which is used for metering SaaS flexible
@@ -600,37 +601,78 @@ module Aws::MarketplaceMetering
       req.send_request(options)
     end
 
-    # API to emit metering records. For identical requests, the API is
-    # idempotent and returns the metering record ID. This is used for
-    # metering flexible consumption pricing (FCP) Amazon Machine Images
-    # (AMI) and container products.
-    #
-    # `MeterUsage` is authenticated on the buyer's Amazon Web Services
-    # account using credentials from the Amazon EC2 instance, Amazon ECS
-    # task, or Amazon EKS pod.
-    #
-    # `MeterUsage` can optionally include multiple usage allocations, to
-    # provide customers with usage data split into buckets by tags that you
-    # define (or allow the customer to define).
-    #
-    # Submit usage records to report events from the previous hour. If you
-    # submit records that are greater than six hours after events occur, the
-    # records won’t be accepted. The timestamp in your request determines
-    # when an event is recorded. You can only report usage once per hour for
-    # each dimension. For AMI-based products, this is per dimension and per
-    # EC2 instance. For container products, this is per dimension and per
-    # ECS task or EKS pod. You can’t modify values after they’re recorded.
-    # If you report usage before the current hour ends, you will be unable
-    # to report additional usage until the next hour begins.
+    # As a seller, your software hosted in the buyer's Amazon Web Services
+    # account uses this API action to emit metering records directly to
+    # Amazon Web Services Marketplace. You must use the following buyer
+    # Amazon Web Services account credentials to sign the API request.
+    #
+    # * For **Amazon EC2** deployments, your software must use the [IAM role
+    #   for Amazon EC2][1] to sign the API call for `MeterUsage` API
+    #   operation.
+    #
+    # * For **Amazon EKS** deployments, your software must use [IAM roles
+    #   for service accounts (IRSA)][2] to sign the API call for the
+    #   `MeterUsage` API operation. Using [EKS Pod Identity][3], the node
+    #   role, or long-term access keys is not supported.
+    #
+    # * For **Amazon ECS** deployments, your software must use [Amazon ECS
+    #   task IAM][4] role to sign the API call for the `MeterUsage` API
+    #   operation. Using the node role or long-term access keys are not
+    #   supported.
+    #
+    # * For **Amazon Bedrock AgentCore Runtime** deployments, your software
+    #   must use the [AgentCore Runtime execution role][5] to sign the API
+    #   call for the `MeterUsage` API operation. Long-term access keys are
+    #   not supported.
+    #
+    # The handling of `MeterUsage` requests varies between Amazon Bedrock
+    # AgentCore Runtime and non-Amazon Bedrock AgentCore deployments.
+    #
+    # * For **non-Amazon Bedrock AgentCore Runtime** deployments, you can
+    #   only report usage once per hour for each dimension. For AMI-based
+    #   products, this is per dimension and per EC2 instance. For container
+    #   products, this is per dimension and per ECS task or EKS pod. You
+    #   can't modify values after they're recorded. If you report usage
+    #   before a current hour ends, you will be unable to report additional
+    #   usage until the next hour begins. The `Timestamp` request parameter
+    #   is rounded down to the hour and used to enforce this once-per-hour
+    #   rule for idempotency. For requests that are identical after the
+    #   `Timestamp` is rounded down, the API is idempotent and returns the
+    #   metering record ID.
+    #
+    # * For **Amazon Bedrock AgentCore Runtime** deployments, you can report
+    #   usage multiple times per hour for the same dimension. You do not
+    #   need to aggregate metering records by the hour. You must include an
+    #   idempotency token in the `ClientToken` request parameter. If using
+    #   an Amazon SDK or the Amazon Web Services CLI, you must use the
+    #   latest version which automatically includes an idempotency token in
+    #   the `ClientToken` request parameter so that the request is processed
+    #   successfully. The `Timestamp` request parameter is not rounded down
+    #   to the hour and is not used for duplicate validation. Requests with
+    #   duplicate `Timestamps` are aggregated as long as the `ClientToken`
+    #   is unique.
+    #
+    # If you submit records more than six hours after events occur, the
+    # records won't be accepted. The timestamp in your request determines
+    # when an event is recorded.
+    #
+    # You can optionally include multiple usage allocations, to provide
+    # customers with usage data split into buckets by tags that you define
+    # or allow the customer to define.
     #
     # For Amazon Web Services Regions that support `MeterUsage`, see
-    # [MeterUsage Region support for Amazon EC2][1] and [MeterUsage Region
-    # support for Amazon ECS and Amazon EKS][2].
+    # [MeterUsage Region support for Amazon EC2][6] and [MeterUsage Region
+    # support for Amazon ECS and Amazon EKS][7].
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ec2
-    # [2]: https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ecs-eks
+    # [1]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
+    # [2]: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
+    # [3]: https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html
+    # [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
+    # [5]: https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.html#runtime-permissions-execution
+    # [6]: https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ec2
+    # [7]: https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ecs-eks
     #
     # @option params [required, String] :product_code
     #   Product code is used to uniquely identify a product in Amazon Web
@@ -893,7 +935,7 @@ module Aws::MarketplaceMetering
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-marketplacemetering'
-      context[:gem_version] = '1.91.0'
+      context[:gem_version] = '1.92.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-marketplacemetering.rb

@@ -54,7 +54,7 @@ module Aws::MarketplaceMetering
   autoload :EndpointProvider, 'aws-sdk-marketplacemetering/endpoint_provider'
   autoload :Endpoints, 'aws-sdk-marketplacemetering/endpoints'
 
-  GEM_VERSION = '1.91.0'
+  GEM_VERSION = '1.92.0'
 
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-marketplacemetering
 version: !ruby/object:Gem::Version
-  version: 1.91.0
+  version: 1.92.0
 platform: ruby
 authors:
 - Amazon Web Services