If you’ve deployed an application or service to the Amazon Web Service (AWS) cloud, you’ve probably made use of an EC2 instance. One of the decisions that you had to make before you could start a new instance, was which instance type to use. Choosing an EC2 instance type can be a complicated process. AWS organizes their instance types into instance families, and within an instance family, there are varying sizes from micro to 32xlarge.

In environments with large numbers of client machines, configuration management tools are often used to simplify and standardize the target state of each host in a seamless, automated and consistent manner. Software like CFEngine, Chef, Ansible, and others offer a high degree of granular control over software packaging and system configurations.

Deploying a stack into AWS is at the core of what Stackery helps you do. So much so that Stackery users deployed over 10,000 times last month! For the most part, this has been a manually executed process in our Web UI or command-line client. As teams grow and take on more work, fast and consistent deployments are key to scaling effectively. That’s why we’ve been working this year on continuous integration and deployment (CI/CD) features, tailor-built for serverless applications.

A lot has happened since VMworld 2019. OK, that might be the understatement of the year. But in that time, VMware Tanzu has evolved into a broad portfolio for building and modernizing applications. Operations teams now have what they need to build a more secure software supply chain. And, at the foundation, vSphere pros have a simplified way to get started with Kubernetes.

Incident retrospectives (or postmortems, post-incident reports, RCAs, etc.) are the most important part of an incident. This is where you take the gift of that experience and turn it into knowledge. This knowledge then feeds back into the product, improving reliability and ensuring that no incident is a wasted learning opportunity. Every incident is an unplanned investment and teams should strive to make the most of it.

Adopting Kubernetes and service-based architecture can bring many benefits to organizations – teams move faster and applications scale more easily. However, visibility into cloud costs is made more complicated with this transition. This is because applications and their resource needs are often dynamic, and teams share core resources without transparent prices attached to workloads.

Today we are pleased to announce the release of Puppet Remediate 1.4. This release brings together the dynamic vulnerability data and prioritization capabilities in Puppet Remediate with Puppet Enterprise’s industry-leading automation to help organizations improve their security posture and reduce the risk of security incidents.

Your team has decided to migrate your monolithic application to a microservices architecture. You’ve modularized your business logic, containerized your codebase, allowed your developers to do polyglot programming, replaced function calls with API calls, built a Kubernetes environment, and fine-tuned your deployment strategy. But soon after hitting deploy, you start noticing problems.

Catchpoint has always embraced new technologies and ideas. We offer a powerful monitoring platform with advanced features such as tracking digital performance from across the globe, capturing analytical data and the ability to get notified across various channels. With all these inbuilt features in hand, Catchpoint encourages its customers to build new monitors and integration that consumes monitoring data that are tailored to specific use cases.

Now you can go beyond measuring your bandwidth usage and regain control via Cloudsmith's new bandwidth controls for Entitlement tokens. You can craft tokens with individual usage limits using the UI, API, and CLI, allowing you to decide the exact level of usage for each token. Combining the new and existing limits for entitlement tokens, allowances are configurable to provide fine-grained control for any combination of properties.