AWS AMI Instance type restrictions

[Steven Denham]

We are trying to deploy a small test deployment so we want to use a T3a.Medium instance, but it is giving an error that it is not supported.
Why are these restrictions on the AMI, it is unnecessary. When using the OVA install it runs just fine on 2cpu and 4GB ram.

I understand what the recommendation is, and that is based on a production system, but it's not really a recommendation if it is forced.
I don't understand why I should have to pay 4x the cost to run a test instance that does not require that amount of resources.

Can these restrictions be removed or bypassed somehow?

[Stuti Gupta]

Hi Steven,
Hope you are doing well today and thank you for using wazuh.

T3a.Medium instances do support Wazuh all-in-one development you can check it here https://documentation.wazuh.com/current/deployment-options/amazon-machine-images/amazon-machine-images.html#packages-list
As for the pricing, it is AWS policies please consult them 

Hope this will help.
Regards,

[Steven Denham]

Hello Stuti,

Currently t3a.medium instances are not supported by the Wazuh All-In-One Deployment AMI.

If I try to use a t3a.medium instance (or many others) I get this error 

"The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems."
This means that the instance size is being restricted in the AMI by Wazuh.

The pricing problem is not AWS, it is Wazuh forcing us to use a more expensive instance when it is not necessary.