AWS launched EC2 Run Command in October 2015 to provide a simple way of automating common administrative tasks like installing software or patches, running shell commands, performing operating system changes, managing local groups and users, altering configuration files and more in Windows instances. AWS quickly followed the launch with the same feature for Linux instances, and in May 2016, they added the power to Manage & Share Commands, and the ability to use additional predefined commands along with any custom commands that users have created for their accounts.
In addition to the announced CloudFormation YAML support, AWS also announced cross-stack references for CloudFormation. (For Flux7 commentary on YAML support, please see our blog post earlier this week here.) As our AWS experts work daily with CloudFormation, we were very interested in this news and couldn’t wait to roll up our sleeves and take a look for ourselves.
In our blog last week we told you that AWS CloudFormation has grown its support beyond JSON to include YAML. Prior to the announcement, our AWS consultants had been writing in YAML and used an in-house YAML CloudFormation generator to help us avoid the typical pain points associated with JSON. We promised in that article to share with you instructions on how to convert existing JSON CloudFormation templates into YAML and are delivering on that promise today.
Today AWS announced that CloudFormation will now support YAML. As big fans of YAML, we have been testing this new feature and are not disappointed in the results. Prior to this announcement, JSON specifications were used to write CloudFormation templates. However, we had been writing in YAML and using an in-house YAML CloudFormation generator which helped us avoid the typical pain points associated with JSON.
Amazon Web Services (AWS), the largest public cloud currently available, has added the ability to use the Elastic Compute Cloud (EC2)’s powerful “Run Command” feature with a single log-in to execute commands in multiple locations, including EC2 instances, on-premises servers or virtual machines (VMs) from other cloud providers. Prior to this, it was necessary to log into each instance, server or VM separately.
Self-service IT is an important goal for many of our clients. They are looking for ways to increase their repeatability and speed the rate at which internal customers are serviced. Service Catalog effectively addresses each of these goals by providing automated infrastructure provisioning through easy buttons. Ops teams create these buttons and make them available to internal customers such as developers, engineers, or QA to easily request, receive and provision pre-approved infrastructure.
Automating common administrative tasks to improve workload reliability and decrease potential risk is a common theme our consultants at Flux7 help our clients with. Doing so simplifies administration, encourages security through consistency and helps improve control over users and permissions. Amazon launched EC2 Run Command in October 2015 to help attain these benefits.
Service Discovery is not new. The idea of a tool that can discover how processes and services talk to each other and help facilitate connections has been around for some time. However, with the rise of increasingly dynamic environments, the important role service discovery plays continues to grow. Indeed, since the beginning of the year at Flux7 we have seen a surge of customers looking for container-based microservices architectures that highlights the need for service discovery due to its dynamic nature.
As AWS consultants, we have helped a wide variety of clients make the transition to Amazon Web Services (AWS) through a migration. Inevitably, one of the more complex and time consuming phases of AWS cloud architecture planning is helping the enterprise get its arms around the assets it intends to migrate and making a plan based upon that data. Luckily, Amazon recently announced a new service called Application Discovery that helps expedite the process and make it much easier to dig in and begin planning.