Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/epomatti/aws-cloudfront-s3-oac-oai
AWS CloudFront S3 origina with OAC and OAI
https://github.com/epomatti/aws-cloudfront-s3-oac-oai
aws aws-security bucket cloudfront end-to-end-encryption enforce-tls oac oai presigned presigned-url s3 signed-url terraform tls
Last synced: 13 days ago
JSON representation
AWS CloudFront S3 origina with OAC and OAI
- Host: GitHub
- URL: https://github.com/epomatti/aws-cloudfront-s3-oac-oai
- Owner: epomatti
- License: mit
- Created: 2023-10-07T23:15:28.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2023-10-11T23:27:03.000Z (about 1 year ago)
- Last Synced: 2024-10-17T08:02:16.397Z (29 days ago)
- Topics: aws, aws-security, bucket, cloudfront, end-to-end-encryption, enforce-tls, oac, oai, presigned, presigned-url, s3, signed-url, terraform, tls
- Language: HCL
- Homepage:
- Size: 851 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# AWS CloudFront OAC OAI
AWS CloudFront S3 origina with OAC and OAI.
As per the current [documentation][1], **OAC** authenticated requests supports:
- All Amazon S3 buckets in all AWS Regions, including opt-in Regions launched after December 2022
- Amazon S3 [server-side encryption][2] with AWS KMS (SSE-KMS)
- Dynamic requests (PUT and DELETE) to Amazon S3
First, create a key pair for the CloudFront signed URL stuff ([ref1][6], [ref2][5]):
```sh
mkdir keys
openssl genrsa -des3 -out keys/private.pem 2048
openssl rsa -in keys/private.pem -outform PEM -pubout -out keys/public.pem
```
Create the `.auto.tfvars` file from the sample:
> The ACM certificate verification will be required
```terraform
cloudfront_price_class = "PriceClass_100"
certificate_domain = "cf.example.com"
cloudfront_minimum_protocol_version = "TLSv1.2_2021"
```
To create the infrastructure:
```sh
terraform init
terraform apply -auto-approve
```
As described in the [S3 origin documentation][3], S3 regional domains should be used:
```sh
# Use the regional bucket domain
.s3..amazonaws.com
```
For server-side encryption (SSE) The implementation enabled `aws:kms` (SSE-KMS) encryption for OAC, and `AES256` (SSE-S3)for OAI.
To test the distribution access the endpoints on paths `/oac` and `/oai` respectively.
Policy implementation between the two authentication methods differ:
| Policy | OAC | OAI |
|-|-|-|
| Principal | `cloudfront.amazonaws.com` | OAI identity id |
| Condition | `AWS:SourceArn` with the distribution ARN | n/a|
## Sharing Objects with URLs
There are two types of share with URLs:
- [S3 presigned URLs][4]
- [CloudFront Signed URLs][7]
### S3 presigned URLs
You can generate a presigned URL which will use the credentials of the user who generated the URLs. This would be useful for users who do not have access to the account with AWS credentials ("anonymous").
Generate a presigned URL, open an anonymous browser session and use the link to access the object:
```sh
# For regions launched prior to 2019
aws s3 presign s3://bucket-presignedurl-vouchers010203/vouchers/voucher.txt --expires-in 604800
```
### CloudFront Signed URLs
Signed URLs are more secure and offer additional controls with [canned policies][8] but specially with [custom policies][9].
Edit the [`policy.json`](policyjson) file accordingly, and generate the signature:
```sh
cat policy | tr -d "\n" | tr -d " \t\n\r" | openssl sha1 -sign keys/private.pem | openssl base64 -A | tr -- '+=/' '-_~'
```
The signed URL will look like this:
```
https://ddddddd00001111.cloudfront.net/vouchers/voucher.txt?Expires=1698637841&Signature=&Key-Pair-Id=KQPALV128937
```
### Ciphers + Enforce TLS
Setting a custom certificate on ACM for CloudFront allows you to select the Ciphers list.
For details, check [Supported protocols and ciphers between viewers and CloudFront](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/secure-connections-supported-viewer-protocols-ciphers.html).
The following S3 bucket policy enforces TLS by denying insecure transport via `"aws:SecureTransport" : "false"`:
```json
"Statement" : [
{
"Sid" : "EnforceTLS",
"Action" : "s3:*",
"Effect" : "Deny",
"Resource" : [
"arn:aws:s3:::DOC-EXAMPLE-BUCKET",
"arn:aws:s3:::DOC-EXAMPLE-BUCKET/*"
],
"Condition" : {
"Bool" : {
"aws:SecureTransport" : "false"
}
}
}
]
```
---
### Clean-up
Destroy the resources when you're done using it:
```sh
terraform destroy -auto-approve
```
[1]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html
[2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/serv-side-encryption.html
[3]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.html#using-s3-as-origin
[4]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html
[5]: https://rietta.com/blog/openssl-generating-rsa-key-from-command/
[6]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-trusted-signers.html#choosing-key-groups-or-AWS-accounts
[7]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html
[8]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-creating-signed-url-canned-policy.html
[9]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-creating-signed-url-custom-policy.html