Wamessages

Project Scope: Wamessages is a WhatsApp automation chrome extension., which is used to Connect with your customers via personalized WhatsApp Messages. this extension is send messages according to the list of numbers, from google Sheets as well as excel sheets.

The frontend of this application is working from Dorik.com and  For the backend, we have deployed API in scalable architecture using EC2. Whenever there is a spike in the website, autoscaling is triggered and deploys a new server to handle the request. Load balancer is also in use for managing the load balance between servers. For network and application security, we have used WAF with custom rules and Detective Inspector, AWS Guard Duty.

Infrastructure: Manually deployed using AWS console and Dorik.

Services used:
1) EC2 as a backend server
2) Autoscaling and Application load balancer for handling/managing traffic.
3) RDS with MySQL as a database engine.
4) Route53 as a DNS
5) AWS backup.
6) Detective, Guard Duty, Inspector and WAF as security tools.
7) ACM from certificate manager.
8) Email from AWS Work-mail.
9) Amazon Simple Email Service.
10) Security groups for allowing particular Ips.
11)Separate VPC for production or staging environment.
12) GitHub action for application deployment.
13) set up Zendesk for customer support.

VetsScout 

Project Name: VetsScout 

Project Scope: Deployment of application on AWS linux machine CI/CD is setup from bitbucket to aws servers using bitbucket pipelines. For website, server is placed behind the application load balancer with Autoscaling for managing the load and traffic.

Infrastructure: Deployed using Terraform with CircleCI

Services used:
Bitbucket secrets credentials for storing secret variables.

1. Virtual private cloud (VPC) for the complete Infra.
2. RDS postgres sql for the database. 
3. Virtual private network (VPN) to access private resources
4. Application Load balancers to handle traffic of applications
5. Security groups for allowing particular Ips

USEReady

Project Scope: Deployment of dot net application on AWS windows machines. CI/CD is setup from bitbucket to aws servers using Jenkins. Jenkin server is using multiple nodes for providing high availability of deployment. For website frontend and backend windows server is placed behind the application load balancer with Autoscaling for managing the load and traffic.

Infrastructure: Deployed using Terraform and packer.

Services used:

1. Jenkin credentials for storing secret variables.
2. Virtual private cloud (VPC) for the complete Infra.
3. RDS postgres sql for the database. 
4. Virtual private network (VPN) to access private resources
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. Jenkin pipelines for deployment

The Credit Pros

Project Name: The Credit Pros

Project Scope: Deployment the multi sites using AWS, API Gateways and Serverless Functions. Using their main site on WordPress. Managing domains and Hosting from Godaddy and Cloudflare respectively. Managing the SSL certificates to secure the website. Using Jira and OpsGenies for the ticketing system. For some of the applications using the LoadBalancers.

Infrastructure: Manually deployed using AWS console, and using Azure Directory.

Services used:

1. EC2 as a backend server
2. Application load balancer for handling/managing traffic
3. RDS with Aurora and MySQL as a database engine
4. SSL2BUY for SSLs
5. Aws CloudFront for static frontend hosting
6. AWS backup as an additional backup of database and EC2 instances
7. CloudWatch and DataDog as monitoring tools
8. Security groups for managing IPs. For a specific server using IP Tables.
9. WordPress plugins and themes
10. GoDaddy and Cloudflare for managing domains
11. AWS Cognito
12. Workspaces for the specific team.
13. OpenVPN server.
14. AWS Lambda Functions.
15. GitHub for the versioning tool.
16. LucidChart.
17. Scribe for recording the sessions.
18. ServerPilot for the specific servers.

Systematic Ventures

Project Name: Systematic Ventures

Project Scope: Continuous deployment with AWS Code pipeline along with code build and code deploy. Every time pipeline is triggered an Amazon Elastic Container Service (ECS) is deployed using AWS Fargate, by using Farget you don’t need to manage servers, handle capacity planning, or isolate container workloads for security. Fargate handles the infrastructure management aspects of your workload. You can schedule the placement of your containers across your cluster based on your resource needs, and availability requirements. 

