# Using the ignore file Policy violations can be excluded locally with a `.isaacignore` file in the root folder of your project containing the ID(s) in question. Here's an example showing the contents of this exclusion file. ``` # No impact in our settings ISA_C220 # Ignore the misconfiguration ISA_C208 ISA_C1070 ISA_C198 ``` **Note:** a comment preceding policy IDs is then reported in the report Policy IDs can be found in the output of the console report (generated by invoking isaac scanner with flag `--report-console`). ## Set resource-specific exclusions Resource-specific exclusions can be set via the `.isaacignore` file. Given the contents of a regular `.isaacignore` file like the one shown above, if you wanted to exclude policy `ISA_C208` only for a specific resource you can achieve that by adding the Resource ID anywhere in a comment preceding the policy ID ``` # Ignore the misconfiguration for aws_sns_topic.bucket_notifications@main.tf ISA_C208 ISA_C1070 ISA_C198 ``` The Resource ID is an identifier made by the name of a resource + @ + the relative path to the configuration file where it is defined. Meterian uses these in the ISAAC analysis. You can find these for reference in the JSON report or the console report (`--report-console`). Alternatively, you can use a regular expression to target specific resources. This is done by using a specific format: r'\'. Here follows an example ``` # Ignore the misconfiguration for r'aws_sns_topic.bucket_notifications@.*' ISA_C208 ISA_C1070 ISA_C198 ``` In this example the policy ISA\_C208 will be excluded for every `aws_sns_topic.bucket_notifications` resource within the project. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.meterian.io/iac-scanner/using-the-ignore-file.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.