AWS just went multi-cloud • Hacker News Board

Re: AWS just went multi-cloud

#61

Post by julianozen » Thu, Dec 03, 2020, 5:36 PM UTC

tixocloud wrote: post #14

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

That's a possibility. Another one would be more out of regulatory requirement within financial services. By default, most top tier banks would need multi-cloud to even begin thinking about a cloud journey so this offering just puts AWS in the right space with their competitors. It's possible that most of the operational workloads will run on AWS with other cloud vendors being in place as backup/secondary workloads. M…

Yeah, once those customers have a set up they can just price them into only using AWS Cloud

Deals already signed, thing are already integrated

Re: AWS just went multi-cloud

#62

Post by Loic » Thu, Dec 03, 2020, 5:45 PM UTC

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

This the AWS extension of the Marketplace part of Amazon retail. Thanks to this, they will know how companies are running their systems on other clouds, the same way the know what independent vendors are selling and how well.

This is going to be very interesting on the long run.

Re: AWS just went multi-cloud

#63

Post by dboreham » Thu, Dec 03, 2020, 5:48 PM UTC

cheesgrateron wrote: post #47

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

I've worked as a consultant in this area for years with large F500 companies and not once have I heard anyone actually be concerned with the "lock in" boogeyman. There used to be a lot of concern around general trust of the cloud, which drove people to stick to on-prem servers. But "lock in", IME, is only something people fret about on HN. What I think is happening is that companies are starting to gain more experien…

Anyone who is not concerned about lock in is a fool. There are many fools in business.

Re: AWS just went multi-cloud

#64

Post by rory_isAdonk » Thu, Dec 03, 2020, 5:53 PM UTC

julianozen wrote: post #58

rory_isAdonk wrote: post #24

Earlier quoted context omitted.

That's great to hear. Often online all you hear are the extremes at both ends. I hear that you're basically put on PIP as soon as you join, any truth to this?

No there isnt. I have only known of one person to get a PIP during my 3 years there, and it took way longer then it should've

Ah that was my fear, not because I feel like I'm a terrible software engineer and I'd be asking for PIP by joining Amazon. More just because mortgages etc, I'm very anxious money wise.

Re: AWS just went multi-cloud

#65

Post by stingraycharles » Thu, Dec 03, 2020, 5:55 PM UTC

qz2 wrote: post #21

abiro wrote: post #19

Don’t read too much into this — they are just catching up with GCP and Azure here. AWS has a history of introducing half-assed products with great fanfare when the lack of such a product could be a disadvantage for customer acquisition (think Beanstalk, Cognito or Amplify).

Don’t forget their ElasticSearch version. Now that is a shit show.

Man I remember, whenever we needed to update a cloudformation template that triggered an ElasticSearch modification it was horrible. And of course, after waiting 1.5h, some dns change failed and it had to be rolled back and you just wasted half a day.

Fun times.

Re: AWS just went multi-cloud

#66

Post by Google234 » Thu, Dec 03, 2020, 5:56 PM UTC

randomanon2020 wrote: post #48

rory_isAdonk wrote: post #12

Earlier quoted context omitted.

Is working at AWS hellish? Or once you get in it's just a normal job? I get its heavily dependent on the team, just wondering from your perspective.

I was recently interviewed for AWS, and its a JOKE :), i said i was proficient in Linux and all the questions i was asked was about docker.. and this is just one example out of 100 :)

Yeah, you sound credible/s

Re: AWS just went multi-cloud

#67

Post by qz2 » Thu, Dec 03, 2020, 5:58 PM UTC

stingraycharles wrote: post #65

qz2 wrote: post #21

Earlier quoted context omitted.

Don’t forget their ElasticSearch version. Now that is a shit show.

Man I remember, whenever we needed to update a cloudformation template that triggered an ElasticSearch modification it was horrible. And of course, after waiting 1.5h, some dns change failed and it had to be rolled back and you just wasted half a day. Fun times.

That reminds me of that time I had to do a snapshot on an EBS volume that had Jenkins on it. Took five days to do a 2TB volume.

Local VMware about ten minutes.

Edit: I notice a flurry of downvotes arriving since US woke up. Must be Amazon team coming on line :)

Re: AWS just went multi-cloud

#68

Post by beachy » Thu, Dec 03, 2020, 5:59 PM UTC

dboreham wrote: post #63

cheesgrateron wrote: post #47

Earlier quoted context omitted.

I've worked as a consultant in this area for years with large F500 companies and not once have I heard anyone actually be concerned with the "lock in" boogeyman. There used to be a lot of concern around general trust of the cloud, which drove people to stick to on-prem servers. But "lock in", IME, is only something people fret about on HN. What I think is happening is that companies are starting to gain more experien…

Anyone who is not concerned about lock in is a fool. There are many fools in business.

Everything in life is about risk vs reward.

Platform lock in is a risk. The reward is faster time to market, thus making more money earlier, thus having more means to ameliorate your risks.

Re: AWS just went multi-cloud

#69

Post by redkoala » Thu, Dec 03, 2020, 5:59 PM UTC

cheesgrateron wrote: post #47

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

I've worked as a consultant in this area for years with large F500 companies and not once have I heard anyone actually be concerned with the "lock in" boogeyman. There used to be a lot of concern around general trust of the cloud, which drove people to stick to on-prem servers. But "lock in", IME, is only something people fret about on HN. What I think is happening is that companies are starting to gain more experien…

It depends on the industry. A lot of retail companies are moving away from Amazon to avoid having competitive data flow through AWS infrastructure. Some companies may have different business units across different cloud providers but push for strategic consolidation on a major cloud provider for new implementations.

The heavier the use of cloud native solutions and managed services, the greater the effort to migrate away from those solutions. Not all workloads run on containers, and even then those applications will need some code refactoring if they depend on cloud infrastructure services (cloud specific storage, queue services, monitoring, etc)

Re: AWS just went multi-cloud

#70

Post by wrinkl3 » Thu, Dec 03, 2020, 6:01 PM UTC

randomanon2020 wrote: post #48

rory_isAdonk wrote: post #12

Earlier quoted context omitted.

Is working at AWS hellish? Or once you get in it's just a normal job? I get its heavily dependent on the team, just wondering from your perspective.

I was recently interviewed for AWS, and its a JOKE :), i said i was proficient in Linux and all the questions i was asked was about docker.. and this is just one example out of 100 :)

> i said i was proficient in Linux and all the questions i was asked was about docker

Why is that bad? The purpose of an interview is to see if you're fit for the role, not quiz you on the skills on your resume.