Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS status updates not working due to S3

twitter.com

Post reply on HN
Print view View original

21–30 of 50 posts

Re: AWS status updates not working due to S3

#21

Post by heavymark »

cwmma wrote: post #14

So the obvious answer would be to host it on like azure or google cloud storage but I can just imagine the institutional push back that would get trying to do that.

Seems like another commenter beat me to the punch, but to me the obvious answer would seem to be not hosting images at all as they could create a red circle in css.

Or as others noted reverse the logic so that it shows red icons by default but as long as the services are working then it replaces that with a green icon. And when those external services are down it would go back to a red icon.

Re: AWS status updates not working due to S3

#22

Post by asp2insp »

simplehuman wrote: post #10
qeternity wrote: post #7

Earlier quoted context omitted.

It is...it's literally the reason products like statuspage.io exist, because if your status page has any dependencies on the services for which is provides statuses, then it's not really a useful status page.

And yet, I cannot find any obvious information on where statuspage is hosted.

Builtwith seems to think they are hosted on EC2 https://builtwith.com/statuspage.io

Re: AWS status updates not working due to S3

#23

Post by jvolkman »

heavymark wrote: post #21
cwmma wrote: post #14

So the obvious answer would be to host it on like azure or google cloud storage but I can just imagine the institutional push back that would get trying to do that.

Seems like another commenter beat me to the punch, but to me the obvious answer would seem to be not hosting images at all as they could create a red circle in css. Or as others noted reverse the logic so that it shows red icons by default but as long as the services are working then it replaces that with a green icon. And when those external services are down it would go back to a red icon.

The status text also didn't update. Seems the S3 dependency is more than just icon hosting.

Re: AWS status updates not working due to S3

#24

Post by smarx007 »

simplehuman wrote: post #10
qeternity wrote: post #7

Earlier quoted context omitted.

It is...it's literally the reason products like statuspage.io exist, because if your status page has any dependencies on the services for which is provides statuses, then it's not really a useful status page.

And yet, I cannot find any obvious information on where statuspage is hosted.

http://metastatuspage.com/ should give a hint

Re: AWS status updates not working due to S3

#27

Post by ohstopitu »

Just to be clear...best practices with designing status pages:

1. ensure it does not depend on your infra (if your api server goes down - it should not take down your status api with it)

2. make sure your service reports to your status page instead of your status page looking for the service.

3. redundancy for your status page?

anything anyone-else wants to add?

Re: AWS status updates not working due to S3

#28

Post by doubleplusgood »

idlewords wrote: post #17
cwmma wrote: post #14

So the obvious answer would be to host it on like azure or google cloud storage but I can just imagine the institutional push back that would get trying to do that.

What if I told you you could make a red dot without hosting an image anywhere?

Red dot as a service?

Re: AWS status updates not working due to S3

#29

Post by cwmma »

idlewords wrote: post #17
cwmma wrote: post #14

So the obvious answer would be to host it on like azure or google cloud storage but I can just imagine the institutional push back that would get trying to do that.

What if I told you you could make a red dot without hosting an image anywhere?

what if I told you that if you the status text didn't update?

Re: AWS status updates not working due to S3

#30

Post by janywer »

ohstopitu wrote: post #27

Just to be clear...best practices with designing status pages: 1. ensure it does not depend on your infra (if your api server goes down - it should not take down your status api with it) 2. make sure your service reports to your status page instead of your status page looking for the service. 3. redundancy for your status page? anything anyone-else wants to add?

Not sure about 2 - What are your arguments for this?

If the status page relies on getting updated information from the service, it may not even notice when the whole thing just crashes and goes down in flames. Attempting to do some predefined calls to the service to evaluate whether it is working correctly appears like a better solution?

Post reply on HN