This Guidance demonstrates how you can improve operational resilience in airline operations, thereby gaining timely operational data to increase productivity, reduce the risk of flight disruptions, and support airline policies and procedures. By deploying Smart4Aviation Smart SUITE on AWS, you can use managed services in a highly available, resilient, and fault-tolerant architecture, and you can assemble Smart SUITE’s interoperable modules to build an airline operations solution tailored to each airline.

Please note: [Disclaimer]

Architecture Diagram


Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • This Guidance lets you respond to incidents and events and monitor key performance indicators (KPIs) like HeapUsage, EnqueueCount, InFlightCount, and DequeueCount. You can use Amazon OpenSearch Service to monitor KPIs, view logs, and detect anomalies.

    Read the Operational Excellence whitepaper 
  • This Guidance protects resources using several AWS services. Shield provides layer 3 and layer 4 distributed denial of service (DDoS) protection, and AWS WAF protects against common layer 7 web exploits and bots that can affect availability, compromise security, or consume excessive resources. Additionally, AWS Key Management Service (AWS KMS) lets you control cryptographic keys to protect business data, and AWS Identity and Access Management (IAM) and AWS IAM Identity Center (successor to AWS Single Sign-On) centrally manage workforce identities with fine-grained permissions access to resources and services.

    Read the Security whitepaper 
  • This Guidance uses AZs to provide high availability and automated failover within a Region and can scale horizontally to increase aggregate workload availability. Services can store data redundantly across multiple AZs or replicate to instances in other AZs. In the event of a regional degradation or outage, Amazon Aurora Global Database has pilot-light disaster recovery infrastructure in place and uses storage-based replication, typically supporting recovery time objective (RTO) measures in minutes and recovery point objectives (RPO) measures in seconds.

    Read the Reliability whitepaper 
  • This Guidance uses Aurora PostgreSQL, which provides three times the throughput of PostgreSQL. Additionally, AWS Graviton processors for Aurora and Amazon EC2 instances have up to 40 percent higher performance than comparable x86 processors. On larger systems, you can decouple OpenWire communication and Simple Text Orientated Messaging Protocol queues on distinct clusters with storage optimization.

    Read the Performance Efficiency whitepaper 
  • This Guidance lets you automatically scale components individually based on demand using Amazon EC2 Auto Scaling groups for cost optimization. Using AWS Graviton processors for Amazon EC2 and Amazon Relational Database Service (Amazon RDS) instances provides up to 20 percent savings.

    Read the Cost Optimization whitepaper 
  • This Guidance implements efficient design to maximize resource use, and it uses Amazon EC2 Auto Scaling groups to dynamically rightsize the compute capability. Instances based on AWS Graviton use up to 60 percent less energy for the same performance than comparable Amazon EC2 instances.

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

SMART4AVIATION is a trademark owned by Smart4Aviation Technologies B.V. SMART4AVIATION, the SMART4AVIATION logo, and all related names, logos, product and service names, designs, and slogans are trademarks of SMART4AVIATION or its affiliates or licensors2, and are used here with permission.

Was this page helpful?