Our labs for cloud provider based sessions are based off individual cloud providers identities (IAM for AWS) and occasionally, some of the accounts basically get corrupted. I’m guessing that this is what happened here. When this happens, we usually need to delete that particular account, and create a new one.
It’s been a few days since this happened, so I’m not sure if we can identify which account we need to do this procedure with. For now, just do another playground session; it’s unlikely you’ll see this again.
If you do see this error again, then:
Open up a private message with either me or another one of the community support engineers;
In the private message, include the account you were using when this happens. We can then tell our AWS team to deal with the account in quesiton.