We have been working closely with a customer who is undergoing a business transformation. As a multimedia equipment manufacturer, the organization has a loyal following of its high quality devices. However, like many companies facing the convergence of markets and new customer demands, the company has embarked on a metamorphosis. Traditionally very focused on hardware, their software was largely ignored even though it offered customers real value. Part of the company’s transformation was a move to treat their software like a full-fledged offering, rather than a free supplement. An upcoming product release marked the first (and biggest steps), in cementing this change in company direction.
There are many reasons an organization might choose Amazon Aurora over the Amazon Relational Database Service (Amazon RDS). Superior performance, greater scalability, and the ability to restart without losing cache are just a few. However, for those organizations who are already running an important application or Website on top of the RDS managed service, it can be a challenge to migrate from it to Aurora, despite the latter’s obvious benefits. After all, you can’t just take down a service that customers expect access to 24x7.
AWS recently announced that Amazon ECS now supports a state for container instances that can be used to drain a container instance in preparation for maintenance or cluster scale down. AWS reports that the draining state prevents new tasks from being started on the container instance and notifies the service scheduler to move tasks that are running on the instance to other instances in the cluster. This is great news that we expect to save a lot of time and scripting when it comes to updating or removing containers from a cluster.
Last fall we asked if you would consider voting for Flux7 in Modern Infrastructure magazine’s annual Impact Awards. We truly value this award as it is given by the community to the companies that they value most in their journey to DevOps and IT modernization. Thank you for voting and naming Flux7 as the winner in the 2017 Best AWS Partner/Consultant Category.
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.
Container technology was a well-read topic on the Flux7 blog in 2016, joining our blog on Continuous Integration Best Practices(CI/CD) and AWS Configuration Management as subject areas that received the most attention from our readers. From hardening containers to container based cloud migration frameworks and Docker-based microservices architecture, our DevOps consultants published a great deal of analysis, advice and best-practice approaches to help our readers achieve success with containers in AWS.
In our last year in review blog, we took a look at how to best use new features and tools to streamline DevOps processes like Continuous Integration and Continuous Delivery (CI/CD). Today we are turning our attention to another topic that garnered a lot of interest this year, Configuration Management.
This week we are highlighting the most talked about issues from the Flux7 blog in 2016. While new AWS services are always being announced, sometimes making it hard to keep up, we found that a lot of discussion revolved around process management and how to best use new features and tools to streamline DevOps processes like continuous integration and continuous delivery (CI/CD).
As we all know CI/CD is a key tenet of successful DevOps with automation playing a starring role. Whether you are getting features to internal customers faster or bringing new products to market before the competition, a continuous delivery pipeline helps speed time to delivery, generating greater value to the business. And when it came to delivering the greatest value to our readers on the topics of CI pipelines and deployment pipelines, these posts scored:
At re:Invent 2016 Werner Vogels, AWS CTO, donned a Transformer shirt to tell us we can be Transformers. And, Andy Jassy, AWS CEO, emphasized in his presentation that we can all be superheroes, with superpowers. This emphasis on the ability to easily control, manage and even transform your AWS environment -- from x-ray vision to immortality -- was a great way to frame the two themes of the show which boiled down to increased ease of use and a greater acceptance for the hybrid cloud model.
Now that the first wave of innovators and early adopters have moved their workloads to the cloud, we are seeing majority, more pragmatist organizations, migrating to the cloud. However, unlike early movers who were willing to navigate the complexity of AWS tools and technology, this second wave of organizations puts a higher premium on ease-of-use. Given that, let’s look at how AWS has done just this through our lens of operations, DevOps and Security.