search

awslabs / ssosync

Populate AWS SSO directly with your G Suite users and groups using either a CLI or AWS Lambda
Apache License 2.0
528 stars 182 forks source link

Lambda Deployment - ssosync: no such file or directory: PathError #84

Closed harrywm closed 2 years ago

harrywm commented 2 years ago

Describe the bug I am using ssosync using a CloudFormation StackSet template, and deployed via terraform resources - a "aws_cloudformation_stack_set" resource to mount the template and an "aws_cloudformation_stack_set_instance" to deploy the application. After some configuration this setup has worked, and I have the application deployed.

Upon a first run of the Lambda function I have been receiving PathError errors from the function.

To Reproduce Steps to reproduce the behavior:

  1. Deploy the application via the CloudFormation StackSet template
  2. Lambda Function is triggered by the Event rule
  3. fork/exec /var/task/dist/ssosync_linux_amd64/ssosync: no such file or directory: PathError null is logged in the Lambda function log stream.

Expected behavior The application runs, Users and Groups are populated in the SSO console.

Additional context I've also tried deprecating the version of the source code used by the function and the same occurs. I'm wondering if due to the way I'm deploying the application there have been some configuration issues, but the infrastructure seems fine and I don't see how my setup would affect the file system of the function.

austbot commented 2 years ago

same here

ChrisPates commented 2 years ago

I've identified the issue here, will be pushing an update (assuming all testing goes to plan) that will resolve this.

ChrisPates commented 2 years ago

The approve path issue has been resolved in this repo additionally, the latest build is available in the Serverless Application Repository : SSOSync