Create an AWS IAM Access Key for AIQ Integrations

To

Create create,an modify,AWS IAM Access Key for AIQ Integrations

Create an AWS IAM access key only when an AIQ integration requires programmatic AWS access and a role-based approach is not available. Follow the customer's cloud security policy and use the minimum permissions required.

Security checklist

• Prefer IAM roles, temporary credentials, or deleteworkload youridentity ownwhen IAM user accesssupported.
• Create keys (console)for
  a dedicated integration user, not a personal administrator account.
• Attach

  Usea yourleast-privilege AWSpolicy account ID or account alias, your IAM user name, and your password to sign inscoped to the IAM console.

  For your convenience, therequired AWS sign-in page uses a browser cookie to remember your IAM user nameservice and account information. If you previously signed in as a different user, choose Sign in to a different account near the bottom of the page to return to the main sign-in page. From there, you can type your AWS account ID or account alias to be redirected to the IAM user sign-in page for your account.

  To get your AWS account ID, contact your administrator.

  resource.

In the navigation bar on the upper right, choose your user name, and then choose Security credentials.

Do one of the following:

To create an access key:

In the Access keys section, choose Create access key. If you already have two access keys, this button is deactivated and you must delete an access key before you can create a new one.

On the Access key best practices & alternatives page, choose the Command Line Interface CLI option and then choose Next.

(Optional) Set a description tag value for the access key. This adds a tag key-value pair to your IAM user. This can help you identify and rotate access keys later. The tag key is set toStore the access key id.and Thesecret tagin valuean isapproved setsecret tomanager or secured AIQ configuration.

Rotate keys on a defined schedule and remove unused keys immediately.

Validation workflow

1. Test the integration with the minimum required permissions.
2. Confirm logs do not print the access key descriptionor that you specify. When you are finished, choose Create accesssecret.
3. Document key. owner, purpose, creation date, rotation date, and AWS account.

OnDisable the Retrievekey access keys page, choose either Show to revealif the valueintegration ofis your user's secret access key,retired or Downloadreplaced .csv file. This is your only opportunity to save your secret access key. After you've saved your secret access key inby a securerole-based location, choose Done.

method.

For more details see the Amazon AWS documentation: Managing access keys for IAM users - AWS Identity and Access Management (amazon.com)