Virtual private cloud

I am thrilled to have you with us today because we have a jam-packed show for cloud architects, developers, and data engineers alike.

In this episode, we will explore, first, massive improvements in compute and containers headlined by direct VPC ingress for Cloud Run, storage optimized Z4M instances, and in-place node upgrades in GKE and automatic capacity failover in cloud workstations.

Next, Our data analytics section is bursting with new capabilities.

BigQuery makes AI text processing native with document chunking and translation functions.

Then, over in Databases, AlloyDB launches Lakehouse Federation to query live BigQuery tables directly, Spanner brings approximate aggregates with HyperLogLog++ for lightning-fast distinct counts, and Firestore makes both data modification language and advanced search generally available.

After that, we step into the Gemini Enterprise agent platform and conversational AI, highlighting single user quota controls, the new anti-gravity enterprise gateway, and a clever feature in Dialogflow CX to salvage phone calls in loud environments.

Finally, we wrap up with security and networking, including critical patch notices across managed PHP runtimes, Cloud NAT troubleshooting in VPC flow logs, and substantial IAM updates.

Let us get right into the details.

Like, yes, state machines could work, but this was good for, like, I already have the logic coded up in a container and things like that.

So, I mean, if you need to run on your own VPC, there's difficulties with it, and all the logic needs to exist within the thing.

So it's,

I don't know how much it's

AWS IAM Identity Center now supports network access controls for Identity Store.

This lets admins lock down the Identity Store API and SCIM API to specific networks, addressing a common security gap where identity management APIs were accessible from anywhere with valid credentials.

Admins can require identity store API traffic to originate only from approved VPC endpoints or source VPCs, while separately restricting SCIM API access to specific IP ranges, such as an external identity provider's published range.

A use case for this would be that an organization uses Okta or Azure AD or a similar provider for SCIM provisioning can now whitelist those providers' IP range.

The prevailing logic was you kind of work in a cloud environment with a bunch of other tenants.

The AI data sovereignty question would push Humana to basically say, no, at a minimum, we need to be in a VPC.

At a maximum, we need to be in an air gap facility that's our own.

So there is going to be a lot of domestic terrestrial build out as a result of these strategic decisions.

Then, of course, we have the SAS model where we provision the hardware and the data would go to us for our GPUs and then go back.

Or we can also install in people VPCs, so virtual private cloud.

But does that mean you always have to have GPUs to make this run? You have to have GPUs.

Yeah, this is an advanced neural network that requires GPUs.