We’re extremely happy to announce that Torq has joined the Cloud Security Alliance (CSA), the world’s leading organization dedicated to defining and raising awareness of best practices to help ensure a secure cloud computing environment. The CSA has more than 80,000 members worldwide and has been endorsed by the American Presidential Administration, which selected the CSA Summit as the venue for announcing the federal government’s cloud computing strategy.

The main street in my town is mostly lined with mom-and-pop shops, and I love to support these businesses. Large online retailers keep making it harder for these stores to compete, so I think it’s important to keep doing business with them when I can. Lately, it’s been interesting to see that these mom-and-pop shops increasingly have something in common with the largest online retailers: They’re reliant on the internet to deliver their goods and services to consumers.

A good chunk of your Amazon Web Services (AWS) public cloud spending goes to the Amazon Elastic Compute Cloud (Amazon EC2) service. Because it is the default compute service on AWS, Amazon EC2 is key to building, running, and scaling your AWS-based applications. That also means Amazon EC2 pricing has a tremendous impact on your AWS budget. Understanding how the EC2 billing model works will help you control and optimize your AWS spending.

Understand how to calculate the composite reliability of your cloud infrastructure to help design Cloud architectures with an optimal SLA.

This blog will discuss running serverless containers in AWS EKS with Fargate. Why and how we can use this configuration and provides a working example of how to use AWS EKS with Fargate. Recently, a customer reached out with an interesting request. They wanted us to run containers in serverless mode with AWS EKS. Their intention was to use Kubernetes features and run containers in serverless mode. Side note: in EKS you should manage NodeGroups and pay for it.

Cloud 66 turned ten this year! While this is a big deal for us, I understand that it is not important to you. After all, who cares if a company turns 10, right? So, why am I writing about it, and why do I think you might also be interested in this? Since we started Cloud 66 in 2012, we and the world around us have changed significantly. We are no longer a scrappy startup with only big dreams to keep us going. Today, hundreds of customers rely on us daily for critical parts of their business.

Your software development team has an enormous number of tools available to them. Some older tools are being used in new ways, which has inspired the creation of more new tools to choose from. For example, JavaScript has grown from a language used to add interactivity on websites to a full-stack language for both frontend and backend needs. JavaScript has paved the way for Express, Nest.js, and many others.

With AWS re:Invent right around the corner, infrastructure has been top of mind at Cortex. Earlier this year, we launched our revolutionary Resource Catalog, which integrates with AWS accounts to automatically ingest all infrastructure components, from s3 buckets to lambdas. Through this process, Cortex allows you to track everything in a single place, while augmenting the information that already exists in AWS. The Resource Catalog surfaces live information about your infrastructure assets.

In-context dashboards for Google cloud storage, customizable, create alert, view logs for better storage system insights at project level and bucket level.