2 Answers
- Newest
- Most votes
- Most comments
1
Hi Simon,
I'm so sorry you ran into this issue. I've alerted our team on the issue. They are looking into it now. In the meantime could you please check if you are on the right account? The token can only be accepted by the account that is being verified
0
Simon - check if an SCP or anything else prohibits you from using us-west-2 - that's what happened to me last week and you don't directly get that form the message of the expired token. Took me a few days to figure it out :-)
As CodeCatalyst is in that region, the "link" also needs to happen within that region...
answered a year ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
Hi, we couldn't replicate the issue. But we have noticed invalid token issues when the user tries to validate their token on a different AWS account instead of the one that they were attempting to connect to the space. could you please confirm if you were on the right AWS account when you tried to verify the token?