We traced the call. It's coming from inside the house.
"Oct 20 8:04 AM PDT ... We have identified that the issue originated from within the EC2 internal network... " -AWS
Investigations showed that the problem began at midnight when the EC2 service turned into a pumpkin. We have stopped looking for a root cause and […]
[Original post on hachyderm.io]
@tychotithonus
According to Amazon's issue page:
"Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1." & "we recommend flushing your DNS caches."
So this was NOT caused by DNS but a bad change by Amazon themselves. DNS […]
These were in solid demand at our @fwdcloudsec.org booth earlier this year and we couldn't help but spread the love among AWS users today. Get yours in the post. #us_east_1 #dns (GCP, Azure, etc peeps can also fill the form 😛 )
