[BUG] GuardDuty service still enabled in the member accounts after deleting the stacks

[aarthkan]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Describe the bug

GuardDuty service is still running in the accounts even after deleting all the stacks for the GuardDuty solution. The delegated admin is cleaned up, but the member accounts still have the service enabled. This causes errors during subsequent deployment of the stack.

To Reproduce

Steps to reproduce the behavior:

1. Deploy the SRA solution for GuardDuty.
2. Once completed successfully, delete the stacks
3. Re-deploy the stacks as-is and check for errors.
4. Error returned - "message": "Unprocessed Member Accounts"

Expected behavior

The service should be completely disabled in all member accounts in the Organization.

Screenshots

NA

Deployment Environment (please complete the following information)

• Deployment Framework [e.g. Customizations for Control Tower and CloudFormation StackSets]: Customizations for Control Tower and CloudFormation StackSets
• Deployment Framework Version [e.g. 1.0, 2.0]:

Additional context

[mlfulleraws]

issue reported has been resolved, thank you for reporting!