Hardware and software limitations and considerations for

supports version 8.2.2104.1 and higher of the Splunk Cloud software.

Security considerations

Customer hereby acknowledges and agrees that has not yet undergone a security audit by an independent third party and therefore does not have SOC2 or ISO27001 certification. The security terms in Splunk's Cloud Security Addendum do NOT apply. Customer may not upload or transmit to this environment any regulated data, such as financial information (including PCI-DSS data), protected health information, ITAR data or classified information.

Product limitations and considerations

As you participate in this beta program, please consider the following limitations and considerations.

Data Manager limitations

For Multiple Account AWS onboarding, the same data account cannot be used in multiple data inputs in Data Manager.

For Single Account AWS onboarding, an account cannot be used in multiple data inputs in Data Manager.

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.

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.

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.

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.