When an AWS account is created, you are signed-in as a root user (a single sign in entity) with unrestricted access to the subscribed AWS services, using an email and password unique to your organization. As a best practice, avoid using the root user account for basic tasks. Use Identity and Access Management (IAM) credentials to authorize OpsRamp to manage your resources.

Install the AWS integration on the OpsRamp console using Identity and Access Management (IAM) by granting access through AssumeRole with External ID. IAM is a web service that helps in securely controlling access to AWS services. For more information, see What is IAM?

External ID is a set of temporary security credentials to access AWS resources using the OpsRamp account. The External ID option aligns with AWS best practices that recommend not to share the static AWS credentials (Access ID and Secret Key) and also addresses the confused deputy problem.

With External ID with Identity and Access Management (IAM) you can permit a role to be assumed (Role ARN) only under specific circumstances. With External ID and Role ARN, you are assured that only OpsRamp assumes a predefined role and manages your resources. The External ID option automatically adds a condition to the trust policy that allows OpsRamp to assume the role only if the request includes the correct External ID. For more information, view How to use an External ID when granting access to your AWS services to a third party.


Process Flow - Installing AWS integrations with IAM AssumeRole and External ID credentials

OpsRamp configuration

To install AWS integration with IAM AssumeRole and External ID credentials:

To configure AWS integration using IAM AssumeRole and External ID:

Get External ID from OpsRamp console.

  1. Go to Setup > Integrations > Integrations.

  2. Click All Clients and from the drop-down list, select a client.

  3. From the Available Integrations page, click Public Cloud and click AWS.

  4. Click Install.

  5. On the Install AWS Integration page:

    • Name: Give a suitable name for the integration.

    • Region(s): Select the AWS region from the drop-down list. The services that belong to the selected region are onboarded.

      You can select multiple regions to onboard the services. If you select two regions A and B, and if you are not authorized to access region B, onboarding fails for both regions A and B.

    • AWSType: Select External ID.

      Your AWS account number and External ID are automatically populated. Copy the account number and External ID in a text editor such as Notepad. You need these details to create a role in the AWS console.

    • AssumeRole ARN:

      The AssumeRole ARN is generated only after creating the role. To enter the ARN in this field, navigate to your AWS account and do the actions described in Step 2.

Do not close the console window.

AWS configuration

Create AssumeARN Role in AWS Console.

  1. Log into your AWS management console.
  2. Navigate to IAM > Roles > Create Role.
    The Create Role window opens.
  3. Click Another AWS account from the options and enter your AWS Account ID.
  4. Select the option Require External ID and enter the External ID (copied from the OpsRamp console in Step 1).
  5. Click Next: Permissions.
  6. Click Create Policy.
  7. On the Create Policy page, click the JSON tab and paste the policy snippet given in the Appendix.
    To learn more about permission policy, refer to Creating IAM Policies (console).
  8. Click Review Policy and give a suitable name to the policy.
  9. Review the role and click Create role.
    The details of the role created are displayed.
  10. Copy the Role ARN at a safe location in a text editor such as Notepad.

OpsRamp configuration

Complete installing the AWS integration in the OpsRamp console.

After you get the credentials from the AWS console, navigate back to the already open OpsRamp console.

  1. Enter the Role ARN (copied from the AWS console) in the AssumeRole ARN field.
  2. Click Install. The AWS icon is displayed in the list of installed integrations with the details such as installed time, installed by, and enable status.
  3. Click the AWS icon. The AWS integration page opens and the credentials and discovery profiles are displayed.

Appendix: Example AWS access permission policy

"Version": "2012-10-17",
	"Statement": [{
		"Effect": "Allow",
		"Resource": "*",
		"Action": [