Audit Manager created with CloudFormation doesn't add contorls

When creating an AWS Audit Manager assessment using CloudFormation, there are a few potential reasons why your controls might not be appearing after the assessment is created:

1. Service-Linked Role Issue: AWS Audit Manager requires a service-linked role (AWSServiceRoleForAuditManager) to function properly. If this role doesn't exist in your account or if there are permission issues with creating it, the controls might not be properly added to your assessment. CloudFormation might successfully create the assessment structure but fail to populate the controls.

2. Framework ID Validation: The framework ID you're using ("a3b2dc50-59c3-401d-8c0b-2fc123175d2d") might not be valid in your specific AWS region or account. Framework IDs can vary across regions, so ensure you're using the correct ID for your region.

3. CloudFormation Limitation: There might be a limitation with how CloudFormation interacts with Audit Manager when creating assessments with pre-populated controls.

To troubleshoot this issue:

1. Manually create the service-linked role for Audit Manager if it doesn't exist:

aws iam create-service-linked-role --aws-service-name auditmanager.amazonaws.com

2. Verify the framework ID by listing available frameworks in your region:

aws auditmanager list-assessment-frameworks --framework-type Standard

3. Try creating the assessment manually through the console to see if the controls appear correctly.

4. Check CloudTrail logs for any errors related to Audit Manager operations during the CloudFormation stack creation.

If the issue persists after these steps, you might need to consider creating a custom framework with your required controls and reference that in your CloudFormation template instead of using the standard SOC2 framework.
Sources
How do I troubleshoot CloudFormation error "Error occurred during operation 'CreateCluster SDK error: Service Unavailable. Please try again later."? | AWS re:Post