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
+25-10Lines changed: 25 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,6 @@
2
2
3
3
This module provisions the infrasructure required for a static website hosted on AWS S3 and CloudFront and optionally allows syncronisation of the website content with a local directory.
4
4
5
-
creates an [S3 Bucket](https://aws.amazon.com/s3/) to creates a [CloudFront Distribution](https://aws.amazon.com/cloudfront/),
6
-
7
-
8
5
## Key Features
9
6
10
7
-[S3 Bucket](https://aws.amazon.com/s3/) to store website content.
@@ -21,16 +18,29 @@ This module provisions the infrasructure required for a static website hosted on
21
18
-[Route 53 Hosted zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html) which is the DNS provider for the domain. [Making Amazon Route 53 the DNS service for an existing domain](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html). Note: the hosted zone only needs to manage the DNS service, domain registration does not need to be migrated!
22
19
-[A second aws porovider configured in us-east-1](https://www.terraform.io/language/providers/configuration) as CloudFront and SSL certificates are only available in us-east-1.
23
20
24
-
To syncronisation of the website content with a local directory, the following is required:
21
+
For syncronisation of the website content with a local directory, the following is required:
-[Configure a named profile](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) using `aws configure --profile NAME` command. This is used for the aws s3 sync command.
23
+
-[Configure a named profile](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) using `aws configure --profile NAME` command. This is used for the aws s3 sync command which is executed locally. Profiles are preferred over keys and secrets.
27
24
28
25
29
26
## Usage
30
27
[Example available here](https://github.com/DevOpsNavy/s3-cloudfront-static-website/tree/main/examples/static_website_with_sync)
31
28
32
29
```javascript
33
-
# Module AP
30
+
terraform {
31
+
required_providers {
32
+
aws = {
33
+
source ="hashicorp/aws"
34
+
version ="4.10.0"
35
+
}
36
+
}
37
+
}
38
+
39
+
# Default provider for resource creation
40
+
provider "aws" {
41
+
region =""
42
+
profile =""
43
+
}
34
44
35
45
# Provider required in useast1 for cloudfront, SSLM Certificate
36
46
provider "aws" {
@@ -177,17 +187,17 @@ NOTE: Be sure to merge the latest changes from "upstream" before making a pull r
177
187
178
188
## To Do
179
189
180
-
## Contributing
190
+
To dos are documented in the [project associated](https://github.com/DevOpsNavy/s3-cloudfront-static-website/projects/1) with this repo.
181
191
182
-
[ToDo are captured within the GitHub project associated with this module](https://github.com/DevOpsNavy/s3-cloudfront-static-website/projects/1)
192
+
## Contributing
183
193
184
194
### Bug Reports & Feature Requests
185
195
186
196
Please use the [issue tracker](https://github.com/DevOpsNavy/s3-cloudfront-static-website/issues) to report any bugs or file feature requests.
187
197
188
198
### Developing
189
199
190
-
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out)with our other projects, we would love to hear from you! Shoot us an [email][email].
200
+
If you are interested in being a contributor and want to get involved in developing this project or with our other projects, we would love to hear from you! Shoot us an [email][Admin@devopsnavy.co.uk].
191
201
192
202
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
193
203
@@ -204,4 +214,9 @@ In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
204
214
| Name | Role |
205
215
|------|---------|
206
216
|[Faizan Raza](https://www.linkedin.com/in/faizan-raza-997808206/)| Lead Developer |
0 commit comments