-
Notifications
You must be signed in to change notification settings - Fork 58
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
generative-ai-cdk-constructs: VectorIndex delete fails #891
Labels
bug
Something isn't working
Comments
Hi @waltmayf , thank you for reporting this issue. I will try to reproduce it on my end and update the ticket here. |
Hi @waltmayf , I am not able to reproduce the issue. Created a new stack in TS using the latest version of the library (0.1.289):
Creation and destruction are working as expected: ![]() ![]() Follow up:
|
Thanks Walt for providing the stack. @dineshSajwan will have a look |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When you delete a bedrock knowledge base backed by an AOSS cluster, the delete fails. with an authorization exception.
Expected Behavior
The cloudformation stack should delete successfully
Current Behavior
Deleting the stack currently causes the errors below:
Error in cloudformatino during stack deletion:
Error in OpenSearchIndexCRProvide lambda cloudwatch logs
Reproduction Steps
Possible Solution
The aoss SecurityPolicy deletes successfully before the custom resource fails. Maybe putting a dependency so that the custom resource will delete before the SecurityPolicy will allow the custom resource to delete successfully? You could also just ignore this error on deletion.
Additional Information/Context
No response
CDK CLI Version
2.173.1 (build 4eac959)
Framework Version
@cdklabs/[email protected]
Node.js Version
v20.18.1
OS
Mac
Language
Typescript
Language Version
TypeScript (5.5.3)
Region experiencing the issue
us-east-1
Code modification
No
Other information
No response
Service quota
The text was updated successfully, but these errors were encountered: