I am testing the SmartStore setup on S3 with Splunk Enterprise running on an EC2 instance. I am attempting this with an IAM role that has full S3 access. When I included the access keys in indexes.conf and started the instance, SmartStore successfully started. However, when I assigned the IAM role permissions to the EC2 instance and removed the key information from indexes.conf, Splunk froze at the loading screen with indexes.conf.... Running AWS commands shows that various files from S3 are listed. Below is the indexes.conf. During the loading process, Splunk freezes and does not start. The splunkd.log shows a shutdown message at the end. If I re-enter the key information in indexes.conf, it works again. I want to operate this using the IAM role. [default] remotePath = volume:rstore/$_index_name [volume:rstore] storageType = remote path = s3://S3バケット名 remote.s3.endpoint = https://s3.ap-northeast-1.amazonaws.com
... View more