ECS manages containers and lets developers run applications in the cloud without having to configure an environment for the code to run in. It enables developers with AWS accounts to deploy and manage scalable applications that run on groups of servers called clusters through API calls and task definitions. Amazon ECS is a scalable service accessible through the AWS Management Console. 

For Frontend deployment used cloudfront for code deploy with s3 bucket.

Infrastructure:  Manual deployed by using AWS console.

Services used: 

1. Virtual private cloud (VPC) for the complete Infra of Systematic-Ventures
2. Mongodb to handle database through VPC peering 
3. EC2 instances to access ECS containers
4. Elastic container registry (ECR) to store docker images
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. ECS task definition
8.  ECS Clusters for micro services
9.  Aws CloudFront and S3 bucket for static frontend hosting
10.  WAF as a security tool
11.  CloudFront for frontend web
12.  Codepipeline with code build and code deploy
13.  IAM roles and policies for services
14.  Datadog for getting ECS containers logs
15.  Route 53 for managing domains
16.  Elastic cache for managing cache

Synoptek

Project Name:  Synoptek

Project Scope: Deployment of application is on AWS, One LOGIN and Cloudamize. In this project we’ve been working on several different things in terms of Deployment and Infrastructure. We set up around 1200 servers for them in their environment. I would also like to mention the names of several different projects on which we worked on like Jostens, CHCS, STX, MDG and ibas. Worked with the issue requesting tickets for Synoptek.     

Infrastructure: Deployed over AWS console and Cloudamize. 

Services used:

1. Virtual private cloud (VPC) for the complete Infra.
2. Virtual private network (VPN) to access private resources.
3. TGW has been used as an endpoint. 
4. Security groups for allowing particular Ips
5. Cloudamize Infrastructure details. 
6. Disaster Recovery Cost Estimation Plans.
7. Worked on Statement of work approvals.  
8. Well architected lab for saving recommendations. 
9. Setup 1200 servers for them in their environment.
10. Worked on Server Hardening Documents. 
11. Well-Architected Lab for cost optimization. 
12. Data migration for Cloudamize.

Squegg

Project Name: Squegg

Project Scope: Continuous deployment with AWS Code pipeline along with code build and code deploy for continuous deployment for source code. Every time pipeline is triggered, a code deploys initiate that takes our commits from GitHub repo for our source codes and deploys it automatically on our servers.

Deployed Application Load balancers to handle traffic of applications with multiple target groups and created SSL certificates using Amazon certificate manager and attached those SSL certificates with load balancer to provide secure connection. MySQL database for managing data with no public access.

Deployment of AWS CloudFront with S3 origin to host static content, store secrets with amazon secret manager. And restrict resources access using IAM policies.

VPC peering for accessing multi region resources and MySQL Database for managing databases with no public accessibility.

Infrastructure: Deployed by using Terraform (Infrastructure as a code) on AWS.

Services used: 

1. Secret Manager for storing secret value like Database password
2. Virtual private cloud (VPC) for the complete Infra of Squegg
3. MySQL database to handle database through VPC peering 
4. EC2 instances to access server
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. Aws CloudFront and S3 bucket for static frontend hosting
8. WAF as a security tool
9. IAM policies for accessing specific resources 
10. KMS for encryption
11. SES for getting notification for pidfront with S3peline failure.

Development

Project Name : SocialEyes(NicholasB.)

Project Scope: SocialEyes is creating myriad points of access for healthcare to serve at-risk populations everywhere. Our team comprises domain experts in basic science, machine learning, medicine, optics, electromechanical design, illumination, clinical decision support software, and user experience.

In this project, the following steps outline a solution that implements the basic components of a Nucleus deployment. To handle communication from end users, an Amazon Elastic Compute Cloud (Amazon EC2) instance configured as an NGINX reverse proxy is deployed in a public subnet. The reverse proxy accepts TLS traffic utilizing a TLS certificate from the Amazon Certificates Manager.
Typically, this component would be an Elastic Load Balancer (ELB), but Nucleus requires path rewrites in the request which is not currently supported by an ELB. The Nucleus Server is an Amazon EC2 instance deployed to a private subnet that only accepts traffic from the reverse proxy subnet. The Nucleus Server is running the Nucleus Enterprise Stack, which is deployed as a Docker Compose Stack. Thus, Nucleus will need a NAT Gateway and Internet Gateway to communicate with the NVIDIA Container Registry.

 And we deploy an Omniverse Virtual Workstation on AWS. An Omniverse Virtual Workstation allows users the ability to create or provision a virtual machine with graphical capabilities with Amazon Web Services (AWS), eliminating the need to run Omniverse applications locally on an RTX-enabled desktop or laptop computer.


