AWS Amplify CLI creates inaccessible bucket for hosting
I have got a strange problem with the Amplify CLI. When adding hosting to my angular app through
amplify hosting add
and subsequently calling
amplify publish
the link provided at the end of the process links to a webpage that just shows an XML document telling me the access was denied. What is happening here? It seems to me like the hosting bucket has a wrong policy attached, but why would the amplify CLI create a private bucket?
Can someone shed some light here?
Here is the bucket policy created by the CLI:
{
"Version": "2012-10-17",
"Id": "MyPolicy",
"Statement": [
{
"Sid": "APIReadForGetBucketObjects",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity xxx"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::xxx/*"
}
]
}
amazon-web-services amazon-s3 command-line-interface aws-amplify
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
add a comment |
I have got a strange problem with the Amplify CLI. When adding hosting to my angular app through
amplify hosting add
and subsequently calling
amplify publish
the link provided at the end of the process links to a webpage that just shows an XML document telling me the access was denied. What is happening here? It seems to me like the hosting bucket has a wrong policy attached, but why would the amplify CLI create a private bucket?
Can someone shed some light here?
Here is the bucket policy created by the CLI:
{
"Version": "2012-10-17",
"Id": "MyPolicy",
"Statement": [
{
"Sid": "APIReadForGetBucketObjects",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity xxx"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::xxx/*"
}
]
}
amazon-web-services amazon-s3 command-line-interface aws-amplify
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
add a comment |
I have got a strange problem with the Amplify CLI. When adding hosting to my angular app through
amplify hosting add
and subsequently calling
amplify publish
the link provided at the end of the process links to a webpage that just shows an XML document telling me the access was denied. What is happening here? It seems to me like the hosting bucket has a wrong policy attached, but why would the amplify CLI create a private bucket?
Can someone shed some light here?
Here is the bucket policy created by the CLI:
{
"Version": "2012-10-17",
"Id": "MyPolicy",
"Statement": [
{
"Sid": "APIReadForGetBucketObjects",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity xxx"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::xxx/*"
}
]
}
amazon-web-services amazon-s3 command-line-interface aws-amplify
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
I have got a strange problem with the Amplify CLI. When adding hosting to my angular app through
amplify hosting add
and subsequently calling
amplify publish
the link provided at the end of the process links to a webpage that just shows an XML document telling me the access was denied. What is happening here? It seems to me like the hosting bucket has a wrong policy attached, but why would the amplify CLI create a private bucket?
Can someone shed some light here?
Here is the bucket policy created by the CLI:
{
"Version": "2012-10-17",
"Id": "MyPolicy",
"Statement": [
{
"Sid": "APIReadForGetBucketObjects",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity xxx"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::xxx/*"
}
]
}
amazon-web-services amazon-s3 command-line-interface aws-amplify
amazon-web-services amazon-s3 command-line-interface aws-amplify
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
edited Nov 14 '18 at 11:50
R. Richards
14.3k93742
14.3k93742
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
asked Nov 14 '18 at 11:21
ppgcc74ppgcc74
9010
9010
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I just encountered this as well. If I go into the Cloudfront distribution and update the origin to include an Origin Path pointing to the main subdirectory in the S3 bucket (folder is the same name as the Amplify project), the problem appears to be resolved.
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53299040%2faws-amplify-cli-creates-inaccessible-bucket-for-hosting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just encountered this as well. If I go into the Cloudfront distribution and update the origin to include an Origin Path pointing to the main subdirectory in the S3 bucket (folder is the same name as the Amplify project), the problem appears to be resolved.
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
add a comment |
I just encountered this as well. If I go into the Cloudfront distribution and update the origin to include an Origin Path pointing to the main subdirectory in the S3 bucket (folder is the same name as the Amplify project), the problem appears to be resolved.
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
add a comment |
I just encountered this as well. If I go into the Cloudfront distribution and update the origin to include an Origin Path pointing to the main subdirectory in the S3 bucket (folder is the same name as the Amplify project), the problem appears to be resolved.
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
I just encountered this as well. If I go into the Cloudfront distribution and update the origin to include an Origin Path pointing to the main subdirectory in the S3 bucket (folder is the same name as the Amplify project), the problem appears to be resolved.
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
answered Nov 29 '18 at 19:11
CyDhartthaCyDharttha
497
497
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53299040%2faws-amplify-cli-creates-inaccessible-bucket-for-hosting%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
