Questions tagged with Account Support
Content language: English
Sort by most recent
How to configure Sender ID on SMS
I am setting up a new environment using a new account under the same payee/root account. In order to set up the env I need to configure Sender ID on SMS messages. I have registered Sender ID in India, have a principal entity, and have approved SMS templates. AWS Support is refusing to configure the Sender ID because the account is new. Root / payee account has been active for more than a year. This is the second time such an incident is happening. Last time I had to tag AWS Support on twitter to get the ticket escalated. Has someone faced similar issue, is there a better way to get help?
how to fix an hacked account please help
i think my account has been hacked using a phishing method, i m struggling for weeks in order to get a real call from your services in order to explain the situation A service called amazon turk mechanical has been activated in my account at the same time as a FMA code that blocked me my access to my account. i tried to fix it but amazon asked me for an affidavit, from a lawyer which i had to execute, Then i had again to fix the fees on turk 25k usd !!! i tried to inform your service that it was not due to me but you still tried to withdraw the amounts from my credit card!! i had on the phone a supposed agent from amazon to fix the problem but i assume it s a fake agent. I'd like your serviceto contact me by phone and by email bothly in order to fix that +xxxxxxxxxxxx ( it s a morrocan number ) i'm rebei karim my email account is firstname.lastname@example.org accept my best regards *Personally Identifiable Information (PII) removed - Randi S.
I keep getting a security concern email from AWS.
Hi, every week or so I keep getting an email from AWS about a security concern even though I have deleted every single instance/ resource and have changed the password multiple times due to AWS requiring me to change my password. Does anyone else have the same issue? If so, how do I fix this?
Problems with AWS Support
We have been using AWS for a year now, have received credits as a startup and everything has been great until now. The AWS org is set up as different accounts under the root/payer account. For one of the new accounts that we are setting up as a test environment, we needed to set up SNS to configure SenderId, and ContentTemplate and raise the SMS limit. The request was rejected by AWS Support for the following reason, "Due to some limiting factors on your account at this time, you are not eligible to send SMS messages in Asia Pacific (Mumbai) region. You will need to show a pattern of use of other AWS services and a consistent paid billing history to gain access to this function. We enforce these limitations on all new accounts. Your continued usage of other AWS services will give us greater flexibility to increase your spending limits in the future. Please open a new case after you have a successful billing cycle and additional use of other AWS services and we will gladly review your account." Since we are using >10 services for a year now under different accounts, I do not understand why AWS will block us? There have not been any missed payments and there is ample credit in the account to pay. We are in internal testing and only send SMS to developers and testers. I want to know if anyone has faced a similar situation.
I received an email on August 29, 2022 to update your IAM policies for AWS Lambda
### Background: Hi, we received an email from AWS Lambda Security recently about how to update the permissions to continue making the API calls using "qualifier" parameter successfully. ### What we have done: We have made the permission modification according to the modification steps ### What we want: Is there any way to verify whether our modification is effective? *So we want to know if there is any way we can verify our changes.* By the way: We saw the end of the email saying `If you want to test your changes before October 15, 2022, or need support in taking the required action, please reach out to AWS Support `. Do we need to create a technical case for validation in AWS Support?
Domain Transfer from closing account.
Closing account do to malicious IP assigned for service after purchasing a domain and before the 60 probation waiting period for domain transfer. Can't I just have the zone file then at 60 days, push the zone file to my register? Should I be billed for the two months my domain is in limbo? The Route-53 console denies me access to the Zone file and errors when unlock transfer option is clicked. Any solutions? Been given a malicious IP by AWS is unacceptable, and is reason for the abrupt cancellation of services and has been verified by AWS as a malicious IP.
Can't Find Support Page
A while ago I saw a section of your site where you could contact an AWS representative for support, and they would be on a live chat and then you’d pay them somewhere around £5 for that one time. Do you know where I was on the AWS site? It's not the £29 a month plan. I can’t remember the page/URL for the life of me. I’ve checked my browser history manually up to a year ago. There was a list of chats down the left hand side, and it was people contacting me regarding my question, and I chose one and he helped me. 1000000% through the AWS site. I can’t even find it in my emails. Thanks, Ryder Cragie
How do I get an AWS customer support against poor AWS "premium" support?
We created many issues on AWS premium supprt, but 1. the reponse time is super long (more than 2 days) 2. premiums support does not solve your problem, but they create new troubes for you. They doesn't understand your question first but ask a bunch of questions, ask you to collect a bunch of redundant information for them. 3. Finally, you got no answer and forgot your issues as time goes by *Edit: Removed case ID — Roxy M.
Support page returning 404s
Hello, For the last 2 hours we have been trying to reach out to support due to production being partially impaired, however, the support panels routing seems to be broken as its returning 404s. We have tried accessing it in multiple different ways and none seems to work, is there any known issue? Attempting to use our account in other browsers throws "Internal error, try again later". We are subscribed to the business support package in case thats relevant here. Thanks!