Setting up Insight AWS integration

Still need help?

The Atlassian Community is here for you.

Ask the community

Here's some info on setting up the Insight AWS integration.

Before you begin

To use this integration, you need:

  • Jira (Core, Software, Service Management)
  • Insight

Download and install Insight AWS Integration

Download the latest version from Atlassian Marketplace.

Setting up Insight

You need to configure an import configuration in Insight. For more info, see Importing AWS data into Insight.

Setting up AWS

Complete these steps to obtain the IAM key, secret, and other details needed for your Insight configuration.

1. Create an IAM user for importing

To create the user and obtain the required key and secret, see AWS Documentation Guide.

2. Create an import policy

  1. Create a policy.
  2. Select JSON and paste the JSON text from the following file: Insight_Import-Policy-Permissions.json
  3. Save the policy, for example as "Insight import permissions". 

    Remember that you need to update the policy when we adding new service support.

    The have added the date of the policy as Sid in the JSON Text.

3. Assign the policy to the IAM user

Assign the policy to the user you created for importing.

4. Create an SSM policy and role

To get detailed attributes for the EC2 instance, you need to have the SSM-Agent installed on the EC2 instance and create an SSM role and attach them to your instances.

  1. Create a policy.
  2. Select JSON and paste the JSON text from the following file: SSM-Role-Policy-Permissions.json
  3. Save the policy, for example as "Insight SSM role".
  4. Change the Trusted Relationships for the role to the following JSON: SSM-Role-Trust-relationships.json

If the Agent isn't available or the role isn't assigned, the information specified in SSM instance details below won't be imported.

For more information about SSM, see AWS-SSM-Documentation.

SSM instance details

When you have configured the SSM role as described above, the Insight AWS integration can execute the following commands on your EC2 instance and receive data.

This requires:

  • SSM agent being installed on the EC2 instance
  • SSM role being assigned

For Linux system that don't have the dmidecode installed, the attribute values that need it will not be available.

Windows commands

Instance attributeWindows command
PlatformName
PlatformType
Hostnamehostname
RamGet-WmiObject Win32_PhysicalMemory | select Capacity"
ModelGet-WmiObject Win32_ComputerSystem | select Model
Serialnumber

Get-WmiObject Win32_BIOS | select SerialNumber

UUID

Get-WmiObject Win32_ComputerSystemProduct | select UUID

Vendor

Get-WmiObject Win32_ComputerSystemProduct | select Vendor

SystemUpTime

(Date)-([Management.ManagementDateTimeConverter]::ToDateTime((gwmi Win32_OperatingSystem).LastBootUpTime))

OS

Get-WmiObject Win32_OperatingSystem | select Caption, Manufacturer, OSArchitecture, Version, BuildNumber, ServicePackMajorVersion, ServicePackMinorVersion | Format-List

Cpus

Get-WmiObject Win32_Processor | select Caption, Name, DeviceID, NumberOfCores, MaxClockSpeed | Format-List

UNIX commands

Instance attributeUNIX command
PlatformName
PlatformType
Hostnamehostname
Ramegrep '^MemTotal' /proc/meminfo
Modeldmidecode | grep 'Product'
Serialnumber

dmidecode | grep 'Serial Number'

UUID

dmidecode | grep 'UUID'

Vendor

dmidecode | grep 'Manufacturer'

SystemUpTime

uptime -p

OS

uname -o -r -i -m && cat /etc/*release

Cpus

egrep '^(model name|cpu MHz|[pP]rocessor|physical id|cpu cores)' /proc/cpuinfo

Last modified on Feb 17, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.