Databases
StackOverflow2013
Postsdbo
POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
    primarykey
    data
    text
    <p>So, in a simple situation, if there is only one instance, then I can store the data into a EBS volume mounted on that instance. e.g. /mnt/db</p> <p>However, how does it work if I scale and have multiple instance (either static or dynamic scaling)? </p> <p>Because one EBS can only attach to one instance, if I have multiple instance, does it mean that I have to attach an EBS volume for each instance? If that's the case, the data on each Instance's EBS volume will be different.</p> <p>It is obvious that I want all instances to access (R &amp; W) a single volume (as data-storage). and the data in the volume will constantly grow and there is no downtime. </p> <p>What is the solution? Is there a way that I don't mount the device (EBS), and just call it for accessing the data?</p> <p>Here is what I can think of: 1) if each instance has its own EBS volume, then each time interval (e.g. 1 hour), all instances will unmount &amp; detach the EBS volume,and attach a new one. Then there is one powerful instance that mount all the EBS volumes just detached, and aggregate all the data. 2) or similar to 1), instead of detach and attach, I just take a snapshot on all volumes for all instances. Then the powerful instance aggregateness the data from the snapshot. And save the result into either another EBS or S3. </p> <p>These two approach seem to be working.. but require a lot of work. is there a smarter way to approach this problem? thanks.</p> <ul> <li>by the way, because of performance issue, I cannot have the instance writes data to S3. :)</li> </ul> <p>OH how about this 3) First, all instances have their own EBS and write data into the EBS. and then each hour, data will be sent to S3. Then another instance will aggregate them. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSteffen Opel
    1. USmurvinlai
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
      1. USJay
      1. VTFavorite
    3. VO
      singulars
      1. POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
      1. USJoris
      1. VTFavorite
    1. COThis is a very good question and a part of the AWS Auto Scaling that I do not understand and came hoping for an answer. How does auto scaling work when the database is on an EBS volume? That is, how do the new EC2 instances have access to it?
      singulars
      1. POhow does multiple EC2 instances (scaling) works on one EBS for data storage?
      1. USSkill M2
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload