(Update 8:00am, June 23rd: All AWS services were restored overnight, according to the company’s status page. No cause of the issues was provided. The original story from last night follows below.)
A problem with one of Amazon Web Services’ most promising new technologies has spread into a wider outage involving its notorious U.S.-East facility in Northern Virginia.
Around 530pm PT on Thursday, users of Amazon’s Lambda serverless technologies started reporting error rates, and the problems spread to other key services, such as its Lex conversational bot service and its API Gateway service. The company acknowledged the issues on its status page, and I’ve reached out to AWS representatives for more information.
Lambda is Amazon’s technology for enabling serverless application development, which is one of the more exciting areas of that world to come around in a while. Serverless promises precision usage pricing and instant scaling for developers that take advantage of the technology, and AWS was first to this game with Lambda in 2014.
US-East is AWS’ oldest facility, and has played host to some widespread outages in the past, most recently in February. AWS has opened state-of-the-art facilities around the world to serve its customers, but when things go wrong, they’ve tended to go wrong in Northern Virginia.
I’ll update this post as we receive more information. The services currently affected (as of 7:10pm PT) are Amazon API Gateway, Amazon Cognito, Amazon Lex, Amazon Pinpoint, AWS Batch, AWS Config, AWS Lambda, and AWS Step Functions.
Update 8:24pm: AWS Greengrass, the company’s new Internet of Things service, is also experiencing issues, as of 8:15pm. All of the above products are still affected by the problems, and AWS has yet to explain the problems.
Update 8:57pm: Amazon seems to have figured out what’s going on with Lambda, which was the first issue to crop up tonight. “We have identified issues in AWS Lambda’s capacity subsystem related to the increased API error rates and latencies in the US-EAST-1 Region and continue to work toward resolution,” the company said on its status page.
Twitter being Twitter:
If you heard Alexa say "Insteon isn't responding" last night, it wasn't us, it was her. Things appear back to normal now.
— Insteon (@Insteon) June 23, 2017
— Evan Sinicin (@ebahsini) June 23, 2017
— A Cloud Guru (@acloudguru) June 23, 2017