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
  1. Integrations
  2. Integrating your Observability tools
  3. Setting up AWS Integration

Multiple AWS Account Integration

Last updated 5 months ago

Setting up multiple AWS accounts in Temperstack is now easier and faster than ever. It allows you to efficiently manage multiple AWS accounts within a single platform, saving time and ensuring seamless operations. With enhanced flexibility and security, this feature is designed to streamline account management and scale effortlessly with your growing infrastructure.

  1. Navigate to the Integration Section: Go to Dashboard > Admin > AWS in your Temperstack account.

    • Here, you’ll find the credentials for the currently integrated AWS account.

    • You’ll also see a separate card for integrating additional AWS accounts.

  2. Select Integration Type: When adding a new account, choose between Role-based Integration or Key-based Integration, depending on your requirements.

    • What to Choose?

      • Key-Based Integration: Choose this method if you require direct access using an access key and secret key.

      • Role-Based Integration: Opt for this if you want to enhance security and avoid sharing access keys by using roles and policies.

  3. Follow the Setup Steps:

    • For Key-Based Integration, follow these steps in your AWS account:

    • Creating IAM User: Temperstack with Policy

      • Generate an access key and secret key.

      • Input the credentials in Temperstack's integration card.

    • For Role-Based Integration, follow these steps in your AWS account:

    • Creating IAM Role: Temperstack with Policy

      • Set up an IAM role with the required policies.

      • Copy the Role ARN from AWS and paste it into Temperstack during integration.

  4. Complete the Integration:

    • After entering the necessary details, click Test Connection to verify that everything is set up correctly.

    • Once verified, the new AWS account will be integrated into Temperstack, allowing you to manage resources across multiple accounts effortlessly.

Note:

Before starting the integration, ensure your IAM setup is complete by referring to the . Proper IAM configuration is crucial for successful integration and security.

IAM Setup Guide