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

Missing prerequisites on deployment guide

Closed this issue · 3 comments

andres-lindo commented

Describe the bug
Tried to deploy the solution with no error on the CloudFormation stack, however when using the solution the following error appears on Lambda execution logs, being unable to create the file system endpoint.

api - ERROR - An error occurred (ValidationError) when calling the DescribeStacks operation: Stack with id efs-manager-ManagedResources-fs-1a862b98 does not exist

I followed this guide: https://docs.aws.amazon.com/solutions/latest/simple-file-manager-for-amazon-efs

To Reproduce
-Launch the stack
-Reset auto-generated password
-Create a file manager Lambda function (never creates file manager)

Expected behavior
The File System ID link previously labeled false now returns true and the file system ID is now an active link.

Please complete the following information about the solution:

  • 1.4.0

To get the version of the solution, you can look at the description of the created CloudFormation stack. If the description does not contain the version information, you can look at the mappings section of the template:

Mappings:
  SourceCode:
    General:
      S3Bucket: "solutions"
      KeyPrefix: "simple-file-manager-for-amazon-efs/v1.0.4"
  • [eu-west-1 ] Region: [e.g. us-east-1]
  • [ No] Was the solution modified from the version published on this repository?
  • If the answer to the previous question was yes, are the changes available on GitHub?
  • [Yes] Have you checked your service quotas for the sevices this solution uses?
  • [Yes] Were there any errors in the CloudWatch Logs?
  • api - ERROR - An error occurred (ValidationError) when calling the DescribeStacks operation: Stack with id efs-manager-ManagedResources-fs-1a862b98 does not exist

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

brandold commented

Hi @andres-lindo, were you able to verify if the stack "efs-manager-ManagedResources-fs-1a862b98" was present in the CloudFormation console?

I'd be curious to know if the error you received is the root cause or just a result of something else. Checking if the stack was actually created will help figure that out.

dreamorosi commented

The root cause was the fact that the EFS file system didn't have a mount target which in turns means it didn't have indication of subnetId nor security groupId which are both required parameters for the creation of the proxy stack.

Andres is a colleague of mine and in this case he was just testing out the solution. The guide assumes that Customers already have an EFS file system deployed and all mount targets + Security Groups are in place. It'd be great to clarify this point in the guide.

simonkrol commented

This documentation change appears to have made it into the limitations section of the Implementation Guide. Closing.