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.
As DevOps consultants, at Flux7 we believe that Continuous Delivery (CD) is a key tenet of successful DevOps. And as heavy users of Amazon Web Services (AWS), we have a keen interest in any tools or features that streamline CD for our clients within AWS. For this reason, we are pretty excited to dive into the Amazon Pipeline Starter Kit. Now, you may be familiar with two services that Amazon has traditionally offered to help facilitate CD: AWS CodePipeline and AWS CodeDeploy.
AWS CodeCommit is a fully managed version control management service offered by Amazon Web Services. It is a highly scalable and fully managed hosted service. It is compatible with Git and hence all of the git commands work with AWS CodeCommit. AWS Codecommit is highly secure in the sense that the data is encrypted both at rest and in transit. The repositories offered under this service are private by default. AWS Codecommit supports both HTTPS and SSH protocols.
Many developers born in the world of agile startups view continuous integration (CI) and continuous delivery (CD) as accepted standard requirements for software development. Yet many companies, particularly large enterprises with traditional infrastructure, still struggle to make this approach part of their development process.
How does the Internet of Things (IoT) change the way we develop, test and release software? Always-on connectivity introduces a new set of risks and challenges for development and operations teams.
For several years, that’s been the challenge for both developers and businesses. And the pressure to condense the dev and test life cycle has only increased.
We’re getting ready to kick off a series of interactive webinars focused on addressing issues we’ve uncovered during our recent IT assessments in regard to DevOps and the cloud. So, we thought now is a good time to share an article, featuring Flux7 CEO Aater Suleman, that sifts through how to successfully move to a DevOps culture.
The article, posted at DevOps.com, is entitled: "Q&A with Aater Suleman: Successfully Moving to DevOps," and it answers the questions:
Setting up a deployment process on the cloud means a variety of choices. Most likely, you’re prepared to make some tradeoffs. But, getting a view across these potential tradeoffs can be difficult. Here are six popular deployments and advice for making the best choice for your organization’s needs.
At Flux7 we are very interested in Docker as a technology and the new capabilities it can add to the DevOps world. To further explore what Docker can do in the hands of brilliant programmers we started a Meetup in Austin to discuss Docker.
Our clients are always deeply interested in creating productive dev environments. The power of a dev environment comes from many places. First is time saved by reducing the number of manual steps and by preventing context switches for a developer. Improving flow enables a developer to catch bugs sooner when they’re still inexpensive. Consequently, moving toward continuous testing and integration is essential. In this post, we’ll discuss a continuous integration workflow using opensource tools.