# Getting FMS Developer Working on AWS AMI Instance

**URL:** <https://the.fmsoup.org/t/getting-fms-developer-working-on-aws-ami-instance/5311>\
**Category:** Floating Topics\
**Created:** [March 3, 2026, 6:30pm UTC](https://the.fmsoup.org/t/getting-fms-developer-working-on-aws-ami-instance/5311 "2026-03-03T18:30:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [March 3, 2026, 6:30pm UTC](https://the.fmsoup.org/t/getting-fms-developer-working-on-aws-ami-instance/5311/1 "2026-03-03T18:30:58Z")

</div>

I have a developer license for FMS.

Doing a test creating an AMI from the working AWS instance, I see that FMS is not happy in the AMI-created instance. Fields like Server ID are blank, and, well, the bottom line is that the Database Server will not start.

Am I trying to do something that’s not allowed? I thought there were three servers allowed for deployment.

Not sure what to try.

Do I need to perhaps (please say this step isn’t necessary!) have to re-install FMS on the AMI-created instance?

Both machine types are identical, same Windows 2022 Server, etc.

Trying to import the same license certificate failed on the AMI-created instance.

Thanks in advance,

---

<div class="post-metadata">

**Author:** ![AndyHibbs](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/andyhibbs/32/3089_2.png) [@AndyHibbs](https://the.fmsoup.org/u/AndyHibbs)\
**Post date:** [March 4, 2026, 7:40pm UTC](https://the.fmsoup.org/t/getting-fms-developer-working-on-aws-ami-instance/5311/2 "2026-03-04T19:40:19Z")

</div>

Hi Oliver

If you’ve cloned a working instance then it will have cloned things like the server ID, but the clone will have a different server ID.

Best uninstall FMS off the clone and then reinstall and reconfigure.

Regards

Andy

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [March 5, 2026, 2:10pm UTC](https://the.fmsoup.org/t/getting-fms-developer-working-on-aws-ami-instance/5311/3 "2026-03-05T14:10:27Z")

</div>

Thanks Andy!

You’re totally right.

In the new AMI-generated instance, I had to uninstall and re-install FMS using “local account”. Then, it worked.

Before re-installing FMS and just using the AMI-generated instance itself, the Server ID was blank. I could not enable logs. Trying to import license didn’t work either. Trying to create a new password from the fmsadmin and my saved PIN didn’t work either.

Of course, I would need to either delete the original instance or get another elastic IP with a new sub-domain for my wildcard certificate to work.

It was interesting that **none** of the Windows incoming firewall rules (like 5003, 2399, …) were present in the AMI-generated instance and I had to recreate these. Of course the rules in AWS were fine since I used those to create the instance.

All in all, I see how to do this now, but it’s a far cry from “create an AMI, generate an instance from the AMI and you’re “good to go””.

I appreciate your kind reply.

Thanks again! 😀