AWS Notes

Простите, кто последний в очереди предложений переписать Windows на Rust? Никто? Тогда просьба за мной не занимать! https://x.com/Perpetualmaniac/status/1814376668095754753

Старожилы не припомнят.

Старожилы не припомнят.

Кто сам не ронял прод в результате апдейта Пусть первый в меня кинет бэкапом.

AWS Health Dashboard — CrowdStrike Falcon Agent Issue Starting at 9:30 PM PDT on July 18th 2024 some Windows Instances, Windows WorkSpaces and Appstream 2.0 Applications experienced connectivity issues and reboots due to a recent update of the CrowdStrike Falcon agent (csagent.sys). This update caused a stop error (BSOD) within the Windows operating system. Windows instances and WorkSpaces that do not use CrowdStrike, were not affected by this issue. AWS services and network connectivity were also not affected by this event and continued to operate normally. While the issue was triggered by the CrowdStrike Falcon agent update within the Windows guest operating system, AWS has taken steps to mitigate the issue for as many Windows instances, Windows WorkSpaces and Appstream 2.0 Applications as possible. For the remaining Windows instances and Windows WorkSpaces that are still affected by this issue, customers need to take action to restore connectivity. Customers using Amazon Appstream 2.0 Applications will no longer see the impact. For EC2 instances, there are currently three paths to recovery. First, in some cases, a reboot of the instance may allow for the CrowdStrike Falcon agent to be updated to a previously healthy version, resolving the issue. However, this is not successful in all cases, in which case an alternative recovery strategy will be needed. Second, the following steps can be followed to delete the CrowdStrike Falcon agent file on the affected instance: (Latest revision: July 19, 7:01 AM PDT) 1. Create a snapshot of the EBS root volume of the affected instance 2. Create a new EBS volume from the snapshot in the same Availability Zone 3. Launch a new instance in that Availability Zone using a different version of Windows 4. Attach the EBS volume from step (2) to the new instance as a data volume 5. Navigate to the \windows\system32\drivers\CrowdStrike\ folder on the attached volume and delete "C-00000291*.sys" 6. Detach the EBS volume from the new instance 7. Create a snapshot of the detached EBS volume 8. Create an AMI from the snapshot by selecting the same volume type as the affected instance 9. Call replace root volume on the original EC2 Instance specifying the AMI just created Finally, customers can relaunch the EC2 instance from a snapshot or image taken before 9:30 PM PDT. We have been able to confirm that the update that caused the CrowdStrike Falcon agent issue is no longer being automatically updated, so the relaunched instance will no longer be affected by the issue. For Amazon WorkSpaces, we recommend a reboot of the affected WorkSpaces. As with EC2, this may recover the instance but it does not work in all cases. Alternatively, we would recommend restoring to a recent backup of the workspace. If you need assistance with any of these actions please contact AWS Support via the AWS Support Center.

CrowdStrike Falcon Agent Issue Starting at 9:30 PM PDT on July 18th 2024 some Windows Instances, Windows WorkSpaces and Appstream 2.0 Applications experienced connectivity issues and reboots due to a recent update of the CrowdStrike Falcon agent (csagent.sys). This update caused a stop error (BSOD) within the Windows operating system. Windows instances and WorkSpaces that do not use CrowdStrike, were not affected by this issue. AWS services and network connectivity were also not affected by this event and continued to operate normally. While the issue was triggered by the CrowdStrike Falcon agent update within the Windows guest operating system, AWS has taken steps to mitigate the issue for as many Windows instances, Windows WorkSpaces and Appstream 2.0 Applications as possible. For the remaining Windows instances and Windows WorkSpaces that are still affected by this issue, customers need to take action to restore connectivity. Customers using Amazon Appstream 2.0 Applications will no longer see the impact. For EC2 instances, there are currently three paths to recovery. First, in some cases, a reboot of the instance may allow for the CrowdStrike Falcon agent to be updated to a previously healthy version, resolving the issue. However, this is not successful in all cases, in which case an alternative recovery strategy will be needed. Second, the following steps can be followed to delete the CrowdStrike Falcon agent file on the affected instance: (Latest revision: July 19, 7:01 AM PDT) 1. Create a snapshot of the EBS root volume of the affected instance 2. Create a new EBS volume from the snapshot in the same Availability Zone 3. Launch a new instance in that Availability Zone using a different version of Windows 4. Attach the EBS volume from step (2) to the new instance as a data volume 5. Navigate to the \windows\system32\drivers\CrowdStrike\ folder on the attached volume and delete "C-00000291*.sys" 6. Detach the EBS volume from the new instance 7. Create a snapshot of the detached EBS volume 8. Create an AMI from the snapshot by selecting the same volume type as the affected instance 9. Call replace root volume on the original EC2 Instance specifying the AMI just created Finally, customers can relaunch the EC2 instance from a snapshot or image taken before 9:30 PM PDT. We have been able to confirm that the update that caused the CrowdStrike Falcon agent issue is no longer being automatically updated, so the relaunched instance will no longer be affected by the issue. For Amazon WorkSpaces, we recommend a reboot of the affected WorkSpaces. As with EC2, this may recover the instance but it does not work in all cases. Alternatively, we would recommend restoring to a recent backup of the workspace. If you need assistance with any of these actions please contact AWS Support via the AWS Support Center.

