Copyright | (c) 2013-2016 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay <brendan.g.hay@gmail.com> |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | None |
Language | Haskell2010 |
AWS Marketplace Metering Service
This reference provides descriptions of the low-level AWS Marketplace Metering Service API.
AWS Marketplace sellers can use this API to submit usage data for custom usage dimensions.
Submitting Metering Records
- MeterUsage- Submits the metering record for a Marketplace product.
- marketplaceMetering :: Service
- _InvalidEndpointRegionException :: AsError a => Getting (First ServiceError) a ServiceError
- _InvalidProductCodeException :: AsError a => Getting (First ServiceError) a ServiceError
- _InvalidUsageDimensionException :: AsError a => Getting (First ServiceError) a ServiceError
- _DuplicateRequestException :: AsError a => Getting (First ServiceError) a ServiceError
- _TimestampOutOfBoundsException :: AsError a => Getting (First ServiceError) a ServiceError
- _ThrottlingException :: AsError a => Getting (First ServiceError) a ServiceError
- _InternalServiceErrorException :: AsError a => Getting (First ServiceError) a ServiceError
- module Network.AWS.MarketplaceMetering.MeterUsage
Service Configuration
marketplaceMetering :: Service Source #
API version '2016-01-14' of the Amazon Marketplace Metering SDK configuration.
Errors
Error matchers are designed for use with the functions provided by
Control.Exception.Lens.
This allows catching (and rethrowing) service specific errors returned
by MarketplaceMetering
.
InvalidEndpointRegionException
_InvalidEndpointRegionException :: AsError a => Getting (First ServiceError) a ServiceError Source #
The endpoint being called is in a region different from your EC2 instance. The region of the Metering service endpoint and the region of the EC2 instance must match.
InvalidProductCodeException
_InvalidProductCodeException :: AsError a => Getting (First ServiceError) a ServiceError Source #
The product code passed does not match the product code used for publishing the product.
InvalidUsageDimensionException
_InvalidUsageDimensionException :: AsError a => Getting (First ServiceError) a ServiceError Source #
The usage dimension does not match one of the UsageDimensions associated with products.
DuplicateRequestException
_DuplicateRequestException :: AsError a => Getting (First ServiceError) a ServiceError Source #
A metering record has already been emitted by the same EC2 instance for the given {usageDimension, timestamp} with a different usageQuantity.
TimestampOutOfBoundsException
_TimestampOutOfBoundsException :: AsError a => Getting (First ServiceError) a ServiceError Source #
The timestamp value passed in the meterUsage() is out of allowed range.
ThrottlingException
_ThrottlingException :: AsError a => Getting (First ServiceError) a ServiceError Source #
The calls to the MeterUsage API are throttled.
InternalServiceErrorException
_InternalServiceErrorException :: AsError a => Getting (First ServiceError) a ServiceError Source #
An internal error has occurred. Retry your request. If the problem persists, post a message with details on the AWS forums.
Waiters
Waiters poll by repeatedly sending a request until some remote success condition
configured by the Wait
specification is fulfilled. The Wait
specification
determines how many attempts should be made, in addition to delay and retry strategies.
Operations
Some AWS operations return results that are incomplete and require subsequent
requests in order to obtain the entire result set. The process of sending
subsequent requests to continue where a previous request left off is called
pagination. For example, the ListObjects
operation of Amazon S3 returns up to
1000 objects at a time, and you must send subsequent requests with the
appropriate Marker in order to retrieve the next page of results.
Operations that have an AWSPager
instance can transparently perform subsequent
requests, correctly setting Markers and other request facets to iterate through
the entire result set of a truncated API operation. Operations which support
this have an additional note in the documentation.
Many operations have the ability to filter results on the server side. See the individual operation parameters for details.