Cannot enable Security Lake

0

An attempt was made to enable security lake through a terraform module, the N. Virginia region and the Ohio region were enabled... the Ohio region remained in Initialized, from terraform/terraspace the changes were reverted, however the Ohio region remains in the same status as initialized, and the following error appears: An error occurred. The request failed because Security Lake isn't fully enabled for your account yet. Wait a few minutes and then try again. It's been like this for more than 2 days and it won't allow anything else to be enabled in security lake – If I try to delete that region of Ohio I get the following error: **An error occurred. User: arn:aws:iam::**********:root is not authorized to perform: securitylake:DeleteDataLake


The same thing happens if you tried to delete it from a user with administrator permissions I need help to eliminate that failed state so we can continue with enabling security lake –

Erwin
asked 4 months ago126 views
3 Answers
0

Hello, Are there any other errors u get when u try to delete that from admin permission? Still, check the link - https://docs.aws.amazon.com/security-lake/latest/userguide/disable-security-lake.html If any more help is needed plz feel free to comment Thanks

answered 4 months ago
  • Hello, when I do the procedure you sent me in the documentation link, I get the exact same error: An error occurred while closing Security Lake. User: arn:aws:iam::********:root is not authorized to perform: securitylake:DeleteDataLake

0

Hello Erwin, Could you share the permission your user has? I think it is a permission issue.

answered 4 months ago
  • I have tried to do it with the root user which should have all the permissions, and I have also used an additional user with the following permissions: AdministratorAccess, AmazonSecurityLakeAdministrator

0

Check the IAM permissions of the user or role that is attempting to make changes. It needs the necessary permissions listed in the Security Lake documentation.

Wait a few more days to see if the region self-resolves from the invalid state. Sometimes it can take longer than expected for all internal processes to complete.

Try deleting the Ohio region resource via the AWS CLI or API. This requires the securitylake:DeleteDataLake permission.

aws securitylake deletedatalake --region us-east-2

Contact AWS Support for further assistance. They may be able to manually reset the region state from the backend.

As a last resort, you can delete the entire Security Lake service and recreate it to get a clean state across all regions.

profile picture
EXPERT
answered a month ago

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.

Guidelines for Answering Questions