You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Fulfillment Lambda fails to update version/alias when Embedding settings change on stack update (credit to @rstrahan on reporting this bug)
Once complete, import questions, and run query through client (should be successful)
Update stack and set EmbeddingsApi to Disabled
Once complete, run query again through client (should be successful)
Update stack and set parameter EmbeddingsApi to SageMaker
Once complete, run query again through client (this time should fail)
Expected behavior
When enabling, disabling, and then reenabling embeddings, the client queries should still work.
Please complete the following information about the solution:
[v5.3.0] Version: [e.g. v0.0.1]
[us-east-1] Region: [e.g. us-east-1]
[No] Was the solution modified from the version published on this repository?
[N/A] If the answer to the previous question was yes, are the changes available on GitHub?
[N/A] Have you checked your service quotas for the sevices this solution uses?
[Yes] Were there any errors in the CloudWatch Logs?
{
"errorType": "AccessDeniedException",
"errorMessage": "User: arn:aws:sts::XXXXXX:assumed-role/v530-qnabot-FulfillmentLambdaRole/v530-qnabot-FulfillmentLambda is not authorized to perform: sagemaker:InvokeEndpoint on resource: arn:aws:sagemaker:us-east-1:XXXXXX:endpoint/qnabotsmprovisionedembeddingendpoint because no identity-based policy allows the sagemaker:InvokeEndpoint action",
"code": "AccessDeniedException",
...
}
Screenshots
Lambda Console - new lambda version has not been created, despite 2 lambda updates:
Empty response in client due to lambda failure:
Additional context
Temporary workaround is to manually point the live alias to $LATEST
The text was updated successfully, but these errors were encountered:
### Fixed
- Bug causing bot Fulfillment to fail on embeddings updates (#566)
### Updated
- VPC documentation update (SageMaker Serverless is not supported within a VPC)
- Security patches for npm and pip packages
Describe the bug
Fulfillment Lambda fails to update version/alias when Embedding settings change on stack update (credit to @rstrahan on reporting this bug)
To Reproduce
EmbeddingsApi
toSageMaker
EmbeddingsApi
toDisabled
EmbeddingsApi
toSageMaker
Expected behavior
When enabling, disabling, and then reenabling embeddings, the client queries should still work.
Please complete the following information about the solution:
Screenshots

Lambda Console - new lambda version has not been created, despite 2 lambda updates:
Empty response in client due to lambda failure:

Additional context
Temporary workaround is to manually point the
live
alias to$LATEST
The text was updated successfully, but these errors were encountered: