Chef Automate configuration steps on AWS Marketplace
- Reconfigure Chef Starter Kit
- Generate an SSH key
- Set your Git identity
- Configure the runner
- Set up knife-ec2
Lab URL: https://learn.chef.io/modules/deploy-infrastructure/ubuntu/aws/set-up-your-workstation#/
When you create instance - dynamic hostname used, so after assigning Elastic IP - chef automate and chef server require reconfiguration. Following commands required:
#Reconfigure and restart backend sevices.
chef-marketplace-ctl hostname
chef-marketplace-ctl stop biscotti
chef-marketplace-ctl start biscotti
automate-ctl reconfigure
chef-server-ctl reconfigure
automate-ctl restart
chef-server-ctl restart
chef-server-ctl restart nginx
You need an SSH key to submit changes to Chef Automate from the command line. The private part of your key, ~/.ssh/id_rsa, stays with you. You associate the public part of your key, ~/.ssh/id_rsa.pub, with your Chef Automate user profile. The process is similar to how systems such as GitHub work.
If you don't have an SSH keypair that you want to use, generate one now. The syntax varies slightly between Windows and other operating systems. Here are a few examples. The email address is not significant for this module, but you can replace "jsmith@example.com" with yours if you prefer.
ssh-keygen -t rsa -b 4096 -C "jsmith@example.com" -f $HOME/.ssh/id_rsa -N ""
Next, run git config to set your Git identity. Git includes this information as metadata when you commit changes. You can omit this step if you've already configured Git to work with other projects.
If you have an existing Git account, such as with GitHub, you can use the same information here (changes you make in this module won't be published as public activity on your GitHub account.) You can use fictitious values if you prefer.
Here's an example.
git config --global user.name "Jane Smith"
git config --global user.email jsmith@example.com
Next, you need to configure software on your runner. The easiest way to do that is from your Chef Automate instance.
Your Chef Automate server requires the SSH key (or password) that you use to connect to your runner. If you use key-based authentication to connect to your runner, copy the SSH key you use to connect to your runner from your workstation to your Chef Automate server. Here's an example that uses the scp utility (note the trailing colon : character at the end of the command.)
scp -i ~/.ssh/private_key ~/.ssh/private_key ec2-user@ec2-34-229-169-235.compute-1.amazonaws.com:
or if you have generated .pem file from AWS you can copy this file. In my case it's looks like this:
scp /home/vagrant/chef-automate/chef-automate-key.pem your-future-runner-fqdn:/home/ec2-user/keys/chef-automate-key.pem
use scp -i "chef-automate-key.pem" chef-automate-key.pem ec2-user@ec2-3-214-123-171.compute-1.amazonaws.com:/home/ec2-user/chef-automate-key.pem to connect to chef-automate server from your runner
copy your runner's private key on chef-automate server
sudo scp -i 'chef-automate-key.pem' ~/.ssh/id_rsa ec2-user@ec2-3-214-123-171.compute-1.amazonaws.com:/home/ec2-user/.ssh/id_rsa
or you can configure runner by using .pem file
sudo automate-ctl install-runner ec2-54-174-222-194.compute-1.amazonaws.com centos -i 'chef-automate-key.pem'
https://learn.chef.io/modules/upgrade-chef-client/aws#step3
To bootstrap your node you need to run following command, for more information follow the link above.
knife ec2 server create --image ami-05a36d3b9aa4a17ac --ssh-key 'chef-automate-key' --flavor t2.micro --ssh-user ubuntu --identity-file "C:\Chef\chef_automate\chef-automate-key.pem" --bootstrap-version 12.21.31 --security-group-id sg-0f15d169b77163332 --region us-east-1 --run-list 'recipe[custom_apache]'
Extract tar.gz archive with 7-zip:
& 'C:\Program Files\7-Zip\7z' x .\chef_client_updater-3.2.4.tar.gz
& 'C:\Program Files\7-Zip\7z' x .\chef_client_updater-3.2.4.tar -ocookbooks