Now, the work environment here is slightly different and is designed for applications that handle background processing tasks. These tasks often interact with Amazon SQS or Simple Q Service to process messages asynchronously, allowing your application to stay responsive to users.

This tier is typically used for applications that do not serve HTTP requests directly but instead perform background operations. The worker tier uses the following AWS resources.

SQS Queue: if you don't already have an SQS Queue operational and configured, Elastic Beanstalk will automatically create one for you when the worker environment is created. SQS is a messaging service that acts as a communication bridge between the worker instances and the tasks they need to process. Messages are stored in the queue and processed asynchronously, meaning tasks can be handled in the background without affecting the application performance.

IAM Service Role: to allow your EC2 instances to monitor and process activity in the SQS Queue, each instance has an associated instance profile role, which includes policies granting the required permissions to read from the queue and processes messages securely.

Auto Scaling: similar to the web server tier, an Auto Scaling group is created to ensure that performance remains consistent even as demand fluctuates. The Auto Scaling group dynamically adjusts the number of worker EC2 instances based on the processing load in the SQS Queue.

EC2 instances: a minimum of one Amazon EC2 instances provisioned in the worker environment tier and as part of the Auto Scaling group. These instances work together to read and process tasks from the same SQS Queue.

Unlike the web server tier, which relies on the host manager, the worker tier installs a daemon on every EC2 instance. The daemon continuously pulls requests from the SQS Queue and sends them to your application for processing.

This setup ensures tasks are handled efficiently and allows the environment to scale as needed. This is why the instance profile role is required to ensure permissions are given to read from a queue.

In many cases, the worker tier is used alongside the web server tier, with the two tiers working together in a decoupled architecture. The web server tier handles incoming HTTP requests and sends tasks to the SQS queue, while the worker tier processes those tasks asynchronously. This separation allows each tier to scale independently based on demand, ensuring high performance and cost efficiency.

​Worker Environment Tier​

About

Worker Environment Tier