@aws-sdk/client-marketplace-metering 3.972.0 → 3.975.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -29,8 +29,8 @@ declare const BatchMeterUsageCommand_base: {
29
29
  /**
30
30
  * <important>
31
31
  * <p>
32
- * The <code>CustomerIdentifier</code> parameter is scheduled for deprecation on March 31, 2026. Use <code>CustomerAWSAccountID</code> instead.</p>
33
- * <p>These parameters are mutually exclusive. You can't specify both <code>CustomerIdentifier</code> and <code>CustomerAWSAccountID</code> in the same request.
32
+ * The <code>CustomerIdentifier</code> and <code>CustomerAWSAccountID</code> are mutually exclusive parameters. You must use one or the other, but not both in the same API request.
33
+ * For new implementations, we recommend using the <code>CustomerAWSAccountID</code>. Your current integration will continue to work. When updating your implementation, consider migrating to <code>CustomerAWSAccountID</code> for improved integration.
34
34
  * </p>
35
35
  * </important>
36
36
  * <p>To post metering records for customers, SaaS applications call
@@ -27,24 +27,50 @@ declare const MeterUsageCommand_base: {
27
27
  getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
28
28
  };
29
29
  /**
30
- * <p>API to emit metering records. For identical requests, the API is
31
- * idempotent and returns the metering record ID. This is used for metering
32
- * flexible consumption pricing (FCP) Amazon Machine Images (AMI) and
33
- * container products.</p>
34
- * <p>
35
- * <code>MeterUsage</code> is authenticated on the buyer's Amazon Web Services account using
36
- * credentials from the Amazon EC2 instance, Amazon ECS task, or Amazon EKS pod.</p>
37
- * <p>
38
- * <code>MeterUsage</code> can optionally include multiple usage allocations, to provide
39
- * customers with usage data split into buckets by tags that you define (or allow the
40
- * customer to define).</p>
41
- * <p>Submit usage records to report events from the previous hour. If you submit records that
42
- * are greater than six hours after events occur, the records won’t be accepted. The timestamp
43
- * in your request determines when an event is recorded. You can only report usage once per hour
44
- * for each dimension. For AMI-based products, this is per dimension and per EC2 instance. For
45
- * container products, this is per dimension and per ECS task or EKS pod. You can’t modify values
46
- * after they’re recorded. If you report usage before the current hour ends, you will be unable to
47
- * report additional usage until the next hour begins.</p>
30
+ * <p>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.
31
+ * You must use the following buyer Amazon Web Services account credentials to sign the API request.</p>
32
+ * <ul>
33
+ * <li>
34
+ * <p>For <b>Amazon EC2</b> deployments, your software must use the
35
+ * <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html">IAM role for Amazon EC2</a>
36
+ * to sign the API call for <code>MeterUsage</code> API operation.</p>
37
+ * </li>
38
+ * <li>
39
+ * <p>For <b>Amazon EKS</b> deployments, your software must use
40
+ * <a href="https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html">IAM roles for service accounts (IRSA)</a>
41
+ * to sign the API call for the <code>MeterUsage</code> API operation. Using
42
+ * <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html">EKS Pod Identity</a>, the node role, or long-term access keys is not supported.</p>
43
+ * </li>
44
+ * <li>
45
+ * <p>For <b>Amazon ECS</b> deployments, your software must use
46
+ * <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html">Amazon ECS task IAM</a>
47
+ * role to sign the API call for the <code>MeterUsage</code> API operation. Using the node role or long-term access keys are not supported.</p>
48
+ * </li>
49
+ * <li>
50
+ * <p>For <b>Amazon Bedrock AgentCore Runtime</b> deployments, your software must use the
51
+ * <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.html#runtime-permissions-execution">AgentCore Runtime execution role</a>
52
+ * to sign the API call for the <code>MeterUsage</code> API operation. Long-term access keys are not supported.</p>
53
+ * </li>
54
+ * </ul>
55
+ * <p>The handling of <code>MeterUsage</code> requests varies between Amazon Bedrock AgentCore Runtime and non-Amazon Bedrock AgentCore deployments.</p>
56
+ * <ul>
57
+ * <li>
58
+ * <p>For <b>non-Amazon Bedrock AgentCore Runtime</b> deployments, you can only report usage once per hour for each dimension.
59
+ * 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
60
+ * 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.
61
+ * The <code>Timestamp</code> request parameter is rounded down to the hour and used to enforce this once-per-hour rule for idempotency.
62
+ * For requests that are identical after the <code>Timestamp</code> is rounded down, the API is idempotent and returns the metering record ID.</p>
63
+ * </li>
64
+ * <li>
65
+ * <p>For <b>Amazon Bedrock AgentCore Runtime</b> deployments, you can report usage multiple times per hour for the same dimension.
66
+ * You do not need to aggregate metering records by the hour. You must include an idempotency token in the <code>ClientToken</code> request parameter. If using an Amazon
67
+ * SDK or the Amazon Web Services CLI, you must use the latest version which automatically includes an idempotency token in the <code>ClientToken</code> request parameter so that the request is processed successfully.
68
+ * The <code>Timestamp</code> request parameter is not rounded down to the hour and is not used for duplicate validation. Requests with duplicate <code>Timestamps</code> are aggregated as long as the
69
+ * <code>ClientToken</code> is unique.</p>
70
+ * </li>
71
+ * </ul>
72
+ * <p>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.</p>
73
+ * <p>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.</p>
48
74
  * <p>For Amazon Web Services Regions that support <code>MeterUsage</code>, see <a href="https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ec2">MeterUsage Region support for Amazon EC2</a> and <a href="https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ecs-eks">MeterUsage Region support for Amazon ECS and Amazon EKS</a>. </p>
49
75
  * @example
50
76
  * Use a bare-bones client and the command you need to make an API call.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-marketplace-metering",
3
3
  "description": "AWS SDK for JavaScript Marketplace Metering Client for Node.js, Browser and React Native",
4
- "version": "3.972.0",
4
+ "version": "3.975.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:types' 'yarn:build:es' && yarn build:cjs",
7
7
  "build:cjs": "node ../../scripts/compilation/inline client-marketplace-metering",
@@ -21,38 +21,38 @@
21
21
  "dependencies": {
22
22
  "@aws-crypto/sha256-browser": "5.2.0",
23
23
  "@aws-crypto/sha256-js": "5.2.0",
24
- "@aws-sdk/core": "3.972.0",
25
- "@aws-sdk/credential-provider-node": "3.972.0",
26
- "@aws-sdk/middleware-host-header": "3.972.0",
27
- "@aws-sdk/middleware-logger": "3.972.0",
28
- "@aws-sdk/middleware-recursion-detection": "3.972.0",
29
- "@aws-sdk/middleware-user-agent": "3.972.0",
30
- "@aws-sdk/region-config-resolver": "3.972.0",
31
- "@aws-sdk/types": "3.972.0",
24
+ "@aws-sdk/core": "^3.973.1",
25
+ "@aws-sdk/credential-provider-node": "^3.972.1",
26
+ "@aws-sdk/middleware-host-header": "^3.972.1",
27
+ "@aws-sdk/middleware-logger": "^3.972.1",
28
+ "@aws-sdk/middleware-recursion-detection": "^3.972.1",
29
+ "@aws-sdk/middleware-user-agent": "^3.972.2",
30
+ "@aws-sdk/region-config-resolver": "^3.972.1",
31
+ "@aws-sdk/types": "^3.973.0",
32
32
  "@aws-sdk/util-endpoints": "3.972.0",
33
- "@aws-sdk/util-user-agent-browser": "3.972.0",
34
- "@aws-sdk/util-user-agent-node": "3.972.0",
33
+ "@aws-sdk/util-user-agent-browser": "^3.972.1",
34
+ "@aws-sdk/util-user-agent-node": "^3.972.1",
35
35
  "@smithy/config-resolver": "^4.4.6",
36
- "@smithy/core": "^3.20.6",
36
+ "@smithy/core": "^3.21.1",
37
37
  "@smithy/fetch-http-handler": "^5.3.9",
38
38
  "@smithy/hash-node": "^4.2.8",
39
39
  "@smithy/invalid-dependency": "^4.2.8",
40
40
  "@smithy/middleware-content-length": "^4.2.8",
41
- "@smithy/middleware-endpoint": "^4.4.7",
42
- "@smithy/middleware-retry": "^4.4.23",
41
+ "@smithy/middleware-endpoint": "^4.4.11",
42
+ "@smithy/middleware-retry": "^4.4.27",
43
43
  "@smithy/middleware-serde": "^4.2.9",
44
44
  "@smithy/middleware-stack": "^4.2.8",
45
45
  "@smithy/node-config-provider": "^4.3.8",
46
46
  "@smithy/node-http-handler": "^4.4.8",
47
47
  "@smithy/protocol-http": "^5.3.8",
48
- "@smithy/smithy-client": "^4.10.8",
48
+ "@smithy/smithy-client": "^4.10.12",
49
49
  "@smithy/types": "^4.12.0",
50
50
  "@smithy/url-parser": "^4.2.8",
51
51
  "@smithy/util-base64": "^4.3.0",
52
52
  "@smithy/util-body-length-browser": "^4.2.0",
53
53
  "@smithy/util-body-length-node": "^4.2.1",
54
- "@smithy/util-defaults-mode-browser": "^4.3.22",
55
- "@smithy/util-defaults-mode-node": "^4.2.25",
54
+ "@smithy/util-defaults-mode-browser": "^4.3.26",
55
+ "@smithy/util-defaults-mode-node": "^4.2.29",
56
56
  "@smithy/util-endpoints": "^3.2.8",
57
57
  "@smithy/util-middleware": "^4.2.8",
58
58
  "@smithy/util-retry": "^4.2.8",