Service: Amazon Elastic Load Balancing
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#elb-ap-northeast-1_1613755243

現在、ap-northeast-1 リージョンでの、ELB API エラー率の上昇について調査を進めております。既存のロードバランサーへの接続には影響はありません。 |  We are investigating increased error rates for ELB APIs in the ap-northeast-1 Region. Connectivity to existing load balancers is not affected.

#elb #apnortheast1

Service: Amazon Elastic Load Balancing
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#elb-ap-northeast-1_1613755661

Between 9:00 AM and 9:18 AM PST we experienced increased API error rates in the AP-NORTHEAST-1 Region. The issue has been resolved and the service is operating normally.

#elb #apnortheast1

Service: Amazon Elastic Compute Cloud
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#ec2-ap-northeast-1_1613756635

We continue to work on addressing the increase in ambient temperature affecting a small section of a single Availability Zone (apne1-az1) in the AP-NORTHEAST-1 region. The increase in temperature is caused by a loss of power to the cooling units within the affected section of the Availability Zone. We have now restored power to a number of the cooling units within this section of the Availability Zone and are starting to see temperatures decreasing. We will continue to work through the remaining cooling units that are still offline, which will return temperatures to normal levels. Once temperatures have recovered, we would expect to see affected EC2 instances and EBS volumes begin to recover. Other systems, including EC2 and EBS APIs, are operating normally within the affected Availability Zone. Customers with affected EC2 instances and EBS volumes can attempt to relaunch in the affected Availability Zone, or another Availability Zone within the AP-NORTHEAST-1 Region.

#ec2 #apnortheast1

Service: Amazon Elastic Compute Cloud
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#ec2-ap-northeast-1_1613760147

We have now restored power to the majority of the cooling units within the affected section of the Availability Zone (apne1-az1) in the AP-NORTHEAST-1 Region. Temperatures are now close to normal levels and we have begun the process of restoring networking, EC2 instances and EBS volumes. The network has been restored within the affected section of the Availability Zone and we are now working on EC2 instances and EBS volumes. As they begin to recover, customers may need to take action on their instance as it will have experienced a reboot. For EBS volumes, degraded I/O performance will return to normal levels as volumes recover. For instances that are stuck “stopping” or “shutting-down”, these will return to the “stopped” or “terminated” state as recovery proceeds.

#ec2 #apnortheast1

Service: Amazon Elastic Compute Cloud
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#ec2-ap-northeast-1_1613762774

We have now restored power to the cooling subsystem within the affected section of the Availability Zone (apne1-az1) in the AP-NORTHEAST-1 Region. Temperatures are now operating at normal levels. We are also seeing recovery for the majority of EC2 instances and EBS volumes and continue to work on the remaining instance and volumes.

#ec2 #apnortheast1

Service: Amazon Elastic Compute Cloud
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#ec2-ap-northeast-1_1613765390

Temperatures within the affected section of the Availability Zone (apne1-az1) remain stable and at normal levels. We have now recovered the vast majority of EC2 instances. The majority of EBS volumes have also recovered but there are a few that have required some engineering intervention that we are working on.

#ec2 #apnortheast1

Service: Amazon Elastic Compute Cloud
Region: 🇯🇵Asia Pacific (Tokyo)
URL: http://status.aws.amazon.com/#ec2-ap-northeast-1_1613768094

Starting at 6:01 AM PST, we experienced an increase in ambient temperatures within a section of a single Availability Zone within the AP-NORTHEAST-1 Region. Starting at 6:03 AM PST, some EC2 instances were impaired and some EBS volumes experienced degraded performance as a result of the increase in temperature. The root cause was a loss of power to the cooling system within a section of the affected Availability Zone, which engineers worked to restore. By 10:30 AM PST, power had been restored to the majority of the units within the cooling system and temperatures were returning to normal levels. By 11:00 AM PST, EC2 instances and EBS volumes had begun to recover and by 12:30 PM PST, the vast majority of affected EC2 instances and EBS volumes were operating normally. A small number of remaining instances and volumes are hosted on hardware which was adversely affected by the event. We continue to work to recover all affected instances and volumes and have opened notifications for the remaining impacted customers via the Personal Health Dashboard. For immediate recovery, we recommend replacing any remaining affected instances or volumes, if possible.

#ec2 #apnortheast1

Кто может подсказать по такому вопросу:
Есть Aws ECS cluster там крутится один инстанс в котором ранятся 4 контейнера (2 стейджинг, 2 прод)
Как разделить эти контейнеры?
То есть что бы стейджинг был отдельно, а прод отдельно ?
Помогите пожалуйста!

разные кластеры использовать стейдж и прода ?

Нужно смотреть, что использует приложение (БД, файловое хранилище, баффы на урон), и тогда можно ответить на вопрос, как их разделять. Контейнеры и так изолированы друг от друга, твой вопрос не очень понятен

Нет, кластер один, просто что бы было 2 инстанс на которых по 2 контейнера
Сейчас все 4 контейнера на одном инстансе

Сейчас вот так

Нужно стейджинг и прод разделить

Как лучше это сделать ?

Скажи, зачем, и тогда можно будет посоветовать)

Я новичок в АВС, мне дали задачу разделить стейджинг с продом, так как в марте будет проходить нагрузочное тестирование, и разрабы боятся что все упадёт

лучше разделить на отдельные кластеры