we can use aurora as it is much easier to scale it and work on it us hisaab se, read replicas also better in it

we store it in the ebs volume, our instnace will be in one az since it has an attached ebs volume:

but when we start using multiple instances, it starts being a problme:

this is bcuz when it is read, imafge is read from the volume of its az, so if user sends image and sotres it into AZ1, but then when goes to read it is directed to AZ2, there will be nothing to read, this is problkem with ebs volume

we solve this porblem using EFS, it will use ENI to connect the isntances to a collective EFS, hence something sotred by the first instnace, will be saved and seen in secodns isntance since using ENI it will be able to read it off

• Aurora Database to have easy Multi-AZ and Read-Replicas

• Storing data in EBS (single instance application)

• Vs Storing data in EFS (distributed application)

  Insitnatiating Applications faster:

  • When launching a full stack (EC2, EBS, RDS), it can take time to: • Install applications • Insert initial (or recovery) data • Configure everything • Launch the application
  • We can take advantage of the cloud to speed that up!

Beans Stalk:

how can we make this web apps deployment easier? beansstalkkkk

Developer problems on AWS • Managing infrastructure • Deploying Code • Configuring all the databases, load balancers, etc • Scaling concerns • Most web apps have the same architecture (ALB + ASG) • All the developers want is for their code to run! • Possibly, consistently across different applications and environments