The goal of high availability for web applications
This is necessary to ensure high availability for any Web application (in this case, SwiftCode) that is deployed in AWS. The following features will be present:
The advantages of the model discussed in this publication are as follows:
Public Internet traffic will not be routed directly to the instance, eliminating any security risks.
Only Clients who have allow to the Bastion host can access the present instances in the VPC.
Security groups and network access control lists can be used to indicate who can access them privately.
Application updates, such as the deployment of a new feature, can be implemented without any problems by existing users during this window.
The instances in which the application runs can be easily fixed by completing and creating a new instance, where each new instance comes with the latest updated program.
The instance device can be avoided because autoscaling automatically detects it and starts a new case if this occurs.
The Auto Scale / ELB scale also contains monitoring screens that detect area failures and trigger new situations in the health zone until AWS recovers the failed zone.
Metrics can be configured on Cloud Watch so that we can track the app based on the number of users using the app, as well as the amount of memory used in a particular instance.
AWS services are used to achieve high availability
Here are the services we'll use in this example:
This is necessary to ensure high availability for any Web application (in this case, SwiftCode) that is deployed in AWS. The following features will be present:
- High availability in multiple areas / multiple availability areas.
- Automatic staging of cases (increase and decrease) according to the number of incoming requests
- Additional security for existing cases / databases in production
- Does not affect end-users while posting new code
- Does not affect the debugging of the copies
- Benefits of High Availability Usage for AWS Web Applications
The advantages of the model discussed in this publication are as follows:
Public Internet traffic will not be routed directly to the instance, eliminating any security risks.
Only Clients who have allow to the Bastion host can access the present instances in the VPC.
Security groups and network access control lists can be used to indicate who can access them privately.
Application updates, such as the deployment of a new feature, can be implemented without any problems by existing users during this window.
The instances in which the application runs can be easily fixed by completing and creating a new instance, where each new instance comes with the latest updated program.
The instance device can be avoided because autoscaling automatically detects it and starts a new case if this occurs.
The Auto Scale / ELB scale also contains monitoring screens that detect area failures and trigger new situations in the health zone until AWS recovers the failed zone.
Metrics can be configured on Cloud Watch so that we can track the app based on the number of users using the app, as well as the amount of memory used in a particular instance.
AWS services are used to achieve high availability
Here are the services we'll use in this example:
- EC2 - Flexible computing computation
- AWS RDS - relational database
- AS - Automatic measurement
- ELB - flexible load balancer
- SNS - Simple Notification Service
- VPC - Virtual Private Cloud
- Route53 - DNS service
- AMI - Image of Amazon device
