Closed SamuelLarkin closed 1 year ago
I accidentally managed to briefly catch a glance of an intermediate substack that had the following error.
EFSAccessor-EFSFileManagerAPI-BR0M9S01XHV6
RestAPI
User: arn:aws:iam::IDIDIDIDIDID:user/ME is not authorized to perform: apigateway:POST on resource: arn:aws:apigateway:ca-central-1::/restapis because no iden tity-based policy allows the apigateway:POST action (Service: AmazonApiGateway; Status Code: 403; Error Code: AccessDeniedException; Request ID: ab2a8d19-8b5f-433 4-a291-b4802a75f519; Proxy: null)
Hi @SamuelLarkin, thanks for your patience here.
In order to deploy the RestAPI included as part of the Simple File Manager CloudFormation template, you are required to have the apigateway:POST permission, please check to ensure that your user has that permission.
Please either open a new issue or respond here if you continue to run into problems.
Thanks, Simon
edit: As a helpful tip, there is a dropdown on the Cloudformation stack page which should let you show deleted stacks. This will let you see stacks that failed and were deleted without having to catch them in the act.
Describe the bug I'm trying to launch a Simple File Manager for Amazon EFS but it fails with
EFSFileManagerAPI
To Reproduce
Launch in the AWS Console
Stack Name
AdminEmail
Next
Submit
CloudFormation
/Stack Detail
/Events
for the error message underEFSFileManagerAPI
Expected behavior I expect the stack to deploy completely without error.
Please complete the following information about the solution:
v1.5.0
[ca-central-1 ]
[No] Was the solution modified from the version published on this repository?
[N/A] If the answer to the previous question was yes, are the changes available on GitHub?
[No] Have you checked your service quotas for the sevices this solution uses?
[ ] Were there any errors in the CloudWatch Logs?