Multi-Cloud Support
Amnify Deploy supports provisioning infrastructure across three major cloud providers from a single interface: Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP). This guide explains how multi-cloud works and how to use it.
Supported Cloud Providers
| Provider | Status |
|---|---|
| Microsoft Azure | Supported |
| Amazon Web Services (AWS) | Supported |
| Google Cloud Platform (GCP) | Supported |
Each provider requires its own cloud integration to be configured before you can deploy into it. Integrations are managed in the Integrations section of the Amnify platform.
How Cloud Providers Are Used
Provider-Level Organization
The Amnify Deploy dashboard is organized by cloud provider. When you navigate to the Deploy section, you choose a provider and see all Projects and Deployments associated with that provider. This keeps your Azure, AWS, and GCP infrastructure clearly separated while still being manageable from one platform.
Deployment-Level Binding
Each Deployment is bound to a specific cloud provider, region (e.g., East US 2, eu-west-1, europe-west1), and account or subscription. These are configured at deployment creation time and cannot be changed without creating a new deployment.
Template Compatibility
Templates are typically designed for a specific cloud provider. When browsing the template library, templates are clearly labeled with the provider(s) they support. You can only use an Azure-specific template with an Azure cloud environment, and so on.
Some templates in the Combinations category may provision resources across multiple providers, but this is uncommon.
Configuring a Cloud Integration
Cloud integrations are the connection between Amnify and your cloud accounts. They must be configured by an Amnify administrator before Deployments can use them.
Azure Integration
- Requires an Azure Service Principal with appropriate permissions on the target subscription
- The service principal's credentials (Client ID, Client Secret, Tenant ID) are stored securely in Amnify
AWS Integration
- Requires IAM credentials (Access Key ID and Secret Access Key) for an IAM user or role with appropriate permissions
- Credentials are stored securely in Amnify
GCP Integration
- Requires a Service Account with the necessary IAM roles on the target project
- The service account key file is stored securely in Amnify
Once configured, integrations appear as options in the cloud environment step of the Deployment Creation wizard.
Setting up cloud integrations requires cloud administrator access. If you need an integration configured and do not have cloud admin access, contact your cloud infrastructure team.
Deploying Across Multiple Clouds
You can have Deployments across different cloud providers within the same Amnify organization. Common multi-cloud patterns:
Separate providers by use case:
- Core infrastructure on Azure
- Data pipelines on AWS
- Machine learning workloads on GCP
Deploy the same template to multiple providers:
- Create one deployment per cloud provider using the same template (if the template supports multiple providers)
- Useful for testing templates across providers or for multi-cloud redundancy
Use Pipelines for cross-cloud sequences:
- A Pipeline can include Deployments from different cloud providers
- The execution order applies regardless of which provider each Deployment targets
Provider-Specific Concepts
Each cloud provider has its own terminology and organizational hierarchy:
| Concept | Azure | AWS | GCP |
|---|---|---|---|
| Top-level account container | Subscription | Account | Project |
| Geographic location | Region | Region | Region |
| Network isolation unit | Virtual Network (VNet) | VPC | VPC |
When filling in deployment variables, use the correct terminology and format for your target provider. Template variable labels and descriptions should guide you to the right format.
Switching Between Providers in the UI
The Amnify Deploy dashboard shows one provider at a time. To switch:
- Navigate to Deploy in the platform
- Select the cloud provider tab (Azure, AWS, or GCP) at the top of the page
- The dashboard, projects, and deployments shown are now scoped to that provider
Next Steps
- Creating Deployments — configure the cloud environment when creating a deployment
- Creating Pipelines — chain deployments across providers in a pipeline