1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
I haven't encountered that error myself, but I have seen similar errors on AWS re:Post a few times.
However, none of the questions include a solution, so the specific course of action is unclear.
There are reports on GitHub issues indicating that the problem was resolved by contacting AWS Support.
So, why not try opening a support case with AWS under "Account and billing" to make an inquiry?
Inquiries under "Account and billing" are free of charge.
https://github.com/kirodotdev/Kiro/issues/6139
Relevant content
- AWS OFFICIALUpdated a year ago
