In this article

There are two common reasons the configuration returns an error message:

• The access credentials or region settings have changed
• The configuration settings are incorrect, missing, or were updated during or after configuration

An email is sent after 20 errors have occurred. 

Misaligned DE + AWS/Splunk values

Follow these steps to resolve the issue. 

1. From the DNSFilter dashboard, navigate to Tools and select Data Exports
2. Select Edit
3. Compare the current settings to the AWS or Splunk configuration
4. Update the data export configuration to align with AWS/Splunk
5. Select Verify & Test Account to ensure that there is no longer an error

Continue with these additional troubleshooting steps if the configurations is aligned.

Manually look for the bad request

If the misalignment isn't obviously from comparing the two value sets, use Developer Tools to dig deeper for a bad request by completing a HAR file capture.

1. Follow standard methods to create a HAR file, retrying the verification while capturing the HAR
2. Open the file and look for an error message, such as incorrect DCE URL
3. Correct the error in the DNSFilter dashboard
4. Select Verify & Test Account to ensure that there is no longer an error

API call workaround

Our engineers created a API call workaround for a customer deploying with Sentinel. The example uses Postman, but it can be modified for any API call tool.