Infrastructure: Manually deployed using AWS console.
Services used:
1) Amazon EC2.
2) Amazon Certificates Manager.
3) Elastic Load Balancer (ELB).
4) NVIDIA Container Registry.
5) NVIDIA Enterprise Omniverse Nucleus packages
6) Nitro Enclaves Marketplace Subscription
7) Amazon Virtual Private Cloud (VPC).
8) Route53 as a DNS
9) AWS backup.
10) Reverse Proxy Server
11) Amazon S3
12) Amazon EBS
13) AWS Certificates Manager for Nitro Enclaves

Showbuilder

Project Name – Showbuilder

Project Scope – Creation of continuous integration and continuous delivery (CI/CD) pipeline that automatically builds and deploys a Java application to an Amazon Elastic compute cloud (EC2).

Infrastructures  – Manually deployed using AWS console.

1. Ec2 as a Backend server  (Production, development and staging servers).
2. VPC ( virtual private cloud) for production and staging environments.
3. AWS backup.
4. ACM for certification manager.
5. Autoscaling and Application load balancer for handling and managing traffic
6. RDS with MYSQL as a database engine.
7. S3 as a storage and backup.
8. Security groups for allowing particular IPs
9. Route 53 as a DNS.
10. Guard Duty, Inspector, WAF as a security tool.
11. Cloudwatch for monitoring resources.
12. AWS cloudfront and s3 bucket for static frontend hosting.

Sendtric

Project Name: Sendtric

Project Scope:
Sendtric Features · Reliable timers built within a robust, tested infrastructure · Optimised for fast loading times within your templates ·
In the project, we have migrated more than 8 servers from DigitalOcean to AWS EC2(redis or WordPress servers).
Load Balancer is also in use for managing the load balance between servers. For network and application security, we have used WAF with custom rules and Detective,AWS Inspector, AWS GuardDuty.

Infrastructure: Manually deployed using AWS console and Heroku.

Services used:
1) EC2 as a backend server
2) Autoscaling and Application load balancer for handling/managing traffic.
3) Postgre as a database engine on Heroku.
4) Route53 as a DNS
5) AWS backup.
6) Detective, Guard Duty, Inspector and WAF as security tools.
7) ACM from certificate manager.
8) Email from AWS Workmail.
9) Amazon Simple Email Service.
10) Security groups for allowing particular IP’s.
11)Separate VPC for production or staging environment.
12) Heroku.
13) set up Zendesk for customer support.
14)Cloudwatch for monitoring resources.

Scratchie

Project Name:  Scratchie 

Project Scope: Handing all the servers and all services hosted on AWS. Also Worked on Security. Installed WAF and Wazuh.

Infrastructure: Manually deployed using AWS console.

Services used:

1) EC2 as a backend server.
2) Virtual private cloud (VPC).
3) Route53 as a DNS.
4) WAF as a security tool.
5) Load balancer.
6)  RDS Mysql for the database.
7) Security groups for allowing particular Ips.
8) ACM.
9) Wazuh.
10) Openvpn.
11) AWS backup.

Robod

Project Name: Robod

Project Scope:  Created an AWS Managed Microsoft AD directory. AWS Directory Service creates two directory servers, one in each of the private subnets of your VPC. And deployed workspace, by using custom image which contains only the OS, software, Microsoft Active Directory (AD) as a managed service and settings for the Workspace. A custom bundle is a combination of both that custom image and the hardware from which a Workspace is launched.

Infrastructure: Deployed by using CloudFormation (Infrastructure as a code) on AWS.

Services used: 

1. CloudFormation stack for workspace deployment.
2. Workspaces with specific bundles.
3. Microsoft Active Directory (AD) as a managed service.

RIA

