Architecture Diagrams
Services relationship
Default diagram with the relationship between services and customer, as well as the AWS services which are being used in typical customer deployment.
loading...Network Diagram
VPC's and network diagram components and relationship. The above diagram shows the needed VPC resources for typical AOS Edge installation, additionally, which resources will be running on each subnet.
loading...Points to highlight:
- Postgres and Redis are working in redundant mode on 2 az's.
- AKS and LB are working on 3 AZ's.
- As up today supported architecture it is implemented for one region only, there is no multiregion feature yet.
- Some components are not shown in the diagram as those are part of the endpoint subnet, the AWS service endpoints will be attached to this subnet which uses external (non subnet) resources such as:
- Cloudfront
- S3
- SecretsManager
- ECR
- ImageBuilder
- Lambda
- AWS Cloudwatch
Simple Icons diagram
Diagram which simplifies the AOS Edge Cloud architecture.
loading...Integration points
The next diagram, tries to show how it will be the interaction between AOS Core (Devices) and AOS Cloud (AWS).
Points to highlight:
- Authentication goes via TLS for all services (even frontend services).
- Certificates must be issued to be able to interact with AOS Cloud.
- Rabbit also uses TLS as authentication mechanism.
- Autoscaling will be handled by AWS/AOS cloud.
- Cloudfront authentication goes through signed url to get updates for devices.