Navigate to the URL https://console.aws.amazon.com/opsworks/cm/home#/chef/
and select Create Chef Automate Server
Step 1: - Now select the region and enter the Chef Server Automate Instance (server) name and - Select the Instance type too.
Step 2: Select an SSH Key No room to create a new key (either you select you don’t want to connect using SSH or you select an existing SSH key).
Step 3: Select the right VPC, Subnet, associate the right EIP, security group. - Create a service role if non-exists at the moment
“AWS OpsWorks for Chef Automate needs your permission to create an IAM service role that allows us to perform actions in AWS CloudFormation, Amazon EC2, Amazon EC2 Simple Systems Manager, and Amazon S3. By continuing, you are allowing us to create a new role to work with these services.” Create an Instance Profile
“AWS OpsWorks for Chef Automate needs your permission to create an instance profile that allows us to perform actions in Amazon S3, and communicate with a Chef server by using Amazon EC2 Simple Systems Manager (SSM). By continuing, you are allowing us to create a new role to work with these services”
Select your maintenance Windows to allow AWS OpsWork to install Updates for Chef Automate minor versions or security packages.
Note: Weekends are always better to have this performed. (select whatsoever time suits you).
For AWS OpsWorks Backup: AWS OpsWorks supports two ways to back up your Chef Automate server: manual or automated. Backups are uploaded to your Amazon S3 bucket. If you ever need to restore your Chef Automate server, you can restore it by applying a backup that you choose.
When you choose yes to Enable automated backup, these options below are available
Number of generations to keep: 30 is usually okay but this depends on your organisation policy.
Step 4: Review and Launch: open its Properties page in the AWS OpsWorks for Chef Automate console. The page below will be prompted to show the progress bar of the AWS OpsWork for Chef Automate creation,
Note: Make sure you download the following before your server is online. The download buttons are not available after a new server is online.
Finally, this message will appear on the dashboard stating your Chef Automate Server is successfully launched
Note: The created role will appear in the IAM section under roles as shown below
Now Access he URL (dashboard) of Chef Automate and perform all necessary configurations etc. as shown below
Note: Ensure you have the ChefDK downloaded and Installed on your local PC from https://downloads.chef.io/chefdk
Otherwise, you cannot work with Chef Automate with Windows 10 . See how to install ChefDk on Windows in the next page
Note: The AWS CLI must be configured on your local work station. simple by downloading it from AWS.
There are different ways to install this but my preferred method is by using an installer which can be downloaded from this site. https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html
Use-Case: Install AWS CLI on Windows
Note: You can also have it installed on MacOS and linux. Please See the URL above for the steps.
The installer can be downloaded here for Windows: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html
After installation, Please verify, it has been installed correctly by using the command below.
Follow the next steps below to configure the AWS CLI
$aws configure AWS Access Key ID [None]: Your Access Key ID AWS Secret Access Key [None]: Your Secret Key Default region name [None]: Enter your desired region in this format (us-west-2) Default output format [None]: I usually leave this by default as (json)
When you type this command, the AWS CLI prompts you for four pieces of information and stores them in a profile (a collection of settings) named
default. This profile is then used any time you run an AWS CLI command that doesn’t explicitly specify a profile to use.