Project Name: RIA

Project Scope: Creation of continuous integration and continuous delivery (CI/CD) pipeline that automatically builds and deploys a Java application to an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on the Amazon Web Services (AWS) Cloud. On every new change applied to source code will deploy new Java application on EKS.

Infrastructure: Manually deployed using AWS console 

Services used: 

1. Secret Manager for storing secret value like Database password with rotation
2. Virtual private cloud (VPC) for the complete Infra of RIA
3. Cluster based Postgres RDS as a database
4. Virtual private network (VPN) to access private resources
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. Redis Cluster as a cache tool
8. Code pipeline for continuous deployment
9. EKS for application deployment
10.  WAF as a security tool
11.  API gateways
12.  Amplify for frontend web

Scratchie

Project Name:  Scratchie 

Project Scope: Handing all the servers and all services hosted on AWS. Also Worked on Security. Installed WAF and Wazuh.

Infrastructure: Manually deployed using AWS console.

Services used:

1) EC2 as a backend server.
2) Virtual private cloud (VPC).
3) Route53 as a DNS.
4) WAF as a security tool.
5) Load balancer.
6)  RDS Mysql for the database.
7) Security groups for allowing particular Ips.
8) ACM.
9) Wazuh.
10) Openvpn.
11) AWS backup.

Pectus Finance

Project Name: Pectus Finance

Project Scope: Deployment of AWS CloudFront with S3 origin to host static data, store secrets with amazon secret manager and attach SSL certificates using amazon certificate manager with CloudFront for secure deployment of CloudFront Distribution. CloudFront is Origin Access Identity (OAI), which restricts access to an S3 bucket and its content to only CloudFront and operations it performs.

Deployment of OpenVPN to provide secure connection to private resources like Database etc. OpenVPN Access Server, the OpenVPN self-hosted solution, simplifies the rapid deployment of a secure remote access solution with a web-based graphic user interface. 

Infrastructure: Deployed by using Terraform (Infrastructure as a code) on AWS.

Services used: 

1. Secret Manager for storing secret values
2. Aws CloudFront and S3 bucket for static frontend hosting 
3. S3 bucket for data storage
4. SSL certificates for secure connection
5. OpenVPN to access private resources

PaykickStart

Project Name: PaykickStart

Project Scope: A wallet based api is deployed in this project on AWS infrastructure. In the project we have deployed API as backend and CloudFront with S3 for frontend. In Frontend we have a lambda functions also attached for dynamic URL rewrite.

For backend we have deployed API in scalable architecture using EC2. Each time whenever there is spike in the website autoscaling is triggering and deploying new server to handle the request. Loadbalancer is also in use for managing the load balance between servers. For the network and application security we have used WAF with custom rules.

Infrastructure: Manually deployed using AWS console.

Services used:

1) Secrets Manager.
2) EC2 as a backend server.
3) Redis Cluster as a cache tool.
4) Autoscaling and Application load balancer for handling/managing traffic.
5) RDS with mysql as a database engine.
6) Queue server for handling queue.
7) Mongodb to handle database for Queue server.
8) Route53 as a DNS.
9) Aws cloudfront and S3 bucket for static frontend hosting.
10) AWS backup as a DR tool.
11) Guard Duty , Inspector , WAF as a security tools.
12) Cloudwatch and Wazuh as monitoring tools.
13) S3 as storage and backup 

ODE Infinity

Project Name:  ODE Infinity

Project Scope: Creation of continuous integration and continuous delivery (CI/CD) pipeline with Github action. Created AWS workspace through the bundle and set the environment for developers. Granted permission to Developers to access different environments.

Infrastructure: Manually deployed using AWS console.

Services used:

1) EC2 as a backend server.
2) Separate VPC for production or staging environment.
3) Route53 as a DNS.
4) WAF as a security tool.
5)  Code pipeline for continuous deployment.
6)  AWS workspace.
7)  RDS.

Mohamaad

Project Name: Mohamaad

Project Scope: Continuous deployment of AWS Code pipeline along with code build and code deploy for continuous deployment for source code. Every time pipeline is triggered bundles are created for workspaces using S3 bucket. Source code is stored in GitHub which is attached to the code pipeline. Storing secrets with amazon secret manager to access private resources.

