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

naming convention for new end point should be the same for updated endpoint for using in production with Lambda function #6

Open
Sandy4321 opened this issue Mar 7, 2024 · 0 comments

Comments

@Sandy4321
Copy link

when new data added and new endpoint created , is new end point created with the same name as old point
since it end point used in lambda function to access end point from local computer
then end point name should not be changed

but by default , for sagemaker new end point can not be created with the same name as old point
and end point configuration should be deleted

naming convention for new end point should be the same for updated endpoint for using in production with Lambda function

as you wrote
Start SM Pipeline Stack: Designed to respond to new training data uploaded to the specified S3 bucket. It utilizes a Lambda function to trigger the SageMaker pipeline, ensuring that your machine learning models are updated with the latest data automatically

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

1 participant