AWS Infra
Storage
StorageS3:We use AWS S3 for storing the client documents, database dump, logs and backup(site backup, user data backup, etc)(OR) can got with EFS for storing the Document which we have already tested in testing environment works good.Related Document:https://docs.google.com/document/d/1Xao2_HmNQausH6IDAjLoVhVOsl8T291mCb_ulvLCABk/edit
S3 STANDRAD (OR) EFS
S3 STANDRADS3 Std used for saving the LMRDocs, PCuploadDocs, E-sign Docs and trustDocs.Related Document:https://docs.google.com/document/d/1Xao2_HmNQausH6IDAjLoVhVOsl8T291mCb_ulvLCABk/edit
aBucket 1 (or) DIR 1
Opportunity Uploaded Files or Docs
Bucket 2 (or) Dir 2
Organization Files or Docs
Bucket 3 (or) Dir 3
Esigned docs
Bucket 4 or Dir 4
E-SignDocs
S3 GLACIER Deep Archive
S3 GLACIER Deep Archive:S3 Glacier used saving the inactive LMRDocs for 180 days and then it will be automaticallyremoved from the bucket.Database backup stored in S3 Glacier will be automatically removed after 90 days.All logs such as access_log, err_log, db_logs and other services logs will be removed after365 days.
Inactive Opportunity related Docs
Backups
Lambda
CloudWatch
CloudWatch:It's an Alarm Service.In case of any failure or issue mails will be triggered from cloudwatch service to customer(Chris/Sam/Kishore)Failure Types:1.Server Failure2.Service Failure3.Lambda service issues
Route 53
Route 53DNS Service
VPC 1
PRODUCTION ENV
EC 2
CLB / ALB
Server 1
Application Server:Application code server details:Instance Type: Reserved(To reduce billing cost)Core: c5n.2xlargeMemory: 21 GBStorage: 50 GBThe reason for choosing c5n.2xlarge instance because our application is php languagebased, and php consume more cpu resource.OS: Centos 6.10 or latestSoftware Details:Major:Apache - 2.4vMySQL - 5.7v (Support upto Oct, 2023)Php - 7.2v (Support upto Nov, 2020)Minor:CurlImagemagickother supporting softwaresAlso we will be enabling load balancer and auto scaling(Horizontal way)
Application Server
Server 2
Replica ServerReplica will be same as prod(including all) but in different AZ so if in case an instance failedthis will be replacing the failed instance.
Replica App Server
Server 3
Cron/Prod Server:Instance ID: i-06679e2a87894ef55Public DNS (IPv4): ec2-18-217-90-199.us-east-2.compute.amazonaws.comIPv4 Public IP: 18.217.90.199Instance type: t2.mediumElastic IPs: 18.217.90.199Private DNS: ip-172-31-27-170.us-east-2.compute.internalAvailability zone: us-east-2bPrivate IPs: 172.31.27.170Security groups: appchromaticsMonthly: $34.475Purpose:Running the cron job for vFax to trigger fax.Fetching the google docs from NodeJS server and getting the merge tags value
Cron/Prod Server
Server 4
NodeJS ServerInstance ID: i-021c1e480fa357fffPublic DNS (IPv4): ec2-3-14-154-251.us-east-2.compute.amazonaws.comIPv4 Public IP: 3.14.154.251Instance type: t2.largeElastic IPs: 3.14.154.251Private DNS: ip-172-31-39-121.us-east-2.compute.internalAvailability zone: us-east-2bPrivate IPs: 172.31.39.121Security groups: appchromaticsMonthly: $69.04
NodeJS Server
Server 5
Esign/Upload ServerCreated on: November 15, 2019 at 7:30:47 PM UTC+5:30Instance ID: i-0ebe9695dbb081fabPublic DNS (IPv4): ec2-3-134-200-242.us-east-2.compute.amazonaws.comIPv4 Public IP: 3.134.200.242Instance type: t2.microElastic IPs: 3.134.200.242Private DNS: ip-172-31-21-121.us-east-2.compute.internalAvailability zone: us-east-2bPrivate IPs: 172.31.21.121Security groups: Upload_ServerVPC ID: vpc-de9b05b6AMI ID: CentOS Linux 7 x86_64
E-sign/Upload Server
VPC 2
PRODUCTION DB
RDS
After forking the database this can be decided.
Database Name: app.lenstacks.com
VPC 3
NON-PRODUCTION
EC 2
Server 6
Non-Production Environment:Instance ID: i-007ff14576eadd374Public DNS (IPv4): ec2-18-217-247-251.us-east-2.compute.amazonaws.comIPv4 Public IP: 18.217.247.251Instance type: t2.mediumElastic IPs: 18.217.247.251Private DNS: ip-172-31-13-100.us-east-2.compute.internalAvailability zone: us-east-2bPrivate IPs: 172.31.13.100Security groups: appchromaticsAMI ID: ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20180912Monthly: $34.475Description:Here we have 3 set of application namely,Dev - For developers to test feature/ bug fix/ CR/Testing - For QA team to test code or application flowStaging - For US Team Testing the application {feature, bug fix and CR}
Dev
Testing
Staging
RDS
RDS Details:Database Engine: MySQLEngine Version: 5.7.23Port: 3306Region & AZ: us-east-2aResource id: db-X4SAYZAJJGAYCVGYIGSMLRPH2YInstance class: db.t2.mediumvCPU: 2Memory: 4 GBStorage: 100 GBEndpoint: theloanpost-dev.csym5hait0cq.us-east-2.rds.amazonaws.comDB identifier: theloanpost-devVPC: vpc-de9b05b6VPC security groups: appchromaticsDescription:This RDS consist of two database namely,theloanp_dev --> Dedicated for developers and testing teamtheloanp_stage --> Dedicated for US team.
Database Name: app.lendstacks_dev
Database Name: app.lendstacks_stage