Hacker News Reader

Comment by shadycuz | Hacker News Reader

I'm seeing issues with SSHing into new ec2 instances and getting those new instances to reach apt to fetch packages. I'm using packer. My last successful build was 4 hours ago. This is in us-west-2. AWS service health dashboard doesn't show anything for me.

EDIT: Health dashboard shows all services as green, not that the dashboard is down.

View on HN

They seem to hide issues from folks they don't think are impacted.

Logged in (1 issue) versus logged out (0 issues) health dashboard: https://imgur.com/a/QRhZMf2

Just for those following along. Even after I login, I still have 0 issues. I'm not sure how AWS determines when to hide a outage from a user.

Ooop, just had "Operational issue - Multiple services (Oregon)" show up.

edit: Aaaaand "Operational issue - Multiple services (N. Virginia)" now.

yup, finally seeing it on my health page.

The issue I'm shown has "Service: Lambda" on it, so I wonder if it's only shown to folks with Lambda functions live. Someone tweeted at me that they're having issues on EKS, and that they use private DNS inside their VPC as I do.

Not sure. We have lambdas in this account, but not that have triggered in a several months.

I'm not sure if we use Private DNS. We have some custom resolvers and rules. I see now they are calling it network issues.

Thanks for the tip... that is mildly infuriating =/

The only power developers have over companies who lie on status boards is to hit them in their wallets and file a support request for every failure, so they have to triage that instead of just being honest and upfront.

Reply on news.ycombinator.com