Nice!

I've built Kvist.ai which is a polished version of this.

It's still on AppSync v1.

It's currently using OpenAI because Bedrock is still too buggy and not yet ready for production.

Whats's going on #AWS?

Can we recommend our clients to use Bedrock for their AI workloads moving forward?

Things break - even at AWS, but what's alarming and unprecedented by this is the complete lack of comms around it. We had to find out via our users who experienced a drop in quality.

Contacted the support who doesn't seem to prioritise getting us back online... 🧵

Well, can't say I've been on top of my tooling work in the past year, but this one triggered me to hack-attack

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.