You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,7 @@ custom:
58
58
fullstack:
59
59
domain: my-custom-domain.com
60
60
certificate: arn:aws:acm:us-east-1:... # The ARN for the SSL cert to use form AWS CertificateManager
61
+
route53: false # Use route53 to manage domains and certificates
61
62
bucketName: webapp-deploy # Unique name for the S3 bucket to host the client assets
62
63
distributionFolder: client/dist # Path to the client assets to be uploaded to S3
63
64
indexDocument: index.html # The index document to use
@@ -259,6 +260,26 @@ The custom domain for your fullstack serverless app.
259
260
260
261
---
261
262
263
+
**route53**
264
+
265
+
_optional_, default: `false`
266
+
267
+
```yaml
268
+
custom:
269
+
fullstack:
270
+
...
271
+
route53: true
272
+
...
273
+
```
274
+
275
+
Use this parameter if you want the plugin to manage domains via route53, including automatic SSL certificate requesting and validation (this means you can omit the `certificateArn` parameter).
276
+
Note: if an issued SSL certificate for the requested domain(s) already exists in ACM, it will be reused.
277
+
278
+
If one or more domains aren't managed by a Hosted Zone in your account, the required DNS entries will be written to the console.
279
+
If there is no issued SSL certificate for all domains combined and one or more aren't managed by a Hosted Zone in your account, deployment will wait for the DNS entries to be added manually and the certificate to be issued.
0 commit comments