- Newest
- Most votes
- Most comments
Hello.
Will it not be deleted even after some time?
In the worst case scenario, you can reduce the cost by deleting only OpenSearch Serverless, so I recommend deleting only this first.
https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-manage.html#serverless-delete
It is possible that the problem is on the AWS side, so I recommend that you open a case with AWS Support under "Account and billing".
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Hello,
I was in same situation and fixed by doing:
-
Delete OpenSearch collection
-
Update data deletion policy: Consider changing the dataDeletionPolicy of the data source to RETAIN instead of DELETE. This can be done by editing the advanced settings of your knowledge base.(Go to amazon Bedrock console > knowledge base, select the knowledge base you want to delete and click on Edit)
-
Delete data source while the dataDeletionPolicy was in DELETE
-
After deleting data source , delete knowledge base with dataDeletionPolicy in RETAIN
The problem here is on the AWS side, and the solutions suggested by support are flimsy and incomplete.
Changing the dataDeletionPolicy to RETAIN does work. But ONLY if your knowledge base doesn't get stuck in a deletion state (mine has been stuck for over a week).
Maybe due to root-user authentication, the knowledge base got stuck in a deletion state. I switched from the root user to another admin user and was finally able to delete all the resources in the knowledge base using vianney01's method.
I am happy to share that I finally managed to delete my knowledge base. If you ask me how I managed to delete it this time, I cannot tell you. I did the same steps I followed before, but this time it worked, it got deleted, I was even surprised. By the way, AWS was not able to assist me when I logged a case with them.
I have a suspicion that AWS might have done something in the background in the past few months because it didn't make sense that I was not able to delete the data source within my knowledge base due to a deleted vector database.
If you have a similar issue, I will urge you to try to delete it again and follow the procedure of deleting the data source with dataDeletionPolicy as RETAIN. If this works for many of you as well, my suspicion that AWS did something will be true.
All the best, and keep building.
I encountered the same issue and wrote a bug report about it. In the end, switching the AWS Console language to English resolved the problem.
- if you are still searching for this, open the data source under knowledge bases
- click edit
- additional settings
- Change data Retention to retain ( it will be at default)
- Save
- Delete data source
- wait 3-5 mins
- Delete Knowledge Bases
Relevant content
- asked 13 days ago
- asked 5 months ago
- asked 2 months ago
- asked 10 months ago
I am happy to share that I finally managed to delete my knowledge base. If you ask me how I managed to delete it this time, I cannot tell you. I did the same steps I followed before, but this time it worked, it got deleted, I was even surprised. By the way, AWS was not able to assist me when I logged a case with them.
I have a suspicion that AWS might have done something in the background in the past few months because it didn't make sense that I was not able to delete the data source within my knowledge base due to a deleted vector database.
If you have a similar issue, I will urge you to try to delete again and follow the procedure of deleting the data source with dataDeletionPolicy as RETAIN. If this works for many of you as well, my suspicion that AWS did something will be true.
All the best, and keep building.