Skip to content

Commit 84d8c5b

Browse files
committed
clarifies using one stack for multiple CF distributions
1 parent c0ab5c6 commit 84d8c5b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ SELECT * FROM cf_access_logs.combined limit 10;
7676

7777
### Q: How can I use the sample application for multiple Amazon CloudFront distributions?
7878

79-
Deploy another AWS CloudFormation stack from the same template to create a new bucket for different distributions or environments. The stack name is added to all resource names (e.g. AWS Lambda functions, S3 bucket etc.) so you can distinguish the different stacks in the AWS Management Console.
79+
If your data does not need to be partitioned by Amazon CloudFront distribution, you can use the same bucket and path (`new/`) for more than one distribution. Then you can query the data by `host` column. If you need to speed up the parquet transformation duration (must stay under 15 minutes) or query duration, deploy another AWS CloudFormation stack from the same template for each distribution. The stack name is added to all resource names (e.g. AWS Lambda functions, S3 bucket etc.) so you can distinguish the different stacks in the AWS Management Console.
8080

8181
### Q: In which region can I deploy the sample application?
8282

0 commit comments

Comments
 (0)