sagemaker: Make IEndpointConfig property of Endpoint optional #23162
Labels
@aws-cdk/aws-sagemaker
Related to AWS SageMaker
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p3
Describe the feature
Even though explicitly defining an
EndpointConfig
resource allows for reusable configuration across endpoints, as discussed on the originalEndpoint
L2 construct PR, customers looking to deploy a single endpoint may find it easier to have the endpoint configuration encapsulated within the endpoint construct.Please 👍 this issue to help with the prioritization of this feature.
Use Case
Customers may not want to have to define their own
IEndpointConfig
resource, instead relying onEndpoint
to instantiate one for them (in the event they don't provide one onEndpointProps
).Proposed Solution
Add each of these members of
EndpointConfigProps
toEndpointProps
as optional arguments (while making the existingIEndpointConfig
prop value optional as well) while ensuring that theIEndpointConfig
property and the new members are mutually exclusive.In this scenario, it likely also make sense to include an
addInstanceProductionVariant
onEndpoint
so that customers can mutate the backingEndpointConfig
in the same manner as they could using their own instance (this does have the added bonus of returning anIEndpointInstanceProductionVariant
instance from the method, eliminating the need for customers to look up the variant by name).Other Information
No response
Acknowledgements
CDK version used
2.54.0-alpha.0
Environment details (OS name and version, etc.)
macOS Ventura
The text was updated successfully, but these errors were encountered: