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

Cannot specify "S3FailurePath" in SageMaker create_endpoint_config #4055

Closed
kblissett opened this issue Mar 20, 2024 · 2 comments
Closed

Cannot specify "S3FailurePath" in SageMaker create_endpoint_config #4055

kblissett opened this issue Mar 20, 2024 · 2 comments
Labels
bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged.

Comments

@kblissett
Copy link

Describe the bug

The create_endpoint_config method of the SageMaker client does not allow specifying the "S3FailurePath" in AsyncInferenceConfig as specified in the documentation https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sagemaker/client/create_endpoint_config.html#create-endpoint-config.

Expected Behavior

I can specify the "S3FailurePath" in the AsyncInferenceConfig.

Current Behavior

---------------------------------------------------------------------------
ParamValidationError                      Traceback (most recent call last)

...

ParamValidationError: Parameter validation failed:
Unknown parameter in AsyncInferenceConfig.OutputConfig: "S3FailurePath", must be one of: KmsKeyId, S3OutputPath, NotificationConfig

Reproduction Steps

import boto3

sm = boto3.client("sagemaker")
response = sm.create_endpoint_config(
    EndpointConfigName="my-endpoint-config",
    ProductionVariants=[
        {
            "VariantName": "my-variant",
            "ModelName": "my-model",
            "InitialInstanceCount": 1,
            "InstanceType": "ml.m5.large"
        }
    ],
    AsyncInferenceConfig={
        "OutputConfig": {
            "S3OutputPath": "s3://my-bucket/out",
            "S3FailurePath": "s3://my-bucket/failures"
        }
    }
)

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.34.64

Environment details (OS name and version, etc.)

macOS Sanoma 14.4

@kblissett kblissett added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Mar 20, 2024
@kblissett
Copy link
Author

This seems to have been an issue with my local jupyter notebook kernel configuration.

Copy link

github-actions bot commented Apr 8, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant