<![CDATA[Topics tagged with aws]]>https://fusionauth.io/community/forum/tags/awsRSS for NodeFri, 17 Jul 2026 21:10:11 GMTInvalid Date60<![CDATA[Can you run fusionauth in AWS fargate?]]>8GB is way plenty. 1 or 2GB is generally adequate, it can depend a bit, but FusionAuth doesn't keep much in RAM. Scaling out horizontallly is likely more effective than more ram per instance. This way you can handle more logins per second--these are going to be cpu bound.

]]>https://fusionauth.io/community/forum/topic/277/can-you-run-fusionauth-in-aws-fargatehttps://fusionauth.io/community/forum/topic/277/can-you-run-fusionauth-in-aws-fargateInvalid Date<![CDATA[Do you support sig4 auth headers for AWS Elasticsearch?]]>If you are using https://aws.amazon.com/elasticsearch-service/ for your Elasticsearch server, you can access it via AWS APIs and use IAM to control access: https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-ac.html

However, FusionAuth doesn't currently support the AWS signature for Elasticsearch requests.

The recommended way of securing such clusters is to place it in a private subnet and restricting traffic to it using a security group. More information: https://fusionauth.io/docs/v1/tech/installation-guide/securing#fusionauth-search

If you have to make it public to make it accessible to resources outside if AWS you could use a source IP lock, a VPN, basic auth if AWS supports it, or you could proxy the request perhaps to another endpoint that can build the AWS sig v4 header.

]]>https://fusionauth.io/community/forum/topic/141/do-you-support-sig4-auth-headers-for-aws-elasticsearchhttps://fusionauth.io/community/forum/topic/141/do-you-support-sig4-auth-headers-for-aws-elasticsearchInvalid Date