reference deployment

Mendix for Amazon EKS—Terraform module

Deploys a Mendix infrastructure in the AWS Cloud

This Amazon Web Services (AWS) Partner Solution uses a Terraform module to deploy an infrastructure that meets the requirements of Mendix for Private Cloud. You deploy this solution in an automated way using Amazon Elastic Kubernetes Service (Amazon EKS). The infrastructure is for users of the Mendix application-development platform who want to deploy and manage Mendix apps to the AWS Cloud.

For more information, refer to the Mendix documentation. If you have questions, feedback, or ideas, you can post them in the Mendix Forum about AWS.

Mendix logo

This Partner Solution was developed by Siemens in collaboration with AWS. Siemens is an AWS Partner. Mendix is a wholly owned subsidiary of Siemens.

  •  What you'll build
  • This Partner Solution deploys into a new virtual private cloud (VPC). It sets up the following:

    • A highly available architecture that spans three Availability Zones.
    • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.
    • An Amazon Route 53 public hosted zone that routes incoming internet traffic.
    • In the public subnets, managed NAT gateways to allow outbound internet access for resources in the private subnet.
    • In the private subnets, Amazon EKS clusters—each with three Kubernetes nodes—inside an Auto Scaling group. Each node is an Amazon Elastic Compute Cloud (Amazon EC2) instance. Each cluster contains the following (not shown):
      • Mendix apps and components.
      • Cert-manager.
      • An open-source logging and monitoring solution with Grafana, Prometheus, Loki, and Promtail.
      • ExternalDNS, which synchronizes exposed Kubernetes services and ingresses with Route 53.
    • A Network Load Balancer to distribute traffic across the Kubernetes nodes.
    • Amazon Simple Storage Service (Amazon S3) to store the files.
    • Amazon Elastic Block Store (Amazon EBS) to provide storage for Grafana, Prometheus, and Loki.
    • Amazon Relational Database Service (Amazon RDS) for PostgreSQL to store Mendix application data.
    • Amazon Elastic Container Registry (Amazon ECR) to provide a private registry.
    • AWS Key Management Service (AWS KMS) to provide an encryption key for Amazon RDS, Amazon EBS, and AWS Secrets Manager.
    • Secrets Manager to replace hardcoded credentials, including passwords, with an API call.
  •  Cost and licenses
  • To use Mendix, you must have an operator license. For more information, refer to Licensing Mendix for Private Cloud

    You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.