Ask HN: AWS account expires in 2 weeks. Can't login, but they keep asking me to
I know my credentials and i can access my email. OTP is always successfull ( One Time Password).
I have my phone with me, but no notifications coming in ( I have never enabled MFA on this account, and i'm not receiving any SMS)
Every customer support issue directs me to urls where I need to login, but I can't.
Is there a way to let them call me and verifying my account without doing that verification step? Because that's literally the issue.
Or any other advice? ( It's a small account, but it will give me a lot of hassle and errors if i have to reconfigure every website/webapp and approve every email again. Setting me back for > 2-3 days)
Edit:
Thank you all!
I changed the default SMS app ( the default was the normal one for Android) and it showed me a lot of missed messages, including OTP ones from Amazon.
39 comments
[ 0.28 ms ] story [ 391 ms ] threadI'm just not sure if it's about a sms.
I haven't enabled MFA in the past, so there's no authenticator app running with Amazon.
https://support.aws.amazon.com/#/contacts/aws-account-suppor...
I only received follow up answers with urls where i needed to sign in. Which is really weird, because I can't.
They mentioned that those urls can be used with blocked accounts, but my account isn't blocked. I submitted screenshots with where the process goes wrong, but it seems that they are ignoring that crutial part :).
I always receive the message to confirm a notification on my phone during logging in, but there isn't one coming and I know they have my correct number and it hasn't changed in years.
Also, that's not the problem. The problem is a "notification" that isn't coming during the login process.
I can enter my password.
Then I need to enter my OTP through mail.
Then a notification on my phone number ( I'm not receiving this one)
I'm 100% sure the email is correct (they emailed me there that my VISA is expired)
Goodness...Elaborate?
I thought it was weird that I'd be the only one with this issue ( i didn't find any related info/similar issues online)
So I think this possibility is really low. I'm pretty sure it's on Amazon's end, other verification messages always worked fine.
Doing an additional test though ( sending works fine, testing receiving now)
The default one of my mobile OS didn't seem to show all the messages!
I once couldn’t receive an OTP from mobile operator unless I unblocked some spam sender (they had alphanumeric caller ID). I guess they use same service/number for sending SMS?
What app? An amazon app? An SMS app? What was it changed from/to?
Some time back I closed my Amazon account without deleting my AWS services first.
The result was that the services kept running and I kept being charged.
When I talked to AWS they said I should login and stop them. But since it's a single-sign-on, I had to talk to Amazon staff, who were insisting that once you delete an account you cannot restore it, so there was no way for me to login to stop the services.
No matter how much I tried to make AWS understand that it doesn’t make sense for my services to still be up when I deleted my account, they wouldn’t have it. I don’t think I have dealt with such arrogant, bad customer support before.
They reimbursed though the charge.
Haven't this scale of federation of services, "move fast and break things" approach, first to market races and rise of ready to use components and related machinery (containers, k8s, AWS, et al.) abused some well defined norms about technology and as a result aren't we in a somewhat broken state?
In the older days, we'd never have this kind of thing overlooked. You just weren't able to. Now things are much more complicated and this complicated services are assembled in a haphazard way to form big applications and platforms (e.g. too lazy to bind a folder with proper config to enable SSL, so put an NGINX https bridge container in front of it). As a result, the edge cases are not as edge anymore and breaking the configuration of a webapp is much easier.
Similarly this onion structure of abstraction over abstraction makes debugging and mending things much harder. To fix a one-off bug in a DB operation, you need to go to relevant container inside the pod, find its DB location, access if you can and update the table. That table maybe anywhere on this planet. This is impossible for a support engineer in most cases since we have convoluted SSO configurations which makes this kind of access impossible and the original developers couldn't care less in many cases.
I'll sound old, but even the new capabilities are fascinating, we have gone backwards in a lot of things, software quality and robustness related IMHO.
The other day I called a benefits company that was supposed to send me a card but didn’t.
When I called they said there was an issue with their system which they would request to be fixed and that I should call in a couple of days to talk about the original request.
That happened after almost 2 hours waiting on the phone to be able to get to someone.
Before we didn’t have all these cool services but companies would do their whole jobs and get back to you when something goes wrong. Now, due to all these complexity and workers not keeping up with it things go way worse for the customer when something breaks.
And I would never trust a third party sms app.
I am at a loss as to how this could've happened. I used Google Authenticator and simply didn't log in for a few months.
1) A completed, signed, and notarized Identity Verification Form and Affidavit, which can be downloaded online at the following link (the link didn't work)
2) A photocopy of the AWS account owner’s primary proof of identification, such as a State driver’s license or passport.
3) A photocopy of the AWS account owner’s proof of address matching the address on file.
So I'm waiting, maybe they'll give up.
While changing to the Samsung SMS app ( which doesn't have a spam detection), the messages were shown.
By now, I have changed the app back and marked the messages as not Spam ( didn't even knew there was spam detection in my SMS app)
I have replied to AWS support what the exact issue was.