-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Components - Third Party
-
None
-
2
-
Severity 3 - Minor
Issue Summary
Currently, some AWS third-party components are falsely showing up as "Degraded" in Statuspage.
Steps to Reproduce
- Go into your third-party components list and look for AWS.
- Find AWS apigateway-us-gov-east-1
- Add it to your page
- You will see that the component shows as degraded
Essentially, the way our automation works is we have RSS feed URLs saved in the config that figure out the current health of AWS components. These determine what we set the status to in our third-party component list.
The API gateway US East 1 RSS file URL is listed below:
- https://status.aws.amazon.com/rss/apigateway-us-east-1.rss
Visiting this URL no longer provides the status of this component and we don't find the service status in the RSS feed, we mark the component as degraded by default.
We will need to analyze each AWS component and figure out the a better way to fetch the status from the RSS feeds.
Expected Results
- The component will show as "Operational" since that is what the AWS website shows.
Actual Results
- The component has the incorrect status and shows falsely as "Degraded".
Workaround
- You can technically override the status of the component manually to "Operational" but this defeats the purpose of automated components. No good workaround is available currently.