Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Running DevOps for WSO2 Products on AWS


Published on

Continuous Integration (CI) is the practice of integrating code changes of various contributors into a shared repository. Continuous Delivery is all about continuously delivering integrated code, bug fixes, new features to the production environment, and continuous deployment is to automatically deploy every change that passes CI.

Using tools like Jenkins, ELK, and Prometheus, WSO2 AWS Pipeline is able to provide an end to end solution to development teams to deliver changes and WSO2 updates effortlessly.

This deck will help you understand how to set up a fully configured pipeline in your AWS environment and how it can be customized easily to fit your requirements.

Discussion areas include:
- Continuous Integration and Continuous Deployment of WSO2 products in just a click.
- Improve product delivery by enhancing predictability, efficiency, and maintainability.
- Deployment of WSO2 products on AWS Cloud with less effort and time.
- GitOps driven, fully customizable, cloud-native and immutable nature of the Pipeline.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Running DevOps for WSO2 Products on AWS

  1. 1. Running DevOps for WSO2 Products on AWS Ching Tien Shi, Senior Software Engineer, WSO2, Shafana Safwan, Software Engineer, WSO2,
  2. 2. Discussion Points • What is a CI/CD Pipeline? • Why do we need a CI/CD Pipeline? • Key features of WSO2 CI/CD Pipeline • AWS Pipeline Architecture • Deployment Infrastructure
  3. 3. What is a CICD Pipeline? • CI Continuous Integration is the process of integrating all new code changes into a shared repository. • CD Continuous Deployment is the process of automated delivery of the integrated code from the development to the production stage. A CI/CD Pipeline is the process of taking code from version control and making it readily available to users of your application in an automated fashion.
  4. 4. Why Do We Need a CI/CD Pipeline? • Single click deployments • End to end automation • Quick delivery of bug fixes and feature • Customer satisfaction • Easy maintenance • Reduce costs
  5. 5. Key Features of WSO2 CI/CD Pipeline • Quick start with minimal default configurations • Preconfigured pipeline with safe defaults • Support for Multiple Environments • Centralized Logging with ELK • Out of the box Monitoring with Prometheus – Performance monitoring via JMX – JVM health monitoring • Automated Devops driven by GitOps • Embedded with WSO2 updates • Customizable to match user requirements
  6. 6. AWS Pipeline Resources for WSO2 Products
  7. 7. WSO2 AWS Pipeline Architecture
  8. 8. Pipeline Demo
  9. 9. Deployment Infrastructure
  10. 10. Q & A
  11. 11. Resources ● ● ● ● ● ● ● ● ● your-key-pair ●
  12. 12. THANK YOU