New
articleMigrating a 20-Year WordPress Blog to Be Agent-Readytechnology bytesAGI Has Arrived. Now Give It a Simpler Problem.podcastEpisode 100: The Next Era of AI — From Agents to Enterprise IntelligencearticleMigrating a 20-Year WordPress Blog to Be Agent-Readytechnology bytesAGI Has Arrived. Now Give It a Simpler Problem.podcastEpisode 100: The Next Era of AI — From Agents to Enterprise Intelligence
Navveen Balani Making systems intelligent, efficient & responsible

Cloud optimisation is an continuous process to cut down on cloud…

Read on LinkedIn View as markdown

Cloud optimisation is an continuous process to cut down on cloud resources not being used and save on cloud cost substantially.

Here are some of the few basic optimization steps that you could follow for your cloud projects. The strategy works for across cloud providers.

Logs management - The storage for logs can grow exponentially, especially if you have central logging enabled. This is across environments (dev, test, prod etc). The first step is to get a tab of log storage being used and filter out logs not being used. For instance, apart from log levels, you can filter out default service logs. Each environment can have a different log optimization strategy. For instance, for Google Cloud you can exclude Google Kubernetes Engine container and pod logs based on GKE internal namespaces i.e knative-serving etc.

Network optimization - Keep a tab of network resources that are lying idle. For instance, Static IPs not associated with a resource adds to your cloud cost. Usually deleting a cloud resource using the static ip, does not delete the static ip and you many not realise this unless you look at the cloud bills in detail.

Idle resource management - Build out a calendar to automate shutting down non-production resources when not-in use (i.e based on non-office hours, weekends). For instance, you can also suspend/hibernate the VM, you will charged only for storage costs. Here is a #AWS reference on using #Lambda to turn on/off resources -https://lnkd.in/gGgVeDTk

Turn on cloud recommendations - Each cloud provider provides certain recommendations to identify idle resources, oversized VMs etc.. For instance, Google Cloud has a Recommender API that provides a dashboard for these details.

Delete unwanted backups and snapshots - Automated database backups, storage and VM snapshots all add to the cloud cost. Each environment (dev, test, prod) needs a different strategy. Identify snapshots not required and delete them periodically.

For more details and references, please visit my blog @ https://lnkd.in/gNsDgc7A

cloud