You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main difference with this pattern is that only a GET method is made available (which will call the invoke-endpoint API). Also, since each ML use case is unique, the construct will require certain properties (such as resource path and request mapping template) to be provided.
Use Case
API Gateway provides a layer of abstraction from the endpoint. This layer of abstraction enables custom authentication approaches and control quotas for specific consumers.
This new pattern is similar to the existing
aws-apigateway-sqs
pattern, but the service integration is with a SageMaker endpoint. The experience will be similar to the one described on this blog post: https://aws.amazon.com/blogs/machine-learning/creating-a-machine-learning-powered-rest-api-with-amazon-api-gateway-mapping-templates-and-amazon-sagemaker/The main difference with this pattern is that only a
GET
method is made available (which will call theinvoke-endpoint
API). Also, since each ML use case is unique, the construct will require certain properties (such as resource path and request mapping template) to be provided.Use Case
API Gateway provides a layer of abstraction from the endpoint. This layer of abstraction enables custom authentication approaches and control quotas for specific consumers.
Proposed Solution
api.RestApiProps
string
string
string
string
Example usage:
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: