Closed bijanmmarkes closed 4 years ago
I've resolved the above issue by updating the s3 endpoint format to the following:
"TemplateURL": {
"Fn::Sub": "https://${pS3}.s3-us-west-2.amazonaws.com/${pSourceFolder}/mediastore.template"
}
It seems the previous endpoint format may have been deprecated, perhaps it should be updated with a PR. @wizage
But now I'm getting this error:
CREATE_FAILED rMP AWS::CloudFormation::Stack Wed Dec 18 2019 04:36:15 GMT-0800 (Pacific Standard Time) S3 error: Access Denied For more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
Is this package still being developed or should it be working? I'm confused. Shouldn't amplify/the video plugin take care of all of this stuff?
The AWS profile I'm using has administrator and S3 administrator access.
This shouldn't be issue as we are following the same methodology use across the amplify CLI:
This seems to be like a fluke that has happened with other resources that have been created using the CLI: https://github.com/aws-amplify/amplify-cli/issues/2732 https://github.com/aws-amplify/amplify-cli/issues/2619
Can you try to run amplify delete
and then try to create a video resource again.
Thanks, @wizage, that seems to have worked, but I don't see how... I believe that depending on the options chosen during the video add
, it throws errors.
From the looks of it, this is not a mobile SDK? I don't see a way to incorporate this code into my project, it seems like all the streaming occurs from the CLI?
It is an error with how S3 propagates. The regional S3 is available immediately but the non regional one (the first error), takes up to 24 hours iirc.
As far as SDK that is correct. This is not at all a SDK or library. We are working on creating library components for livestreaming and video player for it later. For now though it just creates the entire backend and you have to write your own code to integrate with the outputs.
Thank you for all your help @wizage. Looking forward to the future progress of this. Glad someone is working on it. 👍 I guess I'll be using WebDav and custom code for now.
Describe the bug I've tried all combinations of
amplify add video
ranging fromyes/no
for create a distribution,autostart: yes/no
, all types of methods. In the end, all combinations of enabling/disabling options end with error:When I add create distribution I receive even more errors, which I'm assuming are all linked to the first failure of S3:
S3 error: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
To Reproduce Steps to reproduce the behavior:
amplify init
amplify add video
amplify push
Expected behavior I expect it to push resources to the cloud, what am I missing? I followed exact instructions from the
README.MD
.Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Template file: