Skip to content
  • There are no suggestions because the search field is empty.

Integrations : Cloud : AWS

Adding the Amazon Web Services (AWS) Integration and Its Associated Insights

Overview

The AWS connection in Block 64 enables secure access to your AWS resource inventory and cost data.

Because this is a customer-managed integration, you control the AWS access configuration by creating and managing the necessary roles and permissions in your own AWS account.

Once connected, the data collected from this integration appears in the following Block 64 Insights reports:

  • Reports → Public Cloud → Overview – Summary of AWS resources and environment details.

  • Reports → Public Cloud → Compute – Inventory and configuration of EC2 instances.

  • Reports → Public Cloud → Database – Details on RDS instances and other AWS database services.

    • Also used as a source of Azure/Microsoft costs for Compute and Database reporting.

The credentials needed for this Integration

To set up this integration, you’ll need:

  • An AWS account with permissions to create IAM roles and policies.

  • AdministratorAccess (or equivalent permissions) to configure cross-account access for Block 64.

  • Access to AWS Management Console and the ability to follow the role setup instructions in the Block 64 guide.

How to add this Integration

  • Review the full setup guide here: Granting Access to Your AWS Account for Data Inventory

  • In your AWS Management Console, create a new IAM role for Block 64 using the trust policy and permissions detailed in the guide.

  • Copy the Role ARN generated during the setup.

  • In the Block 64 Insights portal, go to Integrations → AWS. 

  • Enter the email address, Role ARN, and AWS regions.

  • Click Connect.
Block 64 will use the cross-account role to collect read-only inventory and cost data.

Why is this Integration failing?

If the integration isn’t working, it’s usually because the IAM role or policy in AWS has been modified, deleted, or does not include the required permissions. It may also fail if the trust relationship is misconfigured or if the Role ARN in Block 64 does not match the role in AWS.
To resolve:

  • Confirm the IAM role and trust policy match the Block 64 setup guide.

  • Ensure the role includes the required read-only permissions for EC2, RDS, and cost data.

  • Verify the Role ARN entered in Block 64 is correct and active.

How to remove this Integration

From Block 64:

You can disable this integration temporarily by clicking on the Enable switch in the integration.

Alternatively, you can disconnect the integration entirely by clicking on the Disconnect button.

 From AWS:

  1. Sign in to the AWS Management Console.

  2. Open the IAM service.

  3. Locate and delete the IAM role created for Block 64.

  4. Remove any associated IAM policies if they were created specifically for this integration.