Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
Acme.Sh
Commits
5b771039
Commit
5b771039
authored
Nov 20, 2016
by
neilpang
Browse files
Support AWS Route53 api
parent
2f1bc586
Changes
3
Show whitespace changes
Inline
Side-by-side
README.md
View file @
5b771039
...
@@ -253,7 +253,7 @@ You don't have to do anything manually!
...
@@ -253,7 +253,7 @@ You don't have to do anything manually!
1.
CloudXNS.com API
1.
CloudXNS.com API
1.
GoDaddy.com API
1.
GoDaddy.com API
1.
OVH, kimsufi, soyoustart and runabove API
1.
OVH, kimsufi, soyoustart and runabove API
1.
AWS Route 53
, see: https://github.com/Neilpang/acme.sh/issues/65
1.
AWS Route 53
1.
PowerDNS.com API
1.
PowerDNS.com API
1.
lexicon DNS API: https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
1.
lexicon DNS API: https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
(DigitalOcean, DNSimple, DNSMadeEasy, DNSPark, EasyDNS, Namesilo, NS1, PointHQ, Rage4 and Vultr etc.)
(DigitalOcean, DNSimple, DNSMadeEasy, DNSPark, EasyDNS, Namesilo, NS1, PointHQ, Rage4 and Vultr etc.)
...
...
acme.sh
View file @
5b771039
...
@@ -3613,6 +3613,11 @@ _initconf() {
...
@@ -3613,6 +3613,11 @@ _initconf() {
#PDNS_Token=\"0123456789ABCDEF\"
#PDNS_Token=\"0123456789ABCDEF\"
#PDNS_Ttl=60
#PDNS_Ttl=60
#######################
#Amazon Route53:
#AWS_ACCESS_KEY_ID=XXXXXXXXXX
#AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXX
" >"$ACCOUNT_CONF_PATH"
" >"$ACCOUNT_CONF_PATH"
fi
fi
}
}
...
...
dnsapi/README.md
View file @
5b771039
...
@@ -185,7 +185,23 @@ acme.sh --issue --dns dns_me -d example.com -d www.example.com
...
@@ -185,7 +185,23 @@ acme.sh --issue --dns dns_me -d example.com -d www.example.com
The
`ME_Key`
and
`ME_Secret`
will be saved in
`~/.acme.sh/account.conf`
and will be reused when needed.
The
`ME_Key`
and
`ME_Secret`
will be saved in
`~/.acme.sh/account.conf`
and will be reused when needed.
# 10. Use custom API
## 10. Use Amazon Route53 domain API
https://github.com/Neilpang/acme.sh/wiki/How-to-use-Amazon-Route53-API
```
export AWS_ACCESS_KEY_ID=XXXXXXXXXX
export AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXX
```
To issue a cert:
```
acme.sh --issue --dns dns_aws -d example.com -d www.example.com
```
The
`AWS_ACCESS_KEY_ID`
and
`AWS_SECRET_ACCESS_KEY`
will be saved in
`~/.acme.sh/account.conf`
and will be reused when needed.
# 11. Use custom API
If your API is not supported yet, you can write your own DNS API.
If your API is not supported yet, you can write your own DNS API.
...
@@ -202,6 +218,6 @@ acme.sh --issue --dns dns_myapi -d example.com -d www.example.com
...
@@ -202,6 +218,6 @@ acme.sh --issue --dns dns_myapi -d example.com -d www.example.com
For more details, please check our sample script:
[
dns_myapi.sh
](
dns_myapi.sh
)
For more details, please check our sample script:
[
dns_myapi.sh
](
dns_myapi.sh
)
## 1
1
. Use lexicon DNS API
## 1
2
. Use lexicon DNS API
https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment