To establish integration with AWS, configure the following connectors, flows, and connector targets. You need to set up tenant level configurations. BMC Helix Multi-Cloud Service Management provides out-of-the-box mappings and application level configurations required for the integration. After you complete the integration, you can broker tickets from Remedy ITSM to AWS, sync AWS ticket details to Remedy ITSM and so on. Each flow in the list of flows is essentially a feature that you can use. Depending upon your use case, you might have to configure multiple flows. BMC Helix Multi-Cloud Service Management logically chains the flows and connector processes to complete the feature.
List of connectors and configuration values for integration with AWS
You must configure the following connectors when setting up integration with AWS. These connectors are integration points for the respective applications. For instance, to send the data from BMC Helix Multi-Cloud Service Management to AWS, you need to configure a flow from Multi-Cloud connector to AWS connector.
ITSM connector
Configuration
If you are integrating BMC Helix Multi-Cloud Service Management with an on-premises instance of Remedy ITSM, enter the following values:
| |
---|
| Select the site that you created for Remedy. |
| Enter the name of your on-premises AR System server. |
| Enter the port number for your on-premises AR System server. |
- Account
Add a Remedy ITSM user account that has permissions to view business service requests and permissions to update incidents, change, or problem requests.
Multi-Cloud connector
- Configuration
While activating BMC Helix Multi-Cloud Service Management, BMC configures the Multi-Cloud connector. Do not modify the default Multi-Cloud connector configuration.
Account
BMC sets up the account for the Multi-Cloud connector.
Click
to re-authenticate after you have changed the password for your tenant administrator user account in BMC Helix Innovation Studio.
For information about changing the user password, see Creating or modifying Person data.
AWS connector
Not applicable
Ensure that you have an AWS access key before you set up your AWS connector. For more details, see AWS documentation.
Enter the following when you click Add Account:
- AWS access key id
- AWS access key secret
SMTP Email connector
Configuration
To send email notifications for errors, specify values for the following fields:
| |
---|
| Enter a name for the connector configuration. |
| Select the appropriate site for your email server. |
| Select the type of connection for your email server. |
- Account
Add an email account to be used for sending error notifications
.
List of flows and configuration values for integration with AWS
You can configure the following flows when setting up integration with AWS. Each flow is self descriptive, for example to create an incident from Remedy ITSM to AWS, you must configure Create Brokered Incident flow.
Create Brokered Incident flow
- Trigger
Specify the name of the Remedy business service for incident brokering in the Service field. Incidents will not be brokered as expected if you do not specify the Service.

Note
The business service is the Technology Provider value that you specified when you configured the vendor data.
Field Mapping
Do not change the following out-of-the-box field mappings.
Note
You can change the following out-of-the-box field mappings:
However, BMC recommends that you retain the existing mappings. If you change the Priority field mapping, you need to set the transformations for source and target field values in the flow.
Create Incident Activity Note flow
Field Mapping
Do not change the following out-of-the-box field mappings.
| |
---|
| |
| |
| |
Attachment Object 1.content | |
| |
Attachment Object 2.content | |
| |
Attachment Object 3.content | |
Note
You can change the out-of-the-box field mapping for the text field. Default value is set to Notes.
However, BMC recommends that you retain the existing mapping.
Create Incident Activity Note with Author flow (Remedy 9.1.06 or later)
Field Mapping
Do not change the following out-of-the-box field mappings.
| |
---|
| |
| |
| |
| |
Attachment Object 1.content | |
| |
Attachment Object 2.content | |
| |
Attachment Object 3.content | |
Note
You can change the out-of-the-box field mapping for the text field. Default value is set to Notes.
However, BMC recommends that you retain the existing mapping.
By default, the Create Incident Activity Note flow is used. Instead of the default flow, if you want to use the Create Incident Activity Note with Author flow, you must make changes to the flow.
For more information about using the flow, see Updating flows.
Resolve Incident flow
Trigger
| |
---|
| Specify the name of the Remedy Business Service for incident brokering in the Service field: . Note: Business Service is the value that you provide when specifying the Technology Provider while configuring vendor data |
| Set status to one of the following values: |
Field Mapping
Do not change the following out-of-the-box field mappings.
Send Error Notification flow
Field Mapping
| |
---|
| Enter the email account that will receive the error notification. |
| |
From Note: The value of this field is set to Integration Service. | |
Note
You can change the following out-of-the-box field mappings:
However, BMC recommends that you retain the existing mappings.
List of connector targets for integration with AWS
When a ticket is brokered from AWS to Remedy ITSM, the ticket data first comes in BMC Helix Multi-Cloud Service Management before being sent to Remedy ITSM. To send the data from BMC Helix Multi-Cloud Service Management to Remedy ITSM, you must configure the MCSM Remedy ITSM connector target and set it in the Connector Process Remedy ITSM. Similarly, when a ticket is brokered from Remedy ITSM to AWS, the ticket data first comes in BMC Helix Multi-Cloud Service Management before being sent to AWS. To send the data from BMC Helix Multi-Cloud Service Management to AWS, you must configure the MCSM AWS connector target and set it in the Connector Process AWS.
MCSM Remedy ITSM connector target
For the MCSM Remedy ITSM connector target, define the connection configuration and profile required by the connector process.
MCSM AWS connector target
For the Connector Targets, define the connection configuration and profile required by the connector process in BMC Helix Platform.