Among all the new features and services that AWS announced during the re:Invent 2020, my favorites were definitely the AWS Lambda updates. And there were many! For example, your code execution is no longer rounded up to the nearest 100ms of duration for billing — you are now billed on a per millisecond. On top of that, AWS increased the Lambda’s memory capacity to 10 GB, and correspondingly the CPU capacity up to 6 vCPUs.

There is no doubt that organizations have a difficult task to address the current requirements for building and managing APIs, especially if they don’t use tools like API Management. APIs require up-to-date and strong documentation, increased security levels, comprehensive testing, routine versioning, and high-reliability to be appropriately utilized.

When you’re troubleshooting an app or a deployment, every second counts! Cloud Logging helps you troubleshoot by aggregating logs from across Google Cloud, on-premises or other clouds, indexing, aggregating logs into metrics, scanning for unique errors with Error Reporting and making logs available for search, all in less than a minute. And now, we’ve built two new features for streaming logs to give you even fresher insights from your logs data.

Amazon DocumentDB is a managed MongoDB-compatible database service provided by AWS. It provides the database in clusters, with multiple instances, for high-availablity. To help with cost-reduction strategies, AWS allows DocumentDB clusters to be stopped and restarted. While the cluster is stopped, you’re not charged. So it’s a great candidate to shut off overnight and on weekends if it’s not needed.

When we talk about going Cloud-Native we often think about Microservices as well, probably because that’s where the actual innovation, time, cost-saving, and better utilization of resources happen. And CloudHedge is keenly focused on helping enterprises to bring the benefits of containers to traditional legacy business applications that are run on a widely used operating system: AIX!

Happy New Year everyone! We are thrilled to be starting 2021 with some exciting news. Come February 2nd, we’ll be kicking off Azure Management Talk, a bite-sized webinar series with a focus on all things Azure management. Azure is fast-evolving, and often, it can get quite complicated. With so many things to learn and not enough time, the huge swathes of learning resources available online can quickly get overwhelming.

Increasingly, we are seeing on-prem workloads being moved onto the cloud. Elasticsearch has been around for many years with our users and customers typically managing it themselves on-prem. Elasticsearch Service on Elastic Cloud — our managed Elasticsearch service that runs on Amazon Web Services (AWS), Google Cloud, and Microsoft Azure across many different regions, is the best way to consume the Elastic Stack and our solutions for enterprise search, observability, and security.

Continuous integration and deployment (CI/CD) processes are becoming the standard for many organizations operating in the cloud—including many Spot by NetApp customers—with Jenkins as a core tool for building, testing and deploying code through CI/CD pipelines. Spot has had an integration with Jenkins since our early days, allowing our users to configure Elastigroups managed by Jenkins and deploy jobs running on spot instances.

In December, AWS announced the new VPC Reachability Analyzer tool. Using this tool, AWS can analyse the paths within your VPC to determine whether the various components in your VPC can communicate with each other or not.

We all know that debugging serverless is time-consuming and hard and that AWS Console doesn’t make it much easier. CloudWatch isn’t quite known for its ease of use. Why? Well to start with, it has suboptimal search features, logs scattered across multiple buckets and groups, little visualization capability, and no structure of Lambda function invocations.