In organizations today, it’s becoming increasingly more common to have your entire infrastructure defined as code. But once code is defined, what happens next? Collectively, the enterprise as a whole is adopting a methodology to repeatedly deploy the infrastructure that applications reside on, as well as the applications themselves.
To exhibit this methodology in action, Amazon Web Services has a solution that simplifies provisioning and management on AWS, allowing users to create templates themselves to deploy servers, PaaS Services, security groups, load balancers, and much more: AWS CloudFormation Templates. To simplify this service even further, AWS even offers a nifty designer that lets users create the templates by dragging and dropping components onto a grid. Once templates are created for the service or application architectures desired, AWS CloudFormation uses those templates for quick and reliable provisioning of applications or services.
Additionally, the entire infrastructure can be defined by a file of text like this:
What do we do now?
Once the infrastructure is defined, the template can be deployed from the command line or from the AWS Graphical User Interface (GUI). But if you’re managing some private infrastructure as well, you might be wondering if there’s a different process needed for your private cloud.
The answer is no. Leveraging your cloud management portal will allow you to manage both your on-premises environment and your AWS environment in a single place. This also allows for less confusion for end users and a consistent message from IT about how services should be provisioned.
Obviously putting resources like this into a cloud management portal isn’t always easy. Some of the leading vendors in the industry don’t have necessary lifecycle management techniques for these types of templates, but with a little work from your orchestration engine, the world is your oyster! Just add some extra code in your orchestration layer and build your own instead of leveraging the CMP.
With all of the options for deploying services available now in the marketplace, having a slew of portals to log in to can become a confusing undertaking for users. Taking a CloudFormation Template from AWS and placing it in one of our cloud management portals like VMware’s vRealize Automation or Cisco’s UCS Director can help to eliminate confusion by keeping all of our requests in a single location.
To learn more about AWS solutions, like CloudFormation Templates, be sure to visit the AHEAD booth at AWS re:Invent, November 28 – December 2, where you can meet with AHEAD engineers and architects to learn how AHEAD can help you accelerate the adoption of AWS in the enterprise!