13 docs tagged with "agents_integrations"

The Cloudwatch agent will run in your EC2 instances to collect metrics and send them to nOps.

The Cloudwatch agent will run in your EC2 instances to collect metrics and send them to nOps.

If you have previously installed the container-insights (nops-k8s-agent) and want to migrate to the unified installation of agents, please refer to this migration guide.

nOps supports sending alerts directly to Slack and Email.

This architecture provides a scalable and automated solution for managing IAM roles in Amazon EKS clusters across multiple AWS regions. It leverages AWS Lambda to dynamically handle the creation, update, and deletion of IAM roles associated with the service account used by the nOps Agent Stack. These roles ensure that the agents have the necessary permissions to gather data and upload it to an Amazon S3 bucket for Container Insights. Additionally, the roles will also have permission to subscribe to an SQS queue that exists in the nOps AWS account, enabling real-time data fetching from the Kubernetes API for the Cluster Dashboard.

EventBridge Integration makes it easier for nOps to automate workflows in the client’s environment.

Introduction

Integrating Jira into your cloud optimization workflow has never been easier!

If you're migrating from a previous installation of the Container Insights Kubernetes agent (originally installed using a bash script), the new installation method involves updating the CloudFormation Stack. This update creates a Lambda function that manages the creation and update of the IAM Roles for Service Accounts (IRSA) required by the agent to push metrics to the S3 Bucket associated with your AWS account. Additionally, you'll need to run a cleanup script to remove the old Helm release and delete any unused namespaces from the previous installation.

You can use your PagerDuty service to receive the security audit trail related to security best practices from nOps. These security best practices are implemented using different nOps rules. Whenever there is a change in violations, a security audit trail is generated. Follow the steps below to integrate PagerDuty with nOps now.

You can use AWS Secrets Manager integration with External Secrets Operator to create/sync the API Keys secret in your EKS cluster.

You can use AWS Secrets Manager integration with External Secrets Operator to create/sync the API Keys secret in your EKS cluster.

Configuring Webhook Integrations for 3rd party apps