github-repos/acme.sh
1
0
Fork 0
mirror of https://github.com/acmesh-official/acme.sh.git synced 2025-01-27 14:30:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

ovh-us

Sergey Ponomarev 2023-06-05 12:53:24 +03:00
parent ca9c4ec922
commit 8b10ace834
1 changed files with 13 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
How-to-use-OVH-domain-api.md

@ -48,17 +48,14 @@ Click "Authorize Access"
```
acme.sh --issue -d mydomain.com --dns dns_ovh --server letsencrypt
```
Done.
## 5. OVH api support OVH, Kimsufi, SoYouStart.
The default is using `ovh-eu` region.
## 5. OVH api support OVH, kimsufi, soyoustart and runabove.
The default is using ovh-eu region.
if you are using ovh-ca region,
If you are using ovh-ca region,
Create app key here: https://ca.api.ovh.com/createApp/
@ -66,31 +63,20 @@ Then please specify the region in the first step:
```
export OVH_END_POINT=ovh-ca
export OVH_AK="your application key"
export OVH_AS="your application secret"
acme.sh --issue -d mydomain.com --dns dns_ovh --server letsencrypt
```
All the supported regions:
```
#'ovh-eu' (default)
#'ovh-ca':
#'kimsufi-eu'
#'kimsufi-ca'
#'soyoustart-eu'
#'soyoustart-ca'
#'runabove-ca'
```
* `ovh-eu` default
* `ovh-us`
* `ovh-ca`
* `kimsufi-eu`
* `kimsufi-ca`
* `soyoustart-eu`
* `soyoustart-ca`
# Advanced Usage
@ -98,6 +84,7 @@ All the supported regions:
## 1. Create application key, secret and consumer
- **OVH Europe**: `https://api.ovh.com/createToken/?GET=/domain/zone/*&POST=/domain/zone/*&PUT=/domain/zone/*&DELETE=/domain/zone/*/record/*`
- **OVH USA**: `https://api.us.ovhcloud.com/createToken/?GET=/domain/zone/*&POST=/domain/zone/*&PUT=/domain/zone/*&DELETE=/domain/zone/*/record/*`
- **OVH Canada**: `https://ca.api.ovh.com/createToken/?GET=/domain/zone/*&POST=/domain/zone/*&PUT=/domain/zone/*&DELETE=/domain/zone/*/record/*`
In the page, please select "Unlimited" for the Validity.
@ -112,7 +99,6 @@ export OVH_CK="your consumer key"
# Generate your certificate
acme.sh --issue -d mydomain.com --dns dns_ovh --server letsencrypt
```
# Security
@ -120,4 +106,5 @@ acme.sh --issue -d mydomain.com --dns dns_ovh --server letsencrypt
It is a good security practice to limit what a given API key can in the event it is lost, stolen or anything wrong happens to limit the potential damages. OVH API keys can be limited to a specific domain zone using a simple pattern mechanism. For example, to restrict an OVH API key to manage "mydomain.com", you may use the following settings. Of course this can easily be customized to support any or multiple domains:
- **OVH Europe**: `https://api.ovh.com/createToken/?GET=/domain/zone/mydomain.com/*&POST=/domain/zone/mydomain.com/*&PUT=/domain/zone/mydomain.com/*&GET=/domain/zone/mydomain.com&DELETE=/domain/zone/mydomain.com/record/*`
- **OVH Canada**: `https://ca.api.ovh.com/createToken/?GET=/domain/zone/mydomain.com/*&POST=/domain/zone/mydomain.com/*&PUT=/domain/zone/mydomain.com/*&GET=/domain/zone/mydomain.com&DELETE=/domain/zone/mydomain.com/record/*`
- **OVH USA**: `https://api.us.ovhcloud.com/createToken/?GET=/domain/zone/mydomain.com/*&POST=/domain/zone/mydomain.com/*&PUT=/domain/zone/mydomain.com/*&GET=/domain/zone/mydomain.com&DELETE=/domain/zone/mydomain.com/record/*`
- **OVH Europe**: `https://api.ovh.com/createToken/?GET=/domain/zone/mydomain.com/*&POST=/domain/zone/mydomain.com/*&PUT=/domain/zone/mydomain.com/*&GET=/domain/zone/mydomain.com&DELETE=/domain/zone/mydomain.com/record/*`