In this scenario, we have a use case where a customer accidentally created a SNS topic and SQS queue without encryption. Our goal here is to detect and remediate the SNS topic and SQS queue.
Here is a valuable use case from AWS about why encrypting SQS and SNS is important: Link to AWS Blog
Here are the configurations that you should apply:
After you complete configurations, click Filter Check again
Locate the Conformity checks that pertains to the misconfigurations of this scenario (SNS Topic Encrypted and Queue Server Side Encryption). Next to each, select Resolve, which will populate the step-by-step instructions for remediating these misconfiguration.
Clicking the (+) icon on the left side of the Conformity checks allows you to see more details about the discovered misconfiguration. It will also provide the direct link to the resource to help you to review and fix it.
Clicking Resolve button will bring you to the Knowledge Base where you will find step-by-step instructions on how to remediate the misconfiguration found by Conformity.
After completing the remediation for those two use cases, you can return to the Conformity click Run Conformity Bot to start a new process.
The default Conformity process for monitoring is hourly checks performed by the Conformity bot. You can also manually run the checks or enable the real-time monitoring feature.
After couple minutes the Conformity Bot check will finish and you can check if the previous configurations will now appear as Succeeded instead of Failed.