It’s great to see that a team at AWS has made COVID-19 datasets readily available to the public (read here for detailed information). The datasets are accessible from a public S3 bucket to anyone with an AWS account. For healthcare providers and payers that want to begin or enhance their analytical efforts around the coronavirus crisis, the COVID-19 data lake can be a useful accelerator.
There are hundreds of monitoring products in the marketplace that cover monitoring from enterprise scale to small and medium businesses. How can a monitoring system help your team? It is imperative that an IT team know the state of the environment and quickly respond to issues.
Most IT teams have a monitoring system, or several monitoring systems. These systems monitor applications, services, operating systems, network devices, and technology infrastructure.
Most IT environments have a requirement to keep systems up to date on vendor patches. Typically, in on-premise environments there are dedicated systems that scan and update patching targets. The patching targets in this case are the operating systems of servers or virtual machines, including Windows servers and many variants of Linux. Examples of this kind of software include Microsoft Windows Server Update Services, Red Hat Satellite, IBM BigFix, or Ivanti. This blog specifically references operating system patching.
The term “technical debt” originated from Ward Cunningham, one of the authors of the Agile Manifesto. He once said that some problems with code are like financial debt. Technical debt is incurred by completing work in a swift way with some known and/or unknown gaps, which is like a financial debt. Like a financial debt, the technical debt results in interest payments, which come in the form of the extra effort that technology professionals must do in future work because of design choices or shortcuts. We can continue paying the interest, or we can pay down the principal by correcting or polishing the hasty work results into more refined results. Technical debt is usually unintentional, but similar to accrued interest, the impact often increases over time.
Infrastructure-as-Code (IaC) is the practice of defining templates that can be used to provision technology infrastructure to support software and applications. Traditionally, physical hardware configuration of network switches/routers, servers, network-attached storage, etc. has been a time-consuming and difficult task that not only was prone to human error—but was also not easily repeatable. Even after the advent of virtualization and the automated software configuration revolution, technology infrastructure was still built on a backbone of (usually) manually-managed hypervisors overseen by IT operations staff.
Impact Makers is very excited to announce that we recently achieved Advanced Consulting Partner status with Amazon Web Services (AWS). For reference, AWS is a cloud computing platform that offers over 100 services, and the Amazon Partner Network (APN) is a global partner program, focused on helping professional services firms build successful AWS-based practices. This achievement reinforces our success building a strong AWS-based business, and it further supports our AWS cloud services expertise and credibility.
Amazon Web Services (AWS) published a case study on Impact Makers’ project with MedStar Health. Impact Makers used AWS to support a new digital presence for MedStar. The collaboration with AWS provides a state-of-the-art platform that is highly secure, scalable and cost-effective.