Problem using Security Lake on standalone account

The error you're encountering suggests that your AWS account may not have the necessary permissions to interact with the Security Lake feature. This could be due to a few reasons:

1. Service Availability: Security Lake is a relatively new service, and it may not be available in all AWS Regions or for all types of AWS accounts. Make sure that you're accessing the service in a Region where it's available.

2. IAM Permissions: Even if you're using an IAM user with admin access, the user may not have the specific permissions required to use the Security Lake feature. You can try creating a new IAM policy that grants the necessary permissions and attach it to your IAM user.

Here's an example of an IAM policy that may grant the required permissions:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "datalake:*",
                "datasource:*",
                "data-catalog:*",
                "s3:*"
            ],
            "Resource": "*"
        }
    ]
}

3. AWS Organizations: The error message about reaching out to your organization administrator suggests that your account may be part of an AWS Organization, even though you've stated that it's not. Check if your account is part of an organization, and if so, ensure that the necessary permissions are granted at the organization or organizational unit (OU) level.

4. Service Limits: It's possible that your AWS account has reached certain service limits, preventing you from using the Security Lake feature. You can check your service limits in the AWS Service Quotas console and request service limit increases if needed.

If you've verified that your account is not part of an AWS Organization and you've granted the necessary IAM permissions, you may need to reach out to AWS Support for further assistance in resolving the issue.