Client Details
March 14, 2023 2023-03-15 9:04Client Details
CLIENT DETAILS
CI / CD
Client 01
About the project
1) CloudFormation code for VPC/Network/EKS Cluster
2) Kubernetes configuration files with options for service-autoscaling and cluster autoscaling.
3) Integration with AWS Parameter Store
4) Deployment through AWS CodePipeline CI/CD.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 5x
Client Team = 2x
Client 02
About the project
The Customer would like to migrate their app to AWS. Currently the staging and prod environments are already containerized using Docker swarm. The Customer is currently using Jenkins for deployments. We will migrate the existing environment to AWS, setup a proper CI/CD pipeline with Gitlab, enable monitoring, and monitor the environment 24x7 for any issues. The customer will also like to migrate to Aurora as part of the migration.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
Client 03
About the project
The client is looking for an AWS partner, their AWS spend is about 10k. The first step, the customer wants us to build a scalable CI/CD pipeline. Currently, a build environment is manually created and very error-prone. The customer wants the build environment which is scalable, at the same it needs to be isolated. The isolation will allow Customer to have third-party developers spin up the containerized environment; the customer has been wanting on implement this kind of CI/CD pipeline for a while. After the CI/CD, the customer wants us to help them to containerize all of applications.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
Layer 1 Team = 2x
Client 01
About the project
We will build the infrastructure using Cloudformation. We'll also automate the deployment using CodeStar. After the Cloudformation automation, we will distribute the workload in three AZs, we will spin up a new region in Oregon, and spin up a pilot light environment. The deployment will keep the code in sync for both of the regions.
The client portal is a single-tenant app, and there are about 30 customers. The custom code is currently saved in SVN, the customer will migrate from SVN to GitHub. During the deployment, we will fetch the custom code build custom AMIs.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 2x
Client Team = 2x
DevOps
Client 02
About the project
The client is looking for us to help with many DevOps projects. Jenkins automation is one of the first projects the Client would like us to tackle. Currently, Jenkins jobs are created manually, Client would like us to build a scalable and fully automated Jenkins environment on ECS. We will be helping with many other DevOps-related projects like building ephemeral environments on AWS and infrastructure automation.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 4x
Client Team = 3x
Layer 1 team = 3x
Client 03
About the project
Customer recently had a security breach; luckily only the QA environment was affected. Customer is now looking for managed services. But the first month of the engagement Customer wants us to focus on making sure all the security best practices are in place, which were discovered during the well-architected assessment. We will attempt to containerize the infrastructure for managed services through containers, but if for some reason it's too much work containerizing apps, we will use Opsworks to manage the infrastructure. In addition to building infrastructure with best practices, we will be responsible for doing OS patch management for the production environment.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 5x
Client Team = 2x
Layer 1 team = 3x
Layer 2 team = 2x
Monitoring
Client 01
About the project
The Customer would like to migrate their app to AWS. Currently the staging and prod environments are already containerized using Docker swarm. The Customer is currently using Jenkins for deployments. We will migrate the existing environment to AWS, setup a proper CI/CD pipeline with Gitlab, enable monitoring, and monitor the environment 24x7 for any issues. Customer will also like to migrate to Aurora as part of the migration
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
Client 02
About the project
Customer is currently using Elastic beanstalk for the application, there is not deployment pipeline. Some of OperationsRx's customers are requiring 24x7 support. Currently there are around 3 database servers, and six beanstalk severs. Aurora migration is in process, migration will be completed in two months. Customer is also looking to build infrastructure with best practices, and build a standby region using aurora.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 2x
Client Team = 2x
Layer 1 Team= 5x
Layer 2 team = 2
Client 03
About the project
Client runs a personalized Sports Entertainment Platform. One of their products support automated creation of highlight reels. Client currently utilizes ECS (with Fargate) fort his. The response time required for ECS Task to come online was found to be unsatisfactory. We will help Client to implement a Customized Scaling mechanism on ECS which would bring down the response time and will also run in a cost-efficient manner. We will also provide 24x7 support for the current Production environment.
Team and Resources Involved
Sales Team = 1x
Project Management Team = 5x
DevOps Team = 1x
Client 01
About the project
Case Study:
Setting up a Kubernetes Cluster on EC2 Instances using Ansible and Terraform
Introduction:
The client wanted to set up a highly available and scalable Kubernetes cluster in AWS EC2 instances for their production applications. The cluster was to include several components, such as etcd, Calico, Helm, Istio, NetApp NFS, Prometheus and Grafans for cluster monitoring, ElasticSearch, Logstash, and Kibana (ELK) for cluster logging. The client also wanted to secure the cluster through DEX and Gangway components and RBAC.
AWS Infrastructure / Migration
Solution:
To fulfill the client’s requirements, the following solution was implemented:
Terraform was used to set up the AWS infrastructure for the cluster. This ensured that the infrastructure was easily manageable, version controlled, and repeatable.
Ansible playbooks were created to automatically set up the Kubernetes cluster and install other components in the cluster. This allowed for easy and efficient management of the cluster components.
The cluster was set up with multiple master nodes to ensure high availability and scalability.
DEX and Gangway components and RBAC were used for cluster security, including authentication and authorization.
A CI/CD pipeline was implemented through Jenkins, allowing for efficient and streamlined deployment of applications.
Conclusion:
The Kubernetes cluster set up on EC2 instances using Ansible and Terraform met the client’s requirements and provided a highly available, scalable, and secure solution for their production applications. The use of Terraform and Ansible ensured that the infrastructure and components were easily manageable, and the CI/CD pipeline through Jenkins provided efficient deployment capabilities.
Client 02
About the project
Case Study:
Modernizing Customer's AWS Infrastructure with Eurus Consulting Services
Introduction:
Optimisers was engaged by a customer to modernize their AWS infrastructure. The initial phase of the project was focused on four key areas: integrating a Security Information and Event Management (SIEM) solution, evaluating and integrating a single-sign-on solution, moving from IAM users to IAM roles, and integrating OpenVPN with SSO if the chosen SSO solution had a LDAP/Active Directory endpoint.
Solution:
The following steps were taken to modernize the customer's AWS infrastructure:
Integrating a Security Information and Event Management (SIEM) Solution:
The customer had two options to choose from: Option A) AWS Security Solutions (AWS GuardDuty, AWS Inspector, and AWS Security Hub) or Option B) AlertLogic SIEM Solution. The customer chose Option A and Optimisers integrated the AWS security solutions to provide comprehensive security visibility and protection for the customer's AWS environment.
Evaluate and Integrate a Single-Sign On Solution:
Optimisers evaluated the customer's requirements and recommended Okta or AWS SSO. The customer chose AWS SSO and Eurus integrated it with the customer's AWS Console Login, providing a streamlined and secure login experience.
Move from IAM Users to IAM Roles:
- Optimisers helped the customer move from IAM users to IAM roles for automated AWS API access. This provided enhanced security and management of AWS API access.
- Integrating OpenVPN with SSO:
- Optimisers integrated OpenVPN with SSO to provide secure access to the customer's AWS resources.
- After the initial phase, Optimisers worked with the customer to prioritize and plan other items from their DevOps backlog. This included advising on the current architecture and ongoing migration from EC2-based services to Lambda and helping with the adoption of App sync and Cognito.
We also carried out a Well-Architected Review on the customer's AWS infrastructure, providing best practices and recommendations to improve the architecture, security, and reliability of the customer's AWS environment.
Conclusion:
The modernizing project was a success and the customer was extremely satisfied with the results. The customer now had a secure and streamlined AWS infrastructure, with a comprehensive SIEM solution and single-sign-on solution, and was well on their way to adopting other AWS services to meet their business needs. Optimisers’ expertise and experience in AWS helped the customer achieve their goals and set the foundation for ongoing success.
