Skip to content

Commit 4021477

Browse files
committed
provider configuration
1 parent bbe91b5 commit 4021477

File tree

2 files changed

+15
-1
lines changed

2 files changed

+15
-1
lines changed

docs/concepts/defang-byoc.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,18 @@ Defang does not install or run any Defang or third party services at runtime.
1515
Defang does run the Defang build service to build your container images, which terminates after every build.
1616
:::
1717

18+
### Configuration
19+
20+
The Defang CLI can be configured to deploy to a cloud provider either by using the `--provider` flag or by setting the `DEFANG_PROVIDER` environment variable. For example:
21+
22+
```bash
23+
# Supported provider values: auto, aws
24+
# Default is auto, which deploys to the Defang Playground
25+
$ defang up --provider=aws
26+
# or
27+
$ export DEFANG_PROVIDER=aws
28+
```
29+
1830
## AWS
1931

2032
:::info

docs/providers/aws/aws.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,12 @@ Getting started with the Defang BYOC AWS Provider is easy. Make sure you have pr
2020
If you have the aws CLI installed, you should be able to successfully run `aws sts get-caller-identity` and see your account ID.
2121
:::
2222

23-
Use the `--provider=aws` flag to tell the Defang CLI to use the AWS Provider.
23+
Use the `--provider=aws` flag to tell the Defang CLI to use the AWS Provider or set the `DEFANG_PROVIDER` environment variable to `aws`.
2424

2525
```bash
2626
$ defang up --provider=aws
27+
# or
28+
$ export DEFANG_PROVIDER=aws
2729
```
2830

2931
:::warning

0 commit comments

Comments
 (0)