This Guidance helps provide visibility into aerospace manufacturing data, including current job status, shortages, and abnormalities. Stakeholders, from mechanics to CEOs, will be able to access safety, quality, delivery, cost, and attendance analytics across multiple product lines at an individual, department, or company level. This Guidance also embeds artificial intelligence and machine learning (AI/ML) to predict optimal manufacturing sequences and recovery, allowing leaders to quickly identify issues and make predictive changes to minimize their impact.

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

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.

  • Customers evaluate their business priorities to identify the manufacturing and procurement key performance indicators (KPIs) that need monitoring. This Guidance is configurable to compute and report the signals of most value. You can evaluate your data compliance requirements and deploy data and security controls to AWS Regions that meet those requirements.

    Read the Operational Excellence whitepaper 
  • This Guidance uses fully managed services with native support for data-at-rest encryption, such as Amazon S3 and Amazon Redshift. Encryption keys are managed by AWS Key Management Service (AWS KMS), which enforces automation of key rotation. Data decryption is performed automatically by these services without user intervention or access to key material, after role-based authentication of the requester. The Guidance uses fully managed services to automate transfer of data, with built-in protocol-level enforcement of data encryption and user authentication (for example, through HTTPS and transport layer security [TLS] 1.3).

    Read the Security whitepaper 
  • External data transfers occur through AWS-managed services, such as API Gateway, AWS Glue, and Amazon Kinesis Data Firehose, which provide high availability and resiliency to network faults. Internal traffic flows on the highly available AWS network within a single Region. Lambda functions that connect data consumers and producers automatically deploy across multiple Availability Zones within a Region, to provide high resilience and availability. CloudWatch metrics are configured for workload performance metrics such as data transfer rates, storage usage, concurrent Lambda requests, and latencies for web response. Alerts are configured in CloudWatch or through Amazon SNS (invoked by Lambda) to notify administrators of critical events.

    Read the Reliability whitepaper 
  • This Guidance uses fully managed, serverless services which automatically scale the computing resources required to match current demand. Serverless database services can be configured for a capacity range that should be evaluated by the customer against predicted and actual usage. Predicted usage is based on expected number of simultaneous users, and actual usage is based on utilization metrics in the database or CloudWatch.

    Read the Performance Efficiency whitepaper 
  • The predominant data transfer is inbound—it includes the nightly synchronization of on-premises ERP, MRP, and HR databases in addition to near real-time inbound streaming of production events. Inbound-to-AWS data transfers are free. Outbound transfers are limited to web portal traffic, which are used to see summary dashboards and maintenance activity, both of which require relatively little network traffic and data transfer cost.

    Read the Cost Optimization whitepaper 
  • This Guidance uses Amazon S3 to store streaming event logs. Amazon S3 can be configured for lifecycle management to automatically archive infrequently-accessed data to lower cost storage tiers or delete it altogether. Amazon Redshift can be configured to automatically generate backups, which are generated incrementally to minimize redundant storage. The Guidance can be implemented to automatically delete database rows that are outdated or are no longer required, with custom code that runs periodically. This capability is particularly efficient if tables are partitioned by time period.

    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.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?