Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

OMi Management Pack for Amazon Web Services1.30

Install > Configure OMi MP for AWS

Configure OMi MP for AWS

Deployment Overview

OMi MP for AWS is installed as an add-on content on OMi. A node must be installed with Operations Agent and configured as a managed node with capabilities to connect to the AWS account through the Internet. Single managed node can monitor multiple AWS accounts.

OMi MP for AWS consists of the AWS Discovery Aspect which contains required parameters, AWS Access Key and AWS Secret Key, to connect to the AWS account. Specify the values for these parameters in the AWS Discovery Aspect and deploy the Aspect to the managed node to discover information about the EC2 instances associated with the AWS account. It also collects details about the regions associated with the EC2 instances. The EC2 instance does not require Operations Agent, but the proxy node must have Operations Agent installed.

The following section provides information about the tasks required to monitor AWS in your environment.

Add nodes and deploy AWS discovery aspect

Task 1: Adding Nodes to the OMi Console

Note If the node already exists in RTSM, you can skip this step and proceed to Task 2.

Before you begin monitoring, you need to add the nodes to the OMi console.

Open the Monitored Nodes pane:

Click Administration > Setup and Maintenance > Monitored Nodes.
In the Node Views pane, click Predefined Node Filters > Monitored Nodes, click New Node and then select Computer > <Select the relevant OS type>.

The Create New Monitored Nodes dialog box appears.
Specify the Primary DNS Name, IP address, Operating System, and Processor Architecture of the node and click OK.
The newly created node is saved as a Configuration Item (CI) instance in Run-time Service Model (RTSM).
You must activate the managed node with Operations Agent on OMi server and grant certificate.

Task 2: Deploying the AWS Discovery Aspect

To discover the AWS EC2 instances on the AWS, you must deploy the AWS Discovery Aspect on the managed node:

Open the Management Templates & Aspects pane:

Click Administration > Monitoring > Management Templates & Aspects.
In the Configuration Folders pane:

Click Configuration Folders > Cloud Management > AWS > AWS Aspects.
In the Management Templates & AWS Aspects pane, click the AWS Discovery Aspect that you want to deploy, and then click Assign and Deploy Item. The Assign and Deploy Item wizard opens.
In the Configuration Item tab, select the computer CI to which you want to deploy the AWS Discovery Aspect and then click Next. The Required Parameters tab opens.
In the Required Parameters tab, specify the mandatory parameters - AWS AccessKey and AWS SecretKey. Make sure AWS AccessKey and AWS SecretKey have required privileges mentioned in the prerequisite.

To specify the required parameters, follow these steps:
1. Select the AWS AccessKey parameter in the list, and then click . The AWS Access Key dialog box opens.
2. Click Value, specify the value, and then click OK.
3. Select the AWS SecretKey parameter in the list, and then click .The AWS SecretKey dialog box opens.
4. Click Value, specify the value, and then click OK.
5. Click Next.
In the Parameter Summary tab, you can change the default values of the any parameters. If multiple subscriptions are required to be monitored, then add new instance of AWS AccessKey to specify corresponding dependent parameters.
1. Select the HTTP Proxy of Host parameter and then click . The Edit Instance Parameter window appears.
  
  You must specify the HTTP Proxy of Host if your managed node is configured with a proxy Internet connection.
2. Click Value, specify the value, and then click OK.
3. Select the HTTP Proxy Port of Host parameter and then click .
  
  The Edit Instance Parameter window appears. You must specify the HTTP Proxy Port of Host if your managed node is configured with a proxy Internet connection. By default, the port is 8080.
4. Click Value, specify the value, and then click OK.
Click Next to go to the Configure Options tab.
(Optional). If you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box. You can enable the assignment later using the Assignments & Tuning pane.
Click Finish.

After the AWS Discovery Aspect is deployed, a message stating the Assignment and deployment jobs created appears. To check the status of the deployment jobs, go to Administration > Monitoring > Deployment Jobs.

Task 3: Verifying Discovery

After you deploy the AWS Discovery Aspect, you must verify if the CIs are populated in the View Explorer.

To view the CIs populated, follow these steps:

Open the Event Perspective pane:

Click Workspaces > Operations Console > Event Perspective.
In the View Explorer, select AWS_EC2 or AWS_ECS_Region view from the drop-down list to see the associated CIs.

AWS_EC2

AWS_ECS_Region

Task 4: Deploying OMi MP for AWS Aspects

Data for EC2, ECB or EBS is collected when respective aspect is deployed.

OMi MP for AWS contains the following out-of-the-box aspects:

Aspects	Method of deployment
AWS CloudWatch Log	Modify the AWS_CloudWatchLogConfig policy and then deploy the latest version of Aspect.
EC2 Instance Health	Enable the auto-assignment rule or deploy the Aspect.
AWS Service Health	Modify the AWS_ServiceHealthURLConfig policy and then deploy the latest version of Aspect.
AWS EBS Health	Enable the auto-assignment rule or deploy the Aspect.
AWS ECS Health	Deploy the aspect to Computer CI.

