@aws_shd Profile picture

Unofficial AWS SHD

@aws_shd

Unofficial Tweet updates from AWS Service Health Dashboard (This is not official)

Similar User
GitHub Status photo

@githubstatus

Fastmail photo

@Fastmail

Last Week in AWS photo

@LastWeekinAWS

Kazunori Sato photo

@kazunori_279

小川晃通(あきみち)PhD。YouTubeでIPv6やTCP/IPの解説動画作ってます! photo

@geekpage

Datadog Ops photo

@DatadogOps

Ryo Suzuki photo

@suzryo

Aya Komuro photo

@ayakomuro

Travis CI photo

@travisci

片山 暁雄 photo

@c9katayama

Brett In Tech photo

@BrettInTech

SendGrid Operations photo

@sendgrid_ops

Eclipse Adoptium photo

@adoptium

角 征典/Masanori Kado photo

@kdmsnr

subicura photo

@subicura

events. ECS and EKS customers using EC2 were not impacted during this event and there was also no impact to any already running tasks or


number of customers may still see failing task and pod launches and we will provide updates to those customers using account specific


pod launch failure rates. The issue has been resolved and customers are now able to launch tasks and pods normally again. A very small


Aug 25, 6:05 AM PDT Between August 24 1:07 PM and August 25 6:00 AM PDT, ECS and EKS customers using Fargate experienced increased task and


Elastic Container Service (N. Virginia) - [RESOLVED] Amazon Elastic Container Service - Increased Rates of Insufficient Capacity Errors -


We still recommend that customers avoid scaling down tasks and pods as they will not be able to launch new tasks until we re-enable Fargate


default of 20 tasks per


task launch rate. We are continuing to monitor recovery and will keep incrementally raising the task launch rate until we return to the


for the ECS RunTask API of 10 tasks per second and we see further reduction in task launch failures due to customers exceeding the maximum


AM PDT We continue making progress with enabling Fargate task launches in the US-EAST-1 Region. All customers now have a task launch rate


Elastic Container Service (N. Virginia) - Amazon Elastic Container Service - Increased Rates of Insufficient Capacity Errors - Aug 25, 4:57


task and pod launches. Customers can also switch to using EC2 with ECS and EKS as a mitigation since ECS with EC2 and EKS with EC2 are not


task launch rate of 20 tasks per


We are no longer seeing elevated task launch failures. It is, however likely to be past 5:00 AM PDT before we have returned to the default


than normal task launch rate means customers can still see task launches failing due to attempting to launch tasks at a higher rate than


As a reminder, all customers are unblocked from launching Fargate tasks at this point, although still at a rate lower than usual. The lower


launch rate until we return to the default of 20 tasks per


to customers exceeding the maximum task launch rate. We are continuing to monitor recovery and will keep incrementally raising the task


This account does not follow anyone
Loading...

Something went wrong.


Something went wrong.