Overview
Use OneIQ Pulse for AWS to connect each AWS region to your IT environment in OneIQ. The connector is deployed using an AWS CloudFormation stack, which provisions an EC2 instance, a small EBS volume, a security group with no inbound rules, and the required IAM role and instance profile with read-only permissions. The EC2 instance receives a public IP address for outbound connectivity only. OneIQ Pulse only requires outbound HTTPS (port 443) access to OneIQ and AWS; no inbound connections to the instance are required, and the SSH service is disabled.
Connectors deployed on or before October 26, 2026 may include an inbound SSH rule that is no longer required. See Removing the Inbound SSH Rule from Existing Cloud Pulse Connectors.
Once active, Pulse collects configuration, performance, and billing data from supported AWS services (EC2, EBS, and RDS) and securely sends it to the OneIQ Portal. With this data you can:
Optimize AWS spend by right-sizing EC2 instances with OneIQ Insights.
Understand dependencies among AWS and other workloads across Hybrid IT.
Identify cost-saving opportunities to repatriate workloads from AWS to the datacenter.
The connector can monitor a single AWS region or multiple regions by setting the TargetRegions parameter during deployment.
Supported services
OneIQ Pulse supports capturing billing, configuration and performance metrics for:
Prerequisites
An AWS account with permission to create CloudFormation stacks, EC2 instances, security groups, and IAM roles and instance profiles.
A default VPC in the region where you deploy the connector. The connector is launched into the default subnet of the Availability Zone you select, so that subnet must assign public IP addresses and have a route to the internet.
Outbound HTTPS (port 443) internet access from that subnet. The connector downloads its software packages during deployment and sends data to OneIQ after that.
Download OneIQ Pulse for AWS
Log in to the OneIQ Portal.
Select IT Environments in the left navigation menu and go to the Connectors tab.
Select Amazon Web Services as the platform to connect.
In Connect your AWS cloud, specify a name for the OneIQ Pulse for AWS connector to distinguish it from other connectors in your IT environment (for example, the AWS region name).
Click Download to save the OneIQ Pulse CloudFormation manifest. The manifest is saved as a .1iq file named after your connector and IT environment (for example, AWS-OneIQ-US-EAST-1(MyITE).1iq). This is the file you upload as the stack template in the next section.
Deploy OneIQ Pulse into AWS
Log in to the AWS CloudFormation console and select the region where you want to deploy the connector.
Create a new CloudFormation stack (you can also use the AWS CLI).
Select Create stack with new resources (standard).
Under Specify template, select Upload a template file, choose the downloaded OneIQ Pulse CloudFormation manifest as the stack template, and click Next.
Enter a Stack name (for example, oneiq-pulse-us-east-1).
Under Parameters, enter the following and click Next:
AvailabilityZone (required): the Availability Zone to deploy the connector into.
InstanceType: the EC2 instance type for the connector. The default, t3a.small, is recommended.
TargetRegions: the AWS regions to collect data from. Leave blank to collect data only from the region where the stack is deployed. See Profiling multiple AWS regions below.
LatestAmiId: leave the default value.
OneIQPulseITEId: pre-filled with your IT environment ID. Do not change it.
On the Configure stack options page, keep the default settings. Under Capabilities, select I acknowledge that AWS CloudFormation might create IAM resources, and click Next.
On the Review and create page, check the following before you continue:
Template: the Template URL ends with the name of the manifest you downloaded. CloudFormation stores uploaded templates in an S3 bucket in your account (named cf-templates-...), so this bucket may be created automatically.
Stack name: the name you entered.
Parameters (5): AvailabilityZone, InstanceType, and TargetRegions show the values you entered, and OneIQPulseITEId has not been changed.
To change anything, click Edit next to that step. When everything is correct, scroll to the bottom of the page and click Submit.Wait for the stack status to change to CREATE_COMPLETE. This usually takes a few minutes. If OneIQ Pulse does not start within 5 minutes, the stack is rolled back; check the stack's Events tab for the reason. The most common cause is the instance not having outbound internet access.
In the OneIQ Portal, go to IT Environments > Connectors. The new connector is listed under the name you entered in Connect your AWS cloud. Once OneIQ Pulse is sending data, the connector shows a green status with Data since and the date data collection started.
Profiling multiple AWS regions
To profile multiple target regions, enter a space-delimited list of AWS regions in the TargetRegions field. If TargetRegions is left blank, Pulse collects data only from the region where the stack is deployed.
For example:
us-west-2 us-east-2
Updating and removing OneIQ Pulse for AWS
OneIQ Pulse for AWS keeps itself up to date by updating its own CloudFormation stack. No action is required, and the stack resources should not be modified manually.
To remove the connector, delete its stack in the AWS CloudFormation console. This removes the EC2 instance, EBS volumes, security group, and IAM role and instance profile.
Enable AWS Cost and Usage report
OneIQ can correlate application and infrastructure costs using billing data from AWS Cost and Usage Reports (CURs). See Collecting Billing Data from Amazon Web Services for instructions on enabling CURs.
Enable Network Flows in AWS
OneIQ Pulse for AWS can capture flow logs from Amazon VPCs, VPC subnets, or Elastic Network Interfaces (ENIs). To enable this, follow the AWS documentation for VPC Flow Logs – Log and View Network Traffic Flows.