777 jili casino register online download.Enjoy Free 888+200 Daily Legal Bonus

greeso
(@greeso)

9 years, 9 months ago

I could not find any documentation on how to setup this plugin to work with AWS CloudFront.

I did the following so far:

1. Create S3 bucket (lets call it my_cool_s3_bucket)

2. Create a CloudFront Distribution (lets call it my_cool_cloudfront), the origin for this distribution is my_cool_s3_bucket

3. Create an IAM account, and give it AmazonS3FullAccess and AmazonCloudFrontFullAccess

4. Activate the Amazon Web Services plugin and create two entries in wp-config.php file as suggested by the Amazon Web Services plugin

5. Activate the Amazon S3 and CloudFront plugin, and choose my_cool_s3_bucket as the source.

Now, I am not sure how I ensure that CloudFront gets used. What do I do, what settings? Is there a detailed document about that somewhere? I could not find any.

Thanks.

https://www.ads-software.com/plugins/amazon-s3-and-cloudfront/

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Contributor A5hleyRich
(@a5hleyrich)

9 years, 9 months ago

You need to ensure that you’re using the CloudFront domain. Here are the full setup instructions, but you can probably skip to step 4:

1. Log into the CloudFront console and click ‘Create Distribution’. Select ‘Web’ as the delivery method.

https://www.dropbox.com/s/1r5vr8ygbsanl7g/step1.png?dl=0

2. On the ‘Origin Settings’ screen select your bucket and leave the ‘Origin Path’ blank. Customise the remaining settings if required, the defaults are usually fine.

https://www.dropbox.com/s/78qz1i3rarz01i5/step2.png?dl=0

3. Once the distribution is created you will see the ‘Domain Name’ listed. The assets can take a while to propagate, so it’s best to come back to this step after a while.

https://www.dropbox.com/s/h3oomur122ozt0s/step3.png?dl=0

4. Add the domain name to the AWS plugin.

https://www.dropbox.com/s/tct98zk5774nrmi/step4.png?dl=0

Your assets will now be served from CloudFront, however this does not update the URLs already embedded within content. You will need to perform a manual find and replace to update those.

5. You can further mask the CloudFront domain by setting up a CNAME, which points to the CloudFront domain.

https://www.dropbox.com/s/natk97ob7zt3mji/step5.png?dl=0

6. Update the domain within the AWS plugin to use the new CNAME.

https://www.dropbox.com/s/fzbx2jkn3fkglq8/step6.png?dl=0

7. Add the CNAME to the CloudFront console.

https://www.dropbox.com/s/kbc9so7nr2yds31/step7.png?dl=0

Thread Starter greeso
(@greeso)

9 years, 8 months ago

Why leave the origin empty? Isn’t that supposed to be the S3 bucket that we created?

Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Working with CloudFront’ is closed to new replies.

Tags