[makethetick]

You should take a look at Amplify (https://aws.amazon.com/amplify/), it will make the whole process considerably less painful, allow you to easily access AppSync (graphql) and Lambda with your code all in one place, then also trigger rebuilds on git commits.

[speedgoose]

Too much vendor lock-in.

[thih9]

Could you give examples where vendor lock in becomes a problem?

Ideally something practical (as opposed to theoretical) or something from personal experience.

I generally agree but I feel that more details could be useful.

[speedgoose]

It's simple, you are not stuck with a vendor.

A practical example that happened to my employer recently : we migrated to Microsoft Azure when they opened two datacenters in our country. We didn't have to change any code because we don't use vendor locked solutions.

[ssss11]

Any time you want to leave that vendor. If they up their prices greatly, reduce service levels, refuse to give attention to improving service levels.. break a clause in the contract... an so on.

[rpadovani]

While this is true in theory, I don't recall a single instance of AWS increasing pricing or reducing service levels - not saying that is impossible, but it hasn't happened so far (at least that I remember)

[rat9988]

When you deal with google cloud and they up their price. Didn't see it with the other vendors though.

[makethetick]

It is but you've already stepped down this path the moment you moved away from shared or self hosting.

[speedgoose]

I think hosting files in a S3 bucket with a CDN in front is easy to replace. You can do the same with two Docker containers or host it the same way in many other clouds.