Service Health
Use this integration to obtain the latest operational status of AWS services.
The AWS System Status action node queries the AWS Service Health Dashboard for information regarding a user-supplied list of services in a region and returns the most up-to-date information available on the status of that service in JSON format. The AWS Service Health Dashboard is a public facing website which doesn't require login credentials, so it can be a good choice for situations when authentication/authorization systems might be experiencing issues.
For more detailed information about specific AWS services, and the ability to trigger workflows from service outage events, see the AWS Health Alert action node and the AWS Personal Health Dashboard.
The AWS Service Health Dashboard is, at its core, a list of RSS feeds providing information on the status of most AWS services. Given a service name and a region, it's possible to go directly to the feed of any given service to see if there are issues or outages being tracked. The AWS System Status action node does exactly that, retrieving the most recent item in the service's feed, evaluating the title of the item to see if there is currently an issue with the service. The action will return a simplified status field based on what it sees in the most recent item's header, as well as the age of the item.
The status returned will be one of the following:
Status | Description |
|---|---|
Ok | The service is operating normally. |
Degraded | There is something going on with the service that is leading to degraded performance or issues in a subset of the availiblity zones for that service. |
Disrupted | There is something wrong resulting in significant outages for that service. |
Unknown | The action node could not determine the status of the service |
You can add these actions in Fylamynt workflow builder, as part of your workflow.
Insert a AWS System Status action node into your workflow. In the right hand configuration pane, you can select a single AWS region, and multiple services to evaluate. Note: Many of the service names on the AWS Service Health Dashboard are different from the names used in places like the AWS Console or AWS CLI. When in doubt, double check on the AWS Service Health Dashboard.
Parameter Name | Description | Required |
Services | AWS services. Select one or more. | True |
Region Name | AWS Region Name | True |
Parameter Name | Type | Description |
output | Object | Status of services in JSON |
execution_status | String | Status of run (ie: S_OK / E_FAIL) |
The output for the AWS System Status action node is a JSON dict called "output", and is in the following format:
{
"AWS Region": { # e.g. 'us-west-1'
"your service": { #
"status": "string", # Status computed from looking at the below fields.
"title": "string", # The title of the most recent entry in the RSS for the service
"description": null, # The description for the most recent entry.
"last_update": "Thu, 04 Oct 2018 08:04:44 PDT", # Formatted date string for the most recent update.
"error": null, # Any errors reported in the most recent entry.
"message": "" # The message included in the most recent entry.
}
}
}
A real-world example. This is the result from a query on US-WEST-2 for the AWS Secrets Manager service. You'll note that "status" field is "OK", because the most recent incident item in the RSS feed is marked "[RESOLVED]" and is (at the time of this writing) several years old.
{
"us-west-2": {
"secretsmanager": {
"status": "OK",
"title": "Service is operating normally: [RESOLVED] Elevated latencies and API Error Rates",
"description": null,
"last_update": "Thu, 04 Oct 2018 08:04:44 PDT",
"error": null,
"message": "Between 2:04 AM and 7:50 AM PDT we experienced increased API error rates and latencies in the US-WEST-2 Region. The issue has been resolved and the service is operating normally."
}
}
}
The best way to make use of this information is using a JSONPath node with a JSON Path Expression like:
$.us-west-2.secretsmanager.status
and feeding the output of that to a conditional node.
Last modified 1yr ago