Cloud Cost Estimation with Infracost


Estimating costs can be a nightmare for many enterprises. Cloud cost estimation is important for organizations to plan their budget and forecast expenses accurately. It is essential to monitor and analyze cloud usage regularly to optimize cloud spending and avoid unexpected expenses.

This process is very time-consuming, so there was a need for change. With Terraform, you can easily estimate cloud costs by leveraging Infracost, and you can easily compare potential bills between different vendors.

Working with cloud providers and DevOps is all about speed, efficiency, and cost management.

Infracost is a tool that is used to figure out how much the cloud resources will cost.

What is Infracost?

Infracost is a super cool tool that lets you calculate the cost of your Terraform resources on AWS, GCP, or Microsoft Azure before you even hit deploy. This enables you to see cloud cost estimates for Terraform in pull requests.

Continue reading “Cloud Cost Estimation with Infracost”

Technical Roadblocks in Edtech: Strategies for Success

Knowing the benefits of cloud technology in education is one thing, but making it happen is a whole new ballgame.

A recent report predicts that the edtech industry will grow at a compound annual growth rate of 13.6% from 2023 to 2030.

That means — 

  • Increased interest to upskill in the comfort of your space and time. 
  • Higher demand for digital content with the benefit of a collaborative space for people of diverse educational backgrounds.
Continue reading “Technical Roadblocks in Edtech: Strategies for Success”

Lambda Function Trigger Enabled Using Code Pipeline.

Why are you doing a lambda function trigger enabled using pipeline?

For the AWS service to invoke your function directly, you need to create a trigger using the Lambda console. A trigger is a resource you configure to allow another AWS service to invoke your function when certain events or conditions occur. Your function can have multiple triggers. Each trigger acts as a client invoking your function independently, and each event that Lambda passes to your function has data from only one trigger. By using the code pipeline we enabled our lambda function trigger when we needed it.

What is the benefit?

People don’t need to add lambda function roles permission manually and don’t need to enable trigger manually because, after policy gets attached to the particular roles then we can enable trigger and it happens by using pipeline whenever we need every time automation happens.

Continue reading “Lambda Function Trigger Enabled Using Code Pipeline.”

AWS Transit Gateway – A Saviour for your Connections


As the Edtech industry continues to grow and evolve, the need for reliable and secure network infrastructure becomes imperative. Recently I got a chance to work on an Edtech project where we had to manage multiple Virtual Private Clouds (VPCs) and on-premises networks in order to accommodate their different environments – development, testing, and production.

Managing these networks separately was quite challenging and also made it difficult to troubleshoot any issues. This is where we thought of leveraging AWS Transit Gateway. In this blog, we’ll explore the capabilities of AWS Transit Gateway.

Transit Gateway can make your routing easy with the simple configuration just by making simple Transit attachments. See how it works.

What is Transit Gateway?

Transit gateways help you to connect multiple VPCs, multiple Transit Gateway, network Appliance, AWS Direct Connect Gateway, and VPN to transit Gateway. It helps you in making your routing flow understandable and easy to maintain. More over you can say it’s serverless of your VPC peering Service.

Continue reading “AWS Transit Gateway – A Saviour for your Connections”

Trigger Jenkins Job using AWS Lambda triggered by S3 Event

The problem that we faced:

There was a cron scheduled in our environment at a particular time which used to run at 8AM. This cron read data from the s3 bucket and used to succeed but failed when there were no objects present.

Problem this Integration solves:

  • Eliminates the need of keeping a scheduler in the system. Lambda will work as a Scheduler.
  • No manual intervention will be required in case the file from one service is delayed by a minute or an hour due to any reason. 
  • Data exchange and processing between teams become more efficient and less error-prone.
  • Eliminates the need of checking the presence of files on S3. It all gets automated.


  1. The object is uploaded to S3
  2. S3 event triggers a Lambda function
  3. Lambda starts Jenkins job using Jenkins API
Continue reading “Trigger Jenkins Job using AWS Lambda triggered by S3 Event”