AWS CodePipeline + CodeDeploy are horrors¹ from what I saw at a client.
They had mandated .Net + Javascript for all development, GitHub for versioning, and AWS for all other cloud services.
The different projects they had going were not complex or huge.
Yet it took months to get it up and running.
The last month at least they paid for AWS specialists to come in and
set it up and even they spent weeks.
Throughout it all, any notion of trying a different CI/CD stack were
rudely dismissed.
Once it was up and running nobody dared touch the pipeline
again.
From all the AWS services that the customer used nothing
was ever comparable to the horrors of their CI/CD.
Setting it up with Azure's offerings would have been damned near trivial.
I have however not used those in production so I do not have the
experience to able to say it is a better solution over all.
¹ In fairness, AWS had just recently released the CI/CD offerings
and things may be a lot better now. I havent look at it again
since then.
The different projects they had going were not complex or huge.
Yet it took months to get it up and running. The last month at least they paid for AWS specialists to come in and set it up and even they spent weeks.
Throughout it all, any notion of trying a different CI/CD stack were rudely dismissed.
Once it was up and running nobody dared touch the pipeline again.
From all the AWS services that the customer used nothing was ever comparable to the horrors of their CI/CD.
Setting it up with Azure's offerings would have been damned near trivial. I have however not used those in production so I do not have the experience to able to say it is a better solution over all.
¹ In fairness, AWS had just recently released the CI/CD offerings and things may be a lot better now. I havent look at it again since then.