Turn it Off
  • Welcome to Turn it Off
  • GETTING STARTED
    • Introducing Turn it Off
    • Create your account
    • Connect a cloud provider
    • Add an application
    • Add an environment
    • Adding the standby page
    • Make Turn it Off active
    • Support
  • SIMPLE MANAGEMENT
    • Managing automation
    • Managing resources
    • Managing alerts
  • ACCOUNT AND BILLING
    • User management
    • Billing and payment
  • TECHNICAL
    • Configuration detail for the Standby Page
      • Azure Provider
      • AWS Provider
    • Partner Accounts (MSP, Agency etc)
  • INTEGRATIONS
    • Cloud providers
      • Introduction to Providers
      • Amazon Web Services (AWS)
        • AWS Supported Resources
        • AWS - Integration & Permissions Configuration
      • Microsoft Azure
        • Azure Supported Resources
        • Azure - Integration & Permissions Configuration
    • Messaging providers
      • Slack
      • Email
    • SSL Certificates
  • SECURITY
    • Controls
    • FAQ
Powered by GitBook
On this page
  • Supported Cloud Providers
  • Integration Methods
  • Managing Multiple Environments
  • Multi-Cloud Resource Management
  • Resource Groupings
  • Security Considerations
  • Best Practices
  • Troubleshooting
  • Additional Resources
  1. INTEGRATIONS
  2. Cloud providers

Introduction to Providers

This guide explains how our platform integrates with cloud providers—specifically Amazon Web Services (AWS) and Microsoft Azure—and how you can manage resources across multiple environments and accounts. It also covers how to coordinate actions on resources from both AWS and Azure within a single environment.

Supported Cloud Providers

  • Amazon Web Services (AWS)

  • Microsoft Azure

Integration Methods

AWS Integration

  • Access Method: IAM Roles

  • Permissions Required: Custom read-only and action-specific policies

Steps to Integrate AWS:

  1. Create an IAM Role: In your AWS account, create an IAM role that our platform can assume.

  2. Attach Custom Policies: Apply the custom read-only and action-specific policies provided by our platform to the IAM role.

  3. Provide Role ARN: Input the Amazon Resource Name (ARN) of the IAM role into our platform to complete the integration.

Azure Integration

  • Access Method: Service Principal

  • Permissions Required: Contributor-level access

Steps to Integrate Azure:

  1. Register an Application: In Azure Active Directory, register a new application for our platform.

  2. Create a Service Principal: Generate a service principal (app registration) for authentication.

  3. Assign Role: Grant the service principal the Contributor role at the subscription or resource group level.

  4. Provide Credentials: Enter the service principal's credentials (Application ID, Tenant ID, and client secret) into our platform.

Managing Multiple Environments

Our platform allows you to create and manage multiple environments (e.g., development, staging, production). Each environment can be associated with different cloud accounts or subscriptions from AWS and Azure.

Features:

  • Flexible Configuration: Assign any number of AWS accounts or Azure subscriptions to an environment.

  • Isolated Management: Manage resources in each environment independently.

  • Consistent Policies: Apply the same cost optimization policies across environments.

Multi-Cloud Resource Management

You can include resources from both AWS and Azure within a single environment. This enables you to perform actions on multiple resources across different cloud providers simultaneously.

Benefits:

  • Unified Control: Start, stop, and manage resources from both AWS and Azure in one place.

  • Synchronized Operations: Coordinate tasks like turning resources on or off at the same time across different clouds.

  • Consolidated Monitoring: View performance metrics and logs for all resources within the environment.

Resource Groupings

Organize your resources into logical groupings to simplify management.

  • Applications: Group resources that make up a single application.

  • Environments: Separate resources based on the deployment stage.

  • Resource Groupings: Further categorize resources based on functionality or teams.

Security Considerations

  • Principle of Least Privilege: Access permissions are limited to the minimum required for operation.

  • Infrastructure-Level Access: The platform operates at the infrastructure level and does not access data within databases or storage accounts.

  • Compliance Alignment: Security controls are aligned with ISO 27001 standards.

Best Practices

  • Regularly Review Permissions: Ensure that the IAM roles and service principals have appropriate permissions.

  • Use Tags and Labels: Utilize tagging in AWS and labeling in Azure to organize resources effectively.

  • Monitor Resource Usage: Keep an eye on resource utilization to optimize costs.

Troubleshooting

  • Integration Issues: If you face problems during integration, double-check the permissions and roles assigned.

  • Resource Control Problems: Ensure that the resources are correctly assigned to the environment and that the platform has the necessary permissions.

  • Contact Support: If issues persist, reach out to our support team for assistance.

Additional Resources


By following this guide, you can effectively integrate AWS and Azure with our platform, manage multiple environments, and coordinate resources across different cloud providers.

PreviousCloud providersNextAmazon Web Services (AWS)

Last updated 7 months ago

AWS Integration Guide
Azure Integration Guide