How to lose and find your account on AWS
A very useful post for 3 sentences, which, however, will help save time and nerves.
A few days ago, the most unpleasant thing happened to me: when I tried to log into the AWS Console from my home computer, I saw the registration screen instead of the list of services. There will be no funny pictures with my face, you already understand the situation - the project is in live mode. After several attempts to log in incognito and in other browsers, the situation remained the same. I had no choice but to complete the registration. After that I received - TA-DAM - a completely virgin account.
The funny thing is that at the same time the domain set up in Route53 continued to work wonderfully. Files from S3 - also give away quickly. And so on. Moreover, I could update the files on S3 via CloudBerry with the saved key, and these updates were applied. But the AWS Console account remained crystal clear.
And now, a week later, the support was unsubscribed. It turned out that somehow 2 accounts were created for one email. It turns out that on that ill-fated evening, when I decided to log in from my home computer, I entered the wrong password (instead of one capital letter I entered a small one) and instead of reporting the wrong password, Amazon asked me to register another account at the same address. With that, he did it in the most unobvious way.
')
Despite the complexity of the situation, the solution proposed by the support turned out to be simple and effective. I just changed the email in the 2m, deserted as the surface of Mars, account. Then he again entered a small letter instead of a large one, received a message about the wrong password, entered a large letter - TA-DAM - my relatives files and domains returned home.
I did not get into 3 sentences, but I hope it is still useful.
A few days ago, the most unpleasant thing happened to me: when I tried to log into the AWS Console from my home computer, I saw the registration screen instead of the list of services. There will be no funny pictures with my face, you already understand the situation - the project is in live mode. After several attempts to log in incognito and in other browsers, the situation remained the same. I had no choice but to complete the registration. After that I received - TA-DAM - a completely virgin account.
The funny thing is that at the same time the domain set up in Route53 continued to work wonderfully. Files from S3 - also give away quickly. And so on. Moreover, I could update the files on S3 via CloudBerry with the saved key, and these updates were applied. But the AWS Console account remained crystal clear.
And now, a week later, the support was unsubscribed. It turned out that somehow 2 accounts were created for one email. It turns out that on that ill-fated evening, when I decided to log in from my home computer, I entered the wrong password (instead of one capital letter I entered a small one) and instead of reporting the wrong password, Amazon asked me to register another account at the same address. With that, he did it in the most unobvious way.
')
Despite the complexity of the situation, the solution proposed by the support turned out to be simple and effective. I just changed the email in the 2m, deserted as the surface of Mars, account. Then he again entered a small letter instead of a large one, received a message about the wrong password, entered a large letter - TA-DAM - my relatives files and domains returned home.
I did not get into 3 sentences, but I hope it is still useful.
Source: https://habr.com/ru/post/263181/
All Articles