The hierarchy to host an object in FlashBlade requires an object account, a user with a connection key and an S3 bucket.
The following steps should be performed on the first FlashBlade.
-
On the FlashBlade, go to the Object Store tab under the Storage view and click the + (add) button against the Accounts section.
-
Provide an account name and click the Create button.
-
Under the Storage > Object Store > Accounts section, click the account that was created in the previous step. This should show the Users section. Click the + (add) button to create a new user.
-
Provide a username and click the Create button.
-
Select the relevant access policies based on your security requirements. For convenience, select the "pure:policy/full-access" policy and click Add.
At the minimum, for Splunk Multisite to work, you need the following policies
object-delete, object-list, object-read, object-write.Note:The
version-deletepolicy is not required as the Splunk indexes.conf parameterremote.s3.supports_versioning = falseis a requirement for Splunk Multisite so the objects can be deleted by placing the delete marker rather than deleting by a version. Deleting by the version will not propagate the deletes to the replicated FlashBlade and you might see object differences between two FlashBlades and hence the parameterremote.s3.supports_versioningshould always be set to False. -
You have the option of creating a new key or importing an existing key. Go ahead and select “Create a new key” and click the Create button.
-
Make a note of the access key and secret key. Optionally use the CSV or JSON button to download them as a file in their respective format. This access key and secret key will be imported on to the second FlashBlade.
Note:
Save or download the key information before closing the popup. The secret access key can only be accessed during the key creation confirmation and cannot be viewed or accessed after the confirmation popup is closed.