Cloud Providers and Scoutflo
Last updated
Last updated
Connecting your cloud provider is a crucial step in leveraging Scoutflo Deploy's capabilities for deploying and managing applications and infrastructure. This page provides a detailed guide on the information required to connect your cloud (AWS, GCP, or Azure) and explains how this data is used across different feature flows.
When integrating AWS, you’ll need to provide the following credentials and configuration details:
1. Access Keys (AWS Access Key ID & Secret Access Key)
Purpose: These keys allow Scoutflo to programmatically interact with your AWS account to manage and deploy resources.
Utilization:
Cluster Creation: Enables Scoutflo to create and manage EKS (Elastic Kubernetes Service) clusters directly from the platform.
Infrastructure Provisioning: This allows Scoutflo to provision necessary AWS resources such as VPCs, subnets, and security groups for your applications.
Deployment: These keys ensure that Scoutflo can deploy Helm-based applications on your AWS-managed clusters.
Security Note: It is recommended to generate these access keys for an IAM user with appropriate permissions specific to managing Kubernetes clusters and AWS infrastructure resources.
2. AWS IAM Role with Required Permissions
Purpose: For enhanced security, Scoutflo recommends using an IAM Role with the required permissions, instead of relying on long-term access keys.
Utilization:
Cluster Management: Scoutflo assumes this role to interact with your AWS resources, allowing secure creation, monitoring, and management of EKS clusters.
Access Control: Offers more granular access management, ensuring that Scoutflo only performs authorized actions.
3. AWS Region
Purpose: Identify the AWS region where your infrastructure (clusters, databases, etc.) will be created and managed.
Utilization: This setting determines the geographic location of your resources, ensuring optimal performance and adherence to regional compliance policies.
4. VPC (Virtual Private Cloud) Configuration
Purpose: Provides details about your existing VPC, allowing Scoutflo to deploy resources within a secure and isolated network.
Utilization:
Cluster Networking: Ensures your Kubernetes clusters and applications are deployed within your specified network environment.
Database Deployments: Facilitates hosting databases within your defined VPC, promoting secure communication between services.
5. Subnets and Security Groups
Purpose: Define the subnets where your resources will reside and control the traffic flow via security groups.
Utilization:
Node Configuration: Specifies the subnets for Kubernetes worker nodes.
Application Access: Security groups regulate how your applications can be accessed within and outside the cluster.
Connecting to Google Cloud Platform (GCP)
When GCP integration becomes available, the required details will include:
Service Account Key: JSON key file for a Service Account with roles such as Kubernetes Engine Admin and Compute Admin.
Project ID: The GCP project where clusters and resources will be created.
Region and Zone: Geographic locations for deploying clusters and resources.
Utilization: These credentials will allow Scoutflo to create, manage, and deploy applications on Kubernetes clusters within GCP.
Connecting to Microsoft Azure
For Azure, you will need:
Service Principal Credentials: Including Client ID, Client Secret, Tenant ID, and Subscription ID.
Resource Group: The group in which clusters and resources will be managed.
Region: The location for deploying resources.
Utilization: These credentials will enable Scoutflo to manage Azure Kubernetes Service (AKS) clusters, deploy applications, and provision cloud infrastructure.
Once your cloud provider is connected, Scoutflo Deploy leverages this information across multiple workflows:
1. Cluster Creation and Management
AWS: Scoutflo provisions and manages EKS clusters using your AWS credentials.
2. Application Deployment
Helm-based Deployments: Cloud credentials enable Scoutflo to deploy Helm charts and applications directly onto your cloud-managed clusters.
Namespace and Resource Configuration: Scoutflo manages namespace setup, network configurations, and resource quotas for deployments.
3. Role-Based Access Control (RBAC) and Permissions Management
RBAC: Integrates with your cloud provider's IAM/RBAC systems, ensuring user permissions are in sync.
Custom Role Management: Allows for workspace-specific roles, granting precise control over cloud resources.
4. Observability and Cost Management
Monitoring: Scoutflo integrates with cloud monitoring services, offering visibility into clusters, applications, and infrastructure.
Cost Management: Scoutflo retrieves cost metrics, helping you monitor and optimize cloud spending.
Connecting your cloud provider to Scoutflo Deploy unlocks the platform's full potential, enabling efficient management and deployment of your infrastructure and applications. With seamless integration and robust security measures, Scoutflo ensures you have complete control over your cloud environment, whether you use AWS, GCP, or Azure.
