Here Robin talks about how to provision nodes with Amazon Web Services (AWS) to implement Chef functionality using a cloud provider.
- [Instructor] Before we bootstrap a node and attach it to our chef server, we need a node to manage in the first place. I'm going to use Amazon Web Services to actually spin up these nodes. However, understand that you could accomplish with any cloud provider or with Vagrant and Virtual Box as well. If you've never used Amazon Web Services, definitely check out their free tier option, where you can actually get started using AWS without incurring a whole lot of cost. If you've never used it before, check out some of the attached links on how to create an instance on AWS.
I'm signing into my account here, and what you'll see is that I'm actually presented with my AWS dashboard. I've actually gone through and already launched a few instances for us to get started with. And I can view these under the instances tab. These are basic centos instances, very similar to what we used with Vagrant. The only difference here is that I've actually gone through and created a username called chef and a password for that user. The reason for this is to make it very easy to authenticate to this node.
You can absolutely use a private key provided by AWS to authenticate as well. So if you're trying this on your own in the future, just keep in mind the only thing I've done is spun up a centos six point eight instance and then configured the chef user. The reason I want you to see this is so that I can grab the public IP address. This node needs to be accessible via SSH at this public IP address for me to attach it to my chef server, so I'm going to copy this public IP address and have it ready for bootstrapping this section.
Now understand there are a lot of ways to actually create nodes, and this just one method. I just wanted you to be aware of where these IP addresses are coming from that I'm going to bootstrap in the next section.
- Configuration management
- Using Chef
- Installing the Chef development kit (ChefDK)
- Provisioning a CentOS instance
- Using recipes and the Apache cookbook
- Working with nodes and node objects
- Using templates and embedded Ruby
- Hosting a Chef server
- Provisioning nodes with AWS
- Testing deployments with Kitchen
- Exploring the Chef Supermarket
- Resolving dependencies with Berkshelf
- Working with server roles, environments, and data bags