-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Sagemaker endpoint L2 construct #441
Comments
This was referenced Jun 30, 2022
This is being actively worked on in #433 |
Closing as a duplicate of #431 |
mrgrain
removed
management/tracking
status/proposed
Newly proposed RFC
l2-request
request for new L2 construct
labels
Nov 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
SageMaker endpoint is the resource used to deploy and host models. It is created with the endpoint configuration provided in the request. This change is to introduce the Sagemaker endpoint L2 construct, which allows clients to define an endpoint with few lines of code. The amount of effort needed to create these resources is about the same as doing it using the AWS console.
Defining an endpoint
Basic definition
In order to define am Endpoint, you must provide the name of an endpoint config. This following codes allow you to define a basic AWS Sagemaker Endpoints:
Applying tags to endpoints
You can apply tags to endpoint resources, example codes:
Additional notes
The construct for Endpoint Configuration will be implemented in a separate change.
The other properties of Endpoint will be add incrementally in separate changes.
Roles
Workflow
status/proposed
)status/review
)api-approved
applied to pull request)status/final-comments-period
)status/approved
)status/planning
)status/implementing
)status/done
)The text was updated successfully, but these errors were encountered: