Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Step 2: Create a Basic Application Server Stack - AWS OpsWorks

Step 2: Create a Basic Application Server Stack

Important

The AWS OpsWorks Stacks service reached end of life on May 26, 2024 and has been disabled for both new and existing customers. We strongly recommend customers migrate their workloads to other solutions as soon as possible. If you have questions about migration, reach out to the AWS Support Team on AWS re:Post or through AWS Premium Support.

A basic application server stack consists of a single application server instance with a public IP address to receive user requests. Application code and any related files are stored in a separate repository and deployed from there to the server. The following diagram illustrates such a stack.

Diagram showing application server stack with Windows instance, IIS layer, and AWS cloud integration.

The stack has the following components:

  • A layer, which represents a group of instances and specifies how they are to be configured.

    The layer in this example represents a group of IIS instances.

  • An instance, which represents an Amazon EC2 instance.

    In this case, the layer configures a single instance to run IIS, but layers can have any number of instances.

  • An app, which contains the information required to install an application on the instance.

  • A cookbook, which contains custom Chef recipes that support the custom IIS layer. The cookbook and app code are stored in remote repositories, such as an archive file in an Amazon S3 bucket or a Git repository.

The following sections describe how to use the AWS OpsWorks Stacks console to create the stack and deploy the application.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.