Temperstack
Main WebsiteFeaturesPricingBlogAbout usRequest a Demo
  • Overview
    • What is Temperstack?
    • Use Cases
  • User Managment
    • Getting started as Admin
      • Inviting Users
      • Mapping multiple services to a Team
      • Single Sign-On (SSO)
      • Customising ALCOM Audit & scanning
    • Getting Started as a User /Responder
    • Managing profile & contact details
  • Integrations
    • Integrating your Observability tools
      • Setting up AWS Integration
        • Multiple AWS Account Integration
        • IAM Setup Guide
          • Creating IAM User: Temperstack with Policy
          • Creating IAM Role: Temperstack with Policy
      • Setting up Microsoft Azure Integration
        • Creating Access for Temperstack in Azure
      • Setting up Google Cloud Platform Integration
        • Creating Access for Temperstack in GCP
      • Setting up Datadog Integration
        • Creating Access for Temperstack in Datadog
        • Managing resources with Datadog
      • Setting up NewRelic Integration
        • Creating Access for Temperstack in NewRelic
        • Managing resources with New Relic
      • Setting up Splunk Integration
        • Creating Access for Temperstack in Splunk
        • Managing resources with Splunk
      • Setting up Appdynamics Integration
        • Creating Access for Temperstack in Appdynamics
        • Managing resources with Appdynamics
      • Setting up Dynatrace Integration
        • Creating Access for Temperstack in Dynatrace
        • Managing resources with Dynatrace
      • Setting up Oracle Cloud Infrastructure
        • Creating Access for Temperstack in OCI
    • Integrating Custom Alerts & Other Alerting sources
      • Webhook Integration
      • Ingesting Emails as alerts
      • Integrating alert listeners from other observability tools
  • Alert routing & Response Managment
    • On-call scheduling and Escalation Policies
    • Setting up Services
    • Alert notification channels
      • Integrating Slack channels
      • Integrating MS Team
    • Mapping resources to Services
      • Rule based resource to Service Mapping
      • Using AI suggested mapping rules
    • Testing Alerting and Notifications
    • Responding to Alerts
  • Monitoring
    • Setting up and maintaining Comprehensive alerting
      • Alerting Templates- metrics & customisation
      • ALCOM and identifying monitoring gaps
      • Programmatically setting up missing alerts in your Observability tool
      • Alert noise Reduction & Optimisation
  • Uptime Monitoring
    • Real time Availability Monitoring
  • Incident analysis & communication
    • External and Internal service Status Pages
      • Instruction to migrate subscribers from Statuspage
  • AI-Powered Issue Resolution
    • AI powered contextual Runbooks
    • Incident command - alert grouping by incident
    • AI Powered Root cause Identification
  • Reporting & Governance
    • Temperstack Dashboard
    • SLO Dashboard
    • MTTA MTTR
  • Billing & Help
    • FAQs
    • Support
Powered by GitBook
On this page
  • AWS resources
  • Installation Process
  • Frequently Asked Questions
  1. Integrations
  2. Integrating your Observability tools

Setting up AWS Integration

A step-by-step guide of how to connect to your AWS account and give Temperstack permissions

Last updated 5 months ago

Temperstack looks for alerts across all of your AWS services, including EC2, RDS, ELB, Lambda, ECS, API Gateway, DynamoDB, S3, SQS, and more.

Requirements

Installing the Temperstack AWS integration requires either an active trial or paid account to get started. You will also need to meet the following requirements:

  • Access to create IAM policies and users in your AWS account

For Key-based Integration, refer to the link provided below:

For Role-based Integration, refer to the link provided below:

Installation Process

  1. Log in to Temperstack and navigate to the Integrations page via Admin > Integrations

3. On the integrations page click on AWS

  1. Select whether it should be Key-based integration or Role-based integration and follow the instructions provided below.

  1. After entering the required details, click on Test Connection. This will verify your credentials to fetch your EC2 instances.

  1. The product takes some time to scan through AWS and give an Alert comprehensiveness score (ALCOM) score

  1. On the integrations view you will see the AWS icon annotated with "Integrated"

Frequently Asked Questions

FAQ 1. Does Temperstack modify my AWS resources?

The AWS integration primarily requires read-only access to your AWS infrastructure to retrieve necessary data. However, write permissions are required for specific actions, such as configuring SNS topics and CloudWatch alarms for setting up alerts.

FAQ 2. Which AWS regions are supported?

The AWS integration currently collects data in the following regions

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • eu-central-1

  • eu-west-1

  • eu-west-2

  • eu-west-3

  • ap-northeast-1

  • ap-northeast-2

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • sa-east-1

FAQ 3. Can I have multiple AWS integrations?

Yes, Temperstack supports multiple AWS accounts, enabling centralized management of resources across different accounts. This feature improves visibility, simplifies resource allocation, and enhances security by applying consistent policies across accounts. It also ensures scalability, allowing for easy integration of additional accounts as your infrastructure grows.

Refer this page on how to setup multiple AWS account:

Resource types available for auto Alert setup

First follow the instructions in the to create an IAM Policy and User to give Temperstack programmatic access to your AWS account. Keep track of the Access Key ID and Secret access key in the final step of the create user process.

IAM Setup Guide
Creating IAM User: Temperstack with Policy
Creating IAM Role: Temperstack with Policy
IAM Set Up guide
Multiple AWS Account Integration
AWS resources
AWS
AWS Elastic Compute Cloud (EC2)
AWS Relational Database Service (RDS)
AWS Elastic Load Balancer (ELB)
AWS Application Load Balancer (ALB)
AWS EC2 Auto Scaling
AWS Simple Queue Service (SQS)
AWS Simple Email Service (SES)
AWS DynamoDB
AWS CloudFront
AWS Elastic Container Service (ECS)
AWS Elastic Kubernetes Service (EKS)
AWS Kinesis
AWS Lambda
AWS MQ | RabbitMQ |ActiveMQ
AWS Kafka | Kafka Broker
AWS ElastiCache - Redis & Memcache
AWS DMS
AWS Cloudfront
AWS API Gateway
Admin > Integrations
AWS > Click on Next button
Selected - Role-based integration
Selected - Role-based integration
ALCOM Score
admin-> Integrations
AWS Elastic Compute Cloud (EC2)
AWS Relational Database Service (RDS)
AWS Elastic Load Balancer (ELB)
AWS Application Load Balancer (ALB)
AWS EC2 Auto Scaling
AWS Simple Queue Service (SQS)
AWS Simple Email Service (SES)
AWS DynamoDB
AWS CloudFront
AWS Elastic Container Service (ECS)
AWS Elastic Kubernetes Service (EKS)
AWS Kinesis
AWS Lambda
AWS MQ | RabbitMQ |ActiveMQ
AWS Kafka | Kafka Broker
AWS ElastiCache - Redis & Memcache
AWS DMS
AWS Cloudfront
AWS API Gateway