Sample AWS Appliance Setup

Setup Process

To prepare infrastructure using CloudCenter appliances for AWS clouds, follow this process.

  1. Request image sharing for the AWS account by opening a CloudCenter Support case ( or In your request, specify the following details:

    1. Your AWS account number

    2. Your CloudCenter version

    3. Your Customer ID (CID)

    4. Your customer name

    5. Specify if your setup is in production or for a POC

    6. You Contact Email

  2. After you open a case, your support case is updated with the shared AMI IDs. Proceed to the next step only after your support case is updated with the AMI IDs.

  3. Go to the AWS cloud console and select:

    1. Region: US East (North Virginia)

    2. Compute: EC2

      Cisco Provided AWS Images

      By default, Cisco only provides images for US East (North Virginia) region.

      If you prefer to use any other region, follow this procedure:

      1. Follow the rest of the process to set up CloudCenter Appliances to launch each CloudCenter component using the AMI provided by Cisco.

      2. Save each component as a new AMI (refer to the AWS documentation for details).

      3. Copy the AMI to the required AWS region (refer to the AWS documentation for details).

      4. Then follow the remainder of this process to set up CloudCenter appliances in the new AWS region.

  4. Locate the AMI ID for each component:

    1. Search for Private Images in the search bar.

    2. Ensure that the selected private image is the same as listed in the AMI ID that was emailed to you.

  5. Launch the instance for each component using the AMI ID:

    1. Choose an instance type (see Phase 1: Prepare Infrastructure > Hardware Requirements for additional context)

    2. Configure the instance details as required by your environment.

    3. Add the storage of your choice.

    4. Tag instance using a descriptive name. See Virtual Appliance Overview > Modes and Roles for CloudCenter names.

    5. Configure the security groups to associate with each VM. See Phase 2: Configure Firewall Rules for additional context. The next section in this process Configure Network Rules provides the minimum required network settings.

      Ensure that Port 22 is open to allow SSH access into the component VM.

    6. Review and update the instance launch settings as required by your environment.

    7. Click Launch and the Select an existing key pair or create a new key pair screen displays. Refer to your AWS documentation for information on key pairs.

      If you do not select a key pair, you will not be able to log into the component VM!

    8. Click Launch Instance to launch the component VM. Check the AWS console for completion of the VM launch process has successfully completed.

  6. Setup hostname – For all launched VMs, update the hostname. Choose a hostname that matches the Virtual Appliance Overview > Role. For example:

    1. hostname – For all launched VMs, update the hostname.

      Don't change the hostname after you install and configure a component as it may cause unknown issues.

      Choose a hostname that matches the Role. For example:

    2. Setup the hostname resolution – Once you update the hostname, ensure that the VM host name is resolvable by running the following command

      1. hostname

      2. If the VM name is not resolvable, edit the file /etc/hosts and add your VM’s hostname.
        For example:

      3. In addition, for AWS you must make sure that the /etc/cloud/cloud.cfg file contains the following entry to ensure that the hostname persists even after the server is rebooted:

        Required for AWS Deployments!
        preserve_hostname: true
    3. Network routing loopback:

      1. Refers to deployed CCMs that are running behind the Network Address Translation (NAT).

      2. This setup places a restriction on machines from internal networks to ensure that they do not use an external IP to access the CCM.

      3. To address this restriction, you must add a line to the CCO and AMQP server's /etc/hosts file and include the internal private IP of the CCM. For example: If the CCM DNS name is and it is behind a NAT, and the internal private IP address is and its external public IP address is, then enter the following line in the local /etc/hosts file:


        When configuring the CCM, the hostname used above ( must match what you configure as the Public DNS while configuring CCM.

  7. Create the CloudCenter Checker JSON file: After you setup the infrastructure for all the CloudCenter components, create a CloudCenter Checker JSON file that lists all the CloudCenter components with their modes and the IP address that correspond to infrastructure elements for each mode and role. This file will be used for network compliance check in Phase 3 of the CloudCenter installation process.

    The overall file structure will depend on factors like modes of various components, number of cloud regions, use of conditional/optional components and repos etc. Also, the region names used in the file should be unique, but do not need to match up with any cloud or datacenter names. These strings are merely used to perform network compliance checks and report results.

Sample JSON File

A sample Checker JSON file based on some common combination of CloudCenter component modes is provided below. Create a Checker JSON file that is specific to your environment and is similar to the following example.

    "CloudCenterComponents": {
        "CCM": {
            "CCM_IP": "",
            "mode": "NON-HA "
        "CloudRegions": [{
            "components": {
                "AMQP": {
                    "AMQP_IP": "",
                    "mode": "NON-HA"
                "CCO": {
                    "CCO_IP": "",
                    "mode": "NON-HA"
            "name": "AWSEast"
        "REPOS": {
            "BUNDLE_STORE": "",
            "DOCKER_REGISTRY": "",
            "PACKAGE_STORE": ""

Once you create the Checker JSON file, proceed to Prerequisite Checker JSON File to understand the file structure.

Back to: Virtual Appliance Process

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks