# Unable to launch EC2 instance as M5, even though my previous Wowza server was M5

**URL:** <https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825>\
**Category:** Wowza Streaming Engine\
**Created:** [March 18, 2020, 6:58pm UTC](https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825 "2020-03-18T18:58:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brandon\_Colton](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brandon\_Colton](https://community.wowza.com/u/Brandon_Colton)\
**Post date:** [March 18, 2020, 6:58pm UTC](https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825/1 "2020-03-18T18:58:36Z")

</div>

I have a reserved M5 instance that saves us some money on a yearly commitment. Our Wowza server was using this M5 reservation. I launched a new server with the latest Wowza AMI and am unable to select M5. I can select M4, but I don’t have a reservation for M4, it costs more, and it doesn’t make much sense that M4 would be supported but M5 is not. Please advise!

---

<div class="post-metadata">

**Author:** ![Brandon\_Colton](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brandon\_Colton](https://community.wowza.com/u/Brandon_Colton)\
**Post date:** [March 19, 2020, 4:04pm UTC](https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825/2 "2020-03-19T16:04:19Z")

</div>

This shows my old server is running m5.large but the new one is at m4.large and unable to be launched as m5

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [March 19, 2020, 2:02am UTC](https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825/3 "2020-03-19T02:02:18Z")

</div>

I know we were looking to add this in early 2020 so let me get an update for you. I may not know until morning though- fyi.

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [March 19, 2020, 4:37pm UTC](https://community.wowza.com/t/unable-to-launch-ec2-instance-as-m5-even-though-my-previous-wowza-server-was-m5/54825/4 "2020-03-19T16:37:30Z")

</div>

We are waiting approval from AWS for the 4.8.0 listing update and that includes machine sizes like M5. It should be any day now.
