I created an Amazon Kendra index back in April and used it for just one day before deleting it. I expected to see charges for that month, which is fine. However, I was surprised to find I was also charged for May, even though the index was already gone. The charge appears to be for a connector, but I've made sure I don't have any remaining indexes. I'm looking for advice on how to stop these charges. Could this be an error?
3 Answers
Hey there! Sorry to hear about those unexpected charges. I suggest you check your Billing Console for more details regarding the charges. You can also delete any active resources by following this guide: https://go.aws/4iKuKAA. If the issue persists, reaching out to the Billing team here: http://go.aws/support-center is a good move.
I'm in a similar boat. AWS support has been pretty unhelpful. I have no Kendra indexes, yet I'm facing a bill of $114! As a solo developer, managing this is frustrating. Why’s it so complicated to get answers compared to other services?
It’s more likely that some resources are still active rather than this being a billing error. I recommend checking the exact usage type that's showing up in your bill, and see if you can track down any lingering services or connectors.
Good point! But just to clarify, I had issues finding Kendra indexes in the console. They were created by some failed Bedrock Knowledge bases and didn’t show up as you’d expect.
I reached out and followed all the steps, but there are no Kendra indexes left. It really seems like a billing mistake. But thanks for the help! I did get a reply from support, which eased my worries after the long wait.