Search: "deploy architecture"

* Configuration of the SSL configuration (HTTPS, TLS, and client certificates) is done in Deploy -> Architecture * Certificate is generated via the support department (with or without CSR) or the client * No actions are needed on the flow level, only in the Deploy Architecture * You need a valid truststore and keystore to make it work == 3. Securing a hosted web service with certificates on-premise == To secure a web service that runs on-premise with the help of certificates, we need to navigate to Deploy -> Architecture. Here, we have the "Runtime settings" option that allows us to configure SSL options, such as HTTPS, TLS, and client certificates).

[[image:Main.Images.Microlearning.WebHome@intermediate-securing-your-data-traffic-securing-a-hosted-webservice-with-certificates-on-premise--truststore-config.png]] Once configuring your endpoint, clients must provide a client certificate to exchange data. === 3.4 Deployment === To update your configuration, you need to create a new release and deploy it to actualize the changes made for TLS, HTTPS, and client certificate configuration. === 3.5 Recap === Important things to remember are: * Configuration of the SSL configuration (HTTPS, TLS, and client certificates) is done in Deploy -> Architecture * Certificate is generated via the support department (with or without CSR) or the client * No actions are needed on the flow level, only in the Deploy Architecture * You need a valid truststore and keystore to make it work == 4.

Situation == Pressing the 'Apply to Environment' button in Deploy Architecture led to an 'Update rollback complete' state. == 2. Problem == The problem in this case was that two routes were pointing at the same port configured in Deploy Architecture. == 3. Analysis == === 3.1 Reproduction === N/A === 3.2 Analysis === We started off by checking the CloudFormation in AWS.

Update Steps Use the final R18 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline of December 14th, 2025

**Update Steps** * Use the final R18 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline of December 14th, 2025

Update Steps Use the final R22 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline is December 14th, 2025

**Update Steps** * Use the final R22 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline is December 14th, 2025

Update Steps Use the final R29 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline is December 14th, 2025

**Update Steps** * Use the final R29 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline is December 14th, 2025

Update Steps Use the final R16 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline of December 14th, 2025

**Update Steps** * Use the final R16 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline of December 14th, 2025

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

Update Steps Use the final R7 template (non service affecting) (duration: 4 minutes) User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all images have been installed according to the active release.

**Update Steps** * Use the final R7 template (non service affecting) (duration: 4 minutes) * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all images have been installed according to the active release. ** Check if messages pass through the bus by verifying a critical message flow in external systems.

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems