-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lite Version only work by deleting MKVConverterLambda and S3ToKVSLambda #31
Comments
After a day of Headache, it seen that S3ToKVSLambda code is not public or deleted, you need to zip yourself and put into a S3, then change the layout with the new path. |
@BurguerJohn did you make any changes in template_lite.yaml ? |
@Prasang13 I had to: This made the deploy work with both stacks, but full still have some bugs after that. Plus I think that the code in here is different from the ones called by the template, so I suggest perhaps trying to edit all CodeURI to the files inside this GIT. |
@BurguerJohn , did you have to make changes in WebAppBootstrapperLambda CodeUri? I am getting error over there |
I don't remember having any error in it. What error are you getting? |
Regarding CodeURI. By default it is ./dashboard. I don't think this is the proper way. Can you please tell me, what is the correct way? |
I did using the template found in the readme This one already reference files found inside S3. I'm not sure the correct way to use the template found inside this git. |
@BurguerJohn I am getting this error
Even though, I have full access of the bucket |
I had the same confusion, its not your bucket the problem, its this bucket: |
I can't create or see the bucket brain-power-fidgetology-demo-bootstrap |
@BurguerJohn , I solved the above problem. I am facing new issue
Did you encounter this? |
@Prasang13 Sorry, this error did not occur with me, not sure what can be happening. |
@BurguerJohn,
|
I'm also getting
|
By using the lite version, it will give a S3 error. I think this happen because it create the Lambda functions before creating the S3-upload bucket, but i didn't managed to find a way to fix it.
The text was updated successfully, but these errors were encountered: