1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
this seemed to work, in case anyone else is having the issue:
- in S3:
-make a bucket with your store name (mystore.com) (no www)
-enable public access
-in permissions -> bucket policy, paste this code to allow people to see your bucket, changing url after resource to your corresponding domain
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadGetObject",
"Effect": "Allow",
"Principal": "",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::mystore.com/"
}
]
}
-in properties tab, under "Static website hosting", select "Redirect requests"
-in the target bucket, write www.mystore.com, note www.
-for protocol: http
-
in Route 53:
-make a CNAME record for www.mystore.com
-alias: no
-value: mystore.bigcartel.com -
in Route 53:
-make an A record for mystore.com (no www)
-alias: yes
-alias target: if AWS does not auto populate your S3 bucket, as it did for me, pick the s3 url WITHOUT your domain name in there. For example, my s3 bucket is called mystore.com so the URL endpoint is mystore.s3-website-us-east-1.amazonaws.com. Just take this part " s3-website-us-east-1.amazonaws.com" and put that in Alias target
beantwortet vor 4 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 9 Monaten