Skip to main content
Merops connects to AWS with an access key ID and secret access key. AWS recommends temporary credentials where possible; if Merops needs a long-lived access key for your workflow, create one for a dedicated IAM user and never use root account credentials.

​
Create an access key

  1. In the AWS Management Console, open IAM and choose Users.
  2. Select a dedicated IAM user, or create one for this integration. Grant only the permissions required for the S3 buckets and objects Merops should manage.
  3. Open Security credentials, find Access keys, and choose Create access key.
  4. Follow the prompts, then securely save the access key ID and secret access key. AWS only displays the secret when the key is created; download the CSV or copy the values before closing the page.

​
Prepare the credential file

Merops can import the CSV downloaded by AWS. Alternatively, create a local plain-text file such as aws-credentials.txt with these lines. Set AWS_REGION to the region you want Merops to use by default; it is optional and defaults to us-east-1.
For temporary credentials, also include the AWS_SESSION_TOKEN value supplied with that credential set.

​
Import the credentials in Merops

  1. In Merops, open Providers and choose Add provider.
  2. Select AWS, import the CSV or text file, and enter a display name if requested.
  3. Open the new connection and check that its Object Storage resources load.
Credential upload accepts a non-empty file up to 10 MiB. A successful import confirms that Merops parsed the file; it does not prove that the identity can perform every operation. Check permissions guidance. For the current AWS Console steps and key-handling guidance, see AWS’s guides to creating and managing access keys and access key security.