3 ms·

We are trying to be all Terraform but its not moving fast enough. We still need the the Azure/AWS consul/cli to do much of the work. I switched from an AWS shop

We are trying to be all Terraform but its not moving fast enough. We still need the the Azure/AWS consul/cli to do much of the work. I switched from an AWS shop to a "migrating to Azure from AWS" shop. The new job is all Kubernetes work so I love it but I cannot get comfortable with Azure. I was so much more productive and confident with AWS its crazy. I miss S3, EBS, Snapshots, Route53, IAM and even fucking AWS role policy. I understand MS realizes this which is why they change there API every 4 months but its getting ridiculous we can't even use AKS (instead of ACS) because for some reason they don't role out services to the US North Central Region. WTF?

maximilianburke 8y ago
Yeah, there's a definite hurdle to get over when moving to Azure. I've been finding analogs to most of the services I need, like Blob storage instead of S3, managed disks instead of EBS. There are some things I definitely prefer in Azure to AWS too; I find the AD-based authentication to be much easier to understand and implement compared to IAM. The SMB shares (File storage) are great, integrate well with Kubernetes, and are a lot faster than EFS. Non-premium VM IO performance is abysmal though, and I really wish I could store SSH public keys in Azure AD.