Tag: aws

serverless technologies
Automation - DevOps - Editor's Pick - Infrastructure as Code - Kubernetes - Managed Cloud Services

What is “Serverless”?

In some cases, serverless is wrongly related to a context in which a server does not exist. However, a server does exist, but no management tasks on a server will be performed; its maintenance and execution is be done by a vendor. In other words, having a “serverless” architecture involves avoiding server management and as…

Automation - DevOps - Editor's Pick - Infrastructure as Code - Kubernetes

What is immutable infrastructure?

Within the Cloud infrastructure space, there are several approaches on how to manage infrastructure. From: old-fashion manual creation and pray, to: everything automated, self-healing, self-scaling and pretty much self-managing. Within the second group, there are several approaches as well; you can have your infrastructure automated provisioned with Terraform and use Ansible for the configuration management,…

DevOps - Infrastructure as Code - Packer - Terraform

Building and Running Custom AMIs on AWS Using Packer and Terraform

Introduction In this article we are going to talk about two open-source infrastructure-as-code tools that we use at Flugel. These tools are Packer, to build machine images for different platforms, and Terraform, to manage infrastructure resources.   By using the two in combination  it’s possible to create infrastructure-as-code solutions that automatically build and run custom…

DevOps - Infrastructure as Code - Kubernetes

Kubernetes: 5 Ways to launch in 5 Minutes

This article describes 5 different ways to launch Kubernetes in 5 minutes. These steps are not intended for production usage; they are my own, personal notes on how to create clusters for use in testing and development. I use them when I want to launch K8s for quick, personal testing. I created this article in…

DevOps - Infrastructure as Code

Success story: From on premise to AWS in 1 hour

The problem: The client required migration of his microservices-based application to AWS, using containers.  The application was running on site, using legacy DevOps tooling, Xen VMs, Chef, and some scripting. So what, exactly, was the problem? Both security concerns and network limitations precluded this migration from being performed progressively. The only component permitted to exist…