Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Easy Setup Fails When Deploying AWS GuardDuty #185

Open
BlakePierantoni opened this issue Oct 12, 2023 · 2 comments
Open

[BUG] Easy Setup Fails When Deploying AWS GuardDuty #185

BlakePierantoni opened this issue Oct 12, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@BlakePierantoni
Copy link

Describe the bug

The easy setup stackset fails to deploy during initial provisioning in a net new AWS Organization.

Stacks Failing:
rGuardDutyOrgLambdaCustom

  • Reason: "An error occured (BadRequestException) when calling the EnableOrganizationAdmin Account Operation: The request is rejected because an invalid or out of range value is specified as an input parameter"

rGuardDutyOrgLambdaCustomResource

  • Reason: "An error occured (BadRequestException) when calling the EnableOrganizationAdmin Account Operation: The request is rejected because an invalid or out of range value is specified as an input parameter"

To Reproduce

Steps to reproduce the behavior:

  1. Deploy SRA Easy setup with the following selections
    • EC2 Default Volume Encryption
    • GuardDuty
      • Malware Protection
    • IAM Access Analyzer
    • IAM Account Password Policy
    • S3 Block Account Public Access

Additional context

I double checked all parameters and didn't see an issue with any being passed through.
The easy setup is pointing at the main branch

@BlakePierantoni BlakePierantoni added the bug Something isn't working label Oct 12, 2023
@liamschn
Copy link
Contributor

Hi @BlakePierantoni we are trying to recreate this issue. When you checked the parameters, can you please confirm that you set:
- pControlTower (set to 'false')
- pGovernedRegions (set to be a comma separated list of regions)
- pSecurityAccountId (set to be your security tooling account ID)
- pLogArchiveAccountId (set to be your log archive account ID)

Can you also tell us what regions you are deploying the SRA too?

@BlakePierantoni
Copy link
Author

@liamschn , it seems this issue was resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants