AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Creates an endpoint configuration that SageMaker hosting services uses to deploy models.
In the configuration, you identify one or more models, created using the
Use this API if you want to use SageMaker hosting services to deploy models into
API, to deploy and the resources that you want SageMaker to provision. Then you call
the CreateEndpoint API.
Use this API if you want to use SageMaker hosting services to deploy models into production.
In the request, you define a
ProductionVariant, for each model that you
want to deploy. Each
ProductionVariant parameter also describes the resources
that you want SageMaker to provision. This includes the number and type of ML compute
instances to deploy.
If you are hosting multiple models, you also assign a
specify how much traffic you want to allocate to each model. For example, suppose
that you want to host two models, A and B, and you assign traffic weight 2 for model
A and 1 for model B. SageMaker distributes two-thirds of the traffic to Model A, and
one-third to model B.
When you call CreateEndpoint, a load call is made to DynamoDB to verify that
your endpoint configuration exists. When you read data from a DynamoDB table supporting
Eventually Consistent Reads , the response might not reflect the
results of a recently completed write operation. The response might include some stale
data. If the dependent entities are not yet in DynamoDB, this causes a validation
error. If you repeat your read request after a short time, the response should return
the latest data. So retry logic is recommended to handle these possible issues. We
also recommend that customers call DescribeEndpointConfig before calling CreateEndpoint
to minimize the potential impact of a DynamoDB eventually consistent read.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginCreateEndpointConfig and EndCreateEndpointConfig.
public virtual Task<CreateEndpointConfigResponse> CreateEndpointConfigAsync( CreateEndpointConfigRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the CreateEndpointConfig service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
|ResourceLimitExceededException||You have exceeded an SageMaker resource limit. For example, you might have too many training jobs created.|
.NET Core App:
Supported in: 3.1
Supported in: 2.0
Supported in: 4.5