What you'll see
- The ticket, before OnLink — “I think it’s one of the frontend boxes in prod”, and the agent goes hunting across AWS accounts and Regions.
- Picking the exact instance from Assets — the Assets field lists real EC2 instances by Name tag, with their account and Region, filtered as you type.
- What the agent sees on the ticket — the AWS account, account ID, Region, environment and team tags, account state and when AWS last saw the instance.
- How the data gets there — a read-only IAM key, ListAccounts and ListResources, and linked Assets objects.
Notes from the video
In this 30-second demo, a requester picks the exact EC2 instance on a Jira Service Management request, and the agent sees its AWS account, Region and tags right on the ticket. OnLink reads accounts from AWS Organizations and instances from AWS Resource Explorer, across every account and Region in one call, and writes them into Assets object types linked by account.
Setup takes a read-only IAM user with Resource Explorer search and Organizations list permissions. The AWS to Assets setup guide has the IAM policy, sample responses, mappings and troubleshooting.
The demo uses example data.
Read the full walkthrough
Setup, object mapping, filters and FAQ · 5 min read