Authenticate an Amazon S3 connection for Edge Processors using access keys

Finish creating an Amazon S3 connection for Edge Processors by configuring authentication using access keys.

After completing the steps described in Create an Amazon S3 connection for Edge Processor pipelines to start creating an Amazon S3 connection, finish creating the connection by configuring authentication settings.
Note:

This page describes how to authenticate the connection using an access key pair. For information about authenticating the connection using an IAM role instead, see Authenticate an Amazon S3 connection for Edge Processors using an IAM role.

Be aware that IAM role authentication is supported only if all the instances of your Edge Processor are installed on Amazon EC2 instances that are associated with the same AWS account as the S3 bucket.

You have already started creating an Amazon S3 connection, and completed the configurations on the Select data store, General, and Select abilities pages. For more information, see Create an Amazon S3 connection for Edge Processor pipelines.

  1. On a different browser tab than the one where you started creating your Amazon S3 connection in the Data Management app, navigate to the AWS IAM console.
  2. In the AWS IAM console, create an IAM user for accessing the S3 bucket that you want to send data to.

    For information on how to create IAM users, see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html in the AWS Identity and Access Management User Guide.

    Note: This user needs specific resource access policies in order to access your Amazon S3 bucket, but you will configure these policies during a later step that's described in Create an Amazon S3 dataset for Edge Processor pipelines.
  3. Generate an access key pair for the IAM user that you created during the previous step.

    For more information, see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html in the AWS Identity and Access Management User Guide.

    CAUTION: The secret access key is only visible once during creation. Ensure that you copy your secret access key immediately and store it in a safe location.
  4. Return to the browser tab that shows the Storage authentication page in the Data Management app, and then configure the following options:
    Option name Configuration instructions
    Access key Enter the access key associated with the IAM user that you are using for the connection.
    Secret access key Enter the secret access key associated with the IAM user that you are using for the connection.
  5. Depending on whether you previously selected other abilities or authentication methods on the Select abilities page for this connection, do one of the following:
    Option Description

    You only selected the Send data from Edge Processor ability, or you also selected the Send data from Ingest Processor ability and then selected the same authentication method for both abilities.

    		 Select Next to proceed to the Review page. Continue on to step 6.
    You also selected the Send data from Ingest Processor ability, and selected the IAM role authentication method for it. You must configure additional authentication settings. For more information, see Authenticate an Amazon S3 connection for Ingest Processor using an IAM role in the Use Ingest Processors manual.

    You also selected the Run federated search ability.

    You must configure additional authentication settings. For more information, see Create an Amazon S3 Connection in the Splunk Cloud Platform Federated Search manual.
  6. On the Review page, ensure that all the entered information is correct, and then select Create to create your connection.
You now have a connection that uses an access key pair to authenticate to Amazon S3.

Next, create a dataset that uses this connection to access an S3 bucket. You can then configure a pipeline to use this dataset as a destination and start sending data from an Edge Processor to the S3 bucket.

For more information, see Create an Amazon S3 dataset for Edge Processor pipelines.