View a markdown version of this page

IFS Maintenix Software Implementation on AWS - IFS Maintenix Software Implementation on AWS
IFS Maintenix implementation diagramFurther readingDiagram history

IFS Maintenix Software Implementation on AWS

Publication date: March 24, 2022 (Diagram history)

You can use AWS to create a highly available, secure, flexible, and cost-effective architecture to host IFS Maintenix Aviation Maintenance Management Software. This architecture connects on-premises systems to AWS with multiple networking options.

This architecture deploys IFS Maintenix software servers across two Availability Zones. It uses Amazon RDS for the database tier and AWS Database Migration Service for data replication to your data warehouse.

IFS Maintenix implementation diagram

Architecture for IFS Maintenix on AWS using Amazon Elastic Compute Cloud, Amazon RDS, and AWS Transit Gateway.

The following steps describe the architecture:

  1. Connect on-premises routers securely with high availability to a Amazon VPC. Use AWS Direct Connect, AWS Site-to-Site VPN, and AWS Transit Gateway.

  2. Deploy Maintenix software servers into Amazon EC2 instances across two Availability Zones with Auto Scaling groups.

  3. Deploy an Oracle database by using Amazon RDS configured with Multi-AZ for high availability with a failover standby instance.

  4. Turn on Change Data Capture (CDC) with AWS Database Migration Service. Push changes to your data warehouse for analytical processing.

  5. Provide access to the application tier for corporate-network users. Route requests through a private Application Load Balancer through AWS Transit Gateway into the Amazon EC2 Auto Scaling group.

  6. Allow internet-connected users to access the application tier through a public Application Load Balancer. Use Route 53 for domain name resolution. Protect the Application Load Balancer with AWS WAF.

  7. Configure the Integration and Reporting tiers for internal access only. Make them accessible from the application tier Auto Scaling group and from on-premises through private Application Load Balancers.

Further reading

For additional information, see the following resources:

Diagram history

To receive updates about this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

March 24, 2022

RSS subscription requirement

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.