Automotive Cloud Developer Portal
Automotive Cloud Developer Portal architecture
The initial deployment of CMS on AWS includes the ACDP and Backstage, which assist in managing the deployment of CMS on AWS modules. The ACDP provides a presentation layer through the Backstage module, which you can use to select, configure, and deploy individual modules. Backstage also allows for monitoring and teardown of these modules, as well as viewing of module documentation. Backstage integrates with AWS CodeBuild for deployment execution. The ACDP is a powerful platform that enables flexibility and quick insights into deployed infrastructure.
Deploying the ACDP creates and configures an AWS CodePipeline for deploying the Backstage
module. The pipeline is configured with the necessary environment to carry out the Backstage
deployment. Values for this configuration are taken from the local environment of the ACDP
deploy, which is configured with Make
The pipeline then handles the deployment of the Backstage module in three stages. These stages are abstracted from the previous diagram:
-
Source - Sources the Backstage source code from an Amazon S3 bucket.
-
Build – Builds the Backstage docker image and pushes it to the private Amazon ECR repository.
-
Deploy - Deploys the Backstage module stack.
Once deployed, you can then use the Backstage module to deploy CMS on AWS modules.
Supported networking scenarios for ACDP
ACDP can be configured with the following networking topologies:
-
Publicly accessible through the internet with Route53 and an auto generated ACM certificate.
-
Publicly accessible through the Internet with an external DNS and a custom certificate uploaded to ACM.
-
Private endpoints with public DNS hosted by Route53 and an auto generated ACM certificate.
-
Private Route53 Hosted Zone with a custom certificate uploaded to ACM.
-
Private VPC linked to a public VPC through a transit gateway.
