Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618339468

We are investigating increased API error rates in the US-EAST-1 Region.

#ec2 #useast1

В копилку многочасовых обучающих курсов по AWS. https://www.youtube.com/watch?v=keoNi7MmAUY

Сам полностью не смотрел, т.к. мне уже не актуально, но вдруг кому пригодится.
За качество не ручаюсь, но по первым кадрам кажется что на скорости 1.7-2х вполне смотрибельно

А какие курсы по dev/ops про можете порекомендовать, и если можно материала по ci/cd в aws с тулзами aws

Маарека

Devops pro

Спасибо гляну

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1618343445

We can confirm increased provisioning and scaling latencies for Elastic Load Balancers in the US-EAST-1 Region.

#elb #useast1

Началось на ранчо утро

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618343768

We continue to work toward recovery for the issue resulting in increased API error rates for the EC2 APIs in the US-EAST-1 Region. We have identified the root cause and applied mitigations to reduce the impact, while we continue to work towards full mitigation. Some APIs may experience errors or “request limit exceeded” when calling an affected API or using the EC2 Management Console. In many cases, a retry of the request may succeed as some requests are still succeeding. Other AWS services that utilize these affected APIs for their own workflows may also be experiencing impact. These services have posted impact via the Personal Health and/or Service Health Dashboards. We will provide an update in 30 minutes.

#ec2 #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618345344

We continue to work towards full resolution for the issue resulting in increased error rates for the EC2 APIs in the US-EAST-1 Region. We have applied some request throttling for the affected APIs, which has reduced error rates, allowing several APIs to see early recovery. We are adjusting these throttling for some of the affected APIs, which are causing some additional API errors and elevated errors in the EC2 Management Console. We would expect API error rates to continue to recover with the mitigation steps we have taken as we work towards full recovery.

#ec2 #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1618346313

We have determined the root cause of increased scaling latencies for Elastic Load Balancers in the US-EAST-1 Region and are working towards mitigation.

#elb #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618348399

We continue to work towards full recovery for the issue resulting in increased error rates for the EC2 APIs in the US-EAST-1 Region. We have adjusted request throttles to reduce error rates for the affected APIs. While this has worked for some of the affected APIs, such as RunInstances, some of the affected APIs are now returning “request limit exceeded”. If this does occur, attempt to reduce your request rate for the affected API and retry. With the request throttling, some of the affected services are also beginning to see recovery. We continue to work on resolving the underlying root cause and expect to be fully recovered within the next hour.

#ec2 #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1618349977

The team is closely monitoring the issue with EC2 APIs, and continues to see reductions in scaling and provisioning latencies. Other load balancing operations, including target registrations and traffic processing are unaffected. Once the issue with the EC2 APIs is resolved, we will process the backlog of any pending operations before we observe full resolution.

#elb #useast1

Опять Кинезису плохо?)

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618351303

We have further adjusted request throttles to reduce error rates for the affected APIs, so “request limit exceeded” errors should now be significantly reduced. We are now in the final stages of resolving the issue with the underlying data store, which once resolved, we will remove all API throttles and we expect all API operations to return to normal levels.

#ec2 #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1618353857

Beginning at 11:13 AM PDT we experienced increased provisioning and scaling latencies for Elastic Load Balancers in the US-EAST-1 Region. Recovery for scaling latency occurred at 1:15 PM PDT, and recovery for provisioning latency occurred at 3:35 PM PDT. The issue has been resolved and the service is operating normally.

#elb #useast1

RDS тоже поломался... Не создаёт новые инстансы и не скейлит существующие кластеры

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1618354504

We have resolved the issue resulting in the increased error rates for the EC2 APIs, and removed all API request throttling, in the US-EAST-1 Region. Beginning at 11:11 AM PDT, we experienced an increase in API error rates for RunInstances and networking related EC2 APIs. At 12:57 PM PDT, request throttling was applied to several of the affected APIs, which helped to improve error rates for the RunInstances API. We continued to work towards full resolution, while removing request throttles, until 3:30 PM PDT, at which time all affected APIs returned to normal levels of operation. The issue has been resolved and the service is operating normally.

#ec2 #useast1

Service: AWS Batch
Region: 🇺🇸US West (Oregon)
URL: http://status.aws.amazon.com/#batch-us-west-2_1618364745

We are investigating increased transitions to INVALID of some AWS Batch Compute Environments in the US-WEST-2 Region.

#batch #uswest2

Service: AWS Batch
Region: 🇺🇸US West (Oregon)
URL: http://status.aws.amazon.com/#batch-us-west-2_1618366350

We can confirm increased transitions to INVALID of some AWS Batch Compute Environments in the US-WEST-2 Region.

#batch #uswest2