Can I hide S3 and Cloudfront endpoints?Amazon route 53 + cloudfront + s3 -> with angularjs2 app in ec2How do I enable redirection on a domain for an S3-hosted website with CloudFront in front of it?HTTPS connection between Cloudfront and S3?Serve two static S3 websites from the same domain, based on geolocationCertificate Mismatch setting up Route53, CloudFront, Custom OriginSetting up CloudFront [Custom Origin] for EC2 instanceSubdomain from different S3 bucket on same cloudfront distributionServing website from Cloudfront and S3 without public bucketcannot get aws cloudfront / route53 to resolve my domain nameHttps configuration on AWSServe a static website on S3 via CloudFront and ACM SSL without Route53
PhD student with mental health issues and bad performance
How were concentration and extermination camp guards recruited?
Finding x,y coordinates where y is largest
What do we gain with higher order logics?
Importance sampling estimation of power function
Why doesn't my simple mesh wall "difference boolean cut" the door away?
How do I write "Show, Don't Tell" as an Asperger?
What happened to all the nuclear material being smuggled after the fall of the USSR?
What is the right way to float a home lab?
What are the words for people who cause trouble believing they know better?
X-shaped crossword
What is in `tex.print` or `tex.sprint`?
Did thousands of women die every year due to illegal abortions before Roe v. Wade?
Is it a problem that pull requests are approved without any comments
What makes linear regression with polynomial features curvy?
How can Iron Man's suit withstand this?
How to pass a regex when finding a directory path in bash?
Did Darth Vader wear the same suit for 20+ years?
How to generate random points without duplication?
How would you say “AKA/as in”?
When writing an error prompt, should we end the sentence with a exclamation mark or a dot?
Is the decompression of compressed and encrypted data without decryption also theoretically impossible?
How can drunken, homicidal elves successfully conduct a wild hunt?
How to skip replacing first occurrence of a character in each line?
Can I hide S3 and Cloudfront endpoints?
Amazon route 53 + cloudfront + s3 -> with angularjs2 app in ec2How do I enable redirection on a domain for an S3-hosted website with CloudFront in front of it?HTTPS connection between Cloudfront and S3?Serve two static S3 websites from the same domain, based on geolocationCertificate Mismatch setting up Route53, CloudFront, Custom OriginSetting up CloudFront [Custom Origin] for EC2 instanceSubdomain from different S3 bucket on same cloudfront distributionServing website from Cloudfront and S3 without public bucketcannot get aws cloudfront / route53 to resolve my domain nameHttps configuration on AWSServe a static website on S3 via CloudFront and ACM SSL without Route53
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have setup a static website on AWS S3 and am accelerating it with AWS Cloudfront, but after, I am able to use AWS Route53 to connect my domain name to the Cloudfront endpoint. Now there are two other point of entries, S3 and Cloudfront (aside from the domain name).
Is it possible to hide the S3 and Cloudfront endpoints from the public so that they can only access website via the set domain name?
Thanks a lot!
amazon-web-services amazon-s3 amazon-route53 amazon-cloudfront
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
add a comment |
I have setup a static website on AWS S3 and am accelerating it with AWS Cloudfront, but after, I am able to use AWS Route53 to connect my domain name to the Cloudfront endpoint. Now there are two other point of entries, S3 and Cloudfront (aside from the domain name).
Is it possible to hide the S3 and Cloudfront endpoints from the public so that they can only access website via the set domain name?
Thanks a lot!
amazon-web-services amazon-s3 amazon-route53 amazon-cloudfront
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
add a comment |
I have setup a static website on AWS S3 and am accelerating it with AWS Cloudfront, but after, I am able to use AWS Route53 to connect my domain name to the Cloudfront endpoint. Now there are two other point of entries, S3 and Cloudfront (aside from the domain name).
Is it possible to hide the S3 and Cloudfront endpoints from the public so that they can only access website via the set domain name?
Thanks a lot!
amazon-web-services amazon-s3 amazon-route53 amazon-cloudfront
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
I have setup a static website on AWS S3 and am accelerating it with AWS Cloudfront, but after, I am able to use AWS Route53 to connect my domain name to the Cloudfront endpoint. Now there are two other point of entries, S3 and Cloudfront (aside from the domain name).
Is it possible to hide the S3 and Cloudfront endpoints from the public so that they can only access website via the set domain name?
Thanks a lot!
amazon-web-services amazon-s3 amazon-route53 amazon-cloudfront
amazon-web-services amazon-s3 amazon-route53 amazon-cloudfront
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
edited Dec 17 '17 at 11:10
user351331
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
asked Jul 24 '16 at 16:10
uberrebuuberrebu
2112822
2112822
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront.
To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than specific ones you want to allow
answered Jul 24 '16 at 17:51
user366914user366914
111
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
add a comment |
Is it possible to hide the S3 endpoints from the public so that they
can only access website via the set domain name?
Well, as far as I'm aware, there is no official solution so far, however there is a workaround suggested by AWS. So here is an implementation that worked out for me:
Create an S3 bucket and enabled website hosting. Go to Bucket Policy section of Permissions and enter a policy similar to this one:
"Version": "2012-10-17",
"Statement": [
"Sid": "PublicReadForGetBucketObjects",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::[YOUR_WEBSITE_BUCKET_NAME]/*",
"Condition":
"StringEquals":
"aws:Referer": "[SOME_LONG_SECRET_VALUE]"
]Create CloudFront distribution and configure:
- the following origin:
[YOUR_WEBSITE_BUCKET_NAME].s3-website-[AWS_REGION_NAME].amazonaws.com. Addressing this concern, from CloudFront perspective, this is not an S3 Bucket Origin, but rather just a Custom Origin. - the following Origin Custom Header:
- Header Name:
Referer - Value:
[SOME_LONG_SECRET_VALUE](from your bucket policy)
- Header Name:
- the following origin:
- Configure the rest of your CloudFront distribution settings as usual.
As a result, bucket policy will allow object GETs if only the request contains Referer header with specified secret value, which will block direct request to you S3 website and allow requests sent via CloudFront. And, obviously, you might think of rotating this secret value every now and then.
Please note that by doing this, CloudFront will overwrite Referer header (if present) of any incoming request before forwarding it to the origin, so if you rely on it, this solution won't work.
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f791658%2fcan-i-hide-s3-and-cloudfront-endpoints%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront.
To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than specific ones you want to allow
answered Jul 24 '16 at 17:51
user366914user366914
111
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
add a comment |
Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront.
To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than specific ones you want to allow
answered Jul 24 '16 at 17:51
user366914user366914
111
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
add a comment |
Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront.
To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than specific ones you want to allow
answered Jul 24 '16 at 17:51
user366914user366914
111
Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront.
To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than specific ones you want to allow
answered Jul 24 '16 at 17:51
user366914user366914
111
answered Jul 24 '16 at 17:51
user366914user366914
111
answered Jul 24 '16 at 17:51
user366914user366914
111
answered Jul 24 '16 at 17:51
user366914user366914
111
111
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
add a comment |
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
Ok great will try how to hide the s3 one allowing only cloudfront. Next is do you know how i can redirect non-www to www using cloudfront? I am hosting a website using cloudfront that gets assets from s3, and i want to redirect all non www to www. What is right way to do this? I have searched over the internet for past 3 hours and nothing works like i want it.
– uberrebu
Jul 24 '16 at 19:26
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
@babababa please don't raise new questions in comments. You may have overlooked this and this and this in your 3 hour search, but tl;dr you need an empty S3 bucket configured to redirect the requests, and a second CloudFront distribution to do this with HTTPS support on the alternate domain from which requests are redirected.
– Michael - sqlbot
Jul 24 '16 at 20:31
1
1
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
@user366914 this answer overlooks one potentially important point -- if you're using any S3 static web site hosting features behind CloudFront, like index and error documents or rewrite rules, you must then be using the web site endpoint for the bucket as the CloudFront origin, and that probably won't work with an origin access identity; this should only work against the bucket's REST endpoint.
– Michael - sqlbot
Jul 24 '16 at 20:48
add a comment |
Is it possible to hide the S3 endpoints from the public so that they
can only access website via the set domain name?
Well, as far as I'm aware, there is no official solution so far, however there is a workaround suggested by AWS. So here is an implementation that worked out for me:
Create an S3 bucket and enabled website hosting. Go to Bucket Policy section of Permissions and enter a policy similar to this one:
"Version": "2012-10-17",
"Statement": [
"Sid": "PublicReadForGetBucketObjects",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::[YOUR_WEBSITE_BUCKET_NAME]/*",
"Condition":
"StringEquals":
"aws:Referer": "[SOME_LONG_SECRET_VALUE]"
]Create CloudFront distribution and configure:
- the following origin:
[YOUR_WEBSITE_BUCKET_NAME].s3-website-[AWS_REGION_NAME].amazonaws.com. Addressing this concern, from CloudFront perspective, this is not an S3 Bucket Origin, but rather just a Custom Origin. - the following Origin Custom Header:
- Header Name:
Referer - Value:
[SOME_LONG_SECRET_VALUE](from your bucket policy)
- Header Name:
- the following origin:
- Configure the rest of your CloudFront distribution settings as usual.
As a result, bucket policy will allow object GETs if only the request contains Referer header with specified secret value, which will block direct request to you S3 website and allow requests sent via CloudFront. And, obviously, you might think of rotating this secret value every now and then.
Please note that by doing this, CloudFront will overwrite Referer header (if present) of any incoming request before forwarding it to the origin, so if you rely on it, this solution won't work.
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
add a comment |
Is it possible to hide the S3 endpoints from the public so that they
can only access website via the set domain name?
Well, as far as I'm aware, there is no official solution so far, however there is a workaround suggested by AWS. So here is an implementation that worked out for me:
Create an S3 bucket and enabled website hosting. Go to Bucket Policy section of Permissions and enter a policy similar to this one:
"Version": "2012-10-17",
"Statement": [
"Sid": "PublicReadForGetBucketObjects",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::[YOUR_WEBSITE_BUCKET_NAME]/*",
"Condition":
"StringEquals":
"aws:Referer": "[SOME_LONG_SECRET_VALUE]"
]Create CloudFront distribution and configure:
- the following origin:
[YOUR_WEBSITE_BUCKET_NAME].s3-website-[AWS_REGION_NAME].amazonaws.com. Addressing this concern, from CloudFront perspective, this is not an S3 Bucket Origin, but rather just a Custom Origin. - the following Origin Custom Header:
- Header Name:
Referer - Value:
[SOME_LONG_SECRET_VALUE](from your bucket policy)
- Header Name:
- the following origin:
- Configure the rest of your CloudFront distribution settings as usual.
As a result, bucket policy will allow object GETs if only the request contains Referer header with specified secret value, which will block direct request to you S3 website and allow requests sent via CloudFront. And, obviously, you might think of rotating this secret value every now and then.
Please note that by doing this, CloudFront will overwrite Referer header (if present) of any incoming request before forwarding it to the origin, so if you rely on it, this solution won't work.
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
add a comment |
Is it possible to hide the S3 endpoints from the public so that they
can only access website via the set domain name?
Well, as far as I'm aware, there is no official solution so far, however there is a workaround suggested by AWS. So here is an implementation that worked out for me:
Create an S3 bucket and enabled website hosting. Go to Bucket Policy section of Permissions and enter a policy similar to this one:
"Version": "2012-10-17",
"Statement": [
"Sid": "PublicReadForGetBucketObjects",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::[YOUR_WEBSITE_BUCKET_NAME]/*",
"Condition":
"StringEquals":
"aws:Referer": "[SOME_LONG_SECRET_VALUE]"
]Create CloudFront distribution and configure:
- the following origin:
[YOUR_WEBSITE_BUCKET_NAME].s3-website-[AWS_REGION_NAME].amazonaws.com. Addressing this concern, from CloudFront perspective, this is not an S3 Bucket Origin, but rather just a Custom Origin. - the following Origin Custom Header:
- Header Name:
Referer - Value:
[SOME_LONG_SECRET_VALUE](from your bucket policy)
- Header Name:
- the following origin:
- Configure the rest of your CloudFront distribution settings as usual.
As a result, bucket policy will allow object GETs if only the request contains Referer header with specified secret value, which will block direct request to you S3 website and allow requests sent via CloudFront. And, obviously, you might think of rotating this secret value every now and then.
Please note that by doing this, CloudFront will overwrite Referer header (if present) of any incoming request before forwarding it to the origin, so if you rely on it, this solution won't work.
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
Is it possible to hide the S3 endpoints from the public so that they
can only access website via the set domain name?
Well, as far as I'm aware, there is no official solution so far, however there is a workaround suggested by AWS. So here is an implementation that worked out for me:
Create an S3 bucket and enabled website hosting. Go to Bucket Policy section of Permissions and enter a policy similar to this one:
"Version": "2012-10-17",
"Statement": [
"Sid": "PublicReadForGetBucketObjects",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::[YOUR_WEBSITE_BUCKET_NAME]/*",
"Condition":
"StringEquals":
"aws:Referer": "[SOME_LONG_SECRET_VALUE]"
]Create CloudFront distribution and configure:
- the following origin:
[YOUR_WEBSITE_BUCKET_NAME].s3-website-[AWS_REGION_NAME].amazonaws.com. Addressing this concern, from CloudFront perspective, this is not an S3 Bucket Origin, but rather just a Custom Origin. - the following Origin Custom Header:
- Header Name:
Referer - Value:
[SOME_LONG_SECRET_VALUE](from your bucket policy)
- Header Name:
- the following origin:
- Configure the rest of your CloudFront distribution settings as usual.
As a result, bucket policy will allow object GETs if only the request contains Referer header with specified secret value, which will block direct request to you S3 website and allow requests sent via CloudFront. And, obviously, you might think of rotating this secret value every now and then.
Please note that by doing this, CloudFront will overwrite Referer header (if present) of any incoming request before forwarding it to the origin, so if you rely on it, this solution won't work.
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
answered Nov 10 '18 at 13:14
Dmitry DeryabinDmitry Deryabin
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f791658%2fcan-i-hide-s3-and-cloudfront-endpoints%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
