Operations | Monitoring | ITSM | DevOps | Cloud

AWS CloudFormation Modules, now available for public use through the AWS CloudFormation Public Registry, are a huge step forward for enterprise IT teams to create large manageable Infrastructure-as-Code (IaC) practices around CloudFormation. We’re excited to support the launch today with our own Bastion module. Unsure what Modules are? Read on.

Simply open up Cloud Storage Manager, then go to the FILE and then SEARCH. Now the Search window will open up in Cloud Storage Manager. Choose the category of the item you want searched for, either an Azure Storage Account, Container, or a Blob can be searched. Type in the name of what you want to search for in the SEARCH box and then finally choose if you want an Exact Match, Starts with, Ends with or Contains, then press Search.

Many organizations have made the shift to the cloud in recent years, and many more are planning to or are just starting their cloud migration journeys now. However, some organizations struggle to realize value from this move. The benefits of cloud are clear: it’s flexible, scalable, and has a low cost of entry. But cloud can also bring complexity—creating new interdependencies, more services to manage, and more data and signals to monitor.

I hate reinventing the wheel once I find a good setup. On top of that, I dislike searching for all the links I used to come up with the “ultimate setup” for different services. So, I decided to outline for myself (and for you of course) my default setup when I deploy on Elastic Cloud to set myself up for success and automate insight for the future. Most of my setup steps make monitoring accessible or automate various warnings to myself.

The pandemic upended business for many or at the very least cast a grim shade of uncertainty, so, as many took to working from home, they also were commissioned with cutting waste. Among the biggest sources of misspend in 2020 – cloud services. And remote work may have actually spurred the problem, as organizations migrate more applications to the cloud to support these workers.

When building a microservices system, configuring events to trigger additional logic using an event stream is highly valuable. One common use case is receiving notifications when errors are seen in one of your APIs. Ideally, when errors occur at a specific rate or frequency, you want your system to detect that and send your DevOps team a notification. Since AWS APIs often use stateless functions like Lambdas, you need to include a tracking mechanism to send these notifications manually.