How to configure cloud provider credentials
Register AWS or Azure credentials so Radius can provision cloud resources.
Radius supports deploying application resources to Amazon Web Services (AWS) and Microsoft Azure. The default Recipe Pack deploys resources to Kubernetes. To use AWS or Azure cloud services, configure credentials, a target Environment, and recipes for those services.
The Radius control plane runs on a supported Kubernetes cluster, including Amazon EKS and Azure Kubernetes Service (AKS). Installing Radius on EKS or AKS does not, by itself, configure recipes to provision cloud services.
With the Environment configured, deploy the application to it.
| Provider | Identity | Description |
|---|---|---|
| AWS | IAM access key | Deploy and connect to AWS resources using an IAM access key |
| IAM Roles for Service Accounts (IRSA) | Deploy and connect to AWS resources using AWS IRSA | |
| Azure | Service principal | Deploy and connect to Azure resources using a service principal |
| Workload Identity | Deploy and connect to Azure resources using Workload Identity |
The community Recipe Packs provide implementations for AWS and Azure. Check the selected pack’s resource mappings, recipe parameters, and prerequisites before deploying. AWS and Azure support does not mean that every Resource Type has a recipe for both clouds.
An application definition can be reused across clouds when each Environment provides recipes that implement the Resource Types and properties it uses. Cloud-specific resource definitions remain tied to their cloud. See Deploying across AWS and Azure for an example.
Register AWS or Azure credentials so Radius can provision cloud resources.
Was this page helpful?
Glad to hear it! Please feel free to star our repo and join our Discord server to stay up to date with the project.
Sorry to hear that. If you would like to also contribute a suggestion visit and tell us how we can improve.