Closed ianic closed 2 years ago
It's pretty much ok in the current version:
mantil aws install --aws-profile org5
Installing setup stack: 50% (2/4)
Error: could not create stack mantil-setup-41c1c71b - MantilSetupLambda - Resource handler returned message: "Your access has been denied by S3, please make sure your request credentials have permission to GetObject for mantil-releases/dev/ianic/v0.2.6-1-g5b160c2/setup.zip. S3 Error Code: AccessDenied. S3 Error Message: Access Denied (Service: Lambda, Status Code: 403, Request ID: a552d1e7-ebd5-4630-bb3a-18fcca7691e6, Extended Request ID: null)" (RequestToken: 9bd05575-59a3-8609-35f0-8f65588300b5, HandlerErrorCode: AccessDenied)
Error: installing setup stack failed
This error is only shown in development when a developer is running non released Mantil version and didn't make deploy which creates S3 objects required for creating node. From S3 we get access denied but we all know that means object not found ;).
Source of the problem is that I started aws install without deploying functions to s3.
It fails with:
log: