# Monitoring AWS media services with workflow monitor
Workflow monitor is a tool for the discovery, visualization, and monitoring of AWS media workflows. Workflow monitor is available in the AWS console and API. You can use workflow monitor to discover and create visual mappings of your workflow's resources, called *signal maps*. You can create and manage Amazon CloudWatch alarm and Amazon EventBridge rule templates to monitor the mapped resources. The monitoring templates you create are transformed into deployable AWS CloudFormation templates to allow repeatability. AWS recommended alarm templates provide predefined best-practice monitoring.
**Discover**
Utilize signal maps to automatically discover interconnected AWS resources associated with your media workflow. Discovery can begin at any supported service resource and creates an end-to-end mapping of the workflow. Signal maps can be used as stand-alone visualization tools or enhanced with monitoring templates.
![\[Workflow monitor discovery components.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/workflowmonitor-discovery.png)
**Monitor**
You can create custom CloudWatch alarm and EventBridge rule templates to monitor the health and status of your media workflows. Best practice alarm templates are available to import into your workflow monitor environment. You can use the best practice alarm templates as they are, or edit them to better fit your workflow. Any templates you create are transformed into CloudFormation templates for repeatable deployment.
![\[Workflow monitor monitoring components.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/workflowmonitor-monitoring.png)
**Note**
There is no direct cost for using workflow monitor. However, there are costs associated with the resources created and used to monitor your workflow.
When monitoring is deployed, Amazon CloudWatch and Amazon EventBridge resources are created. When using the AWS Management Console, prior to deploying monitoring to a signal map, you will be notified of how many resources will be created. For more information about pricing, see: [CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) and [EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/).
Workflow monitor uses AWS CloudFormation templates to deploy the CloudWatch and EventBridge resources. These templates are stored in a standard class Amazon Simple Storage Service bucket that is created on your behalf, by workflow monitor, during the deployment process and will incur object storage and recall charges. For more information about pricing, see: [Amazon S3 pricing](https://aws.amazon.com/s3/pricing/).
Previews generated in the workflow monitor signal map for AWS Elemental MediaPackage channels are delivered from the MediaPackage Origin Endpoint and will incur Data Transfer Out charges. For pricing, see: [MediaPackage pricing](https://aws.amazon.com/mediapackage/pricing/).
## Components of workflow monitor
Workflow monitor has four major components:
+ CloudWatch alarm templates - Define the conditions you would like to monitor using CloudWatch. You can create your own alarm templates, or import predefined templates created by AWS. For more information, see: [CloudWatch alarm groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-alarms.md)
+ EventBridge rule templates - Define how EventBridge sends notifications when an alarm is triggered. For more information, see: [EventBridge rule groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-notifications.md)
+ Signal maps - Use an automated process to create AWS Elemental workflow maps using existing AWS resources. The signal maps can be used to discover resources in your workflow and deploy monitoring to those resources. For more information, see: [Workflow monitor signal maps](monitor-with-workflow-monitor-configure-signal-maps.md)
+ Overview - The overview page allows you to directly monitor the status of multiple signal maps from one location. Review metrics, logs, and alarms for your workflows. For more information, see: [Workflow monitor overview](monitor-with-workflow-monitor-operate-overview.md)
## Supported services
Workflow monitor supports automatic discovery and signal mapping of resources associated with the following services:
+ AWS Elemental MediaConnect
+ AWS Elemental MediaLive
+ AWS Elemental MediaPackage
+ AWS Elemental MediaTailor
+ Amazon S3
+ Amazon CloudFront
**Topics**
+ [Components of workflow monitor](#monitor-with-workflow-monitor-components)
+ [Supported services](#monitor-with-workflow-monitor-supported-services)
+ [Configuring workflow monitor to monitor AWS media services](monitor-with-workflow-monitor-configure.md)
+ [Using workflow monitor](monitor-with-workflow-monitor-operate.md)
# Configuring workflow monitor to monitor AWS media services
To setup workflow monitor for the first time; you create the alarm and event templates, and discover signal maps that are used to monitor your media workflows. The following guide contains the steps necessary to setup both Administrator and Operator level IAM roles, create workflow monitor resources, and deploy monitoring to your workflows.
**Topics**
+ [Getting started with workflow monitor](monitor-with-workflow-monitor-configure-getting-started.md)
+ [Workflow monitor groups and templates](monitor-with-workflow-monitor-configure-templates.md)
+ [Workflow monitor signal maps](monitor-with-workflow-monitor-configure-signal-maps.md)
+ [Workflow monitor quotas](monitor-with-workflow-monitor-configure-quotas.md)
# Getting started with workflow monitor
The following steps provide a basic overview of using workflow monitor for the first time.
1. Setup workflow monitor IAM permissions for administrator and operator level roles: [Workflow monitor IAM policies](monitor-with-workflow-monitor-configure-getting-started-IAM.md)
1. Build alarm templates or import predefined templates created by AWS: [CloudWatch alarms](monitor-with-workflow-monitor-configure-alarms.md)
1. Build notification events that will be delivered by EventBridge: [EventBridge rules ](monitor-with-workflow-monitor-configure-notifications.md)
1. Discover signal maps using your existing AWS Elemental resources: [Signal maps ](monitor-with-workflow-monitor-configure-signal-maps.md)
1. Attach the alarm templates and notification rules to your signal map: [Attaching templates](monitor-with-workflow-monitor-configure-signal-maps-attach.md)
1. Deploy the templates to begin monitoring the signal map: [Deploying monitoring templates](monitor-with-workflow-monitor-configure-deploy.md)
1. Monitor and review your workflow monitor resources using the overview section of the AWS console: [Overview](monitor-with-workflow-monitor-operate-overview.md)
![\[The individual steps of setting up workflow monitor. Begin by creating the IAM roles. Next, create templates for alarms and events. Next, discover a signal map and attach your templates to the map. After a signal map has templates attached, the templates must be deployed. The final step is monitoring using the templates and overview resources.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/workflowmonitor-overview-steps.png)
# Workflow monitor IAM policies
Workflow monitor interacts with multiple AWS services to create signal maps, build CloudWatch and EventBridge resources, and CloudFormation templates. Because workflow monitor interacts with a wide range of services, specific AWS Identity and Access Management (IAM) policies must be assigned for these services. The following examples indicate the necessary IAM policies for both administrator and operator IAM roles.
## Administrator IAM policy
The following example policy is for an administrator-level workflow monitor IAM policy. This role allows for the creation and management of workflow monitor resources and the supported service resources that interact with workflow monitor.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"cloudwatch:List*",
"cloudwatch:Describe*",
"cloudwatch:Get*",
"cloudwatch:PutAnomalyDetector",
"cloudwatch:PutMetricData",
"cloudwatch:PutMetricAlarm",
"cloudwatch:PutCompositeAlarm",
"cloudwatch:PutDashboard",
"cloudwatch:DeleteAlarms",
"cloudwatch:DeleteAnomalyDetector",
"cloudwatch:DeleteDashboards",
"cloudwatch:TagResource",
"cloudwatch:UntagResource"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"cloudformation:List*",
"cloudformation:Describe*",
"cloudformation:CreateStack",
"cloudformation:UpdateStack",
"cloudformation:DeleteStack",
"cloudformation:TagResource",
"cloudformation:UntagResource"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"cloudfront:List*",
"cloudfront:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeNetworkInterfaces"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"events:List*",
"events:Describe*",
"events:CreateEventBus",
"events:PutRule",
"events:PutTargets",
"events:EnableRule",
"events:DisableRule",
"events:DeleteRule",
"events:RemoveTargets",
"events:TagResource",
"events:UntagResource"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"logs:Describe*",
"logs:Get*",
"logs:TagLogGroup",
"logs:TagResource",
"logs:UntagLogGroup",
"logs:UntagResource"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediaconnect:List*",
"mediaconnect:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"medialive:*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackage:List*",
"mediapackage:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackagev2:List*",
"mediapackagev2:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackage-vod:List*",
"mediapackage-vod:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediatailor:List*",
"mediatailor:Describe*",
"mediatailor:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"resource-groups:ListGroups",
"resource-groups:GetGroup",
"resource-groups:GetTags",
"resource-groups:GetGroupQuery",
"resource-groups:GetGroupConfiguration",
"resource-groups:CreateGroup",
"resource-groups:UngroupResources",
"resource-groups:GroupResources",
"resource-groups:DeleteGroup",
"resource-groups:UpdateGroupQuery",
"resource-groups:UpdateGroup",
"resource-groups:Tag",
"resource-groups:Untag"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:*"
],
"Resource": "arn:aws:s3:::workflow-monitor-templates*"
},
{
"Effect": "Allow",
"Action": [
"sns:TagResource",
"sns:UntagResource"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"tag:Get*",
"tag:Describe*",
"tag:TagResources",
"tag:UntagResources"
],
"Resource": "*"
}
]
}
```
------
## Operator IAM policy
The following example policy is for an operator-level workflow monitor IAM policy. This role allows for limited and read-only access to the workflow monitor resources and the supported service resources that interact with workflow monitor.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"cloudwatch:List*",
"cloudwatch:Describe*",
"cloudwatch:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"cloudformation:List*",
"cloudformation:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"cloudfront:List*",
"cloudfront:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeNetworkInterfaces"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"events:List*",
"events:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"logs:Describe*",
"logs:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediaconnect:List*",
"mediaconnect:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"medialive:List*",
"medialive:Get*",
"medialive:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackage:List*",
"mediapackage:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackagev2:List*",
"mediapackagev2:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediapackage-vod:List*",
"mediapackage-vod:Describe*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"mediatailor:List*",
"mediatailor:Describe*",
"mediatailor:Get*"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:Get*",
"s3:List*"
],
"Resource": "arn:aws:s3:::workflow-monitor-templates*"
},
{
"Effect": "Allow",
"Action": [
"tag:Get*",
"tag:Describe*"
],
"Resource": "*"
}
]
}
```
------
# Workflow monitor groups and templates
Before you can deploy workflow monitoring to a signal map, you must create the groups and templates for CloudWatch alarms and EventBridge notifications. The CloudWatch templates define what scenarios and thresholds will be used to trigger the alarms. The EventBridge templates will determine how these alarms are reported to you.
If you only want mappings of your connected resources and do not want to use the monitoring template capabilities of workflow monitor, signal maps can be used without CloudWatch and EventBridge templates. For more information about using signal maps, see: [Signal maps ](monitor-with-workflow-monitor-configure-signal-maps.md)
**Topics**
+ [CloudWatch alarm groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-alarms.md)
+ [EventBridge rule groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-notifications.md)
# CloudWatch alarm groups and templates for monitoring your AWS media workflow
Workflow monitor alarms allow you to use existing CloudWatch metrics as the foundation of alarms for your signal maps. You can create an alarm template group to sort and classify the types of alarming that is important to your workflow. Within each alarm template group, you create alarm templates with specific CloudWatch metrics and parameters that you want to monitor. You can create your own alarm templates or import recommended alarm templates created by AWS. After creating an alarm template group and alarm templates within that group, you can attach one or more of these alarm template groups to a signal map.
You must create an alarm template group first. After you have created an alarm template group, you can create your own templates or use recommended templates created by AWS. If you want to create your own alarm templates, continue on this page. For more information about importing recommended templates, see: [Recommended templates](monitor-with-workflow-monitor-configure-alarms-recommended-templates.md)
This section covers the creation of CloudWatch alarms using workflow monitor. For more information about how the CloudWatch service handles alarms and details of the alarm components, see: [Using CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) in the *Amazon CloudWatch User Guide*
## Creating alarm template groups
Alarm template groups allow you to sort and classify the types of alarms that are important to your workflow.
**To create an alarm template group**
1. From the workflow monitor console's navigation pane, select **CloudWatch alarm templates**.
1. Select **Create alarm template group**.
1. Give the alarm template group a unique **Group name** and optional **Description**.
1. Select **Create**, You will be taken to the newly created alarm template group's details page.
## Creating alarm templates
You can create alarm templates with the CloudWatch metrics and parameters that you want to monitor.
**To create an alarm template**
1. From the alarm template group's details page, select **Create alarm template**.
1. Give the alarm template a unique **Template name** and optional **Description**.
1. In the **Choose metric** section:
1. Select a **Target Resource Type**. The target resource type is a resource for the respective service, such as a channel for MediaLive and MediaPackage or a flow for MediaConnect.
1. Select a **Metric Name**. This is the CloudWatch metric that acts as the foundation for the alarm. The list of metrics will change depending on the selected **Target Resource Type**.
1. In the **Alarm settings** section:
**Note**
For more information about how the CloudWatch service handles alarms and details of the alarm components, see: [Using CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) in the *Amazon CloudWatch User Guide*
1. Select the **Statistic**. This is a value such as a **Sum** or an **Average** that will be used to monitor the metric.
1. Select the **Comparison Operator**. This field references the **Threshold** that you set in the next step.
1. Set a **Threshold**. This is a numeric value that the **Comparison Operator** uses to determine greater than, less than, or equal to status.
1. Set a **Period**. This is a time value, in seconds. The **Period** is the length of time that the **Statistic**, **Comparison Operator**, and **Threshold** interact to determine if the alarm gets triggered.
1. Set the **Datapoints**. This value determines how many datapoints are needed to trigger the alarm.
1. Select how to **Treat Missing Data**. This selection determines how this alarm reacts to missing data.
1. Select **Create** to complete the process.
An example of a completed alarm template could have the following parameters: A MediaConnect flow **Target Resource Type** is monitored for the Disconnections **Metric Name**. The **Statistic** value is set to Sum with a **Comparison Operator** of "greater than or equal to" and a **Threshold** of 10. The **Period** is set to 60 seconds, and only requires 1 out of 1 **Datapoints**. **Treat Missing Data** is set to "ignore."
The result of these settings is: workflow monitor will monitor for disconnections on the flow. If 10 or more disconnections occur within 60 seconds, the alarm will be triggered. 10 or more disconnections in 60 seconds only needs to happen one time for the alarm to be triggered.
# Recommended alarm templates for monitoring your AWS media workflow
Workflow monitor's recommended templates are a curated selection of AWS Elemental service metrics with predefined alarm settings appropriate for the metric. If you do not want to create customized alarm templates, recommended templates provide you with best-practice monitoring templates that are created by AWS.
Workflow monitor contains recommended template groups for each supported service. These groups are designed to apply best-practice monitoring to specific types of workflows. Each template group contains a curated selection of alarms configured from service-specific metrics. For example, a recommended template group for a MediaLive multiplex workflow will have a different set of preconfigured metrics than a MediaConnect CDI workflow.
**To use recommended alarm templates**
1. Follow the steps to [create an alarm template group](monitor-with-workflow-monitor-configure-alarms.md#monitor-with-workflow-monitor-alarms-groups-create), or select an existing one.
1. In the **Alarm templates** section, select **Import**. You will need to import the AWS recommended templates into your template group.
1. Use the **CloudWatch alarm template groups** dropdown to select an AWS recommended group. These groups contain curated alarms for specific services.
1. Select the templates to import using the check boxes. Each template will list its metrics, preconfigured monitoring values, and provide a description of the metric. When you are done selecting templates, select the **Add** button.
1. The selected templates will move to the **Alarm template(s) to import** section. Review your choices and select **Import**.
1. After the import is complete, the selected templates will be added to the template group. If you want to add more templates, repeat the import process.
1. Imported templates can be customized after import. Alarm settings can be modified to fit your alarming needs.
# EventBridge rule groups and templates for monitoring your AWS media workflow
CloudWatch uses Amazon EventBridge rules to send notifications. You begin by creating an event template group. In that event template group, you create event templates that determine what conditions create a notification and who is notified.
This section covers the creation of EventBridge rules using workflow monitor. For more information about how the EventBridge service uses rules, see: [EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html) in the *Amazon EventBridge User Guide*
## Creating event template groups
Event template groups allow you to sort and classify events based on your use case.
**To create an event template group**
1. From the workflow monitor console's navigation pane, select **EventBridge rule templates**.
1. Select **Create event template group**.
1. Give the alarm template group a unique **Group name** and optional **Description**.
1. Select **Create**, You will be taken to the newly created alarm template group's details page.
## Creating event templates
You can send notifications based on event templates you create.
**To create an event template**
1. From the event template group's details page, select **Create event template**.
1. Give the event template a unique **Template name** and optional **Description**.
1. In the **Rule settings** section:
1. Select an **Event type**. When selecting an event type, you can choose between several events created by AWS or select **Signal map active alarm** to use an alarm created by an alarm template.
1. Select a **Target service**. This determines how you would like to be notified of this event. You can select Amazon Simple Notification Service or CloudWatch logs.
1. After selecting a target service, select a **Target**. This will be a Amazon SNS topic or a CloudWatch log group, depending on your target service selection.
1. Select **Create** to complete the process.
# Workflow monitor signal maps
Signal maps are visual mappings of AWS resources in your media workflow. You can use workflow monitor to start the signal map discovery on any of the supported resource types. During the discovery process, workflow monitor will automatically and recursively map all connected AWS resources. After the signal map has been created, you can use the workflow monitor console to do things like deploy monitoring templates, view metrics, and view details of the mapped resources.
**Topics**
+ [Creating signal maps for AWS media workflows](monitor-with-workflow-monitor-configure-signal-maps-create.md)
+ [Viewing signal maps of AWS media workflows](monitor-with-workflow-monitor-configure-signal-maps-view.md)
+ [Attaching alarm and event templates to the signal map of your AWS media workflow](monitor-with-workflow-monitor-configure-signal-maps-attach.md)
+ [Deploying templates to the signal map of your AWS media workflow](monitor-with-workflow-monitor-configure-deploy.md)
+ [Updating the signal map of your AWS media workflow](monitor-with-workflow-monitor-configure-signal-maps-update.md)
+ [Deleting the signal map of your AWS media workflow](monitor-with-workflow-monitor-configure-signal-maps-delete.md)
# Creating signal maps for AWS media workflows
You can use workflow monitor signal maps to create a visual mapping of all connected AWS resources in your media workflow.
**To create a signal map**
1. From the workflow monitor console's navigation pane, select **Signal maps**.
1. Select **Create signal map**.
1. Give the signal map a **Name** and **Description**.
1. In the **Discover new signal map** section, resources in the current account and selected region are displayed. Select a resource to begin signal map discovery. The selected resource will be the starting point for discovery.
1. Select **Create**. Allow a few moments for the discovery process to complete. After the process is complete, you will be presented with the new signal map.
**Note**
Previews generated in the workflow monitor signal map for AWS Elemental MediaPackage channels are delivered from the MediaPackage Origin Endpoint and will incur Data Transfer Out charges. For pricing, see: [MediaPackage pricing](https://aws.amazon.com/mediapackage/pricing/).
# Viewing signal maps of AWS media workflows
Workflow monitor signal maps allow you to see a visual mapping of all connected AWS resources in your media workflow.
**Signal map views**
After selecting a signal map, you have two views that can be used to monitor or configure the signal map. **Monitor signal map** and **Configure signal map** is a context-sensitive button found in the upper-right of the signal map console section.
If you select the signal map using the **Signal maps** section of the navigation pane, your signal map will be displayed in the configuration view. The configuration view allows you to make changes to the template groups attached to this signal map, deploy the attached templates, and view the basic details and tags of the signal map.
If you select the signal map using the **Overview** section of the navigation pane, your signal map will be displayed in monitoring view. The monitoring view displays the CloudWatch alarms, EventBridge rules, alerts, logs, and metrics for this signal map.
The view can be changed at any time by selecting the **Monitor/Configure signal map** button in the upper-right. The configuration view requires administrator-level IAM permissions. Required IAM permissions can be viewed here: [Workflow monitor IAM policies](monitor-with-workflow-monitor-configure-getting-started-IAM.md)
**Navigating the signal map**
A signal map will contain nodes for every supported AWS resource discovered by workflow monitor. Certain resources, such as MediaLive channels and MediaPackage endpoints can display thumbnail previews of the content, if thumbnail previews are available.
Selecting a resource node, and selecting **View selected resource details** from the **Actions** dropdown menu will take you to the associated service's details page. For example, selecting a MediaLive channel and selecting **View selected resource details** will open the MediaLive console's details page for that channel.
Selecting a resource node will filter the list of active alarms to only that node. If you select the resource's **Target ARN** in the active alarm, you will be taken to the associated service's details page, with the selected resource open.
# Attaching alarm and event templates to the signal map of your AWS media workflow
After you have created alarm and event templates, you need to attach these to a signal map. Any of the alarm and event templates you have created can be attached to any discovered signal maps.
**To attach alarm and event templates to your signal map**
1. From the workflow monitor console's navigation pane, select **Signal maps** and select the signal map you want to work with.
1. In the upper-right of the signal map page, in the **CloudWatch alarm template groups** tab, select **Attach CloudWatch alarm template groups**.
1. In the new section that opens, choose all of the alarm template groups that you want to apply to this signal map, then select **Add**. This will cause the selected alarm template groups to move to the **Attached CloudWatch alarm template groups** section.
1. Selecting **Save** will save your changes and return you to the signal map page.
1. At the right of the signal map page, select the **EventBridge rule template groups** tab then select **Attach EventBridge rule template groups**.
1. In the new section that opens, choose all of the event template groups that you want to apply to this signal map, then select **Add**. This will cause the selected rule template groups to move to the **Attached EventBridge rule template groups** section.
1. Selecting **Save** will save your changes and return you to the signal map page.
1. You have assigned CloudWatch alarm and EventBridge rule templates to the signal map, but the monitoring is not yet deployed. The next section will cover the deployment of the monitoring resources.
# Deploying templates to the signal map of your AWS media workflow
After you have attached the alarm and event templates to your signal map, you must deploy the monitoring. Until the deployment is complete, the monitoring of your signal map will not be active.
Workflow monitor will only deploy alarms that are relevant to the selected signal map. For example, the attached alarm template group might contain alarms for multiple services, such as MediaLive, MediaPackage, and MediaConnect. If the selected signal map only contains MediaLive resources, no MediaPackage or MediaConnect alarms will be deployed.
**To deploy the monitoring templates**
1. After attaching alarm and event template groups to your signal map and saving your changes, select **Deploy monitor** in the **Actions** dropdown menu.
1. You will be asked to confirm the deployment and presented with the number of CloudWatch and EventBridge resources that will be created. If you would like to proceed, select **Deploy**.
**Note**
There is no direct cost for using workflow monitor. However, there are costs associated with the resources created and used to monitor your workflow.
When monitoring is deployed, Amazon CloudWatch and Amazon EventBridge resources are created. When using the AWS Management Console, prior to deploying monitoring to a signal map, you will be notified of how many resources will be created. For more information about pricing, see: [CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) and [EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/).
Workflow monitor uses AWS CloudFormation templates to deploy the CloudWatch and EventBridge resources. These templates are stored in a standard class Amazon Simple Storage Service bucket that is created on your behalf, by workflow monitor, during the deployment process and will incur object storage and recall charges. For more information about pricing, see: [Amazon S3 pricing](https://aws.amazon.com/s3/pricing/).
1. The status of the deployment is displayed next to the name of the signal map. The deployment status is also visible in the **Stacks** section of the CloudFormation console. After a few moments of resource creation and deployment, your signal map monitoring will begin.
# Updating the signal map of your AWS media workflow
If a change is made to your workflow, you might need to rediscover the signal map and redeploy monitoring resources. Workflow monitor is a visualization and monitoring tool that does not have the ability to make any changes to your workflow. Signal maps represent a point-in-time visualization of your workflow. In the event that you add, remove, or significantly modify parts of your media workflow, we recommend that you rediscover the signal map. If you have monitoring resources attached to the signal map, we recommend you redeploy monitoring after the rediscovery process.
**To rediscover a signal map**
1. From the workflow monitor console's navigation pane, select **Signal maps** and select the signal map you want to work with.
1. Verify that you are in the **Configure signal map** view. For more information about changing views, see: [Viewing signal maps ](monitor-with-workflow-monitor-configure-signal-maps-view.md)
1. In the upper-right of the signal map page, select the **Actions** dropdown menu. Select **Rediscover**.
1. You will be presented with the rediscovery screen. Select a resource that is a part of the workflow you are rediscovering. Select the **Rediscover** button.
1. The signal map will be rebuilt according to the current workflow. If you need to redeploy monitoring resources, stay on this signal map's page. Any previously attached monitoring templates will remain attached, but will need to be redeployed.
**To redeploy monitoring templates after a signal map rediscovery**
1. After the rediscovery, you will be directed to the updated signal map. To redeploy the monitoring templates, select **Deploy monitor** from the **Actions** dropdown menu.
1. You will be asked to confirm the deployment and presented with the number of any CloudWatch and EventBridge resources that will be created. If you would like to proceed, select **Deploy**.
1. The status of the deployment is displayed next to the name of the signal map. After a few moments of resource creation and deployment, your signal map monitoring will begin.
# Deleting the signal map of your AWS media workflow
If you not longer need a signal map, it can be deleted. If you have monitoring templates deployed on the signal map, the deletion process will ask you to delete any CloudWatch and EventBridge resources that have been deployed to this signal map. Deleting the deployed resources does not affect the templates that created them. This resource deletion is to ensure that you do not have CloudWatch and EventBridge resources that are deployed but not used.
**To delete a signal map**
1. From the workflow monitor console's navigation pane, select **Signal maps** and select the radio button next to the signal map you want to delete.
1. Select the **Delete** button. You will be asked to confirm the deletion of the monitoring resources. Select **Delete** to begin the monitoring resource deletion process.
1. The **Monitor deployment** column will display the current status. When the status has changed to **DELETE\$1COMPLETE**, select the **Delete** button again.
1. You will be asked to confirm deletion of the signal map. Select **Delete** to proceed and delete the signal map.
# Workflow monitor quotas
The following section contains quotas for workflow monitor resources. Each quota is on a "per account" basis. If you need to increase a quota for your account, you can use the [AWS Service Quotas console](https://console.aws.amazon.com/servicequotas/home) to request an increase, unless otherwise noted in the following table.
**Quotas**
| Resource type | Quota |
| --- | --- |
| CloudWatch alarm template groups | 20 |
| CloudWatch alarm templates | 200 |
| EventBridge rule template groups | 20 |
| EventBridge rule templates | 200 |
| Signal maps | 30 |
| Signal maps: CloudWatch alarm template groups attached to a single signal map | 5You cannot increase this quota. |
| Signal maps: EventBridge rule template groups attached to a single signal map | 5You cannot increase this quota. |
# Using workflow monitor
Use the **overview** and **signal maps** sections of the workflow monitor console to review the current status of the workflows and any associated alarms, metrics, and logs.
**Topics**
+ [Workflow monitor overview](monitor-with-workflow-monitor-operate-overview.md)
+ [Overview logs and metrics for workflow monitor](monitor-with-workflow-monitor-operate-logs-metrics.md)
+ [Using workflow monitor signal maps](monitor-with-workflow-monitor-operate-signal-maps.md)
# Workflow monitor overview
The **Overview** section of the workflow monitor console is a dashboard that provides at-a-glance information about your signal maps. In the overview section, you can see the current state of each signal map's monitoring, as well as CloudWatch metrics and any associated CloudWatch logs. You can select any signal map to be taken to that signal maps console page.
**Overview filtering**
Using the **Search** bar in the overview section, you can filter the list of signal maps using context sensitive constraints. After selecting the search bar, you will be presented with a list of **Properties** to filter by. Selecting a property will present **Operators** such as Equals, Contains, Does not equal, and Does not contain. Selecting an operator will create a list of resources from the selected property type. Selecting one of these resources will cause the signal map list to only display signal maps that fit the constraint you defined.
# Overview logs and metrics for workflow monitor
To view CloudWatch metrics and logs for a signal map, select the radio button next to the name of the signal map. A tabbed interface for both metrics and logs will appear beneath the signal map list.
**CloudWatch Metrics**
CloudWatch metrics for the selected signal map will be context-sensitive and only display metrics associated with the services used in that signal maps workflow. You can use the on-screen metrics tools to customize the displayed metric periods and time ranges.
**CloudWatch Logs **
If you associated a CloudWatch log group with the signal map, that group will be displayed here.
# Using workflow monitor signal maps
From the **overview** section of the console, you can select a specific signal map to view more information about that signal map and its attached monitoring resources.
After selecting a signal map, you will be presented with the signal map and a number of tabbed section containing more information:
+ CloudWatch alarms
+ EventBridge rules
+ AWS Elemental alerts
+ Metrics
+ Logs
+ Basic details
**Navigating the signal map**
A signal map will contain nodes for every supported AWS resource discovered by workflow monitor. Certain resources, such as MediaLive channels and MediaPackage endpoints can display thumbnail previews of the content, if thumbnail previews are available.
Selecting a resource node, and selecting **View selected resource details** from the **Actions** dropdown menu will take you to the associated service's details page. For example, selecting a MediaLive channel and selecting **View selected resource details** will open the MediaLive console's details page for that channel.
Selecting a resource node will filter the list of active alarms to only that node. If you select the resource's **Target ARN** in the active alarm, you will be taken to the associated service's details page, with the selected resource open.