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.
Top comments (21)
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.
😂😂😂😂😂
I would use AWS and avoid any other cloud provider just if they:
Yup. Except this is by design (along with Amazon's intentionally broken APIs).
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.
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
Now you're just being silly.
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.
I know it should be only one, but these are all what I'm asking AWS
This is all by design.
But since we're piling onto the wishlist:
Unfortunately, broken and incomplete AWS APIs is also intentional and by design.
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/
Get all those machines running on solar and wind
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.
hire you.