Realistically skills in one are transferrable as long as you're thinking of the components in terms of abstractions. For instance, use a deployment pipeline to

Realistically skills in one are transferrable as long as you're thinking of the components in terms of abstractions. For instance, use a deployment pipeline to deploy your microservice with a frontend api for queries against your scalable database, subscribe to your event source and create your faas consumers to push data to your next bounded, isolated component. This is something you can do with any provider, the names are irrelevant. Some features are lock in, but this lock in can be seen as tech debt prior to delivery. Being able to architect cloud systems is just being able to architect distributed systems. Specializing in one isn't a huge problem.