aws-solutions / simple-file-manager-for-amazon-efs

Serverless web application to manage data in your Amazon EFS Filesystem
Apache License 2.0
79 stars 30 forks source link

The following resource(s) failed to create: [RestAPI]. #186

Closed SamuelLarkin closed 1 year ago

SamuelLarkin commented 1 year ago

Describe the bug I'm trying to launch a Simple File Manager for Amazon EFS but it fails with EFSFileManagerAPI

Embedded stack arn:aws:cloudformation:ca-central-1:IDIDIDIDIDID:stack/EFSAccessor-EFSFileManagerAPI-
  1W4QUA1DG6MRC/XXXXXXXX-6c41-11ed-9c09-0e965e613246 was not successfully created: The following resource(s) failed to
  create: [RestAPI].

To Reproduce

Expected behavior I expect the stack to deploy completely without error.

Please complete the following information about the solution:

SamuelLarkin commented 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)
simonkrol commented 1 year ago

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.