Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

Document or increase 60 second connect limit for SageMaker Feature Store Runtime APIs #752

Closed
tim-finnigan opened this issue May 21, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation feature-request New feature or request sagemaker-featurestore-runtime service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation

Comments

@tim-finnigan
Copy link
Contributor

tim-finnigan commented May 21, 2024

Original issue: boto/boto3#4021. (ref: P131007386)

@tim-finnigan tim-finnigan added documentation Improvements or additions to documentation feature-request New feature or request service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation sagemaker-featurestore-runtime labels May 21, 2024
@tim-finnigan tim-finnigan self-assigned this May 21, 2024
@tim-finnigan
Copy link
Contributor Author

We have reported this to the SageMaker team for consideration as to whether they could better improve the behavior or documentation here. It's still being tracked in their backlog, so we're going to close this on our end. Please refer to the SageMaker blog or your SDK's CHANGELOG for updates related to this.

Copy link

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation feature-request New feature or request sagemaker-featurestore-runtime service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation
Projects
None yet
Development

No branches or pull requests

1 participant