Live data from Hacker News

OpenAI frontier models and Codex are now available on AWS

openai.com

101–110 of 158 posts

Re: OpenAI frontier models and Codex are now available on AWS

#101

This is a great move for OpenAI and one that should worry Anthropic. Bedrock was the only way I could use foundation models for a while given AWS lock-in and security requirements.

Claude is already available as both a pass-through to Anthropic's servers from AWS and in Bedrock. https://aws.amazon.com/claude-platform/ I imagine they're not thrilled that their first mover advantage has gone now, but they'll have seen it coming a mile off.

Re: OpenAI frontier models and Codex are now available on AWS

#102
post #8

If you are wondering why anyone would spend more money to use these APIs through AWS instead of going direct: In some companies it’s nearly impossible to get new vendors approved. If the company has an AWS contract then you have to use what AWS offers.

Wait, is AWS just reselling access to some AI company's servers, or is AWS running the models on their own hardware?

Re: OpenAI frontier models and Codex are now available on AWS

#103
post #10

If you've used AI coding models in a large corporate setting, you'll know that a lot of big corporate deployments basically require using AWS Bedrock for two simple reasons: 1. Large companies tend to already have an existing relationship with AWS, which makes things way easier to go through vs. setting up a new vendor relationship 2. Large companies tend to have strong internal requirements about making sure that in…

[dead]

Re: OpenAI frontier models and Codex are now available on AWS

#104

Every time somebody questions why you might "trust" AWS (or Azure or GCP or whatever), or why you'd pay this premium, I realize they are not accustomed to working in enterprise environments. In my case, I work at a large enterprise with strict data governance built into customer contracts, and (partly related, partly not) our own governance concerns. Using vendors where you not only have infosec permission, but they…

In my company is simpler, we deal with data under EU Export Control so we cannot use any US provider due to the CLOUD Act.

Re: OpenAI frontier models and Codex are now available on AWS

#108

Earlier quoted context omitted.

I would absolutely fire someone for using Azure without extenuating circumstances.

Are you the CTO of a $1b+ revenue company?

Are they the only people allowed to fire someone?

Re: OpenAI frontier models and Codex are now available on AWS

#109

Every time somebody questions why you might "trust" AWS (or Azure or GCP or whatever), or why you'd pay this premium, I realize they are not accustomed to working in enterprise environments. In my case, I work at a large enterprise with strict data governance built into customer contracts, and (partly related, partly not) our own governance concerns. Using vendors where you not only have infosec permission, but they…

Have you considered checking the actual AWS contract and the limited liability they explicitly stipulate in contracts and even linked docs from marketing materials? If you read the fine print, you'll notice something funny. You are largely responsible for data loss, SLA claims require you to present concrete evidence, and the remediation you accepted is usually credits for future spend on specifically the same produc…

They didn't mention anything about SLAs. This is about all the time, effort, paperwork and risk it takes to add yet another vendor. Having fewer vendors does actually reduce risk, as long as your chosen vendors are reasonably good. Though the bigger reason is certainly avoiding the additional bureaucracy, which is partly self-inflicted in larger companies but also not without merit.

Re: OpenAI frontier models and Codex are now available on AWS

#110

Earlier quoted context omitted.

Are you the CTO of a $1b+ revenue company?

Are they the only people allowed to fire someone?

What GP meant is that the CTO of a $1b company wold absolutely not fire someone for going Azure because at those scale it's very likely they have a set of customers that exclusively want to work on Azure, so that choice makes sense.

It's easy to do blanket statements like "never choose azure", "avoid GCP at all cost" or "never again on AWS". Until real world comes your way and you are forced to deal with it.

That being said: I'd fire anyone choosing to deploy a workload on GCP.

Post reply on HN