Skip to main content

AWS Managed Services Deployment

[edit on GitHub]

Follow the steps below to deploy Chef Automate High Availability (HA) on AWS (Amazon Web Services) cloud with Managed AWS Services.

Steps to install Chef Automate HA on AWS with Managed AWS Services

Prerequisites

  • Setup AWS RDS Postgresql 13.5 (Ref link)

  • Setup AWS OpenSearch 1.2 (Ref link).

  • For Backup and Restore with Managed Service (Ref link).

  • Virtual Private Cloud (VPC) should be created in AWS before starting or use default. Reference for VPC and CIDR creation

  • Get AWS credetials (aws_access_key_id and aws_secret_access_key) which have privileges like: AmazonS3FullAccess, AdministratorAccess, AmazonAPIGatewayAdministrator. Ref. to create IAM Users
    Set these in ~/.aws/credentials in Bastion Host:

    sudo su -

    mkdir -p ~/.aws
echo "aws_access_key_id=<ACCESS_KEY_ID>" >> ~/.aws/credentials
echo "aws_secret_access_key=<SECRET_KEY>" >> ~/.aws/credentials

  • Have DNS certificate ready in ACM for 2 DNS entries: Example: chefautomate.example.com, chefinfraserver.example.com
    Reference for Creating new DNS Certificate in ACM

  • Have SSH Key Pair ready in AWS, so new VM’s are created using that pair.
    Reference for AWS SSH Key Pair creation

Run these steps on Bastion Host Machine

  1. Before starting, switch to sudo:

    sudo su -

  2. Download Chef Automate CLI

    curl https://packages.chef.io/files/current/latest/chef-automate-cli/chef-automate_linux_amd64.zip | gunzip - > chef-automate && chmod +x chef-automate | cp -f chef-automate /usr/bin/chef-automate

  3. Download Airgapped Bundle Download latest Bundle with this:

    curl https://packages.chef.io/airgap_bundle/current/automate/latest.aib -o latest.aib

    Download specific version bundle with this, example version: 4.0.91:

    curl https://packages.chef.io/airgap_bundle/current/automate/4.0.91.aib -o automate-4.0.91.aib

  4. Generate init config Then generate init config for existing infra structure:

    chef-automate init-config-ha aws

  5. Update Config with relevant data

    vi config.toml
    • Give ssh_user which has access to all the machines. Example: ubuntu
    • Give ssh_key_file path, this should have been download from AWS SSH Key Pair which we want to use to create all the VM’s. Thus, we will be able to access all VM’s using this.
    • Set backup_config to "efs" or "s3"
    • If backup_config is s3 then set s3_bucketName to a Unique Value.
    • Set admin_password which you can use to access Chef Automate UI for user admin.
    • Don’t set fqdn for this AWS deployment.
    • Set instance_count for Chef Automate, Chef Infra Server, Postgresql, OpenSearch.
    • Set AWS Config Details:
      • Set profile, by default profile is "default"
      • Set region, by default region is "us-east-1"
      • Set aws_vpc_id, which you had created as Prerequisite step. Example: "vpc12318h"
      • If AWS VPC uses CIDR then set aws_cidr_block_addr.
      • If AWS VPC uses Subnet then set private_custom_subnets and public_custom_subnets Example: example : ["subnet-07e469d218301533","subnet-07e469d218041534","subnet-07e469d283041535"]
      • Set ssh_key_pair_name, this is the SSH Key Pair we created as Prerequsite. This Value should be just name of the AWS SSH Key Pair, not having .pem extention. The ssh key content should be same as content of ssh_key_file.
      • Set setup_managed_services as true, As these deployment steps are for Managed Services AWS Deployment. Default value is false which should be changed.
        • Set managed_opensearch_domain_name, managed_opensearch_domain_url, managed_opensearch_username, managed_opensearch_user_password from the Managed AWS OpenSearch which you created in the Prerequsite steps.
        • Set managed_rds_instance_url as the URL with Port No. Example: ["database-1.c2kvay.eu-north-1.rds.amazonaws.com:5432"]
        • Set managed_rds_instance_url, managed_rds_superuser_username, managed_rds_superuser_password, managed_rds_dbuser_username, managed_rds_dbuser_password from the Managed AWS RDS Postgresql which you created in the Prerequsite steps.
      • Set ami_id, this value depends on your AWS Region and the Operating System Image you want to use.
      • Please use the Hardware Requirement Calculator sheet to get information for which instance type you will need for your load.
      • Set Instance Type for Chef Automate in automate_server_instance_type.
      • Set Instance Type for Chef Infra Server in chef_server_instance_type.
      • Set Instance Type for OpenSearch in opensearch_server_instance_type.
      • Set Instance Type for Postgresql in postgresql_server_instance_type.
      • Set automate_lb_certificate_arn with the arn value of the Certificate created in AWS ACM for DNS entry of chefautomate.example.com.
      • Set chef_server_lb_certificate_arn with the arn value of the Certificate created in AWS ACM for DNS entry of chefinfraserver.example.com.
      • Set automate_ebs_volume_iops, automate_ebs_volume_size based on your load needs.
      • Set chef_ebs_volume_iops, chef_ebs_volume_size based on your load needs.
      • Set automate_ebs_volume_type, chef_ebs_volume_type. Default value is "gp3". Change this based on your needs.

  6. Confirm all the data in the config is correct:

    cat config.toml

  7. Run Provision Command

    chef-automate provision-infra config.toml --airgap-bundle latest.aib

    Using specific version of Chef Automate, example: automate-4.0.91.aib

    chef-automate provision-infra config.toml --airgap-bundle automate-4.0.91.aib

  8. Run Deploy Command

    Deploy latest.aib with set config.toml

    chef-automate deploy config.toml --airgap-bundle latest.aib

    If deploying specific version of Chef Automate, example: Deploy automate-4.0.91.aib with set config.toml

    chef-automate deploy config.toml --airgap-bundle automate-4.0.91.aib

  9. After Deployment is done successfully. Check status of Chef Automate HA services:

    chef-automate status

  10. Check Chef Automate HA deployment info, using the command below:

chef-automate info

  1. Set DNS entries: DNS should have entry for chefautomate.example.com and chefinfraserver.example.com pointing to respective Load Balancers as shown in chef-automate info command.

  2. Check if Chef Automate UI is accessible by going to (Domain used for Chef Automate) https://chefautomate.example.com.

Was this page helpful?

×









Search Results