We are using Sophos UTM in AWS with PAYG license. Some month ago we changed the instance type from t2.small to m3.medium. This worked fine. We live in eu-west-1.
Now setting up another instance with the same AMI [1] and same instance type (m3.medium) fails on boot.
Even more rediculous, we stopped an m3.medium instance four weeks ago and starting this instance now fails.
We can solve this problem when switching from m3.medium to m4.large. Then everything works. But obviously m4.large is much more expensive than m3.medium.
Question: Is this problem with m3 instances a known problem?
What exactly is meant by "fails on boot"?
When we start the m3.medium instance it is never reachable via its IP address. In addition the AWS "Status Checks" in web console keep in state "Initializing". When we fetch an instance screenshot we see the last message "Booting from Hard Disk ..." but it never shows the Linux login prompt.
From my perspective it looks like a problem of the AMI with m3 instance type. In general m3 instance type is an old instance type which AWS want to have deprecated. But it is the only instance type with "medium" size. There is no m4.medium supported by Sophos UTM (regarding AWS Marketplace [2]).
[1] used AMI - aws-marketplace/sophos_utm_standalone_9.714-4.1-mp-9823791a-d242-49d1-8833-0a674195d6e2
[2] aws.amazon.com/.../prodview-gekyqjee5hefo
This thread was automatically locked due to age.
