Skip to content

Conversation

@shinzero999
Copy link

No description provided.

@shinzero999 shinzero999 marked this pull request as draft December 12, 2025 05:53
@limwz01
Copy link

limwz01 commented Dec 24, 2025

I can confirm that this fix makes osls work again with AWS Lambda with runtime python3.12 (which uses NodeJS 24). For those who are stuck waiting for 1 hour, before you try to delete the stack, replace the handler with an "always success" handler generated by AI. Moreover, for your sanity in the future, you could edit the osls code to give a more sensible value for the service timeout. For example, for custom S3 resource you could edit lib/plugins/aws/package/compile/events/s3/index.js to add the ServiceTimeout parameter:

              customS3Resource = {
                [customS3ResourceLogicalId]: {
                  Type: 'Custom::S3',
                  Version: 1.0,
                  DependsOn: [eventFunctionLogicalId, customResourceFunctionLogicalId],
                  Properties: {
                    ServiceToken: {
                      'Fn::GetAtt': [customResourceFunctionLogicalId, 'Arn'],
                    },
                    ServiceTimeout: 60,
                    FunctionName,
                    BucketName: bucket,
                    BucketConfigs: [
                      {
                        Event: notificationEvent,
                        Rules: rules,
                      },
                    ],
                    ...(forceDeployProperty && { ForceDeploy: forceDeployProperty }),
                  },
                },
              };

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants