Skip to content
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

Closed
1 of 11 tasks
unavailablealfaa opened this issue Jun 30, 2022 · 2 comments
Closed
1 of 11 tasks

Add Sagemaker endpoint L2 construct #441

unavailablealfaa opened this issue Jun 30, 2022 · 2 comments

Comments

@unavailablealfaa
Copy link
Contributor

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:

const endpoint = new sagemaker.Endpoint(this, 'MyEndpoint', {
  endpointName: 'MyEndpoint',
  endpointConfigName: 'MyEndpointConfig',
});

Applying tags to endpoints

You can apply tags to endpoint resources, example codes:

new sagemaker.Endpoint(this, 'MyEndpoint', {
  endpointName: 'MyEndpoint',
  endpointConfigName: 'MyEndpointConfig',
  tags: {
    'key1': 'value1',
    'key2': 'value2',
  },
});

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

Role User
Proposed by @unavailablealfaa
Author(s) @unavailablealfaa, @SeekerWing
API Bar Raiser @alias
Stakeholders @alias, @alias, @alias

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
  • Kick off meeting
  • RFC pull request submitted (label: status/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label api-approved applied to pull request)
  • Final comments period (label: status/final-comments-period)
  • Approved and merged (label: status/approved)
  • Execution plan submitted (label: status/planning)
  • Plan approved and merged (label: status/implementing)
  • Implementation complete (label: status/done)

Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

@kaizencc
Copy link
Contributor

This is being actively worked on in #433

@kaizencc
Copy link
Contributor

Closing as a duplicate of #431

@evgenyka evgenyka added the l2-request request for new L2 construct label Oct 11, 2023
@mrgrain 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants