Operations | Monitoring | ITSM | DevOps | Cloud

A multicloud strategy is a necessity for modern businesses, as the recent AWS outages made clear, but managing this infrastructure remains a huge challenge. Infrastructure management teams have long struggled to juggle diverse technology solutions, policies and services to get access to a point-in-time view of their resources. The result is either waste through overprovisioning or huge overheads for nitpicking manual management and repetitive tasks.

The key challenge with modern visibility on clouds like AWS is that data originates from various sources across every layer of the application stack, is varied in format, frequency, and importance and all of it needs to be monitored in real-time by the appropriate roles in an organization. An AWS centralized logging solution, therefore, becomes essential when scaling a product and organization.

Any new technological breakthrough tends to be greeted by two opposing factions. On one hand, you have promoters, for whom this technology is a panacea, the cure for every ailment plaguing the current environment.

Every Lambda function comes with 512MB of ephemeral storage in the shape of a /tmp directory. This storage space can be reused across multiple invocations for the same instance of a Lambda function. Each instance of a function has its own /tmp directory and data is not shared amongst different instances of a function.