Infrastructure: Deployed by using CloudFormation (Infrastructure as a code) on AWS.

Services used: 

1. CloudFormation stack for pipeline deployment.
2. Workspaces with specific bundles
3. Secret Manager for storing secret values
4. Code pipeline for continuous deployment

MDG (MedData Group)

Project Name –  MDG (MedData Group)

Project Scope – MedData Group, an IQVIA business, is the leading provider of Healthcare Professional (HCP) data fueling omnichannel digital targeting and engagement at scale. 

In this project we were handling all the servers for MDG, their service hosted on AWS and they are using various services of AWS like EC2 , VPC, RDS, Load Balancer, Autoscaling, Backup service, ACM etc. 

Infrastructures –  Manually deployed using AWS console.

1. Ec2 as a Backend server (Production, development and staging servers).
2. Autoscaling and Application load balancer for handling and managing traffic.
3. VPC ( virtual private cloud) for production and staging environments.
4. RDS with MYSQL as a database engine.
5. AWS backup.
6. ACM for certification manager.
7. Security groups for allowing particular IPs.
8. S3 as a storage and backup.
9. Guard Duty, Inspector, WAF as a security tool.
10. Cloudwatch for monitoring resources.
11. Route 53 as a DNS.
12. Amazon Active directory service.
13. Secret Manager for storing secret values like database password .
14. Virtual private network (VPN) to access private resources.

Make the dot

Project Name:  Make the dot

Project Scope: Deployment of Laravel  based application on AWS Linux machine. CI/CD is setup from bitbucket to aws servers using aws code pipelines. For website frontend its deployed on S3 with CloudFront. For backend Linux server is placed behind the Network load balancer and directly communicate with API gateways.

Infrastructure: Manually deployed using AWS console 

Services used:

1. AWS API gateway’s is setup for REST.
2. Virtual private cloud (VPC) for the complete Infra.
3. RDS postgres sql for the database. 
4. Virtual private network (VPN) to access private resources
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. AWS code pipeline is used for deployments

Marco

Project Name: Marco

Project Scope: 
Run a new keycloak container inside the isolated docker network.  The keycloak should also only be accessible through the reverse proxy. Keycloak operates within realms, which are isolated environments that contain users, roles, and applications, define user attributes, and enable multi-factor authentication.

Infrastructure: 
Keycloak is installed on Amazon Web Services. Keycloak is installed through Docker.

Services used: 
Used AWS(EC2) and Docker for Keycloak installation. Set up the Keycloak container inside an isolated Docker network and installed it through the Keycloak image from Docker Hub.

Instacuts

Project Name: Instacuts

Project Scope: Continuous deployment with AWS Code pipeline along with code build and code deploy for continuous deployment for source code. Every time pipeline is triggered an Amazon Elastic Container Service (ECS) is deployed using AWS Fargate, by using Fargate you don’t need to manage servers, handle capacity planning, or isolate container workloads for security. Fargate handles the infrastructure management aspects of your workload. You can schedule the placement of your containers across your cluster based on your resource needs, and availability requirements. 

ECS manages containers and lets developers run applications in the cloud without having to configure an environment for the code to run in. It enables developers with AWS accounts to deploy and manage scalable applications that run on groups of servers called clusters through API calls and task definitions. Amazon ECS is a scalable service accessible through the AWS Management Console. 

Infrastructure: Deployed by using Terraform (Infrastructure as a code) on AWS.

Services used: 

1. Secret Manager for storing secret value like Database password
2. Virtual private cloud (VPC) for the complete Infra of Instacuts
3. Mongodb to handle database through VPC peering 
4. Virtual private network (VPN) to access private resources
5. EC2 instances to access ECS containers
6. Elastic container registry (ECR) to store docker images
7. Application Load balancers to handle traffic of applications
8. Security groups for allowing particular Ips
9. ECS task definition
10.  ECS Clusters for micro services
11.  Aws CloudFront and S3 bucket for static frontend hosting
12.  WAF as a security tool
13.  API gateways
14.  Amplify for frontend web

Ideal Poultry

