# Resizing EC2 instance after launch?

**URL:** <https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959>\
**Category:** Wowza Streaming Engine\
**Created:** [June 10, 2014, 2:53pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959 "2014-06-10T14:53:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Mcdonald](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@Chris\_Mcdonald](https://community.wowza.com/u/Chris_Mcdonald)\
**Post date:** [June 10, 2014, 2:53pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/1 "2014-06-10T14:53:48Z")

</div>

Hello, is it possible to resize the Amazon EC2 instance size that Streaming Engine runs on after it’s already been launched?

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [June 11, 2014, 12:53am UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/2 "2014-06-11T00:53:50Z")

</div>

Hi,

No, this is not possible with EC2 instances.

Richard

---

<div class="post-metadata">

**Author:** ![Ian\_Beyer](https://avatars.discourse-cdn.com/v4/letter/i/e99b99/32.png) [@Ian\_Beyer](https://community.wowza.com/u/Ian_Beyer)\
**Post date:** [June 27, 2014, 1:44pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/3 "2014-06-27T13:44:02Z")

</div>

You can, however, capture an AMI image of it and boot up a new one in a larger instance size. If you’re using ElasticIP you can associate the address with the new instance, or you can change a CNAME in Route53 as long as you have a nice low TTL (like, 60 seconds).

---

<div class="post-metadata">

**Author:** ![Ian\_Beyer](https://avatars.discourse-cdn.com/v4/letter/i/e99b99/32.png) [@Ian\_Beyer](https://community.wowza.com/u/Ian_Beyer)\
**Post date:** [June 27, 2014, 1:49pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/4 "2014-06-27T13:49:35Z")

</div>

It’s not quite as seamless as rebooting to a new size, but has the advantage that you can boot it up while the smaller instance is still running, and then you can just flip the switch. In my experience, an ElasticIP association can take a few minutes,but once it’s off the old one and onto the new one, there’s no risk of connections to the old one continuing. The Route53 trick might work a little better depending on what you’re needing to do. I think you can set the Route53 TTL as low as 5 seconds.

Also be aware that the process of capturing an AMI takes about half an hour and reboots the instance, so it’s not something you’ll want to do on the fly, but rather ahead of time.

---

<div class="post-metadata">

**Author:** ![Chris\_Mcdonald](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@Chris\_Mcdonald](https://community.wowza.com/u/Chris_Mcdonald)\
**Post date:** [June 10, 2014, 9:24pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/5 "2014-06-10T21:24:40Z")

</div>

ok.

---

<div class="post-metadata">

**Author:** ![Chris\_Mcdonald](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@Chris\_Mcdonald](https://community.wowza.com/u/Chris_Mcdonald)\
**Post date:** [June 27, 2014, 2:46pm UTC](https://community.wowza.com/t/resizing-ec2-instance-after-launch/38959/6 "2014-06-27T14:46:07Z")

</div>

Whoaaa! this would be awesome! Thank you. I will look into it!