In a recent post by the Splunk Threat Research team, we addressed permanent and temporary token/credential abuse in AWS and how to mitigate credential exposure. With 94% of Enterprises using a cloud service, and some using at least five different cloud platforms, it’s imperative to stay ahead of threats across multicloud environments. Let’s now turn our attention to Google Cloud Platform (GCP) and how to detect and mitigate OAuth Token Abuse.

We are excited to announce the preview of the Splunk extension for AWS Lambda, a new way to integrate monitoring and observability in Lambda environments. Splunk is already the pioneer in providing real-time observability into serverless environments. With the Splunk extension, capturing and ingesting observability data become seamless without the need to instrument function code.

Any application built today is expected to be highly responsive, highly available, and required to adapt to enormous changes in real-time at peak business hours, store ever-increasing volumes of data, and make that stored data available for users a fraction of seconds. To achieve such low latency and high availability, you need to deploy these applications’ Instances in data centers that are close to their users.

The Console Connect ecosystem is rapidly expanding. To help you keep up-to-speed, each month we are bringing you updates on all our latest data centre, cloud and SaaS interconnect locations, as well as introducing you to some of our newest ecosystem partners. This month, we’ve extended your reach even further! We have on-boarded over 40 data centres and over 20 new SaaS PoPs! Here is the full list of our new locations and clouds.

Serverless computing simplifies IT operations by delegating infrastructure setup, configuration, provisioning, and management to a cloud vendor.

There is a growing ecosystem of vendors that are helping AWS customers gain better observability into their serverless applications. All of them have been facing the same struggle: how to collect telemetry data about AWS Lambda functions in a way that’s both performant and cost-efficient. To address this need, Amazon is announcing today the release of AWS Lambda Extensions.

Every decision that an engineer makes in the cloud impacts cost. Yet we know that engineers aren’t cost experts, and many worry that asking them to care about cloud cost will slow them down and distract them from delivering customer value. Top cloud-native companies dedicate entire teams of engineers to build custom tools to measure unit cost and deliver cloud cost to engineering teams. But I’m guessing you don’t have eight engineers you can spare to build internal cost tools?

Modern applications are platform-agnostic which means that they can run seamlessly in hybrid and multi-cloud environments. Google Anthos, released in 2019, is an application management platform that allows developers and IT to build and run applications across on-prem and public clouds (including competing cloud providers). Hosted on Google Kubernetes Engine (GKE), Anthos helps organizations create enterprise-grade containerized applications that are secure and portable across multiple venues.

We are excited to announce a new integration to help developers add partner solutions to their serverless applications. AWS recently released Lambda Extensions to allow Lambda to augment the Function invocation lifecycle. Extensions from AWS, AWS Lambda Ready partners, and open source projects are useful for a wide range of use cases. For example, Extensions simplify a development workflow by automatically instrumenting Lambda functions or deploying operational tools without needing code changes.

Welcome to the final installment of our Complete AWS Lambda Handbook series! Given Lambda is often the central point for many serverless applications, we wanted to make sure we didn’t skip or breeze past any part. In this episode, we’re looking at some limitations and difficulties using AWS Lambda and how to overcome them, and the importance of monitoring for performance and failure remediation.