Integration with AWS S3

Before you take any steps please back up your files and database. The plugin works only with default CMS pattern. If you manually changed CMS patterns, the plugin might not help you.

Login to the AWS Console and navigate to S3.

Create an S3 bucket (define the Bucket Name and the Region you want)

Upload content to your S3 bucket.

Enable Website Hosting and define the Index Document (does not need to exist e.g. index.html) for your S3 bucket under Properties > Static Website Hosting.

Use the following example to set a Bucket Policy (replace "example-bucket" with your S3 bucket name):

{

 "Version":"2012-10-17",
 "Statement":[{
   "Sid":"PublicReadGetObject",
       "Effect":"Allow",
     "Principal": "*",
     "Action":["s3:GetObject"],
     "Resource":["arn:aws:s3:::example-bucket/*"
     ]
   }
 ]
}

Add the bucket policy in the Permissions drop-down menu.

Check accessibility of the file at the URL link in the browser. For example, the link for the file from this guide is bucket.s3-website.eu-central-1.amazonaws.com/logo.png

Log in your G-CORE Labs control panel and create a CDN-Resource. Use S3 Endpoint as an origin source. For example, bucket.s3-website.eu-central-1.amazonaws.com

As soon as you create a Resource check accessibility of the content through the CDN by opening the URL link in the browser. For example CNAME: awss3.site.com/logo.png. Ensure that your CNAME record has been configured in a proper way before using it for integration.

Integration has been completed! We highly recommend you to check the HTML code of your web page to ensure that URLs have been rewritten properly from your original ones to CNAME from the control panel.

To do that press F12 or open Developers Tools in your browser, choose the Network tab and refresh the page. All static files should have your CNAME in URLs.

Was this article helpful?
Recently viewed articles