Step 2: Create a Simple Application Server Stack - Chef 11 - AWS OpsWorks

Step 2: Create a Simple Application Server Stack - Chef 11

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 users, internet, and AWS components.

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 PHP App Server instances.

  • An instance, which represents an Amazon EC2 instance.

    In this case, the instance is configured to run a PHP app server. Layers can have any number of instances. AWS OpsWorks Stacks also supports several other app servers. For more information, see Application Server Layers.

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

    The code is stored in a remote repository, such as Git repository or an Amazon S3 bucket.

The following sections describe how to use the AWS OpsWorks Stacks console to create the stack and deploy the application. You can also use an AWS CloudFormation template to provision a stack. For an example template that provisions the stack described in this topic, see AWS OpsWorks Snippets.

Topics