Configuring AWS Credentials Using Credential Manager

This article explains how to configure AWS credentials within the Strobes Platform using the Credential Manager. Once set up, these credentials allow Strobes to integrate with your AWS environment for various scans and automation workflows.

Prerequisites

Before setting up AWS credentials in Strobes, ensure the following:

  • You have an active AWS account with programmatic access enabled.
  • You possess the Access Key ID and Secret Access Key for the IAM user.
  • The IAM user must have relevant permissions such as:
  • Make sure you're an Admin user within your Strobes organization to access the Credential Manager.

Steps to Configure AWS Credentials

Step 1: Access Credential Manager

  • Log in to your Strobes instance.
  • Navigate to the Settings section from the left sidebar.
  • Click on Credential Manager.

Step 2: Add a New Credential

  • Click on the Add Credential button.
  • Under the Connector Type, select AWS from the dropdown list.

Step 3: Fill in AWS Credential Details

You will now be prompted to enter the following details:

  • Name: Give your configuration a meaningful name (e.g., AWS-Prod-Account).
  • Access Key ID: Paste your AWS Access Key ID.
  • Secret Access Key: Paste your AWS Secret Access Key.

Note: Ensure that the credentials have the appropriate permissions for the scans or syncs you intend to run.

Step 4: Save Configuration

Click on the Save button to store the credentials. Your AWS credentials will now be securely stored within the platform.

Where Can This Be Used?

Once saved, the AWS credentials can be selected in configurations for:

  • Infrastructure Scanners: e.g., Prowler
  • Asset Sync Jobs: For fetching cloud resources.
  • Security Posture Assessments for AWS environments.

Troubleshooting Tips

  • If you receive a permission denied error, verify the IAM policy attached to your AWS user.
  • Ensure that your Secret Access Key is correct and not expired.
  • If the scan fails, check CloudTrail logs in AWS to validate API access.

Was this article helpful?