They will undoubtedly sell some aspect of Kuiper through AWS. They already have IP addresses and DNS in the AWS product list, and they have all kinds of data transport services.
I don’t know if the government implication is as big as you think, as the US government has been doing secure satellite communications for decades and has already given SpaceX the contract for Starshield. So undoubtedly Kuiper would love a piece of the action but there is already competition and Kuiper is a bit late to the game.
The federal acquisition regulations have fairly strict rules against acquiring duplicate systems. It totally permits buying systems from multiple vendors, but there are interoperability requirements, and these would have to be interpreted and negotiated. If Kuiper wants to provide services to the government, I’d expect that they would have to be compatible with the Starshield user equipment at a minimum. The military doesn’t want to be lugging around multiple satellite terminals to connect to both the SpaceX and Kuiper versions of Starshield. I doubt the government would go so far as to require SpaceX and Kuiper make their constellations interoperable in space, but even just requiring compatibility with the ground terminals is a pretty big hurdle.
SpaceX has proprietary info in practically all of their comm layers, so interoperability is not easy. The government probably did not buy full rights to the protocols. So the first step to Kuiper getting a piece of the pie is convincing the government that it is worth paying to license SpaceX’s comm standards so Kuiper can use them. That is not an easy task.
There are a dozen hypothetical ways that Kuiper might get a portion of government programs, but the fact is that SpaceX has been embedding themselves into the US government’s space infrastructure for years without competition, and has used that lack of competition to build up a bunch of technical hurdles to purchasing services from other contractors. For the past several years there has been no reason for the government to spend money and effort to prevent these hurdles because there was no other contractor that might be able to offer a similar service. So SpaceX has got a pretty sweet position right now, and Kuiper is going to have to invest heavily before the government changes course.
Starshield is like a private totally separate Starlink for the US government (and controlled/operated by the US government). I am not sure what sort of neutrality you were expecting as US government is SpaceX's biggest customer and is obviously a critical infra company.
Why would you assume any space company anywhere can be neutral to their nations military. These companies depend on government for far too many things (projects, permits) and are much more tied to government than other industries.
Currently “space” as an AWS region is only ground stations communicating with satellites the customer owns, so nothing from AWS is actually in space. But with the way AWS allows customers to configure their network configurations, I expect there will be an option to communicate between AWS data centers using Kuiper for people who have a use case and care enough to pay for it. I expect it to be pretty niche, as most customers are fine with public fiber and Amazon’s own fiber, but I’ll bet they sell it to someone, like a remote AWS Outpost with Kuiper terminal on it for people that work in the field.
I don’t know if the government implication is as big as you think, as the US government has been doing secure satellite communications for decades and has already given SpaceX the contract for Starshield. So undoubtedly Kuiper would love a piece of the action but there is already competition and Kuiper is a bit late to the game.