HTTP GET /comfort-zone?exist=vote
Anonymous Poll
7%
Error 301: Moved Permanently.
3%
Error 401: Unauthorized.
10%
Error 402: Payment Required.
9%
Error 404: Comfort Zone Not Found.
6%
Error 410: Gone.
6%
Error 429: Too Many Requests.
5%
Error 451: Unavailable For Legal Reasons.
4%
Error 500: Internal Comfort Error.
7%
Error 503: Service Unavailable.
44%
👀 See results.
👍1
☒ Beating the CAP Theorem Checklist
Your blog/presentation/post/comment advocates a way to beat the CAP theorem. Your idea will not work.
Here is why it won't work:
✖ you are assuming that software/network/hardware failures will not happen
✖ you pushed the actual problem to another layer of the system
✖ your solution is equivalent to an existing one that doesn't beat CAP
✖ you're actually building an AP system
✖ you're actually building a CP system
✖ you are not, in fact, designing a distributed system
Specifically, your plan fails to account for:
❌ latency is a thing that exists
❌ high latency is indistinguishable from splits or unavailability
❌ network topology changes over time
❌ there might be more than 1 partition at the same time
❌ split nodes can vanish forever
❌ a split node cannot be differentiated from a crashed one by its peers
❌ clients are also part of the distributed system
❌ stable storage may become corrupt
❌ network failures will actually happen
❌ hardware failures will actually happen
❌ operator errors will actually happen
❌ deleted items will come back after synchronization with other nodes
❌ clocks drift across multiple parts of the system, forward and backwards in time
❌ things can happen at the same time on different machines
❌ side effects cannot be rolled back the way transactions can
❌ failures can occur while in a critical part of your algorithm
❌ designing distributed systems is actually hard
❌ implementing them is harder still
And the following technical objections may apply:
Furthermore, this is what I think about you:
❎ nice try, but blatantly false advertising
❎ you are badly reinventing existing concepts and should do some research
❎ in particular, you should read the definition of the word 'theorem'
❎ also you should read the definition of 'distributed system'
❎ you have no idea what you are doing
❎ do you even know what a logical clock is?
❎ you shouldn't be in charge of people's data
Source: https://ferd.ca/beating-the-cap-theorem-checklist.html
#architecture #distributed_system
Your blog/presentation/post/comment advocates a way to beat the CAP theorem. Your idea will not work.
Here is why it won't work:
✖ you are assuming that software/network/hardware failures will not happen
✖ you pushed the actual problem to another layer of the system
✖ your solution is equivalent to an existing one that doesn't beat CAP
✖ you're actually building an AP system
✖ you're actually building a CP system
✖ you are not, in fact, designing a distributed system
Specifically, your plan fails to account for:
❌ latency is a thing that exists
❌ high latency is indistinguishable from splits or unavailability
❌ network topology changes over time
❌ there might be more than 1 partition at the same time
❌ split nodes can vanish forever
❌ a split node cannot be differentiated from a crashed one by its peers
❌ clients are also part of the distributed system
❌ stable storage may become corrupt
❌ network failures will actually happen
❌ hardware failures will actually happen
❌ operator errors will actually happen
❌ deleted items will come back after synchronization with other nodes
❌ clocks drift across multiple parts of the system, forward and backwards in time
❌ things can happen at the same time on different machines
❌ side effects cannot be rolled back the way transactions can
❌ failures can occur while in a critical part of your algorithm
❌ designing distributed systems is actually hard
❌ implementing them is harder still
And the following technical objections may apply:
✕ your solution requires a central authority that cannot be unavailable✕ read-only mode is still unavailability for writes✕ your quorum size cannot be changed over time✕ your cluster size cannot be changed over time✕ using 'infinite timeouts' is not an acceptable solution to lost messages✕ your system accumulates data forever and assumes infinite storage✕ re-synchronizing data will require more bandwidth than everything else put together✕ acknowledging reception is not the same as confirming consumption of messages✕ you don't even wait for messages to be written to disk✕ you assume short periods of unavailability are insignificant✕ you are basing yourself on a paper or theory that has not yet been provenFurthermore, this is what I think about you:
❎ nice try, but blatantly false advertising
❎ you are badly reinventing existing concepts and should do some research
❎ in particular, you should read the definition of the word 'theorem'
❎ also you should read the definition of 'distributed system'
❎ you have no idea what you are doing
❎ do you even know what a logical clock is?
❎ you shouldn't be in charge of people's data
Source: https://ferd.ca/beating-the-cap-theorem-checklist.html
#architecture #distributed_system
🔥12🤝3
Amplify Gen 2
https://aws.amazon.com/blogs/mobile/amplify-gen2-ga/
With Amplify Gen 2, every part of your app’s cloud backend is defined in TypeScript. Need an Auth backend? TypeScript. Data backend? TypeScript. Storage backend? TypeScript. Everything is defined in TypeScript. What’s not changing? Amplify is built by and on AWS, giving you the ability to add any of the 200+ AWS services when you need to. Including generative AI services such as Amazon Bedrock? You guessed it: TypeScript.
#Amplify
https://aws.amazon.com/blogs/mobile/amplify-gen2-ga/
With Amplify Gen 2, every part of your app’s cloud backend is defined in TypeScript. Need an Auth backend? TypeScript. Data backend? TypeScript. Storage backend? TypeScript. Everything is defined in TypeScript. What’s not changing? Amplify is built by and on AWS, giving you the ability to add any of the 200+ AWS services when you need to. Including generative AI services such as Amazon Bedrock? You guessed it: TypeScript.
#Amplify
Amazon
Fullstack TypeScript: Reintroducing AWS Amplify | Amazon Web Services
We are thrilled to announce the general availability of AWS Amplify Gen 2, a fullstack TypeScript experience for building cloud-connected apps. AWS Amplify helps you accomplish two jobs: Host your web app Build and connect to a cloud backend With Amplify…
👍2
Forwarded from Rinat Uzbekov
Календарь AWS Hands-on Workshops на ближайшее время
https://aws-experience.com/emea/smb/events/series/aws-cloudboost
https://aws-experience.com/emea/smb/events/series/aws-cloudboost
AWS Connected Community
AWS CloudBoost
Gain hands-on AWS cloud experience through our exciting series of webinars and workshops. From foundational to specialist topics, put theory into practice as you build your cloud skills.
Forwarded from Viktor Vedmich (AWS)
Вот и вышло наше новое видео! Совместно с архитектором Anton Kovalenko мы рассматриваем Amazon CodeCatalyst. Подробно разбираемся в его возможностях и функционале. https://youtu.be/WEK7lTsL7ek
В этом видео вы узнаете:
- Зачем нужен CodeCatalyst и почему он появился
- Как авторизоваться и начать работу
- Создание нового проекта с нуля
- Обзор основных возможностей и функционала
- Работа с Dev Environment
- Создание собственных Workflows
- Настройка Production окружений
- Использование секретов (Secrets)
- Демонстрация полного цикла разработки - от изменения кода до деплоя
- Интеграция с Amazon Q - ассистент теперь может решать задачи сам
В этом видео вы узнаете:
- Зачем нужен CodeCatalyst и почему он появился
- Как авторизоваться и начать работу
- Создание нового проекта с нуля
- Обзор основных возможностей и функционала
- Работа с Dev Environment
- Создание собственных Workflows
- Настройка Production окружений
- Использование секретов (Secrets)
- Демонстрация полного цикла разработки - от изменения кода до деплоя
- Интеграция с Amazon Q - ассистент теперь может решать задачи сам
YouTube
Разбираем Amazon CodeCatalyst за 50 минут
В этом видео мы вместе с архитектором Антоном Коваленко подробно разбираем новый облачный сервис Amazon CodeCatalyst:
• Зачем нужен CodeCatalyst и почему он появился
• Как авторизоваться и начать работу
• Создание нового проекта с нуля
• Обзор основных…
• Зачем нужен CodeCatalyst и почему он появился
• Как авторизоваться и начать работу
• Создание нового проекта с нуля
• Обзор основных…
👍6
Forwarded from AWS User Group 3City
Kick Off Infoshare 2024 with AWS User Group 3city! 🚀
Before diving into the excitement of Infoshare, the largest tech and startup conference in CEE, why not warm up with our AWS User Group 3city meetup? We're hosting a special meetup, offering the perfect prelude to the conference days. Two technical sessions and a networking pizza break await you.
📅 When: May 21, 17:00 (GMT)
📍 Where: Amazon Development Center Office
al. Grunwaldzka 472E, Gdańsk Olivia Prime A, Floor 2
📺 Can't make it in person? Join our online stream on YouTube (exclusive access for registered participants)
This meetup is an ideal opportunity to set the stage for two days of learning and networking. Join us to share knowledge, connect with peers, and gain insights from industry experts. Let’s build momentum together and make the most out of the upcoming Infoshare conference!
Check the detailed agenda and register now ➡️https://epa.ms/Cygfr
Don’t forget to use our discount code for Infoshare conference ISC24-AWS3city to get 10% off any ticket on https://infoshare.pl/ . 😉
See you there! 👋
Before diving into the excitement of Infoshare, the largest tech and startup conference in CEE, why not warm up with our AWS User Group 3city meetup? We're hosting a special meetup, offering the perfect prelude to the conference days. Two technical sessions and a networking pizza break await you.
📅 When: May 21, 17:00 (GMT)
📍 Where: Amazon Development Center Office
al. Grunwaldzka 472E, Gdańsk Olivia Prime A, Floor 2
📺 Can't make it in person? Join our online stream on YouTube (exclusive access for registered participants)
This meetup is an ideal opportunity to set the stage for two days of learning and networking. Join us to share knowledge, connect with peers, and gain insights from industry experts. Let’s build momentum together and make the most out of the upcoming Infoshare conference!
Check the detailed agenda and register now ➡️https://epa.ms/Cygfr
Don’t forget to use our discount code for Infoshare conference ISC24-AWS3city to get 10% off any ticket on https://infoshare.pl/ . 😉
See you there! 👋
❤2
Forwarded from Rinat Uzbekov
Installing, Configuring, & Using Amazon Q Developer with JetBrains IDEs (How-to)
https://youtu.be/-iQfIhTA4J0
https://youtu.be/-iQfIhTA4J0
YouTube
Installing, Configuring, & Using Amazon Q Developer with JetBrains IDEs (How-to)
🤘 Learn more about Amazon Q: https://aws.amazon.com/developer/generative-ai/amazon-q/
Are you interested in leveraging the full power of Amazon Q Developer inside your JetBrains IDEs? Wojtek Gawroński (Senior Developer Advocate at AWS) will show you how…
Are you interested in leveraging the full power of Amazon Q Developer inside your JetBrains IDEs? Wojtek Gawroński (Senior Developer Advocate at AWS) will show you how…
🔥3
AWS Notes
Installing, Configuring, & Using Amazon Q Developer with JetBrains IDEs (How-to) https://youtu.be/-iQfIhTA4J0
Всем привет!
На видео выше, можно видеть как сейчас выглядит интеграция/аутентификация. Честно говоря расстроен тем, как неудобно сделано.
Я хочу публично собрать пожелания клиентов по упрощению интеграции. А именно прямой интеграции JetBrains AI assistant Platform (через нее работают все продукты JetBrains) с Amazon Q for Developers - без этой лишней шняги с аутентификацией в AWS и SSO.
Всех кому интересно получить более удобную интеграцию прошу добавить +1 и коменты к моему коменту/посту в LinkedIn. Там протэганы руководство сервисной команды Amazon Q for Developers и я также все ваши пожелания донесу до руководства и сервисных команд JetBrains.
https://www.linkedin.com/feed/update/urn:li:activity:7194289034846760960?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7194289034846760960%2C7194293080072552448%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287194293080072552448%2Curn%3Ali%3Aactivity%3A7194289034846760960%29
Надеюсь на поддержку Community!
На видео выше, можно видеть как сейчас выглядит интеграция/аутентификация. Честно говоря расстроен тем, как неудобно сделано.
Я хочу публично собрать пожелания клиентов по упрощению интеграции. А именно прямой интеграции JetBrains AI assistant Platform (через нее работают все продукты JetBrains) с Amazon Q for Developers - без этой лишней шняги с аутентификацией в AWS и SSO.
Всех кому интересно получить более удобную интеграцию прошу добавить +1 и коменты к моему коменту/посту в LinkedIn. Там протэганы руководство сервисной команды Amazon Q for Developers и я также все ваши пожелания донесу до руководства и сервисных команд JetBrains.
https://www.linkedin.com/feed/update/urn:li:activity:7194289034846760960?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7194289034846760960%2C7194293080072552448%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287194293080072552448%2Curn%3Ali%3Aactivity%3A7194289034846760960%29
Надеюсь на поддержку Community!
Linkedin
Installing, Configuring, & Using Amazon Q Developer with JetBrains IDEs… | Rinat Uzbekov
Installing, Configuring, & Using Amazon Q Developer with JetBrains IDEs
Wojtek Gawroński 🥑
Doug Seven Deepak Singh
Amazon Web Services (AWS)
#JetBrains #AmazonQ #AWS
Wojtek Gawroński 🥑
Doug Seven Deepak Singh
Amazon Web Services (AWS)
#JetBrains #AmazonQ #AWS
🔥6
Всем кому интересно продолжение темы с Amazon Q for Developers в JetBrains IDE - приглашаем на Workshop с нашим архитектором @antkovalenko. Тема будет интересна в первую очередь девелоперам кто постоянно работает в JetBrains IDE и DevOps кто использует IDE для IaaC. Так что приглашайте ваших девелоперов.
https://aws-experience.com/emea/dach-cee/e/c2e17/empower-your-coding-with-generative-ai-hands-on-workshop-on-amazon-q-developer
https://aws-experience.com/emea/dach-cee/e/c2e17/empower-your-coding-with-generative-ai-hands-on-workshop-on-amazon-q-developer
AWS Experience
Empower your coding with Generative AI: hands-on workshop on Amazon Q Developer
On this hands-on workshop you will learn how to:
• Automate repetitive tasks leveraging generative AI and receive code explanations in natural language.
• Run code quality and security checks: Amazon Q scans code, identifies potential bugs, suggests alternative…
• Automate repetitive tasks leveraging generative AI and receive code explanations in natural language.
• Run code quality and security checks: Amazon Q scans code, identifies potential bugs, suggests alternative…
🔥4👍1
Добрая пятничная история
Пару недель назад AWS выкатил поддержку CloudFront OAC для Lambda function URLs, чтобы можно было удобно ходить в приватные Лямбды.
Сначала все обрадовались, полезное дело, безопасности, все дела, но после выяснилось, что работают лишь GET запросы, а на POST/PUT отдаётся ошибка.
Потом все расстроились, потому что зря обрадовались — ведь это не фича, а баг.
Но один хороший человек упоролся и выяснил, что если посчитать SHA256 хэш и добавить его в заголовок
https://twitter.com/rooToTheZ/status/1788606025265975505
Он написал запрос на обновление AWS документации для CloudFront и теперь там:
ℹ️ Note
If you use PUT or POST methods with your Lambda function URL, your user must provide a signed payload to CloudFront. Lambda doesn't support unsigned payloads.
В итоге расстроились и те, кто обрадовался, когда другие расстроились, потому что рано обрадовались.
Какая же здесь мораль? Документация — важна. Грамотно задокументированный баг всегда можно сделать фичей.
#CloudFront #Lambda
Пару недель назад AWS выкатил поддержку CloudFront OAC для Lambda function URLs, чтобы можно было удобно ходить в приватные Лямбды.
Сначала все обрадовались, полезное дело, безопасности, все дела, но после выяснилось, что работают лишь GET запросы, а на POST/PUT отдаётся ошибка.
Потом все расстроились, потому что зря обрадовались — ведь это не фича, а баг.
Но один хороший человек упоролся и выяснил, что если посчитать SHA256 хэш и добавить его в заголовок
x-amz-content-sha256, то и POST/PUT тоже работают.https://twitter.com/rooToTheZ/status/1788606025265975505
Он написал запрос на обновление AWS документации для CloudFront и теперь там:
ℹ️ Note
If you use PUT or POST methods with your Lambda function URL, your user must provide a signed payload to CloudFront. Lambda doesn't support unsigned payloads.
В итоге расстроились и те, кто обрадовался, когда другие расстроились, потому что рано обрадовались.
Какая же здесь мораль? Документация — важна. Грамотно задокументированный баг всегда можно сделать фичей.
#CloudFront #Lambda
X (formerly Twitter)
David Behroozi (@rooToTheZ) on X
My wayward sons! Remember that CloudFront Lambda OAC release we were super sad about because it didn't support PUT/POST? IT ACTUALLY DOES! You just need to calculate the SHA256 hash of the body client side and set the x-amz-content-sha256 header to it. I…
😁8👍7
Analysis of 3 million public AMIs for leaked secrets.
https://securitycafe.ro/2024/05/08/aws-cloudquarry-digging-for-secrets-in-public-amis/
#AMI #security
https://securitycafe.ro/2024/05/08/aws-cloudquarry-digging-for-secrets-in-public-amis/
#AMI #security
👍15🔥2
aws-amicleaner — a cost-saving tool for deleting unused AMIs and EBS snapshots.
https://github.com/widdix/aws-amicleaner
#EC2 #AMI #cost_optimization
https://github.com/widdix/aws-amicleaner
#EC2 #AMI #cost_optimization
GitHub
GitHub - widdix/aws-amicleaner: To clean up your AWS AMIs: First, include AMIs by name or tag. Second, exclude AMIs in use, younger…
To clean up your AWS AMIs: First, include AMIs by name or tag. Second, exclude AMIs in use, younger than N days, or the newest N images. Third, manually confirm the list of AMIs for deletion. - wid...
👍5
E1S - Easily Manage AWS ECS Resources in Terminal 🐱
https://github.com/keidarcy/e1s
For working with ECS in the console, this is a must-have tool. It is quick to install and convenient to use in CloudShell (which should be opened in a separate window in order to work properly with the keyboard shortcuts). You can take a quick look at the logs. Or you can go into the container.
Bottom line — a great tool for working with ECS, I recommend it, definitely give it a try!
#ECS
https://github.com/keidarcy/e1s
For working with ECS in the console, this is a must-have tool. It is quick to install and convenient to use in CloudShell (which should be opened in a separate window in order to work properly with the keyboard shortcuts). You can take a quick look at the logs. Or you can go into the container.
Bottom line — a great tool for working with ECS, I recommend it, definitely give it a try!
#ECS
❤7🔥4🙈2😱1
AWS Notes
Добавлено в следующий спринт. https://twitter.com/jeffbarr/status/1785386554372042890
https://docs.aws.amazon.com/AmazonS3/latest/userguide/ErrorCodeBilling.html
P.S. Amazon S3 team has 2 week sprints.
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥37❤5👍4🎉3🤪1
⚡️ Oracle switched from Terraform to OpenTofu
https://blogs.oracle.com/ebsandoraclecloud/post/ebs-cloud-manager-24111-now-available
▫ In this release, we have switched from Terraform to OpenTofu due to forthcoming Terraform licensing changes. You must therefore upgrade your Cloud Manager by June 30, 2024 at the latest.
▫ We highly recommend that you uptake this new release of Cloud Manager at your earliest convenience.
P.S. Лёд тронулся, господа присяжные заседатели!
#Terraform #OpenTofu
https://blogs.oracle.com/ebsandoraclecloud/post/ebs-cloud-manager-24111-now-available
▫ In this release, we have switched from Terraform to OpenTofu due to forthcoming Terraform licensing changes. You must therefore upgrade your Cloud Manager by June 30, 2024 at the latest.
▫ We highly recommend that you uptake this new release of Cloud Manager at your earliest convenience.
P.S. Лёд тронулся, господа присяжные заседатели!
#Terraform #OpenTofu
👍13😱4🤮2
❎ Adam Selipsky to step down.
✅ Matt Garman will become CEO of AWS, effective June 3rd.
https://www.aboutamazon.com/news/company-news/leadership-update-aws-adam-selipsky-matt-garman
✅ Matt Garman will become CEO of AWS, effective June 3rd.
https://www.aboutamazon.com/news/company-news/leadership-update-aws-adam-selipsky-matt-garman
US About Amazon
Andy Jassy makes AWS leadership announcement
This morning, Andy Jassy, Adam Selipsky, and Matt Garman shared the following messages with our teams.
👍1
AWS Notes
AWS-EU — новая будущая отдельная часть AWS European Sovereign Cloud и новый будущий AWS-EU регион в Германии: https://aws.amazon.com/blogs/aws/in-the-works-aws-european-sovereign-cloud/ AWS-EU будет физически располагаться только на территории Евросоюза…
AWS Summit Berlin — весомое событие, в честь которого Amazon даже ещё раз напомнил со всей серьёзностью о своих планах на создание "Европейского AWS":
https://www.aboutamazon.eu/news/aws/aws-plans-to-invest-7-8-billion-into-the-aws-european-sovereign-cloud
С одной стороны просто подтвердив ранее озвученные планы, с другой — продемонстрировав, как важно для AWS европейское направление.
В общем, мы на пути к тому, чтобы иметь не просто специалистов по AWS, а с суверенной специализацией:
▪️AWS EU Solutions Architect
▪️AWS China DevOps Engineer
▪️AWS India Fullstack Developer
P.S. Будущий AWS EU регион в Германии будет работать 100% на возобновляемых источниках энергии.
#AWS_EU_Regions
https://www.aboutamazon.eu/news/aws/aws-plans-to-invest-7-8-billion-into-the-aws-european-sovereign-cloud
С одной стороны просто подтвердив ранее озвученные планы, с другой — продемонстрировав, как важно для AWS европейское направление.
В общем, мы на пути к тому, чтобы иметь не просто специалистов по AWS, а с суверенной специализацией:
▪️AWS EU Solutions Architect
▪️AWS China DevOps Engineer
▪️AWS India Fullstack Developer
P.S. Будущий AWS EU регион в Германии будет работать 100% на возобновляемых источниках энергии.
#AWS_EU_Regions
EU About Amazon
AWS plans to invest €7.8 billion into the AWS European Sovereign Cloud
AWS’s investment reflects long-term commitment to meeting Europe's digital sovereignty requirements.
Универсальная таблица оценки задач
▪️ изян — 1ч
▪️ изи — 2ч
▪️ просто — 4ч
▪️ вроде просто — 6ч
▪️ норм — 8ч
▪️ норм так — 12ч
▪️ хз — 16ч
▪️ хз как-то — 20ч
▪️ как-то сложно — 24ч
▪️ сложно — 30ч
▪️ очень сложно — 40ч
▪️ бля — 48ч
▪️ пиздец — 60ч
▪️ пиздец какой-то — 80ч
▪️ вроде изян — 100ч
первоисточник
#пятничное
▪️ изян — 1ч
▪️ изи — 2ч
▪️ просто — 4ч
▪️ вроде просто — 6ч
▪️ норм — 8ч
▪️ норм так — 12ч
▪️ хз — 16ч
▪️ хз как-то — 20ч
▪️ как-то сложно — 24ч
▪️ сложно — 30ч
▪️ очень сложно — 40ч
▪️ бля — 48ч
▪️ пиздец — 60ч
▪️ пиздец какой-то — 80ч
▪️ вроде изян — 100ч
первоисточник
#пятничное
🤪21😁18👍8❤3
Forwarded from AWS Weekly (Max Skutin)
✈️ Issue #124 | 19 May 2024
▪️ Bedrock Knowledge Bases
▫️ configure Guardrails
▫️ configure inference parameters
▪️ Bottlerocket NVIDIA Fabric Manager for Multi-GPU Workloads
▪️ CodeBuild connecting to a VPC from reserved capacity
▪️ Connect Contact Lens analytics for Flows and Flow Modules
▪️ Connect creating rules for monitoring and alerting on Flow metrics
▪️ Detective EKS audit logs in Security Lake integration
▪️ EBS direct APIs now support VPC endpoint policies
▪️ EC2 C7i-flex instances
▪️ ECS VPC flow logs
▪️ EKS native support for autoscaling CoreDNS Pods
▪️ EMR
▫️ additional metrics for enhanced monitoring
▫️ now supports Trino 435, Python 3.11
▪️ EventBridge Customer Managed Keys (CMK) for Event Buses
▪️ HealthImaging
▫️ cross-account data imports
▫️ retrieval of DICOM Part 10 instances
▪️ IAM Identity Center PKCE-based authorization for AWS applications
▪️ Managed Grafana version 10.4
▪️ Managed Service for Prometheus inline editing of alert manager and rules configuration
▪️ MSK removal of brokers from MSK provisioned clusters
▪️ MWAA Airflow REST API with web server auto scaling
▪️ OpenSearch Ingestion new UI for easy blueprint discovery
▪️ RDS for MySQL Extended Support minor 5.7.44-RDS.20240408
▪️ RDS for PostgreSQL Extended Support minor 11.22-RDS.20240418
▪️ S3 no longer charge for several HTTP error codes
▪️ Security Hub CIS AWS Foundations Benchmark 3.0
▪️ VPC Lattice TLS Passthrough
▪️ WorkSpaces Core Windows Server bundles
▪️ Bedrock Knowledge Bases
▫️ configure Guardrails
▫️ configure inference parameters
▪️ Bottlerocket NVIDIA Fabric Manager for Multi-GPU Workloads
▪️ CodeBuild connecting to a VPC from reserved capacity
▪️ Connect Contact Lens analytics for Flows and Flow Modules
▪️ Connect creating rules for monitoring and alerting on Flow metrics
▪️ Detective EKS audit logs in Security Lake integration
▪️ EBS direct APIs now support VPC endpoint policies
▪️ EC2 C7i-flex instances
▪️ ECS VPC flow logs
▪️ EKS native support for autoscaling CoreDNS Pods
▪️ EMR
▫️ additional metrics for enhanced monitoring
▫️ now supports Trino 435, Python 3.11
▪️ EventBridge Customer Managed Keys (CMK) for Event Buses
▪️ HealthImaging
▫️ cross-account data imports
▫️ retrieval of DICOM Part 10 instances
▪️ IAM Identity Center PKCE-based authorization for AWS applications
▪️ Managed Grafana version 10.4
▪️ Managed Service for Prometheus inline editing of alert manager and rules configuration
▪️ MSK removal of brokers from MSK provisioned clusters
▪️ MWAA Airflow REST API with web server auto scaling
▪️ OpenSearch Ingestion new UI for easy blueprint discovery
▪️ RDS for MySQL Extended Support minor 5.7.44-RDS.20240408
▪️ RDS for PostgreSQL Extended Support minor 11.22-RDS.20240418
▪️ S3 no longer charge for several HTTP error codes
▪️ Security Hub CIS AWS Foundations Benchmark 3.0
▪️ VPC Lattice TLS Passthrough
▪️ WorkSpaces Core Windows Server bundles
Upgrading EKS clusters: from v1.23 to v1.30 — in-depth instructions
https://www.cncf.io/blog/2024/05/13/a-step-by-step-guide-to-securely-upgrading-your-eks-clusters/
1️⃣ Plan ahead: Regularly assess Kubernetes releases and upgrade in stages – development, staging, and production.
2️⃣ Control Plane & Data Plane sync: Ensure both are on the same Kubernetes version.
3️⃣ Tools & Automation: Utilize tools like Pluto and Nova for deprecated API checks and Helm releases.
4️⃣ AWS management: Leverage AWS's managed upgrade process for control planes but remember to manage your data plane.
#EKS
https://www.cncf.io/blog/2024/05/13/a-step-by-step-guide-to-securely-upgrading-your-eks-clusters/
1️⃣ Plan ahead: Regularly assess Kubernetes releases and upgrade in stages – development, staging, and production.
2️⃣ Control Plane & Data Plane sync: Ensure both are on the same Kubernetes version.
3️⃣ Tools & Automation: Utilize tools like Pluto and Nova for deprecated API checks and Helm releases.
4️⃣ AWS management: Leverage AWS's managed upgrade process for control planes but remember to manage your data plane.
#EKS
CNCF
A step-by-step guide to securely upgrading your EKS clusters
Member post originally published on Fairwinds’s blog by Stevie Caldwell As an agile open source project, Kubernetes continues to evolve, as does the cloud computing landscape. Keeping up with the…
❤3👍1