reference deployment

Micro Focus Operations Orchestration on AWS

Automation and orchestration of repeatable IT operations across teams, tools, and environments

This Quick Start automatically deploys Micro Focus Operations Orchestration (OO) on the Amazon Web Services (AWS) Cloud in about 20 minutes. The Quick Start is automated by AWS CloudFormation templates and deploys two Micro Focus OO components: OO Workflow Designer and OO Central.   

Micro Focus OO is a system to create and perform actions in structured sequences called flows. These structured sequences enable seamless automation and orchestration of repeatable IT operations across teams, tools, and environments. Examples of these operations include:

  • Maintaining and troubleshooting IT resources.
  • Conducting health checks; diagnosing and repairing networks, servers, software applications, and workstations.
  • Automating elements, runbooks, and business services.

This Quick Start is for you, if you are:

  • An existing Micro Focus OO customer who wants to implement OO on the AWS Cloud.
  • New to Micro Focus OO, and interested in automating and orchestrating repeatable IT operations and infrastructure or application processes—across any infrastructure (physical, virtual servers, storage, network, cloud) and any application.
portworx logo

This Quick Start was developed by Micro Focus, Inc. in collaboration with AWS. Micro Focus, Inc. is an APN Partner.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • Use this Quick Start to automatically set up the following environment on AWS:

    • A highly available architecture that spans two Availability Zones.*
    • A virtual private cloud (VPC) configured with two public and two private subnets (one public and one private subnet in each Availability Zone).*
    • In the public subnets:
      • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
      • A Linux bastion host in an Auto Scaling group, to allow inbound Secure Shell (SSH) access to the Amazon Elastic Compute Cloud (Amazon EC2) instances in the public and private subnets.*
    • In the private subnets:
      • An Amazon Relational Database Service (Amazon RDS) for PostgreSQL database instance. If deployed in Multi-AZ mode, the Multi-AZ deployment creates a primary RDS DB instance to which OO products connect, and a standby RDS DB instance in another Availability Zone.
      • An Application Load Balancer configured with one listener and three listener rules for routing traffic to the OO Workflow Designer server, the Identity Management (IDM) server for Workflow Designer, and the OO Central server cluster.
      • OO Central instances (nodes) in an Auto Scaling group for ensuring that the desired number of nodes is up at all times.
      • Security groups for defining SSH access to OO instances (based on user input), and for limiting traffic to the RDS DB instance, so that traffic comes only from the OO instances.
      • An Amazon CloudWatch Logs group.  
    • An AWS Identity and Access Management (IAM) role with a policy that has fine-grained permissions needed for OO Central instances to deploy in cluster mode.
    • An optional Amazon Simple Notification Service (Amazon SNS) topic to inform the operator via email about possible failed scaling operations.
    • A bootstrap process inside the OO Central instances, which creates a self-signed certificate for the Application Load Balancer, imports it into AWS Certificate Manager (ACM), and then configures the Application Load Balancer’s listener to use it.

    *  The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy Micro Focus OO on AWS, follow the instructions in the deployment guide. The deployment process takes about 20 minutes and includes these high-level steps:

    1. If you don't already have an AWS account, sign up at, and sign in to your account.
    2. Launch the Quick Start, choosing from the following options:
    3. Test the deployment by logging in to your newly created OO Central cluster.
    4. (Optional) Obtain and apply a license.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. Some of these settings, such as instance type, will affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you will be using. Prices are subject to change.

    Tip     After you deploy the Quick Start, we recommend that you enable the AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an S3 bucket in your account. It provides cost estimates based on usage throughout each month, and finalizes the data at the end of the month. For more information about the report, see the AWS documentation.

    This Quick Start deploys Micro Focus OO with a 90-day trial license. When the trial ends, you need to purchase a commercial license or request a trial extension, as follows:

    After you obtain the license, log in to the OO Central cluster and apply it, as described in the deployment guide.