Operations | Monitoring | ITSM | DevOps | Cloud

A few months ago, I wrote an article about a serious outage of Azure and how eG Enterprise enabled us and our customers to understand the issue long before Microsoft had confirmed the issue and updated their service status pages.

When it comes to deploying web applications, two popular options are Heroku and AWS Elastic Beanstalk. While both services aim to simplify the deployment process, they differ in several key areas. In this article, we'll compare Heroku and AWS Elastic Beanstalk and discuss the pros and cons of each service.

Since the very first version, Epinio has made use of an internal S3 endpoint to store the user’s projects in the form of aggregated tarballs. Those objects are then downloaded and staged by the internal engine’s pipeline and, finally, they are deployed into the Kubernetes cluster as consumable applications. Epinio makes use of S3 as an internal private service. In this scenario, S3 can be thought of as an internal ephemeral cache with the purpose of storing temporary objects.

Virtual machines (VMs) have been around for quite some time now and have become a cornerstone of modern-day IT infrastructure. They provide a convenient way to run multiple operating systems on a single physical machine, allowing users to consolidate their hardware and save costs. However, as VM technology has evolved, newer versions of VMs have been introduced, such as generation 1 and generation 2 VMs.

AWS Marketplace + FireHydrant: your path to easier compliance, consolidated spend, and faster procurement.

With the dawn of microservices and serverless, event-driven architectures have become the way to go when building a new system in the cloud. This approach has allowed for greater scalability, as the system can easily adapt and respond to changes in traffic or demand without having to overhaul the entire architecture. Additionally the Event-driven approach means your application is mainly concerned with routing event data to the right services.

We have a couple of internal websites hosted on Azure. Websites that require authentication and should only be accessed from our IP. This can easily be configured using Access Restrictions in Azure. But when doing so, you exclude the dynamic IP range for Microsoft-hosted Azure DevOps build agents. In this post, I'll show you how we set up deployment to the Access Restricted websites with a bit of PowerShell magic.