App Server Auto Scaling (root360)
Component description
The App Server Auto Scaling is used when the number of web servers for delivering an application is to be kept flexible. Auto Scaling means automatic addition and removal of EC2 instances when threshold values such as load speed or CPU are reached ("horizontal scaling"). A load balancer is set up for this purpose. The App Server Auto Scaling is thus automatically also designed to be redundant, since at least two EC2 instances are always active. They are also normally distributed geo-redundantly to two different Availability Zones (data centers) by default.
Variants
Code Deploy: Root360 Code Deploy by root360 connects the App Server directly to your repository, S3 Bucket or other sources and takes care of error-free delivery to your app server.
BYO AMI: You “bring your own” Amazon Machine Image (AMI) - we provide a cloud environment to let it run securely.
Spot Instances: This meta-variant can be used in combination with other variants. It uses spot instances (https://aws.amazon.com/de/ec2/spot/) instead of on-demand instances , which can result in cost savings of up to 60% in practice.
Common use cases
Web-Server: A web-server using App Server Auto Scaling can serve mission critical or stateless applications based on PHP, Java, Node.js and many more.
Lift & Shift: Easy migration (known as “lift and shift”) of legacy applications via Amazon Machine Image. Applications need to be stateless.
Software from AWS Marketplace: Usage of software from the AWS Marketplace via Amazon Machine Image. Software needs to be stateless.
Currently supported versions
Version | known issues |
---|---|
PHP Support:
| PHP 8.0 does not support JIT feature due to an existing PHP bug |
We support Node.JS versions based on Ubuntu Supported Versions |
|
Java OpenJDK 11 - 15 |
|
BYI AMI in context of Managed Services
An Amazon Machine Image (AMI) is used to create a virtual machine within the Amazon Elastic Compute Cloud (EC2). Within the AMI, the operating system, applications, configurations, etc. are encapsulated. For that reason we implemented a "shared responsibility" model: You are responsible for everything "inside" the AMI, while root360 is responsible for everything "outside" the AMI.
Pricing
For AWS pricing see https://aws.amazon.com/ec2/pricing/.
For root360 Managed Services pricing please contact our Service Team.
Related tutorials
intermediate
Related questions
root360 Knowledge Base - This portal is hosted by Atlassian (atlassian.com | Privacy Policy)