If you were the new CEO of Amazon Web Services what would be your first executive order?

#aws

Feb 7 ・1 min read

Andy Jassy who is the current CEO of Amazon Web Services (AWS) is going to be the new CEO of Amazon. It's uncertain who will be next to the CEO of AWS.

If you could have full control of AWS what would you decree?

I would add a Dark Theme to the AWS Console.

Discussion (21)

Aaron J Spetner • Feb 7

AWS Snowblower: Move files from on-prem to the cloud using a swarm of drones.
AWS Hot Tub: A much better name for Aurora Serverless's "warm pools"
AWS Interstellar: New regions in the Alpha Centauri and Sirius systems to eliminate downtime in the event the sun unexpectedly explodes.

Jason C. McDonald • Feb 8

😂😂😂😂😂

Yaser Al-Najjar • Feb 7

I would use AWS and avoid any other cloud provider just if they:

Simplified AWS like DigitalOcean (better UI and UX).
Made monthly cost calculation easier (before using any service).

cubiclesocial • Jun 8

Yup. Except this is by design (along with Amazon's intentionally broken APIs).

Dustin Krysak • Feb 7

Labbing improvements. An optional setting where you can shut down all cost infrastructure based on a $ amount. Projects like gcp (deleting a project deletes all infra/cost), and a "reset all" at the AWS account level. This all makes it easier to learn and protect yourself from a mortgage sized bill as someone who is new to the platform. Reduces financial risk.

Butch • Feb 8

They need to create a simulator services for AWS architecture, this is highly needed everytime we need to assessed the architecture and its expenditure before the actual dev work is implemented... Something similar to this but absolutely free.

app.cloudcraft.co/

Ariel Costas • Feb 8

I know it should be only one, but these are all what I'm asking AWS

Fix the fkn console's UI
Remove the AWS/Amazon name mixing, keeping only Amazon.
Make cost calculations simpler.
Add better ways to prevent 60k$ bills, like having a "circuit breaker" that when you exceed X monthly expenses all services are shut down and an email is sent to you.

cubiclesocial • Jun 8 • Edited

This is all by design.

But since we're piling onto the wishlist:

APIs that are feature-complete and not gimped in any way. For example, the Cloud Drive API never had the ability to delete files but you could manually delete files via the web interface.

Unfortunately, broken and incomplete AWS APIs is also intentional and by design.

Ibrahim Cesar • Feb 7

For me is easy: Effectivelly immediatelly uniform all product names to AWS X and drop the Amazon/AWS cacophony. After that, I could take a breath and start to work

Aaron J Spetner • Feb 7

Now you're just being silly.

ssg-cnc • Feb 7

As AWS CEO, I would split AWS into several companies. AWS, AI/ML, Gaming, Mobile/IoT, Media, and Business. The issue isn't features and product offering but too many of each. Most of us use a dozen or more of the common services and don't need the other specialty type services.

Luke Westby • Feb 8

Get all those machines running on solar and wind

Aaron J Spetner • Feb 7

Eliminate the mandatory 12 hour (regardless of last activity) sign-out of the AWS console. Too many times I'll log in at 11:30pm to take care of something. Then the next morning I'm still logged in and I am working on the console when BAM at 11:30am I am automatically logged out regardless of what I was doing at the time.
The same issue exists with Cognito, although the timeout is customizable.

Cas Hoefman • Feb 7

Massive wage increases.

Pato • Feb 8

hire you.

Serhii Vasylenko • Feb 8

I would hire someone to proofread and validate the naming for the new services.
I love AWS, but "DevOps Guru"? Really? 🙃

amirtime • Mar 29

I would apply these changes:
-Stop changing the names, icons, UIs, every day.
-Making the documentation more simplified and less scripted, and replacing the scripts with visual method and actual environment demo.
-Centralize and simplify the cost dashboard and alerts throughout the whole ecosystem