amazonka-sagemaker-runtime-1.6.1: Amazon SageMaker Runtime SDK.

Copyright(c) 2013-2018 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay <brendan.g.hay+amazonka@gmail.com>
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellNone
LanguageHaskell2010

Network.AWS.SageMakerRuntime

Contents

Description

Amazon SageMaker runtime API.

Synopsis

Service Configuration

sageMakerRuntime :: Service Source #

API version 2017-05-13 of the Amazon SageMaker Runtime 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 SageMakerRuntime.

ServiceUnavailable

_ServiceUnavailable :: AsError a => Getting (First ServiceError) a ServiceError Source #

Service is unavailable. Try your call again.

ModelError

_ModelError :: AsError a => Getting (First ServiceError) a ServiceError Source #

Model (owned by the customer in the container) returned an error 500.

InternalFailure

_InternalFailure :: AsError a => Getting (First ServiceError) a ServiceError Source #

Internal failure occurred.

ValidationError

_ValidationError :: AsError a => Getting (First ServiceError) a ServiceError Source #

Inspect your request and try again.

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.

InvokeEndpoint

Types