Vlad Ionescu (he/him)
@vladionescu.me
sugarbaby cosplaying as a tech consultant • mean eastern european with unrealistically high expectations and unreasonable quality standards
🏳️🌈he/him🏳️🌈
🏳️🌈he/him🏳️🌈
As a complete aside, it have been nice for AWS to also maintain, update, and enhance the github.com/bottlerocket... 🙃
GitHub - bottlerocket-os/bottlerocket-ecs-updater: A service to automatically manage Bottlerocket updates in an Amazon ECS cluster.
A service to automatically manage Bottlerocket updates in an Amazon ECS cluster. - bottlerocket-os/bottlerocket-ecs-updater
github.com
October 7, 2025 at 10:58 AM
As a complete aside, it have been nice for AWS to also maintain, update, and enhance the github.com/bottlerocket... 🙃
Are the images used that different from the official Bottlerocket ECS AMIs at docs.aws.amazon.com/AmazonECS/la... ?
They would have to automate the AMI rollout which, assuming folks aren't using pet EC2s, is not *that* complex. It's not easy but it's not "13% of EC2 spend" levels of complex either
They would have to automate the AMI rollout which, assuming folks aren't using pet EC2s, is not *that* complex. It's not easy but it's not "13% of EC2 spend" levels of complex either
October 7, 2025 at 10:56 AM
Are the images used that different from the official Bottlerocket ECS AMIs at docs.aws.amazon.com/AmazonECS/la... ?
They would have to automate the AMI rollout which, assuming folks aren't using pet EC2s, is not *that* complex. It's not easy but it's not "13% of EC2 spend" levels of complex either
They would have to automate the AMI rollout which, assuming folks aren't using pet EC2s, is not *that* complex. It's not easy but it's not "13% of EC2 spend" levels of complex either
Wooo welcome to Bucharest 🎉👋🎉
June 19, 2025 at 12:09 PM
Wooo welcome to Bucharest 🎉👋🎉
(I felt that I had to reply to this since I was a big fan of AVP's potential aaaaaand then I totally dissapeared from social media)
June 14, 2025 at 9:41 AM
(I felt that I had to reply to this since I was a big fan of AVP's potential aaaaaand then I totally dissapeared from social media)
AVP isn't a product that AWS takes seriously so I'd suggest also taking a look at Oso 😅
June 14, 2025 at 9:37 AM
AVP isn't a product that AWS takes seriously so I'd suggest also taking a look at Oso 😅
*hugs*
This was also (one of the reasons) I was driven away from social media / dramatically reduced my public web presence too. The tech community is wildly toxic but the open-source fanatics are... a particular level of abhorrent
This was also (one of the reasons) I was driven away from social media / dramatically reduced my public web presence too. The tech community is wildly toxic but the open-source fanatics are... a particular level of abhorrent
April 26, 2025 at 1:00 PM
*hugs*
This was also (one of the reasons) I was driven away from social media / dramatically reduced my public web presence too. The tech community is wildly toxic but the open-source fanatics are... a particular level of abhorrent
This was also (one of the reasons) I was driven away from social media / dramatically reduced my public web presence too. The tech community is wildly toxic but the open-source fanatics are... a particular level of abhorrent
Lol, I would argue that before moats they need an actual product first (you know, something that's not a short-lived feature arbitrage)
March 13, 2025 at 1:25 PM
Lol, I would argue that before moats they need an actual product first (you know, something that's not a short-lived feature arbitrage)
It was all custom — some using GitHub Actions, some using custom tools.
November 18, 2024 at 5:35 PM
It was all custom — some using GitHub Actions, some using custom tools.
Still, this is not trivial to implement and, worse, this requires a serious company and serious developers (not only software engineers but product, testing, sales, support, etc).
That's surprisingly rare so... yeah, it'll remain a super-high-performing thing that few people talk about :(
That's surprisingly rare so... yeah, it'll remain a super-high-performing thing that few people talk about :(
November 18, 2024 at 4:08 PM
Still, this is not trivial to implement and, worse, this requires a serious company and serious developers (not only software engineers but product, testing, sales, support, etc).
That's surprisingly rare so... yeah, it'll remain a super-high-performing thing that few people talk about :(
That's surprisingly rare so... yeah, it'll remain a super-high-performing thing that few people talk about :(
A few teams measured this and the metrics after 6 months were *mindblowingly* better!
One exception: on-boarding slowed a bit :lolsob: It was so hard getting new devs in and having them get used to "no, seriously, if checks are green we ship whatever to prod and it's fine! We have intense checks!"
One exception: on-boarding slowed a bit :lolsob: It was so hard getting new devs in and having them get used to "no, seriously, if checks are green we ship whatever to prod and it's fine! We have intense checks!"
November 18, 2024 at 3:59 PM
A few teams measured this and the metrics after 6 months were *mindblowingly* better!
One exception: on-boarding slowed a bit :lolsob: It was so hard getting new devs in and having them get used to "no, seriously, if checks are green we ship whatever to prod and it's fine! We have intense checks!"
One exception: on-boarding slowed a bit :lolsob: It was so hard getting new devs in and having them get used to "no, seriously, if checks are green we ship whatever to prod and it's fine! We have intense checks!"
My answer: not enough tooling.
I worked with a bunch of teams that did post-PR code reviews (if the code is under a feature flag => PR is automatically approved, merged, and deployed to prod) but the setup required was non-trivial 😞
Everybody (including compliance) was super-happy with it tho!
I worked with a bunch of teams that did post-PR code reviews (if the code is under a feature flag => PR is automatically approved, merged, and deployed to prod) but the setup required was non-trivial 😞
Everybody (including compliance) was super-happy with it tho!
November 18, 2024 at 3:54 PM
My answer: not enough tooling.
I worked with a bunch of teams that did post-PR code reviews (if the code is under a feature flag => PR is automatically approved, merged, and deployed to prod) but the setup required was non-trivial 😞
Everybody (including compliance) was super-happy with it tho!
I worked with a bunch of teams that did post-PR code reviews (if the code is under a feature flag => PR is automatically approved, merged, and deployed to prod) but the setup required was non-trivial 😞
Everybody (including compliance) was super-happy with it tho!
They fixed it, with impressive speed: the docs are now a lot clearer and even the changelog has been updated with additional details ❣️
AWS received feedback and they took super-prompt action to address it — awesome job AWS!
AWS received feedback and they took super-prompt action to address it — awesome job AWS!
September 17, 2024 at 7:09 PM
They fixed it, with impressive speed: the docs are now a lot clearer and even the changelog has been updated with additional details ❣️
AWS received feedback and they took super-prompt action to address it — awesome job AWS!
AWS received feedback and they took super-prompt action to address it — awesome job AWS!
I was annoyed I was missing it but now I am properly devastated I won't be there 😭
September 16, 2024 at 7:10 AM
I was annoyed I was missing it but now I am properly devastated I won't be there 😭
They have everything: from high-scale stuff (how delivery works at Tazz) to fast prototyping (prototype to prod in ~6 months with both tech and non-tech drama) to executive strategy, and so much more.
There's even a preview for re:Invent 2024!
There's even a preview for re:Invent 2024!
September 16, 2024 at 7:10 AM
They have everything: from high-scale stuff (how delivery works at Tazz) to fast prototyping (prototype to prod in ~6 months with both tech and non-tech drama) to executive strategy, and so much more.
There's even a preview for re:Invent 2024!
There's even a preview for re:Invent 2024!
Fix is coming, as per the attached conversation with an AWS WAF PM.
September 15, 2024 at 6:55 AM
Fix is coming, as per the attached conversation with an AWS WAF PM.
AWS WAF Bot Control moving bots from "un-verified" to "verified" means that bots that were previously blocked by default will now just get... counted.
Totally unexpected and not at all clear, right?
Don't you think this deserved a warning in the docs/announcement?
14/14
Totally unexpected and not at all clear, right?
Don't you think this deserved a warning in the docs/announcement?
14/14
September 14, 2024 at 5:22 PM
AWS WAF Bot Control moving bots from "un-verified" to "verified" means that bots that were previously blocked by default will now just get... counted.
Totally unexpected and not at all clear, right?
Don't you think this deserved a warning in the docs/announcement?
14/14
Totally unexpected and not at all clear, right?
Don't you think this deserved a warning in the docs/announcement?
14/14
Folks can of course change the default actions but we all know the power of defaults.
See Internet Explorer, Apple, Google, Chrome, and all the new cases on this topic 🫠
13/14
See Internet Explorer, Apple, Google, Chrome, and all the new cases on this topic 🫠
13/14
September 14, 2024 at 5:22 PM
Folks can of course change the default actions but we all know the power of defaults.
See Internet Explorer, Apple, Google, Chrome, and all the new cases on this topic 🫠
13/14
See Internet Explorer, Apple, Google, Chrome, and all the new cases on this topic 🫠
13/14
By default, un-verified bots are a BLOCK.
If AWS WAF Bot Control doesn't know how to check the bot is indeed who it's saying it is, that means that it could be an attacker pretending to be a bot, so it is blocked by default.
12/14
If AWS WAF Bot Control doesn't know how to check the bot is indeed who it's saying it is, that means that it could be an attacker pretending to be a bot, so it is blocked by default.
12/14
September 14, 2024 at 5:22 PM
By default, un-verified bots are a BLOCK.
If AWS WAF Bot Control doesn't know how to check the bot is indeed who it's saying it is, that means that it could be an attacker pretending to be a bot, so it is blocked by default.
12/14
If AWS WAF Bot Control doesn't know how to check the bot is indeed who it's saying it is, that means that it could be an attacker pretending to be a bot, so it is blocked by default.
12/14
By default, verified bots are a COUNT.
AWS WAF Bot Control is able to guarantee this is indeed the bot it's saying it is, so the request is neither blocked nor allowed.
11/14
AWS WAF Bot Control is able to guarantee this is indeed the bot it's saying it is, so the request is neither blocked nor allowed.
11/14
September 14, 2024 at 5:21 PM
By default, verified bots are a COUNT.
AWS WAF Bot Control is able to guarantee this is indeed the bot it's saying it is, so the request is neither blocked nor allowed.
11/14
AWS WAF Bot Control is able to guarantee this is indeed the bot it's saying it is, so the request is neither blocked nor allowed.
11/14