At Flux7, we get the opportunity to work with organizations across many industries and with a variety of challenges. As a result, we often get asked how other companies approach and solve different challenges. One challenge we are frequently asked about is website performance, security and elasticity, especially as it relates to eCommerce. As such, we’re happy to share with you today the story of a customer who was looking to balance these goals and how with the help of Flux7 consultants they were able to do so.
We recently had the opportunity to work with a quick serve restaurant (QSR) to help it achieve security with agility, effectively balancing IT governance with their workload reduction and wait time elimination goals. This household name reached out to the AWS experts at Flux7 as they looked for solutions that would allow the development team to quickly build a new digital platform that would support this organization's digital evolution.
How Flux7 Helped Increase Developer Productivity with AWS Service Catalog
At Flux7, we are expert at helping healthcare organizations gain a competitive advantage in the market through IT modernization projects that amplify their inherent business strengths. So when were approached by this healthcare organization who sees technology as a competitive advantage, we were quite excited to dive in.
For the past few days we’ve been reviewing the most widely read themes of 2016 here on the Flux7 blog. In case you are just joining us, we’ve already discussed the benefits and challenges of containers, configuration management, and Continuous Integration and Continuous Delivery (CI/CD) in an AWS DevOps environment. Wrapping it all together, we end our Best of 2016 series with our most talked about articles on Amazon cloud computing.
This month’s re:Invent in Las Vegas drew over 32,000 attendees and the show did not disappoint as AWS delivered on its precedent to unveil a number of new features and products at the show. With numerous announcements, AWS news was peppered throughout two days of lengthy keynote sessions, we’ve asked Ali Hussain, Flux7 co-founder and CTO, to weigh in on what caught his attention and where he thinks the most impact will be seen to enterprise organizations like those that Flux7 serves.
AWS kicked off November with the announcement of a new Amazon Linux container image for cloud and on-premises workloads. As power users of AWS, EC2 and Docker, our AWS consultants are excited at this news; it will greatly ease the upfront planning process for clients, eliminating a dimension from the complex decision matrix we navigate designing a Docker-based setup in AWS.
According to IT Revolution press (hat tip to Gene Kim for the great article on this), there are three principles underpinning DevOps: an emphasis on the performance of the entire system over silos; creating tight, right to left feedback loops; and fostering a culture of continual experimentation, learning, and the understanding that practice is prerequisite to mastery. Today we’re going to examine how these underpinnings apply when it comes to Desktop-as-a-Service (DaaS) generally and AWS WorkSpaces specifically.
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 AWS 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.