In this episode we'll show you how to enforce your AWS tagging standards with Sentinel, restrict which instance types can be run, and centralize your Terraform state management for maximum efficiency and cost savings.
Hi, I'm Sean Carolan, Solutions Engineer with HashiCorp. I’m a former systems administrator. In a past life I worked in the gaming industry. I’ve got many years experience caring for and feeding Linux servers.
In part one of this webinar, we showed you how to use Terraform to deploy a serverless application. A simple tagging system was used to mark instances for deletion after their time-to-live expires. Hopefully you saved a ton of money and learned a bit about Terraform and AWS Lambda in the process. But how can you make sure everything gets tagged properly to begin with? In part two we will show you how to securely and safely provision cloud infrastructure with Terraform Enterprise.
Everyone wants to move to the cloud. Infrastructure on demand – what’s not to like. Just pay as you go and your cloud vendor will manage all the hardware and low-level infrastructure for you.
But it’s not that easy! Your vendors and devops unicorns will tell you it’s great. Just sprinkle some devops on there, and you’ll be good to go. But as anyone who’s done a cloud migration project will tell you, it’s not quite that easy. If you simply “lift and shift” your current legacy processes and code into the cloud you’ll be a little better off, but you still won’t achieve the velocity or level of efficiency you were promised.
In the cloud everything is an API. All the way down to the network level. You can describe entire networks and virtual data centers using code.
AWS is a service oriented architecture. There was a famous memo that Jeff Bezos created back in 2002. It was a mandate. Every single department had to move to a Service Oriented Architecture. Instead of calling up someone over in marketing you had to interact with their API. And all those APIs had to be build to be public-facing right from the get go.
https://plus.google.com/+RipRowan/posts/eVeouesvaVX
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Welcome.html
You absolutely must master infrastructure as code to get the most out of cloud
The GUI is training wheels. You have to learn to ride without them [slide]
Giving your users unrestricted access to your AWS account is dangerous.