- Newest
- Most votes
- Most comments
Hi Robert,
I have seen recently that error also in this forum. The reason, for that case, was that account was considered “compromised”, and the solution was to reach out to AWS Support so they can help out: https://support.console.aws.amazon.com/support/home?#/case/create
Hi all,
Thank you for all the support. Manage to figure out the issue. It seems that somehow they thought that my account was compromised and restricted my access to some of the AWS functions. I has to answer these questions and now they lifted the restrictions. It's annoying because the error in the UI doesn't give you any clue that that was the issue .... what ever, now all my lambda functions are there.
Questions I had to answer:
- Which location are you trying to access the account from (country/city)?
- Does anyone other than you have access to the account (for example, an IT developer)?
- If you answered yes to the previous question, where is that person accessing the account from?
- Are all active Identity and Access Management (IAM) users and roles authorized by you?
- What AWS services and resources are you using on your account currently?
- Confirm that you have reset your account password. This is required before we can continue with this process.
Thanks again guys.
Thanks Robert, glad it got solved. I would then appreciate if you could accept my above answer so that can benefit community for clarity. Thanks
Something else to check: That the console says "Last updated 53 years ago" is very odd. Check the time (and timezone!) on your local machine and make sure it is correct and synched with a reliable NTP source.
Relevant content
- asked 3 years ago
- asked 6 days ago
- asked 6 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- Why can't I view the EventBridge trigger in my Lambda function that my CloudFormation stack created?AWS OFFICIALUpdated a month ago
Even if you have Basic support, you can open an "Account and billing" case.