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.

Sign up for GitHub

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

Jump to bottom

GuardDuty auto-created Detector not CloudFormation-managed #11

Open
tomwwright opened this issue Sep 28, 2020 · 0 comments
Open

GuardDuty auto-created Detector not CloudFormation-managed #11

tomwwright opened this issue Sep 28, 2020 · 0 comments
Labels
priority/low Low priority tickets type/debt Technical debt that needs to be addressed in the future

Comments

@tomwwright
Copy link
Owner

When an account is enabled as the GuardDuty Organization Admin account, a Detector resource is auto-created and cannot be removed. This means the Little Orange GuardDuty stack cannot create the Detector so its properties are not managed by CloudFormation

It may be better to roll the Detector config management into the GuardDutyOrganizationConfiguration Custom Resource to ensure it gets managed
@tomwwright tomwwright added the type/debt Technical debt that needs to be addressed in the future label Sep 28, 2020
@tomwwright tomwwright added the priority/low Low priority tickets label Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/low Low priority tickets type/debt Technical debt that needs to be addressed in the future
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomwwright