How Event driven-architecture gives value:
A global company having a large and distributed cloud-based (AWS) application environment. They use cloud for the test, pre-prod and prod environments. Due to the continuous requirement to add features and release new updates to their application, their cloud infrastructure is constantly scaling and evolving.
This leads to a problem:
Their security team relied on CIS AWS Foundation Benchmarking to assess the security of their cloud assets. These assessments were done manually and at half yearly cycles. The pace of their cloud evolution meant that their cloud assets remained potentially exposed in between assessment cycles.
How Botprise No-Code, DevSecOps platfrom helped to solve the problem?
Continuous compliance framework was put in place that allowed the security team to ensure that the CIS AWS Foundation Benchmarking and reporting was fully automated.
The Smartbots are able to inform the security teams on the security gaps identified and re-run assessments when fixes to previous non-compliances are performed, thereby ensuring that the cloud infrastructure is secure and compliant at all times.
Solution:
- Security events or change related events without consuming valuable resources time.
- Notifications and remediation actions were automated on the Botprise automation framework.
- The cloud infrastructure is secure and compliant at all times.
- Notifications and remediation actions were automated on the Botprise automation framework.
How event-driven-architecture affects the process:
- Scaling/Failing independence – it makes services work free of interdependence issues.
- The development process became truly agile – each event is unique; it helps not to overwhelm the process chain with custom code polls, filters, route events, etc.
- Central audition – all the ongoing events exist in the same place; making it handy to check, control, classify or perform any actions the user would like to.
- Cut costs – all the actions can be divided into small components with high compatibility levels. Operating with small independent objects improves the sustainability in updates, edits, closing, etc.
How to create Botprise Trigger Unit
Botprise Trigger Unit creation
To create BTU:
- Go to EventHub
- Chouse Event
Note: There are requirements of BTU creation – It should be created from events of the same type, source, details data patterns.
- In Event Review pop-up click “Next”
- The next step is tagging:
- Input a unique tag name for user’s filtered event set
- Input a description for user’s data set
- To add alternative tags if you user wish’s to
- Follow next steps of testing and entity extraction evaluation.
- Then the platform will ask to “look at other apps” or “Launch the app in Studio”.
- The further process is Smart Bot Creation.