Is AWS having issues for anyone else? Seems everyt...
# help
g
Is AWS having issues for anyone else? Seems everything died
t
good for me
"everything died" sounds bad!
g
Every lambda request was getting 500 errors seems to be working now (even seed.run was not working for like 5 minutes for me)
and aws sso is still down for me right now
m
I’m getting 500s too now
us-east-1
g
yeah us-east-1 for me as well
m
not seeing anything on https://status.aws.amazon.com/
t
ah I'm in us-east-2
yeah seeing it on twitter
g
It's back up and it looks like they might have just done an update that broke everything because the SSO login screen changed now lol
t
It looks the same in us-east-2
d
there was also chatter in serverless about everything going down
s
AWS status page says everything is fine though 🤦‍♂️
a
DynamoDB seems to be the only service APIs that aren’t working for us besides the management console. Perhaps DDB is the root cause. Anyone else having issues with apps using DDB in us-east-1?
g
Dynamo is partially working for me - normal put/update/get/queries work but streams are not
or if the streams are working then its eventbridge not working because we push from streams -> eventbridge to actually handle events
a
Yeah, it is weird. Scans are working for me but some query operations aren’t.. but the requests work intermittently
g
assuming issues are still loading from cloudwatch on seed then I havent had a single operation fail from dynamo
Oh they updated status again apparently dynamo is having issues says "control plane apis" not really sure what that means tbh
g
what normal people do without aws? Should I go outside? Damn it’s cold
s
holy crap, this is a serious outage.. geez
t
yeah I'm kinda stuck
s
I’m glad the most critical part of our application isn’t down (it’s old school, hosted on EC2). our customers would be suuuuper pissed
g
Only thing I have noticed is either dynamo streams or event bridge... not sure which is the one having issues since I cannot login to the console to see which lambdas are running 😅
Lambdas were only down for a few minutes at one point
s
some of my API endpoints work, some don’t. basic Lambda funcs are OK.. but one of my API calls that gets a CloudFront signed cookie fails completely
t
Anything that requires on "global" infrastructure is down
So cloudfront for example is global, and all the stuff that runs globally depends on us-east-1 for their control plane
s
ahh
t
that's why I avoid us-east-1 - it's where aws runs a bunch of their own stuff and is burdened in general
s
I was torn between choosing us-east-1 and us-east-2. I figured us-east-1 is a better option, because if there’s an outage in that region, it affects a larger part of the Internet. so if we’re down, people will just see it as “the Internet is broken”
whereas if we’re on a less populated region and we’re down, our customers will think it’s just us
t
yeah that's true
tradeoffs
s
the big question is, why is Amazon.com working perfectly? 🤔
t
apparently it's not, my friend was saying he had some issues checking out his cart
s
ahhh. I was just browsing around, looking at my orders, etc. all totally snappy