# Questions related to Elastic Cloud: upsizing, load-balancing, auto-restarts, S3 archiving

**URL:** <https://discuss.elastic.co/t/questions-related-to-elastic-cloud-upsizing-load-balancing-auto-restarts-s3-archiving/196459>\
**Category:** Elasticsearch\
**Created:** [August 23, 2019, 7:14am UTC](https://discuss.elastic.co/t/questions-related-to-elastic-cloud-upsizing-load-balancing-auto-restarts-s3-archiving/196459 "2019-08-23T07:14:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![marko\_vranjkovic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marko_vranjkovic/32/52881_2.png) [@marko\_vranjkovic](https://discuss.elastic.co/u/marko_vranjkovic)\
**Post date:** [August 23, 2019, 7:14am UTC](https://discuss.elastic.co/t/questions-related-to-elastic-cloud-upsizing-load-balancing-auto-restarts-s3-archiving/196459/1 "2019-08-23T07:14:26Z")

</div>

Hello,

I'm doing a research on Elastic Cloud using AWS and have several questions:

1. Can we down/upsize elastic instances without downtime?

2. The endpoint here:  

3. If an instance goes down due to an issue with e.g. JVM, who is responsible for bringing it up?

4. Is there an option to archive and offload indices to e.g. S3 as part of ILM delete phase?

5. The instance used for aws.data.highio.i3 in AWS is i3.8xlarge, how many vCPUs are going to be dedicated to my cluster? How are cores shared between instances that are deployed on the same machine?

Regards  
Marko

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 30, 2019, 6:32pm UTC](https://discuss.elastic.co/t/questions-related-to-elastic-cloud-upsizing-load-balancing-auto-restarts-s3-archiving/196459/2 "2019-08-30T18:32:56Z")

</div>

> [@marko\_vranjkovic](#):
>
> Can we down/upsize elastic instances without downtime?

Yes.

> [@marko\_vranjkovic](#):
>
> Is that an endpoint to a load balancer? If is, which one, AWS ELB?

Possibly, but that is an internal component of the managed service, so there should be no need to be concerned about this.

> [@marko\_vranjkovic](#):
>
> If an instance goes down due to an issue with e.g. JVM, who is responsible for bringing it up?

I believe that should be automatic, but someone from the Cloud team should be able to confirm.

> [@marko\_vranjkovic](#):
>
> Is there an option to archive and offload indices to e.g. S3 as part of ILM delete phase?

As far as I know that is not currently supported by ILM and therefore not the service either.

> [@marko\_vranjkovic](#):
>
> The instance used for aws.data.highio.i3 in AWS is i3.8xlarge, how many vCPUs are going to be dedicated to my cluster? How are cores shared between instances that are deployed on the same machine?

I believe CPU is time-shared based on the size of the node compared to the size of the host, but someone from the Cloud team can hopefully correct me if I am wrong.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 27, 2019, 6:32pm UTC](https://discuss.elastic.co/t/questions-related-to-elastic-cloud-upsizing-load-balancing-auto-restarts-s3-archiving/196459/3 "2019-09-27T18:32:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.