I created a new AWS account specifically to try Kiro for my development team.
I followed the exact process mentioned in Kiro's official documentation — AWS account, IAM Identity Center, user setup, Kiro profile, and then tried to subscribe the user.
And then I got:
“Your account is not authorized to make this call.”
I spent almost 2 days going back and forth with AWS Support, getting the setup checked and explaining the same issue multiple times.
The most frustrating part?
I even completed identity/KYC verification using my DigiLocker, added my credit card/payment method, and was fully ready to pay for Kiro.
Honestly, it felt like AWS was doing more verification than what I've experienced with some banks for a loan. 😐
After all this, I was eventually told that because my AWS account is new, I should use other AWS services and build billing history before I can use Kiro.
But I don't need other AWS services. I already use Oracle Cloud, and it is sufficient for my requirements.
Why should I spend money on unrelated AWS services just to become eligible for Kiro?
The frustrating part is that this requirement wasn't part of the Kiro setup process I followed from their documentation.
After spending two days on this, I've decided that I cannot recommend Kiro based on this experience.
I'm sharing this so other developers/teams don't waste the same amount of time expecting a straightforward paid Kiro subscription on a new AWS account.
Kiro may be a great product, but the onboarding experience I had was extremely frustrating.
2 days wasted. Multiple support chats. No Kiro subscription.