Enabling the Automatic Assignment Rules

Automatic Assignment Rule is created for EC2 Instance Health Aspect to start monitoring every new instance of AWS that is discovered. By default, the data collection frequency is set to 5 minutes. You can modify the collection frequency or any other parameter to a create new automatic assignment rule.

To deploy the Automatic Assignment Rule for the AWS_EC2 Instance on a managed node, follow these steps:

Open the Auto-Assignment Rules pane:

Click Administration > Monitoring > Automatic Assignment Rules.
In the Auto-Assignment Rules pane, select the AWS_EC2 > EC2 Instance Health or AWS EBS Health under the Assigned Item column and click Activate.

Verifying Automatic Assignment Rules

You can check if the automatic assignment rule is successfully created with the expected assignments as follows:

Open the Assignments & Tuning pane:

Click Administration > Monitoring > Assignments & Tuning.
In the Browse Views tab, select the view you identified when creating your automatic assignment rule.
Select the specific managed node on which Auto-Assignment was deployed, from the list associated with AWS_EC2 Instances.
In the Assignment table, the EC2 Instance is displayed in the Assigned Item column. The value in the Assigned By column displays AutoAssignment.

You can consider the following options for tuning the assignment:

Use the Auto-Assignment Rules pane to tune the parameter values for all assignments triggered by the automatic assignment rule.
Use the Assignments pane to tune, redeploy, delete, and enable or disable individual assignments.

Configure the AWS CloudWatch Log Aspect

You can monitor account for the log files. You can drill-down to specify the particular stream in specific zone in any region. Modify the AWSCloudWatchLogConfig policy and then deploy the latest version of Aspect.

Follow the steps to edit and deploy:

Open the Management Templates & Aspects pane:

Click Administration > Monitoring > Management Templates & Aspects.
In the Configuration Folders pane:

Click Configuration Folders > Cloud Management > AWS > AWS Aspects.
In the AWS Management Templates folder, click AWS CloudWatch Log Aspect and then click .

The AWS CloudWatch Log: Edit Aspect window appears.
In the Policy Template tab, select the AWSCloudWatchLogConfig policy and click Edit Policy Template (Raw Mode).

The Edit Policy Template window appears.
In the Policy Data tab, specify the Account, region, zone, and stream that you need to monitor. By default, all accounts that are discovered are monitored. If you require to monitor specific account, region, zone or stream, then uncomment the required block and modify the policy with following syntax.
```
<Accounts>
  <accessKey>accessKey</accessKey>
  <Region>
 	<regionId>regionId</regionId>
	<logGroup>
	   <groupName>groupName</groupName>
	   <logStreamName>logStreamName</logStreamName>
	</logGroup> 
  </Region>
</Accounts>
```
If only accessKey value is provided in the Account block, then all the regions, groups and streams available under that account are monitored. If accessKey and regionId are specified, then all the groups and streams under that region are monitored. If accessKey, regionId, and groupName are specified, then all the log streams are monitored.

You can specify multiple accounts by repeating the Account block. Accordingly, for specifying multiple regions, groups or log streams, repeat the respective block.
Click Save and Close. New version of policy is created.
In the Management Templates & Aspects pane, select the AWS CloudWatch Log Aspect and click .
In the Policy Templates tab, select the latest version of AWS_CloudWatchLogConfig policy and click OK.
In the Management Templates & Aspects pane, select the latest version of the Aspect and click .
In the Configuration Item tab, select the CI and click Next.
In the Parameter Summary tab, click Finish.

Editing the AWS Service Health Aspect (Optional)

To monitor specific regions that appear in the AWS Service Health Dashboard in the AWS console, you must edit the AWS Service Health Aspect. To edit the Service Health Aspect, follow these steps:

Open the Management Templates & Aspects pane:

Click Administration > Monitoring > Management Templates & Aspects.
In the Configuration Folders pane:

Click Configuration Folders > Cloud Management > AWS > AWS Aspects.
In the AWS Management Templates folder, click AWS Service Health Aspect and then click .

The AWS Service Health: Edit Aspect window appears.
Click Edit Policy Template (Raw Mode).

The Edit Policy Template window appears.
Select the AWS_ServiceHealthURLConfig
Click in the Edit Policy Template (Raw Mode) tab.
Specify the RSS Feed URL for specific service in a region. Remove the # symbol at the beginning of the RSS Feed URL.

You can obtain the RSS Feed URL from the AWS Service Health Dashboard.
Click Save and Close.
Select the latest version of the Aspect and click .
In the Configuration Item tab, select the CI and click Next.
Click Finish.

Send Help Center feedback