TruMedia is a web development agency focused on Multimedia content with multiple customers in the Cloud of AWS. The company is focused on development and customer satisfaction. They employ advanced AWS technologies to deliver content efficiently to their clients, but they weren’t aware of AWS billing spikes.  The Objective:1. Reduction of AWS Costs.2. Increment visibility of AWS Billing.3. Replacement of traditional services with high-performance services, increasing the speed.4. Management of their DevOps department (which they didn’t have). Our implemented service:After launching our Server and AWS discovery process, we identified and mapped redundant resources and wrote a plan to mitigate this concern.Some activities to set up were automated scripts to stop instances when not needed and identify and replace instances with Reserved instances. The agency was using Load balancers inside Ec2 instances. We switched to Elastic Load Balancer (ELB), which costs $18-$20, and the GB is .008 of data proceeded, reducing by 65%.We identified other potential reductions with our technical checklist that overall lowered the billing by 40%.Our team also made additional activities to increase the speed of TruMedia’s site. We replaced the traditional services they had with high-performance services. By tagging all the instances; adding AWS Auto Scaling and limit provisioning; adding CDN and reducing bandwidth towards Amazon S3; and much more.In other areas, we took ownership of all the AWS management to implement DevOps practices and stabilize an EC2 instance that was facing a bottleneck/Memory leak in one of their PHP Laravel apps. We provided 24/7 support by frequently monitoring, proactively finding problems, and leveraging new AWS technologies for its customers. Result:We were able to reduce its AWS Cloud spending by 40%, increasing the firm revenue and helping them to focus on its development and creativity to design web products more efficiently.

The challenge:The client needed to improve the way code was deployed to the application so that this process could be done faster and securely across multiple environments.Even though some essential tools were previously used, such as CodePipeline and CodeBuild, the process was still incomplete and sometimes was stuck, making workflow unreliable.Besides this, the fact of applying a change on the CloudFormation stacks had a complicated debugging process to fix the templates when required. Sometimes, the deployment process was stuck or incomplete, and the developer team had problems defining which feature they were testing on the QA environment. Our implemented service:We implemented AWS CloudFormation as Infrastructure as Code solution. Then, our team created a CI/CD pipeline for infrastructure and code. And we also worked on the implementation of AWS ECS for container orchestration. Results:AWS CloudFormation helps you model and provision AWS and third-party resources in your cloud environment.This allows you to use programming languages to model and provision, secure and automatically, the resources needed for your applications across regions. Reduce time and optimize the deployment of your services without a problem. The client now has a cloud-native environment with the use of microservices.

The challenge:The client owned multiple AWS accounts, each one representing an environment; the different accounts were Production, Staging, five testing accounts, and one environment per developer.They needed to perform maintenance on the infrastructure for all environments used by their developers on different AWS accounts. Also, they wanted to completely remove the use of EC2 instances, so going serverless was one of their main concerns for them. Our implemented service:We implemented AWS CloudFormation as Infrastructure as Code solution and created a CI/CD pipeline for infrastructure and code. We also worked on the integration of AWS Fargate as a serverless solution. Results:- ECS Fargate was implemented for the php services.- CI/CD was implemented for infrastructure, making use of Bitbucket Pipelines and inf.sh.- CloudFormation was configured to provide IaC, simplifying the maintenance of infrastructure.- With the help of CloudFront, the speed of the application improved.