The previous chapter in this WhiteHat Security series discussed Codebase as the first step of the Twelve-Factor App and defined a security best practice approach for ensuring a secure source control system. Considering the importance of applying security in a modern DevOps world, this next chapter examines the security component of step two of the Twelve-Factor methodology. Here follows some actionable advice from the WhiteHat Security Addendum Checklist, which developers and ops engineers can follow during the SaaS build and operations stages ...
SignalFx announced support for Amazon Elastic Container Service for Kubernetes (Amazon EKS).
SignalFx’s support for Amazon EKS furthers the company’s commitment to empowering its customers with real-time visibility into any cloud and container environment.
SignalFx has been a provider in Kubernetes monitoring for several years and has natively supported Amazon Elastic Compute Cloud (Amazon EC2) Container Service (Amazon ECS) as part of its collaboration with Amazon Web Services (AWS). Supporting Amazon EKS specifically will make it easier for Kubernetes users to monitor and manage their container environments and optimize their cloud resources and costs.
SignalFx was a launch company for the AWS Serverless Application Repository in 2017 and provides extensive support for AWS Lambda. This means customers using both containers and functions on AWS can have an end to end real-time monitoring solution for their entire environment. Furthermore, the SignalFx AWS Cost Optimizer provides direct visibility into the cost and resource allocation of both reserved and on-demand Amazon EC2 instances.
“With more than 150 integrations for technologies and applications across the cloud landscape, SignalFx provides enterprises with the real-time visibility tools they need to innovate rapidly and be reliable in today’s hyper competitive market,” said Karthik Rau, co-founder and CEO of SignalFx. “Supporting Amazon EKS makes it even easier for companies to manage their applications’ performance in Kubernetes environments and maximize the benefits of adopting containers at scale.”