Service: AWS Internet Connectivity
Region: 🇺🇸US West (Oregon)
URL: http://status.aws.amazon.com/#internetconnectivity-us-west-2_1639599296

Between 7:14 AM PST and 7:59 AM PST, customers experienced elevated network packet loss that impacted connectivity to a subset of Internet destinations. Traffic within AWS Regions, between AWS Regions, and to other destinations on the Internet was not impacted. The issue was caused by network congestion between parts of the AWS Backbone and a subset of Internet Service Providers, which was triggered by AWS traffic engineering, executed in response to congestion outside of our network. This traffic engineering incorrectly moved more traffic than expected to parts of the AWS Backbone that affected connectivity to a subset of Internet destinations. The issue has been resolved, and we do not expect a recurrence.

#internetconnectivity #uswest2

Пошли обновления критические явы:

https://github.com/NCSC-NL/log4shell/tree/main/software#a

Друзья подскажите s3 lifecycle policy поддерживает wildcard?

Если речь про my-path/*, то это есть prefix (my-path/).

Видимо речь про my-path/*/some, то такого указать возможности нет.

спасибо, вот тут в принципе то что надо https://docs.aws.amazon.com/mediastore/latest/ug/policies-object-lifecycle-components.html

Ребята, всем привет! Знаю, тут только профи, но у меня тупой вопрос, прошу помощи🙏. Подскажите, будьте добры, можно ли подключить ssl-сертификат к домену от aws стандартному, который выдаётся для каждого EC2? или именно только к стороннему, покупному? При вводе стандартного домена в новый ssl сертификат почти сразу статус у него failed😞

Сертификаты можно выписывать только на то, чем владеете

машинки с доменом ec2…. они вам даются временно

Я так и думала, но решила уточнить. Огромное спасибо!

Ну почему же, через certbot можно выписать сертификат, никаких проблем )

ну тут вопрос я так понимаю про ACM 🙂

всем спасибо) про certbot тоже почитаю :) хорошего всем дня!

Service: AWS Elastic Beanstalk
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elasticbeanstalk-us-east-1_1640158400

We are investigating an issue where customers are unable to upload and deploy new application versions through the Elastic Beanstalk console in multiple Regions. Customers who need to update or deploy a new application version should do so using the AWS CLI. Existing applications are not impacted by this issue

#elasticbeanstalk #useast1

Service: AWS Elastic Beanstalk
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elasticbeanstalk-us-east-1_1640162070

We continue to investigate an issue where customers are unable to upload and deploy new application versions through the Elastic Beanstalk console in multiple Regions. We are determining the root causes and working through steps to mitigate the issue. Customers who need to update or deploy a new application version should do so using the AWS CLI while we work towards resolving the issue. Existing applications are not impacted by this issue.

#elasticbeanstalk #useast1

Service: AWS Elastic Beanstalk
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elasticbeanstalk-us-east-1_1640164826

We have identified the root cause and prepared a fix to address the issue that prevents customers from uploading new application versions through the Elastic Beanstalk console in multiple Regions. The service team is testing this fix and preparing for deployment to the Regions that are affected by this issue. We expect to see full recovery by 3:00 AM PST and will continue to keep you updated if this ETA changes. Customers who need to update or deploy a new application version should do so using the AWS CLI until the issue is fully resolved.

#elasticbeanstalk #useast1

Service: AWS Elastic Beanstalk
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elasticbeanstalk-us-east-1_1640171976

Between December 21, 2021 at 6:37 PM  and December 22, 2021 at 3:17 AM PST, customers were unable to upload their code through the Elastic Beanstalk console due to a Content Security Policy (CSP) error. Customers were impacted when they attempted to upload a new application version for existing environments or upload their code when creating a new environment in multiple regions. The issue has been resolved and the service is operating normally.

#elasticbeanstalk #useast1

Service: AWS Elastic Beanstalk
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elasticbeanstalk-us-east-1_1640172112

Between December 21, 2021 at 6:37 PM  and December 22, 2021 at 03:17 AM PST, customers were unable to upload their code through the Elastic Beanstalk console due to a Content Security Policy (CSP) error. Customers were impacted when they attempted to upload a new application version for existing environments or upload their code when creating a new environment in multiple regions. The issue has been resolved and the service is operating normally.

#elasticbeanstalk #useast1

Да уж...