Working on an integration with a SaaS that gives me HTTP status 429 whatever I do.

The best way to find out why they don't scale is to look at their job openings.

#serverless

On Oct 20, Amazon Bedrock had an issue that strangled access to the Bedrock models we prior to that had full access to. This happended to lots of customers.

We went from 20rpm to just 1rpm without prior notice and no comms after. We have a fallback on OpenAI, so our app carried on working... 🧵

I swapped to N.Virgina and my invocation went through! Once - the rest got throttled.

My client wanted this inference done ASAP and gave me an OpenAI API key.

I will move it over to Bedrock once I get this sorted, but why, #AWS, does it have to be so difficult to start using Bedrock?

Today I worked on a client's account. I saw that Claude 3.5 Sonnet had a green Access Granted in both Frankfurt and N.Virgina. I thought "nice - someone has already done the support ping-pong" and started building. I started in Frankfurt, but every request got throttled.

Under account & billing support there's a Bedrock Allowlisting option. I'm going with that. A couple of days later I hear back from someone who said they passed the issue on to tech support.

Another day goes by and voila, I have access.

I wanted to enable Claude 3.5 Sonnet in Frankfurt because an official #AWS blog post said it's available there.

It wasn't available, so I had to contact support. It's a brand new account and I'm on basic support, so can't raise a technical support ticket.