DEV Community: Govardhana M K

5 Myths Causing Cloud Waste

Govardhana M K — Fri, 17 Mar 2023 04:10:47 +0000

I (actually) tried this with my 15+ clients so far.

More often than not, I was right about these myths.

Want to become a (much) better FinOps specialist or a cloud designer?

Here are my top 5 myths you should understand first:

Stable Cost ≠ Optimum Cost
Reservations are not limited to compute services
Orphan's are sleeper cells, don't take it light.
Prefer sustainable and cost effective approach than quick wins
Storage costs can surpass your imagination, keep a watch.

Hope you find the next few seconds useful! 🚀

Feel freel to follow me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more cool content related to cloud and devsecops !

Pick cost effective compute choice in 2 mins

Govardhana M K — Fri, 17 Mar 2023 04:04:11 +0000

Selecting a cost-effective instance in AWS may be complex for many, hence we see a lot of unnecessary on-demand instances usage.

I tried to simplify this exercise so that one can pick in 2 minutes.

Here I am sharing this with you all 👇

Feel freel to follow me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more cool content related to Cloud and DevOps!

How to detect a terraform drift and remediate it? A quick overview...

Govardhana M K — Fri, 24 Feb 2023 05:00:36 +0000

Drift is one of the most frequent and fundamental challenges of the infrastructure built with the terraform.

To understand drift better, let's walkthrough

[1] Desired State: It is the state of a resource that is configured in the resource block of your terraform (.tf) file.

[2] Current State: It is the actual configuration state of a resource that is in service.

Drift is nothing but the deviation between the desired state and the current state !!

Why does a drift happen?
Though it is recommended to centralize terraform to provision the infra, it doesn't stop an individual with the provisioning access to modify/remove the resources spun by terraform.

Some of the best practices to limit the drift:
🔷 Provide least privilege access to the users with permission boundaries
🔷 Integrate Terraform with version control tools (GIT) and CI/CD pipelines

How to detect a drift?
🔶 terraform State: The state file tracks the resources defined in the desired state and those that exist in the infrastructure (current state)

🔶 terraform plan –refresh-only: The refresh command to reconcile the real-world drift outside of terraform

Note:
This is a refresh-only plan, so Terraform will not take any actions to undo the detected drift.

How to remediate the drift then?
🔶 Running 'terraform apply' would reset the current state to the desired state.

Look at the below diagram to understand the sample architecture to detect the drifts and remediate them 👇

Follow: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more content related to Professional Development/ Cloud / DevSecOps / Infrastructure as Code / CyberSecurity

How do you detect secrets in you source code ?

Govardhana M K — Tue, 21 Feb 2023 06:02:32 +0000

Hackers Stole Source code and are inside Go Daddy for nearly 3 years !!

When this news broke out, Security became the Talk of the Tech World for the nth time again.

Most of the service providers came forward with statements, about how secure they are and the clients can sleep on them peacefully.

The truth is "We are as good as our weakest link".

I Know Security is a vast and deep subject, but it is a good time to revisit the basics and understand the secrets management in the source code.

🔷 What is a Secret?
In simple terms, anything that you would want to hide from others / the outside world.

🔷 Some of the common forms of Secrets are:
[1] Credentials
[2] Database connection strings
[3] API Keys and Tokens
[4] RSA Keys
[5] Certificates

When these secrets are accidentally / intentionally infused into the source code, the application and infra may be compromised for attacks.

🔷 Is my DevSecOps pipeline not good enough?
Secrets detection in the CI/CD pipeline may not be a good preventive measure, as we are running secrets scan and aspiring from redemption only after the secrets are infused. This is a poor reactive approach.

🔷 How can I make it Proactive then?
There are a few good resources like git leaks, git secrets, trufflehog to detect the secrets in the code and block the code commits.

❗ Remember, Security is everyone's responsibility. Any tool, automation, process, or framework is just an enabler. One shouldn't trade off security for faster delivery.

See the below diagram for the illustration of details. 👇

Follow Me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/
for more content related to Cloud / DevSecOps / Infrastructure as Code / CyberSecurity / Life

What are the different Route 53 Routing Policies?

Govardhana M K — Mon, 20 Feb 2023 05:43:09 +0000

Simple
Route traffic to a single resource. As simple as that !
Weighted
Specify how much % of requests a specific resource should handle.
Fun fact: if you specify the weight=0 for all the resources, traffic would be equally distributed.
Failover
Primarily used for the DR purpose, an active-passive setup tied up with the resource health checks. If the primary health check fails, requests are auto routed to the secondary.
Latency based
Redirect the users to the AWS regions with the least latency
Fun fact: need not be the region closest to the user always!
Geolocation
To route traffic based on the user location.
Matched users are routed to the pre-configured locations, the default location is mandatory in this policy to re-direct the users from the no-match locations.
Multi-Value Answer
when you want route53 to respond to DNS queries with up to 8 healthy records selected at random.
Note: multi-value by any means is not a replacement for a load balancer.
Geoproximity
Shifts traffic based on bias.
To allow more traffic (bias range: 1 to 99)
To shrink traffic (bias range: -1 to -99)

The diagram below shows all 7 available Route 53 Routing Policies.

Feel freel to follow me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more cool content !

How to set up a real-time leaderboard for an online gaming application?

Govardhana M K — Mon, 20 Feb 2023 04:56:44 +0000

AWS Elasticache is an in-memory database that provides high performance with low latency. Elasticache for Redis would be the ideal solution for this scenario.

Redis sorted sets are used for computationally complex use cases like gaming leaderboards and it guarantees:

Uniqueness
Element ordering
Real-time re-ranking of new elements

Salient Features of Elasticache-Redis:

Auto-Failover capability / Multi A-Z
Seamless scaling
High Availability with Read Replicas
Backup and restoration

Note: Redis is not suitable for multi-thread architectures.

See the below diagram for the sample architecture and "how it works" details.

Feel freel to follow me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more cool content !