Blog

How to Connect Fullon Pulse to Amazon Connect Using an IAM Role

Fullon Pulse connects to Amazon Connect through an IAM role created in the customer's AWS account with the required read permissions. Your AWS team configures the access; the integration does not require handing over long-term AWS access keys.

The setup brings together two groups: the people responsible for the AWS environment and the people who will use the queue information. Preparing both sides helps the connection lead to a useful operational view.

This guide explains the sequence and checks. Use the current Fullon Pulse onboarding instructions for the exact policies and connection values.

1. Identify the environment and the owners

Confirm which Amazon Connect instance should be connected and who is authorized to configure IAM access in its AWS account.

Have the AWS account, Region, and instance details available. Nominate the person who will complete the Fullon Pulse side of onboarding and a supervisor who can validate the resulting queue view.

Agree on the initial scope: the queues to review, the users who need access, and whether the first rollout includes wall displays, browser access, or mobile apps.

2. Obtain the current onboarding configuration

Request the current Fullon Pulse instructions, including the required permissions policy, trusted AWS principal, and any required external ID or other trust conditions.

Do not infer these values from an example found elsewhere. The permissions determine what the integration can read, while the trust configuration determines who can assume the role.

Apply the exact values from your Fullon Pulse onboarding materials, including the external ID if required.

3. Have your AWS team create and review the role

The authorized administrator creates the IAM role using the supplied configuration and reviews it against your organization's access requirements.

Use the permissions required for the integration. If a connection problem appears later, investigate the failing requirement rather than broadening access to an administrator policy as a shortcut.

Keep a record of the role's purpose and owner so that it can be maintained alongside your other third-party integrations.

4. Complete the Fullon Pulse connection process

Provide the role ARN and the other values requested by the current Fullon Pulse onboarding process. The exact fields and interface may change, so follow those instructions rather than relying on a generic screen sequence.

If the connection cannot be established, check the selected account and instance, the role identifier, the trust configuration, and the required permissions with the administrator.

Where an external ID is required, verify that the value matches the onboarding configuration exactly.

5. Validate the operational view

Once connected, ask the nominated supervisor to confirm that the expected queues are present and recognizable. Compare selected values with the corresponding Amazon Connect view using matching scope and timing where possible.

Fullon Pulse refreshes its displayed information every ten seconds. Individual metrics may update at different times, so check the field definitions and report settings if you notice persistent discrepancies.

Use our real-time metrics guide to structure that review.

6. Complete the operational handover

Set up the intended user access, agree who owns the daily monitoring routine, and verify each display or device included in the rollout.

If you enable alerts, document the selected conditions and response owners. Test the configuration through an approved process and make sure the team knows where to ask for help.

The technical connection is one part of readiness. A clear view, understood metrics, and named owners make it useful during a working shift.

Read our wallboard guide to plan the display, or visit Fullon Pulse for current onboarding information.