Class: Aws::MarketplaceMetering::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::MarketplaceMetering::Client
- Includes:
- ClientStubs
- Defined in:
- gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb
Overview
An API client for MarketplaceMetering. To construct a client, you need to configure a :region and :credentials.
client = Aws::MarketplaceMetering::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the developer guide.
See #initialize for a full list of supported configuration options.
Instance Attribute Summary
Attributes inherited from Seahorse::Client::Base
API Operations collapse
-
#batch_meter_usage(params = {}) ⇒ Types::BatchMeterUsageResult
The
CustomerIdentifierandCustomerAWSAccountIDare mutually exclusive parameters. -
#meter_usage(params = {}) ⇒ Types::MeterUsageResult
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.
-
#register_usage(params = {}) ⇒ Types::RegisterUsageResult
Paid container software products sold through Amazon Web Services Marketplace must integrate with the Amazon Web Services Marketplace Metering Service and call the
RegisterUsageoperation for software entitlement and metering. -
#resolve_customer(params = {}) ⇒ Types::ResolveCustomerResult
ResolveCustomeris called by a SaaS application during the registration process.
Instance Method Summary collapse
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
Methods included from ClientStubs
#api_requests, #stub_data, #stub_responses
Methods inherited from Seahorse::Client::Base
add_plugin, api, clear_plugins, define, new, #operation_names, plugins, remove_plugin, set_api, set_plugins
Methods included from Seahorse::Client::HandlerBuilder
#handle, #handle_request, #handle_response
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
480 481 482 |
# File 'gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb', line 480 def initialize(*args) super end |
Instance Method Details
#batch_meter_usage(params = {}) ⇒ Types::BatchMeterUsageResult
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
consumption pricing (FCP). Identical requests are idempotent and can
be retried with the same records or a subset of records. Each
BatchMeterUsage request is for only one product. If you want to
meter usage for multiple products, you must make multiple
BatchMeterUsage calls.
Usage records should be submitted in quick succession following a recorded event. Usage records aren't accepted 6 hours or more after an event.
BatchMeterUsage can process up to 25 UsageRecords at a time, and
each request must be less than 1 MB in size. Optionally, you can have
multiple usage allocations for usage data that's split into buckets
according to predefined tags.
BatchMeterUsage returns a list of UsageRecordResult objects, which
have each UsageRecord. It also returns a list of
UnprocessedRecords, which indicate errors on the service side that
should be retried.
For Amazon Web Services Regions that support BatchMeterUsage, see
BatchMeterUsage Region support.
BatchMeterUsage, see BatchMeterUsage code
example in the Amazon Web Services Marketplace Seller Guide.
599 600 601 602 |
# File 'gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb', line 599 def batch_meter_usage(params = {}, = {}) req = build_request(:batch_meter_usage, params) req.send_request() end |
#meter_usage(params = {}) ⇒ Types::MeterUsageResult
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 to sign the API call for
MeterUsageAPI operation.For Amazon EKS deployments, your software must use IAM roles for service accounts (IRSA) to sign the API call for the
MeterUsageAPI operation. Using EKS Pod Identity, the node role, or long-term access keys is not supported.For Amazon ECS deployments, your software must use Amazon ECS task IAM role to sign the API call for the
MeterUsageAPI 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 to sign the API call for the
MeterUsageAPI 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
Timestamprequest parameter is rounded down to the hour and used to enforce this once-per-hour rule for idempotency. For requests that are identical after theTimestampis 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
ClientTokenrequest 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 theClientTokenrequest parameter so that the request is processed successfully. TheTimestamprequest parameter is not rounded down to the hour and is not used for duplicate validation. Requests with duplicateTimestampsare aggregated as long as theClientTokenis 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 and MeterUsage Region
support for Amazon ECS and Amazon EKS.
763 764 765 766 |
# File 'gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb', line 763 def meter_usage(params = {}, = {}) req = build_request(:meter_usage, params) req.send_request() end |
#register_usage(params = {}) ⇒ Types::RegisterUsageResult
Paid container software products sold through Amazon Web Services
Marketplace must integrate with the Amazon Web Services Marketplace
Metering Service and call the RegisterUsage operation for software
entitlement and metering. Free and BYOL products for Amazon ECS or
Amazon EKS aren't required to call RegisterUsage, but you may
choose to do so if you would like to receive usage data in your seller
reports. The sections below explain the behavior of RegisterUsage.
RegisterUsage performs two primary functions: metering and
entitlement.
Entitlement:
RegisterUsageallows you to verify that the customer running your paid software is subscribed to your product on Amazon Web Services Marketplace, enabling you to guard against unauthorized use. Your container image that integrates withRegisterUsageis only required to guard against unauthorized use at container startup, as such aCustomerNotSubscribedExceptionorPlatformNotSupportedExceptionwill only be thrown on the initial call toRegisterUsage. Subsequent calls from the same Amazon ECS task instance (e.g. task-id) or Amazon EKS pod will not throw aCustomerNotSubscribedException, even if the customer unsubscribes while the Amazon ECS task or Amazon EKS pod is still running.Metering:
RegisterUsagemeters software use per ECS task, per hour, or per pod for Amazon EKS with usage prorated to the second. A minimum of 1 minute of usage applies to tasks that are short lived. For example, if a customer has a 10 node Amazon ECS or Amazon EKS cluster and a service configured as a Daemon Set, then Amazon ECS or Amazon EKS will launch a task on all 10 cluster nodes and the customer will be charged for 10 tasks. Software metering is handled by the Amazon Web Services Marketplace metering control plane—your software is not required to perform metering-specific actions other than to callRegisterUsageto commence metering. The Amazon Web Services Marketplace metering control plane will also bill customers for running ECS tasks and Amazon EKS pods, regardless of the customer's subscription state, which removes the need for your software to run entitlement checks at runtime. For containers,RegisterUsageshould be called immediately at launch. If you don’t register the container within the first 6 hours of the launch, Amazon Web Services Marketplace Metering Service doesn’t provide any metering guarantees for previous months. Metering will continue, however, for the current month forward until the container ends.RegisterUsageis for metering paid hourly container products.For Amazon Web Services Regions that support
RegisterUsage, see RegisterUsage Region support.
852 853 854 855 |
# File 'gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb', line 852 def register_usage(params = {}, = {}) req = build_request(:register_usage, params) req.send_request() end |
#resolve_customer(params = {}) ⇒ Types::ResolveCustomerResult
ResolveCustomer is called by a SaaS application during the
registration process. When a buyer visits your website during the
registration process, the buyer submits a registration token through
their browser. The registration token is resolved through this API to
obtain a CustomerIdentifier along with the CustomerAWSAccountId
and ProductCode.
ResolveCustomer, see ResolveCustomer code example in
the Amazon Web Services Marketplace Seller Guide.
Permission is required for this operation. Your IAM role or user
performing this operation requires a policy to allow the
aws-marketplace:ResolveCustomer action. For more information, see
Actions, resources, and condition keys for Amazon Web Services
Marketplace Metering Service in the Service Authorization
Reference.
For Amazon Web Services Regions that support ResolveCustomer, see
ResolveCustomer Region support.
915 916 917 918 |
# File 'gems/aws-sdk-marketplacemetering/lib/aws-sdk-marketplacemetering/client.rb', line 915 def resolve_customer(params = {}, = {}) req = build_request(:resolve_customer, params) req.send_request() end |