- Newest
- Most votes
- Most comments
The error you're encountering with the CloudQuest "Compliance Enforcement" task is related to missing required document parameters in your AWS Config remediation configuration.
The issue is likely in how you've mapped the parameters between AWS Config and your SSM document. When setting up the remediation configuration for the AWS Config rule "required-tags", you need to ensure that all required parameters for the SSM document are properly specified.
In your case, you've mapped instanceId to RESOURCE_ID, which is correct, but there might be additional requirements:
-
Make sure you've replaced
<account-id>in the Lambda function ARN with your actual AWS account ID in the SSM document. -
Verify that the parameter mapping in the remediation configuration is exactly as required. The parameter name should be
instanceId(case-sensitive) and the value should beRESOURCE_ID. -
Check if there are any other required parameters that you might have missed. Sometimes AWS Config remediation requires additional parameters beyond what's explicitly defined in your document.
-
Ensure that the IAM role associated with the remediation action has the necessary permissions to invoke the SSM document and the Lambda function.
-
Verify that the Lambda function "labFunction" exists and has the correct permissions to tag EC2 instances.
If you've already checked all these points and are still encountering the error, try recreating the remediation configuration from scratch, ensuring that all parameter mappings are correctly specified.
Sources
Why is EventBridge getting Invalid input for target message from Systems Manager Document | AWS re:Post
Use DescribeDocument with a CLI - AWS SDK Code Examples
Relevant content
- asked 6 months ago
- asked a year ago