Лучи поддержки команде тестирования CrowdStrike.

Рефакторинг. #пятничное

​​💥 Коллеги из Варшавы, 18 сентября все дружно приходим на первый AWS Cloud Day Warsaw! 🎉 https://aws.amazon.com/events/cloud-days/warsaw/ 👉🏻 Мероприятие бесплатное, поэтому регистрируйтесь прямо сейчас, пока еще есть свободные места: https://pages.awscloud.com/aws-cloud-day-warsaw-2024-registration.html Кто ещё не осилил польский, не страшно — доклады будут на английском. В общем, ждём конкретно вас, обязательно приходите. Лично приду и проверю!

Продаётся GitLab, недорого: https://www.reuters.com/markets/deals/google-backed-software-developer-gitlab-explores-sale-sources-say-2024-07-17/ В очереди на покупку: ▫️ AWS ▫️ Datadog ▫️ Google Ваши ставки, кто купит GitLab?

​​EKS 1.26-1.27 — end of standard support ❌ В июне закончилась стандартная поддержка EKS 1.26. ⚠️ 24 июля закончится для EKS 1.27. ❗ Если у кого-то крутился три года без обновления EKS 1.21, то у меня для вас две новости, хорошая и плохая. Хорошая — поздравляю, у вас вчера версия кластера обновилась до EKS 1.22. Плохая — не работает, потому что у вас вчера версия кластера обновилась до EKS 1.22. https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html #EKS

​​Microfrontends on AWS https://docs.aws.amazon.com/prescriptive-guidance/latest/micro-frontends-aws/introduction.html • Foundational concepts • Alternative architectures • Architectural decisions • Frameworks and tools • API integration ‒ BFF • Styling and CSS • Organization • Governance • Platform team #design

​​Just Use Postgres for Everything: ▪️ Redis -> Postgres with UNLOGGED tables and TEXT as a JSON ▪️ Kafka -> Postgres with SKIP LOCKED ▪️ MongoDB -> Postgres with JSONB ▪️ ElasticSeacrh -> Postgres ▪️ Data warehouse -> Postgres with Timescale ▪️ Analytics -> Postgres with pg_analytics ▪️ CRON -> Postgres with pg_cron ▪️ Geospacial -> Postgres with PostGIS ▪️ Audit -> Postgres with pgaudit ▪️ GraphQL -> Postgres with a GraphQL adapter https://www.amazingcto.com/postgres-for-everything/ #PostgreSQL

Всем привет . Мы выпустили новый релиз 0.12.1 Добавлено: - lfcs mock exam 1 - lfcs mock exam 1 solutions - Cka lab 5. PriorityClass - lfcs mock exam 1 solutions на данный момент подготовлены mock экзамены cka (mock1 mock2 ) , cks(mock1 ) , ckad (mock1 mock2 ) , lfcs (mock 1 ) Для запуска платформы нужен личный акаунт AWS. Все рессурсы создаются с terraform + terragrunt по умолчанию используются ec2 spot и t4g.medium (graviton ) пример запуска выпуск на devops kitchen talks , где обсуждали как готовиться к экзаменам CKA, CKS, CKAD в 2024 году github платформы канал с решениями мок экзаменов и лабораторных работ.

Всем привет . Мы выпустили новый релиз 0.12.1 Добавлено: - K8s version 1.30 добавлена в k8s_self_management модуль. - k8s version 1.30 используется в cka-mock 1 (решения) - k8s version 1.30 is used in cka-mock 2 (решения) - kube-bench in cks mock1 is updated to version 0.7.3 - k8s version 1.30 используется в cks mock1 (решения) - k8s version 1.30 используется в ckad mock1 (решения) - k8s version 1.30 используется в ckad mock2 (решения) на данный момент подготовлены mock экзамены cka (mock1 mock2 ) , cks(mock1 ) , ckad (mock1 mock2 ) Для запуска платформы нужен личный акаунт AWS. Все рессурсы создаются с terraform + terragrunt по умолчанию используются ec2 spot и t4g.medium (graviton ) пример запуска выпуск на devops kitchen talks , где обсуждали как готовиться к экзаменам CKA, CKS, CKAD в 2024 году github платформы канал с решениями мок экзаменов и лабораторных работ.

Developers: — Наш CI/CD pipeline нестабилен! — Им невозможно пользоваться! DevOps Engineer: #пятничное

​​Global CDN Services Market About $5B in 2023, Expected To Grow 3% In 2024, Driven by AWS https://www.streamingmediablog.com/2024/07/cdn-market-size.html #CDN #CloudFront #info