Service: Amazon API Gateway
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#apigateway-us-east-1_1638926631

Between 9:02 AM and 5:01 PM PST we experienced increased error rates and latencies for invokes in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

#apigateway #useast1

Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1638927102

ECS has recovered from the issue earlier in the day. Task launches using the EC2 launch type are fully recovered. We have identified the root cause for the increased Fargate launch failures and are starting to see recovery. As we work towards full recovery, customers may experience insufficient capacity errors and these are being addressed as well.

#ecs #useast1

Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1638928810

Event delivery latency for new events is in the US-EAST-1 Region have returned to normal levels. We continue to process a backlog of events.

#events #useast1

Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1638934207

ECS has recovered from the issue earlier in the day. Task launches using the EC2 launch type are fully recovered. Fargate task launches are currently experiencing increased insufficient capacity errors. We are working on addressing this. In the interim, tasks sizes smaller than 4vCPU are less likely to see insufficient capacity errors.

#ecs #useast1

Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1638936149

Improvement from the delay in job state transitions of AWS Batch Jobs in the US-EAST-1 Region is accelerating, we continue to work towards full recovery.

#batch #useast1

Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1638937742

Between 7:35 AM and 8:13 PM PST, we experienced increase job state transition delays of AWS Batch Jobs in the US-EAST-1 Region.  The issue has been resolved and the service is now operating normally for new job submissions.  Jobs that were delayed from earlier in the event will be processed in order until we clear the queue.

#batch #useast1

Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1638940918

Between 7:30 AM and 8:40 PM PST we experienced elevated event delivery latency in the US-EAST-1 Region. Event delivery latencies have returned to normal levels. Some CloudTrail events for API calls between 7:35 AM and 6:05 PM PST may be delayed but will be delivered in the coming hours.

#events #useast1

Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1638946897

ECS has recovered from the issue earlier in the day. Task launches using the EC2 launch type are fully recovered. Fargate task launches are currently experiencing increased insufficient capacity errors. We are working on addressing this and have recently seen a decrease in these errors while continuing to work towards full recovery. In the interim, tasks sizes smaller than 4vCPU are less likely to see insufficient capacity errors.

#ecs #useast1

хватило бы и заранее подумать о сценариях рекавери в другом регионе

Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1638959387

Between 7:31 AM PST on December 7 and 2:20 AM PST on December 8, ECS experienced increased API error rates, latencies, and task launch failures. API error rates and latencies recovered by 6:10 PM PST on December 7. After this point, ECS customers using the EC2 launch type were fully recovered. ECS customers using the Fargate launch type along with EKS customers using Fargate continued to decreasing impact in the form of insufficient capacity errors between 4:40 PM PST on December 7 and 2:20 AM on December 8. The service is now operating normally. A small set of customers may still experience low levels of insufficient capacity errors and will be notified using the Personal Health Dashboard in that case. There was no impact to running tasks during the event although any ECS task that failed health checks would have been stopped because of that failing health check.

#ecs #useast1

чатик, что есть luks-like для macos, но linux compatible  ? veracrypt/truecrypt не рассматриваю из-за gui
надо поверх богомерзкой ntfs c wsl, в которую one drive гонять git
mount с metadata все равно не работает

macOS - свой, Linux - luks, Windows - bitlocker. Пока нигде не видел, чтобы в проде что-то другое юзали.

не, вопрос не про прод

Всем привет - может кто в курсе - создал eks - все по умолчанию - далее создаю ресурс PersistentVolumeClaim - создался успешно но в статусе
status:
 phase: Pending
при этом сам PersistentVolume не создался
может кто сталкивался с этим

@a_nex , а что за storage class используете?

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1639055699

We are investigating elevated error rates for the Redshift Management Console in the US-EAST-1 region and are actively working to resolve the issue.

#redshift #useast1

что describe по клэиму говорит?

https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html @a_nex

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1639056853

We continue to investigate elevated error rates for the Redshift Management Console in the US-EAST-1 region. We have identified the issue causing elevated error rates and are actively working to resolve the issue. Customer clusters remain available and are operating normally. Customers can use API and CLI to manage their clusters and can use SQL clients using ODBC/JDBC and DATA API to run queries.

#redshift #useast1

В целом разобрался - storage class по умолчанию gp2 - я писал в pvc volumeName: "..." - без этого параметра все создалось