Answers: <p>There are no "agnostic" products due to the dramatic differences of the design of the Cloud Services provided by different companies.</p>
  
  <p>My best recommendation is to write your code to support the different cloud providers. Whether you choose Ansible or Terraform this can be done with Ansible Roles or Terraform Modules that are specific to the cloud provider. Just the same as you would write Ansible roles specific to Operating Systems or different scenarios.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-02-19T17:25:06.930Z
Answers: 2020-02-19T17:25:06.930Z
Answers: Steven K7FAQ
Body: <p>Are there any infrastructure automation technologies which do a better job at being portable than terraform?</p>
  
  <p>We heavily leverage terraform as it is a cloud-agnostic technology (vs, say, ARM templates in azure, or cloud formation in AWS).</p>
  
  <p>I was very depressed a year ago when we deployed an app from azure to AWS to see that a basic scale-set + load balancer basically required a complete rewrite between Azure and AWS though.  Having used ansible equivalents, the same seems to be true there. Both basically use cloud-specific extensions to create cloud resources meaning that, while you understand the tool still, any project you code has to be re-coded for deployment in a new cloud.</p>
  
  <p>I understand that a generic tool would  have to understand numerous differences like:</p>
  
  <ul>
  <li>Azure uses resource groups to encapsulate all resources.</li>
  <li>AWS has security groups to define network boundaries.</li>
  <li>AWS load balancers require separate target groups/listeners vs Azure's  simpler backend pool concept.</li>
  <li>IAM differences, and so on.</li>
  </ul>
  
  <p>I'm surprised there aren't any companies or OSS projects trying to simplify/automate the translations here with a higher level DSL or something though.  So, I'm thinking I might be missing something.</p>
  
  <p>Note: We are heavy kubernetes users, so I do understand that kubernetes mitigates most of these issues <strong>once you've brought up a cluster</strong> (and if you have ported all your apps to it).</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-02-17T06:00:14.580Z
Comments: So, you've answered yourself))
Comments: Vasiliy  Shakhunov
Tags: <amazon-web-services><terraform><azure><automation>
Title: Cloud agnostic infrastructure automation better than terraform?
UserDisplayName: John Humphreys
ThreadText: # Cloud agnostic infrastructure automation better than terraform?
  
  (Asked by: username_0 on 2020-02-17)
  
  Are there any infrastructure automation technologies which do a better job at being portable than terraform?
  
  We heavily leverage terraform as it is a cloud-agnostic technology (vs, say, ARM templates in azure, or cloud formation in AWS).
  
  I was very depressed a year ago when we deployed an app from azure to AWS to see that a basic scale-set + load balancer basically required a complete rewrite between Azure and AWS though. Having used ansible equivalents, the same seems to be true there. Both basically use cloud-specific extensions to create cloud resources meaning that, while you understand the tool still, any project you code has to be re-coded for deployment in a new cloud.
  
  I understand that a generic tool would have to understand numerous differences like:
  
  * Azure uses resource groups to encapsulate all resources.
  * AWS has security groups to define network boundaries.
  * AWS load balancers require separate target groups/listeners vs Azure's simpler backend pool concept.
  * IAM differences, and so on.
  
  I'm surprised there aren't any companies or OSS projects trying to simplify/automate the translations here with a higher level DSL or something though. So, I'm thinking I might be missing something.
  
  Note: We are heavy kubernetes users, so I do understand that kubernetes mitigates most of these issues **once you've brought up a cluster** (and if you have ported all your apps to it).
  
  **Tags:** amazon-web-services, terraform, azure, automation
  
  > **Comments:**
  > **username_1**: So, you've answered yourself))  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-02-19. Score: 3 | Accepted answer
  
  There are no "agnostic" products due to the dramatic differences of the design of the Cloud Services provided by different companies.
  
  My best recommendation is to write your code to support the different cloud providers. Whether you choose Ansible or Terraform this can be done with Ansible Roles or Terraform Modules that are specific to the cloud provider. Just the same as you would write Ansible roles specific to Operating Systems or different scenarios.
  
  
  ---
  
  