Project Name: Ideal Poultry
Project Scope:
Ideal Poultry is the largest supplier of backyard poultry including chickens, ducks, geese, turkeys, guineas, and bantams in the United States.In this project, we migrate their database (oracle database) and their website and customer portal to AWS.
In which are using Loadbalancer is also in use for managing the load balance between servers. For network and application security, we have used WAF with custom rules and Detective,AWS Inspector, AWS GuardDuty.
Cloudwatch is used for monitoring resources.

Infrastructure: Manually deployed using AWS console

1) EC2 as a backend server
2) Autoscaling and Application load balancer for handling/managing traffic.
3) Postgres as a database engine on Heroku.
4) Route53 as a DNS
5) AWS backup.
6) Detective, Guard Duty, Inspector tools.
7) ACM from certificate manager.
8) Security groups for allowing particular IP’s.
9)Separate VPC for production or staging environment.
10) Cloudwatch for monitoring resources.

Comit International

Project Name:  Comit International

Project Scope: Deployment of dot net application on AWS windows machine. CI/CD is setup from bitbucket to aws servers using Jenkins. Jenkin server is using multiple nodes for providing high availability of deployment. For website frontend its deployed on S3 with CloudFront. For backend windows server is placed behind the application load balancer for managing the load.

Infrastructure: Manually deployed using AWS console and Jenkin for CI/CD

Services used:

1. Jenkin credentials for storing secret variables.
2. Virtual private cloud (VPC) for the complete Infra.
3. RDS postgres sql for the database. 
4. Virtual private network (VPN) to access private resources
5. Application Load balancers to handle traffic of applications
6. Security groups for allowing particular Ips
7. Jenkin pipelines for deployment.

Buzznerd

Project Name: Buzznerd

Project Scope: Deployment of multisite using AWS EC2, handling most of the AWS services, Migration of sites from one region to another using WordPress migration plugins, managing domains on GoDaddy and Cloudflare, updated all the WordPress plugins and themes for all the Buzznerd domains and handled all the SSL certificates for secure connection using AWS certificate manager.

Infrastructure: Manually deployed using AWS console.

Services used:

1) EC2 as a backend server.
3) Redis Cluster as a cache tool.
4) Application load balancer for handling/managing traffic.
5) RDS with aurora as a database engine.
6) Certificate manager for SSLs.
7) Aws CloudFront for static frontend hosting.
8) AWS backup as an additional backup of database and EC2 instances.
9) CloudWatch as monitoring tools.
10) EFS with multiple instances.
11) Security groups for managing Ips.
12) WordPress plugins and themes.
13) GoDaddy and Cloudflare for managing domains.

Builder AI

Project Name –  Builder AI

Project Scope –  Builder.ai is an artificial intelligence-powered software development engine that helps businesses develop the applications they need, exactly how they need them, without requiring technical knowledge. Builder AI is a software development organisation who provides the platform for every size of companies. Builder AI has all types of clients whatever they are: Retail, Ecommerce, healthcare, Financial services, Construction, Travel Hospitality, Education, Media Entertainment etc. 

Technologies used in Builder AI –

Infrastructure – Builder uses Kubernetes, Azure, AWS to provide the platform for application developers. 70% of the infrastructure is on Azure Kubernetes and the rest of the infrastructure is on AWS.

For AKS deployment, Terreform has been used.
For AWS kubernetes has been setup on ec2 instances and has been automated with KOPS.

For Storage –    Minio and S3 has been used.

For DB –   POSTGRESQL, REDIS

Evolphin

Project Name:  Evolphin

Project Scope: Deployment of application on AWS ECS. CI/CD is setup from github to aws servers using AWS code pipelines. For website frontend and backend server is placed behind the application load balancer with Autoscaling for managing the load and traffic.

Infrastructure: Deployed using Cloudformation

Services used:

1. Jenkin credentials for storing secret variables.
2. Virtual private cloud (VPC) for the complete Infra.
3. RDS Mysql for the database. 
4. Virtual private network (VPN) to access private resources.
5. Application Load balancers to handle traffic of applications.
6. Security groups for allowing particular Ips.
7. Bluegreen deployments is used for the code deploy.