Known Issues
The following are known issues and workarounds for this version of Data Manager.
Date filed | Issue number | Description |
---|---|---|
2021-04-27, 2021-03-28 | ADDON-36212, ADDON-36249 | When editing either a Single Account AWS data input or a Multiple Account AWS data input in Data Manager to remove one or more regions, the deployment status on the Data Management page shows Success before the editing process is actually successful. This is misleading because you still need to follow the instructions under the Setup AWS Accounts tab to remove the regions. When the edit process is really a success, you do not see the instructions anymore. |
2021-04-26 | ADDON-36207 | When editing a Single Account AWS data input in Data Manager to add a region, if you skip the instructions under the Setup AWS Accounts tab and click Review Finish Setup and Monitor Data Input instead, you see a "No action is needed" message even though the input is still in Mismatch status. |
2021-03-03 | ADDON-34565 | When you select IAM Analyzer as one of the data sources, and then click Review Data Input, you might see an error message that Data Manager cannot detect data sources. The issue is intermittent and you can clear it by clicking Refresh on the Data Input Details page in Data Manager. |
2021-02-24 | ADDON-34344 | The Refresh button on the Data Input Details page in Data Manager does not always change the deployment status. For example, if you get an error such as "An error occurred (InvalidClientTokenId) when calling the CreateStack operation: The security token included in the request is invalid." and then you refresh, you might still see the Summary status of "N/A" even though you see data flowing into Data Last Received. |
After AWS the cleanup process is complete in Splunk Data Manager and you click the Delete button to kick off the deletion process, the AWS Cleanup button is still available for further clicking. Do not click the AWS Cleanup button again or the status will change from "Deleting..." back to "Marked for delete" and here you will lose track of the actual status. | ||
In step 2 of onboarding a new data input, if there is whitespace between the comma-separated account IDs, the data account prerequisite template stays greyed out. If you accidentally input whitespace and navigate away from the text box or press the enter key, the whitespace cannot be deleted. If you have already run the CLI commands in step 1, then AWS resources have been created. The workaround is to delete the current data input, remove the AWS resources, and start over with a new data input. See Delete your data input for Splunk Data Manager. | ||
2022-01-19 | ADDON-47602 | AWS Data Manager inputs check for disabled regions / Splunk Cloud Platform on regions that would disallow API calls. If a region is blocked by a service control policy, and if a user onboards data from that region in the AWS input, the user will not be able to edit and remove the region from the input. The workaround is that the user will need to delete and recreate the input without the blocked region. An upcoming release will include an enhancement to block the user from being able to save the input if a blocked region is being onboarded. |
PREVIOUS Fixed Issues |
NEXT How to find answers and get help with Data Manager |
This documentation applies to the following versions of Data Manager: 1.3.1
Feedback submitted, thanks!