Ask Sendai

Amazon Web Services will offer AWS-branded servers that will work with existing cloud services. AWS is taking on traditional hardware vendors with its on-premises service. Amazon Web Services will offer AWS-branded servers that will work with existing cloud services. AWS is taking on traditional hardware vendors with its on-premises service. Amazon cloud chief Andy Jassy said that during the first half of 2018, he was consistently getting requests from customers who wanted Amazon’s help not just in the cloud, but also in their own data centers.

Firecracker is an eye-catching virtual machine from AWS. It is lightweight, secure, and uses Linux. Forget bloat, minimalism is the future of serverless. Firecracker is a new virtualization technology that enables customers to deploy lightweight micro Virtual Machines or microVMs. Firecracker microVMs combine the security and workload isolation properties of traditional VMs with the speed, agility and resource efficiency enabled by containers. They provide a secure, trusted environment for multitenant services, while maintaining minimal overhead.

I am excited to announce the public-release of modules.tf, which allows a conversion from visual AWS diagrams using cloudcraft.co to infrastructure code using Terraform. Resources with arguments once specified during creation of diagrams are present in infrastructure code. Most popular EC2 types of resources are supported, more will be added in the future. VPC, Security group, Autoscaling Group, RDS, ELB, ALB, SNS, SQS, EC2 instances are implemented already. Many of relations between resources and their dependencies are respected in infrastructure code.

When I look back on the history of AWS and think about the launches that truly signify the fundamentally dynamic, on-demand nature of the cloud, two stand out in my memory: the launch of Amazon EC2 in 2006 and the concurrent launch of CloudWatch Metrics, Auto Scaling, and Elastic Load Balancing in 2009. The first launch provided access to compute power; the second made it possible to use that access to rapidly respond to changes in demand.

AWS CloudFormation supports you in your efforts to implement Infrastructure as Code (IaC). You can use a template to define the desired AWS resource configuration, and then use it to launch a CloudFormation stack. The stack contains the set of resources defined in the template, configured as specified. When you need to make a change to the configuration, you update the template and use a CloudFormation Change Set to apply the change.

The AWS cloud provider for Kubernetes enables a couple of key integration points for Kubernetes running on AWS; namely, dynamic provisioning of Elastic Block Store (EBS) volumes, and dynamic provisioning/configuration of Elastic Load Balancers (ELBs) for exposing Kubernetes Service objects. Unfortunately, the documentation surrounding how to set up the AWS cloud provider with Kubernetes is woefully inadequate. This article is an attempt to help address that shortcoming. Source: heptio.com