Aidan W Steele

12.8K posts

Aidan W Steele

Aidan W Steele

@__steele

I try to tweet novel things about AWS.“Shit-poster extraordinaire” according to @LastWeekInAWS. He/him. AWS Serverless Hero

Melbourne, Australia Se unió Nisan 2011
2.3K Siguiendo9.7K Seguidores
Aidan W Steele
Aidan W Steele@__steele·
New frustration just dropped: AWS won't let me run even one t4g.nano in us-west-2. This account has spent a few hundred bucks in the past few months. I've had EC2 instances running in ap-southeast-2 for months. How can I get out of this service quota naughty corner?
Aidan W Steele tweet mediaAidan W Steele tweet media
Aidan W Steele@__steele

Today's frustration: my Lambda functions are limited to 3008 MB of RAM. I've filed a case in both dev and prod accounts. Mind you, my "please enable S3 transfer acceleration" case is still unassigned, 8 days later.

English
6
1
17
6.1K
Michael Timbs
Michael Timbs@michael_timbs·
If I'm one of the employees at block im praying to be on that cut list.
English
3
0
8
550
Michael Timbs
Michael Timbs@michael_timbs·
@__steele yeah days after big layoffs are always such a strange atmosphere
English
1
0
1
23
Aidan W Steele
Aidan W Steele@__steele·
@michael_timbs It’s not bad at all. It’s just going to be hard to get any work done with everyone in a shitty mood
English
1
0
1
19
Aidan W Steele
Aidan W Steele@__steele·
@michael_timbs It went up 20-something percent and then they gave the survivors massive RSU refreshers on the same morning as the “you’re fired/not fired”’email
English
1
0
1
16
Michael Timbs
Michael Timbs@michael_timbs·
@__steele did the stock really go up that much? I forgot to even check
English
1
0
1
20
dan nolan
dan nolan@dannolan·
Man maybe I was wrong
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
10
1
33
10.6K
Aidan W Steele
Aidan W Steele@__steele·
It's frustrating that CloudFront signed URLs only support SHA-1, and KMS only supports newer algorithms. It seems there's no way to do signed URLs without having to store key material. It's even more annoying that my account can't just use S3 transfer acceleration instead.
English
1
1
15
2.1K
Aidan W Steele
Aidan W Steele@__steele·
Today's frustration: my Lambda functions are limited to 3008 MB of RAM. I've filed a case in both dev and prod accounts. Mind you, my "please enable S3 transfer acceleration" case is still unassigned, 8 days later.
Aidan W Steele@__steele

It's exhausting to have an AWS org has been through multiple billing cycles, spending over $100/month and still get papercuts on Every. Single. Little. Thing. Domains fail to register. CodeBuild allowlisting. S3 transfer acceleration allowlisting. And it's per account!

English
13
0
16
9.7K
Aidan W Steele
Aidan W Steele@__steele·
Claude Code on the web, Codex Web, et al should make an OIDC token available to the container. This would be better than an AWS access key, GCP keys, etc. On the team/enterprise plans it would identify the session itself, the user who kicked it off, the repo, the enterprise ID.
English
2
2
18
1.3K
Aidan W Steele
Aidan W Steele@__steele·
301 (out of 1,436 total) of AWS' IAM managed policies got a version bump a few days ago. It all happened in a 6 minute window (centred around 2026-02-12T18:00Z), with zero actual changes to the policy documents. Weird.
English
1
1
29
4.6K
Aidan W Steele
Aidan W Steele@__steele·
It's exhausting to have an AWS org has been through multiple billing cycles, spending over $100/month and still get papercuts on Every. Single. Little. Thing. Domains fail to register. CodeBuild allowlisting. S3 transfer acceleration allowlisting. And it's per account!
English
7
2
22
9K
Aidan W Steele
Aidan W Steele@__steele·
Today a CloudFront distribution took over an hour to deploy and I had flashbacks to ~2012, waiting 90 minutes for deployments (45 minutes to fail, 45 minutes for CloudFormation to rollback those changes)
English
2
0
23
1.6K
Aidan W Steele
Aidan W Steele@__steele·
Be sure to unescape your HTML before you do a production run of collectibles.
Aidan W Steele tweet media
English
0
0
9
709
Jane Manchun Wong
Jane Manchun Wong@wongmjane·
@__apf__ Get the electric box cutter and recycling bin! It saved me a ton of headache
Jane Manchun Wong tweet mediaJane Manchun Wong tweet media
English
4
1
22
2.6K
Adriana Porter Felt
Adriana Porter Felt@__apf__·
happy cardboard sculpture season to all who celebrate
Adriana Porter Felt tweet media
English
13
13
431
27.8K
Aidan W Steele
Aidan W Steele@__steele·
AWS, let me pay you $100 when I spin up a new org just so I can get past all these hurdles. I’m even willing to wait a month cooling-off period. I just don’t want to have to beg to use each service on a feature-by-feature basis.
English
0
0
6
1.2K
Aidan W Steele
Aidan W Steele@__steele·
I tell someone they should use CloudFront. They ask “won’t we need to request permission to use it?” because their Route 53 domain registration failed yesterday. I said I’m sure it’s fine. Then they get this error. This onboarding is so bad, it’s embarrassing.
Aidan W Steele tweet media
English
5
0
7
1.7K
Aidan W Steele
Aidan W Steele@__steele·
@theburningmonk What do these resolve to? Doesn’t the serverless transform resolve to “native” CloudFormation types?
English
1
0
3
140
Yan Cui
Yan Cui@theburningmonk·
Looks like you have to use SAM's AWS::Serverless::Function and AWS::Serverless::CapacityProvider types to create a Lambda function with managed instances for now. Am I missing something here? 🤔
English
3
0
3
917
Yan Cui
Yan Cui@theburningmonk·
mm.. did AWS release Lambda Managed Instances without CloudFormation support? The AWS::Lambda::Function type doesn't let you choose the managed instance option, but the CreateFunction API does. And there doesn't appear to be a CloudFormation type for Lambda capacity providers.
English
2
1
24
3.2K