OpenEdge on AWS

Partner Solution Deployment Guide

QS

August 2023
Edsel Garcia, Progress Software
Dave May, AWS Integration & Automation team

Refer to the GitHub repository to view source files, report bugs, submit feature ideas, and post feedback about this Partner Solution. To comment on the documentation, refer to Feedback.

This Partner Solution was created by Progress in collaboration with Amazon Web Services (AWS). Partner Solutions are automated reference deployments that help people deploy popular technologies on AWS according to AWS best practices. If you’re unfamiliar with AWS Partner Solutions, refer to the AWS Partner Solution General Information Guide.

Overview

This guide covers the information you need to deploy the OpenEdge Partner Solution in the AWS Cloud.

The Partner Solution is for users who want to deploy a highly available three-tier Progress OpenEdge stack on the AWS Cloud.

Progress OpenEdge on AWS is a convenient way to create the infrastructure required to run an n-tier OpenEdge Advanced Business Language (ABL) application with a web user interface (UI), representational state transfer (REST) data services, and the OpenEdge database. It combines AWS services and OpenEdge functionality to achieve high availability, redundancy, and scalability.

You can use the Partner Solution CloudFormation template to create a new infrastructure, or use the CloudFormation CLI to automate deployments of OpenEdge applications from a CI/CD pipeline.

The template has user-provided deployment packages for the web server, Progress Application Server (PAS) for the OpenEdge application, and OpenEdge Relational Database Management System (RDBMS) for the OpenEdge database. Using this approach, you can package your on-premises application to deploy it to the AWS Cloud.

The web server and PAS for OpenEdge dynamically download and install the latest packages when Amazon Elastic Compute Cloud (Amazon EC2) instances are created. This can be used to roll out new versions of the application if desired. The database configuration can use OpenEdge replication sets to provide redundancy.

Costs and licenses

There is no cost to use this Partner Solution, but you will be billed for any AWS services or resources that this Partner Solution deploys. For more information, refer to the AWS Partner Solution General Information Guide.

This Quick Start requires an OpenEdge license. To use the Quick Start in a production environment, sign up for a license through the Progress website. After the OpenEdge infrastructure launches, enter the license key to activate the software.

The Quick Start requires a subscription to the Amazon Machine Image (AMI) for OpenEdge RDBMS and the AMI for PAS for OpenEdge. Additional pricing, terms, and conditions may apply. For more information, see step 2 in the deployment section.

Architecture

Deploying this Partner Solution with default parameters builds the following OpenEdge environment in the AWS Cloud.

Architecture
Figure 1. Partner Solution architecture for OpenEdge on AWS

As shown in Figure 1, this Partner Solution sets up the following:

  • A highly available architecture that spans two Availability Zones.

  • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.

  • In the public subnets:

    • Managed Network Address Translation (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 EC2 instances in public and private subnets.

  • In the private subnets:

    • EC2 instances running a Web Server in an Auto Scaling group.

    • EC2 instances running PAS for OpenEdge in an Auto Scaling group.

    • Three EC2 instances running OpenEdge RDBMS with support for replication sets.

Deployment options

This Partner Solution provides the following deployment options:

  • Deploy OpenEdge into a new VPC. This option builds a new AWS environment that consists of the VPC, subnets, NAT gateways, security groups, bastion hosts, and other infrastructure components. It then deploys OpenEdge into this new VPC.

Predeployment steps

Subscribe to the OpenEdge AMI

This Quick Start requires a subscription to the AMI for OpenEdge in AWS Marketplace.

  1. Open the Progress Application Server (PAS) for OpenEdge page in AWS Marketplace, and then choose Continue to Subscribe.

  2. Open the Progress OpenEdge RDBMS page in AWS Marketplace, and then choose Continue to Subscribe.

  3. Review the terms and conditions for software usage, and then choose Accept Terms.
    A confirmation page loads, and an email confirmation is sent to the account owner. For detailed subscription instructions, see the AWS Marketplace documentation.

  4. When the subscription process is complete, exit out of AWS Marketplace without further action. Do not provision the software from AWS Marketplace—the Quick Start deploys the AMI for you.

Deployment steps

  1. Sign in to your AWS account, and launch this Partner Solution, as described under Deployment options. The AWS CloudFormation console opens with a prepopulated template.

  2. Choose the correct AWS Region, and then choose Next.

  3. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  4. On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. When you finish reviewing and customizing the parameters, choose Next.

    Unless you’re customizing the Partner Solution templates or are instructed otherwise in this guide’s Predeployment section, don’t change the default settings for the following parameters: QSS3BucketName, QSS3BucketRegion, and QSS3KeyPrefix. Changing the values of these parameters will modify code references that point to the Amazon Simple Storage Service (Amazon S3) bucket name and key prefix. For more information, refer to the AWS Partner Solutions Contributor’s Guide.

  5. On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.

  6. On the Review page, review and confirm the template settings. Under Capabilities, select all of the check boxes to acknowledge that the template creates AWS Identity and Access Management (IAM) resources that might require the ability to automatically expand macros.

  7. Choose Create stack. The stack takes about 20 minutes to deploy.

  8. Monitor the stack’s status, and when the status is CREATE_COMPLETE, the OpenEdge deployment is ready.

  9. To view the created resources, choose the Outputs tab.

Postdeploy
Figure 2. CloudFormation outputs

Postdeployment steps

When the stack is successfully created, you can access the PAS for OpenEdge server and the web server using the values PASOEURL and WebURL, respectively, from the Outputs tab of the top-level stack.

Troubleshooting

For troubleshooting common Partner Solution issues, refer to the AWS Partner Solution General Information Guide and Troubleshooting CloudFormation.

Customer responsibility

After you deploy a Partner Solution, confirm that your resources and services are updated and configured—including any required patches—to meet your security and other needs. For more information, refer to the Shared Responsibility Model.

Feedback

To submit feature ideas and report bugs, use the Issues section of the GitHub repository for this Partner Solution. To submit code, refer to the Partner Solution Contributor’s Guide. To submit feedback on this deployment guide, use the following GitHub links:

Notices

This document is provided for informational purposes only. It represents current AWS product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided "as is" without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at https://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "as is" basis, without warranties or conditions of any kind, either expressed or implied. Refer to the License for specific language governing permissions and limitations.