Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

AWS Account Reinstated but Lambda Service Still Unavailable – Seeking Advice

0

Hello AWS Community,

I’m looking for some advice regarding an issue with our AWS account.

Our AWS account was recently temporarily restricted due to a security-related issue. We have completed the security steps requested by AWS Support, including resetting the root password, enabling MFA, and addressing the affected access credentials.

AWS Support has since confirmed that our account has been reinstated and that the restrictions related to the security event have been lifted.

However, we are still unable to fully use some AWS services, particularly AWS Lambda. We are also seeing issues with other account functionalities, and CloudShell previously showed a message indicating that account verification was still in progress.

We have already contacted AWS Support regarding this through our support case, but we are still waiting for a clear explanation of whether there is any remaining verification or security review that is preventing the services from returning to normal.

Has anyone experienced a similar situation after an AWS account reinstatement?

If so, could you please share:

How long did it take for Lambda and other services to become fully available after reinstatement? Was there any additional verification or action required from your side? Is there anything we can check from the AWS Console to determine whether the account is still under some form of restriction or verification?

We understand that AWS Support is the appropriate channel for account-specific issues, and we are continuing to follow up with them. We are posting here in the hope that someone from the AWS Community may have experienced a similar situation and can provide some guidance.

Any advice or insight would be greatly appreciated.

Thank you in advance for your help.

Topics
Management & Governance
Tags
AWS Account Management
Language
English

asked a month ago39 views

1 Answer
0
  1. Has anyone else experienced a similar situation?

There are multiple reports on re:Post. Specifically, regarding the pattern where "Lambda remains unusable even after being told that security restrictions have been lifted," the cause is identified as the persistence of the "compromised" attribute on the account. Only the security team can remove this attribute; standard technical support cases cannot resolve it.

  1. Time required for full recovery of services like Lambda

This varies significantly depending on the specific case. In one reported instance, the restriction was not lifted even after five days; although the member account was initially cleared, the parent (organization) account was subsequently deemed compromised as well, requiring the remediation process to start over.

  1. Additional actions required by the user

The following steps are effective:

  • Check the case category. You must open the case under the "account-management" or "account-verification" category (which is free of charge) rather than "technical support."
  • If you are using AWS Organizations, request a status check on the parent account as well.
  • Verify that the contact email address associated with the root account is capable of receiving emails.
EXPERT

answered a month ago

  • Weareserial
    a month ago

    Thank you for the information.

    I have already checked the account, and there are no remaining security issues. We have also followed all the instructions provided by AWS, including completing the required security remediation steps.

    However, despite the account being reinstated and the security restrictions reportedly being lifted, the services are still not functioning properly. In particular, AWS Lambda and CloudShell remain unusable.

    Could you please help us verify whether the “compromised” status or any other security-related restriction is still associated with our account, and if so, have the AWS Security Team remove it?

    We would greatly appreciate your assistance in escalating this matter, as the affected services are critical to our business operations and are still preventing our systems from running normally.

    Thank you for your continued support.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content