Customize and Extend EL2 EC2 Linux Launch to create any Linux AWS Architecture

You may download, use and experience the feelings of amazement, inner peace and security that come with EL2 and Air GAP as standard; which is entirely normal, but by customizing and extending this powerful  infrastructure as code  - you can paint infrastructure masterpieces in the cloud. Get exposure to 100% of the AWS configuration surface, plus gain the ability to customize every minute detail, learn from and extend both EL2, Air GAP and other components, to create your own 'one click' automated setup and tear down AWS infrastructure application to your precise requirements. EL2 SV and Air GAP SV come with powerful advanced features , source and equivalent ports for OpenStack, so you can run your infrastructure application on your own hardware whether colocated or not, as well as AWS. As the implementation is in the form of Terraform modules you can invoke them from yet other modules or change the implementation to make other external calls.

Customizing professionally developed infrastructure as code is a good option and you can most probably do it yourself, but if you require, REVVOPS can do it for you, or simply support you in your own customization endeavour. If you consider the situation with Terraform prior to version 0.12, things were not so smooth. Terraform 0.11 and earlier required one to put in many more hours to gain confidence, there were a lot of issues - and their solutions weren't pretty; there was only one authoritative book and many of its pages emphasized how tricky it can be to obtain the behaviour one would expect from experience gained with less declaratively oriented languages (i.e. imperatively programmed languages, such as C or Java). Nowadays the situation is so much more welcoming and easier for people of different experience backgrounds and levels - the Terraform you can work with today feels almost like cheating compared to the earlier versions.

As the infrastructure as code tooling market mushrooms, it's worth trying to be as objective as possible in one's tooling choices; try to be aware of your own predispositions towards a particular language, system or technique and at least try to give everything some consideration - this is not as easy as it sounds, as noise volume has too great an influence on everyone. Who says you can't program great infrastructure in C++ (with more tailored sophistication than any tool could offer)?

If you are using REVVOPS SV edition for OpenStack, be aware that you can actually run OpenStack inside AWS, BUT if you ask AWS if they will let you colocate your own hardware inside their data centers, the answer is going to be NO, unfortunately - that would be nice, but you have vastly more colocation options with other data center providers than AWS could offer, not to mention the massive streamlining of your costs.