The architecture and operating guides for our hybrid application.
This handbook brings the system design, deployment steps and recovery notes into one documentation space.
Read Hybrid application architecture for the path from our data center to AWS. Use the Deployment guide when preparing a release.
Architecture explains how the parts fit together. Operations covers the work of running them.
How the on-premises application connects to its AWS services.
The on-premises server connects to the EC2 application server in the AWS VPC. EC2 reads and writes application data in RDS.
The Blueprint above shows the application path and the boundary around the AWS VPC.
Release the EC2 application server after the database migration is complete. Keep the on-premises connection available during the rollout.
If validation fails, restore the previous application release. Follow Data recovery for the database restore procedure.
| Recovery check | Expected result |
|---|---|
| Snapshot | The RDS snapshot matches the selected restore point. |
| Restore target | The restored database is available in an isolated environment. |
| Application | The previous application release starts successfully on EC2. |
| Configuration | The application uses the restored database endpoint and credentials. |
| Connectivity | A test request from the on-premises server reaches the application. |
| Validation | A test transaction completes and the application health checks pass. |
A repeatable release process for the hybrid application.
Confirm that the application package is ready and the on-premises connection is healthy.
Record the current release and verify the RDS backup before running a database migration.
Check the health endpoint and confirm that a test transaction reaches RDS. Retain the previous application package until the checks pass.