Ground stations -- which are how you talk to and listen to satellites -- available to the public opens up the market for flight ops folk like me with extensive experience, but not currently working for a big company.
See, if you want to launch, either you're going skin of your teeth like a school or you're hiring... let's say the crew of the Enterprise. Not a small number of people. This AWS ground station deal? This lets you hire anywhere from Han Solo (me, effectively) to the Firefly crew (me plus a few others, and I'm a Wash/Kaylee combination.)
Hiring a freelance/small-scale independent flight ops specialist is going to be more cost-effective for any organization that's not a large company. At least half your console time during normal ops for one satellite is sitting there waiting for contact. Hourly, that gets pretty pricey. So... hire for four hours. You're not paying for an entire shift of waiting around, and if there's a missed contact or an emergency you have the flexibility to allow for that. This, however, is for satellites already up and flying.
Pre-launch and LEOPS (Launch and Early OperationS) -- which I have experience in and not everyone does -- is critical for prepping to launch. And again, normally this is several people and a lot of insanity... and a lot of coordination that eats time and money. You need testing, scripts, standard operating procedures, documentation, and training for anyone who comes in later. All of those are well within my experience to the point that I forget to mention them; they're standard issue for me.
Another key thing that the AWS ground station capability opens up is the ability to command from theoretically anywhere. This is huge. There is a reason that NASA has multiple ground control centers; everyone knows about Houston, but did you know that there's a backup at NASA Goddard in Greenbelt, MD? I used to work in the same building that houses it, and now and then I'd wander by just to smile. The ability to command from multiple locations allows flexibility for ground equipment failure (as much as possible with flight operations), operator illness, inability to get to the command center due to weather or other concerns... I'll tell you from personal experience that you can fly a satellite with a nasty head cold, but your coworkers will NOT appreciate it. You can take out an entire flight ops team AND Engineering with one unprotected sneeze – or unexpected snowstorm.
The ability to command from anywhere also means that there's no need to lease and build out commercial space for a control center. This is a significant change from the current model of satellite operations; there is no need for a dedicated control center, even a shared one.
The key thing here is that this opens up satellite ownership and operation to a much wider audience... and those satellites need someone experienced to fly, troubleshoot, fix, and talk to them. Which is where I come in. I have the extremely uncommon mix of LEO (Low Earth Orbit) flight operations, spacecraft flight engineering, testing, project management, incident response, technical writing, scripting, and training to be able to help anyone get from concept to smooth daily operations.
If you can build it, I can fly it and keep it going as long as the hardware holds out.