What is Infrastructure as Code (IaC)? Infrastructure as Code is a process of managing and provisioning computing infrastructure with some declarative approach while setting their configuration using definition files instead of traditional interactive configuration tools.
What are the benefits of IaC?
Consistency
Consistently achieve standardised provisioning or deployment
Accelerating
Accelerating provisioning or deployment rapidly
Reusability
Reusable JSON code for repeatable or similar provisioning or deployment
Extensibility
Extensible JSON code for incorporating with additional items
Have any developer ever waited for weeks or months to get a development environment delivered by their internal IT operations? This demand has driven IT industry to deliver new tool set to ensure that one can deliver on time and meet the standard requirement constantly. Reference: Ryen Kia Zhi Tang
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
