Skip to main content

​
Overview

The AWS integration allows administrators to connect AWS accounts to G360. Once configured, G360 securely connects to your AWS environment and collects cloud infrastructure and operational metrics for analysis and reporting.

​
Prerequisites

Before creating a connection, ensure you have:
  • An AWS account and access to the AWS Management Console
  • Permission to create or view IAM Roles and IAM Users
  • An IAM Role or an IAM User with the permissions G360 needs to collect AWS metrics
If your organization manages AWS centrally, contact your AWS administrator for these credentials or the permissions to create them.

​
Access AWS Connections

  1. Log in to G360.
  2. From the left navigation panel, click Integrations.
  3. Scroll down to Cloud Provider Metrics Integrations.
  4. Click Connect on the AWS Connections card.
  5. Click Add Connections button.
Each row also includes a View Data Scopes button, which shows the metrics and resource scopes currently being collected for that connection. Use the search bar at the top of the page to find a connection by name.

​
Prepare AWS credentials

G360 authenticates to AWS using either an IAM Role (assumed via its ARN) or an IAM User’s access keys — never both. Pick the method that matches how your organization manages AWS access, and complete only the steps for that method.
1

Sign in to AWS

Open the AWS Management Console and sign in with your AWS account.
2

Note the AWS Region

Copy the Region that contains the resources you want G360 to monitor. It’s shown in the upper-right corner of the console, for example us-east-1.
3

Choose an authentication method

G360 supports two ways to connect: an IAM Role, or an IAM User’s access keys. Complete either Step 4 (Role) or Step 5 (access key) below — not both.
4

Option A — IAM Role

Search for IAM in the console, open Roles, and create a new role (or use one your organization has already created for G360). Open the role and copy its ARN, for example arn:aws:iam::123456789012:role/G360MonitoringRole.
5

Option B — IAM User access key

In IAM → Users, create or select a user and generate a new access key. AWS returns an Access Key ID and Secret Access Key.
If using an access key (Option B), note that AWS shows the Secret Access Key only once. Copy it immediately and store it securely — if it’s lost, you’ll need to generate a new access key.

​
Create a connection

  1. In G360, go to Cloud Provider Metrics → AWS Connections.
  2. Click Add Connection.
Use the Active toggle to control whether G360 starts collecting metrics as soon as the connection is saved. Disabled connections are saved but collect no metrics until enabled.

​
Test and save

  1. Click Test Connection. G360 calls AWS’s sts:GetCallerIdentity using the credentials you provided — either assuming the Role ARN or authenticating with the Access Key ID and Secret Access Key — to confirm the credentials are valid. A successful call is also a good sign the Region is reachable, though this isn’t something Test Connection explicitly checks. Test Connection does not confirm that the IAM Role or User has the permissions G360 needs to collect metrics; a missing-permissions issue will only surface once metric collection actually runs.
  2. Click Save Connection.
Test Connection and Save Connection aren’t enforced in sequence in the UI — you can click Save Connection without running Test Connection first. Testing before saving is still recommended, since it’s the only way to catch invalid credentials before the connection goes live.
The connection now appears in the AWS Connections dashboard. If Active is enabled, metric collection begins immediately.

​
Manage connections

Click the Edit icon under Actions, update the fields, then Test Connection and Save Connection. Changes take effect immediately.
Click the Delete icon under Actions and confirm. This removes the integration and stops future metric collection for that account.
Active connections collect metrics on an ongoing basis. Inactive connections stay configured but collect nothing until re-enabled.

​
Troubleshooting

  • Re-check the Access Key ID and Secret Access Key, if that’s your authentication method
  • Confirm the IAM Role ARN is valid and belongs to the correct account, if that’s your authentication method
  • Confirm you haven’t entered both a Role ARN and access keys — use only one method
  • Verify the Region and, if used, the External ID
  • Confirm the IAM User or Role hasn’t been deleted or disabled
  • Confirm the connection is Active
  • Confirm the credentials haven’t expired
  • Confirm the IAM Role or User has the required permissions — this isn’t checked by Test Connection
  • Confirm the Region is correct and the expected resources exist there
  • Confirm all required fields (marked *) are filled in
  • Confirm you’ve entered either a Role ARN or an Access Key ID and Secret Access Key, not both
  • Confirm the IAM Role and IAM User still exist in AWS

​
Best practices

  • Use a dedicated IAM Role for G360 instead of sharing administrator credentials
  • Grant only the permissions required for metric collection
  • Store access keys securely and rotate them periodically
  • Use descriptive connection names that identify the AWS environment
  • Test every connection before saving it
  • Disable unused connections instead of deleting them if they may be needed again
  • Review IAM permissions regularly to keep access to the minimum required