bug: lambda Add permission accepts non-compliant statement IDs

[wunderbarb]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Statement ID should be [0-9a-zA-z_/-]+ but localstack accepts for instance "example.com"

Expected Behavior

No response

How are you starting LocalStack?

With a docker run command

Steps To Reproduce

	c := lambda.NewFromConfig(cfg)
	api := &lambda.AddPermissionInput{
		Action:              aws.String("lambda:InvokeFunction"),
		FunctionName:        aws.String(arn),
		Principal:           aws.String("events.amazonaws.com"),
		StatementId:         aws.String("example.com),
		EventSourceToken:    nil,
		FunctionUrlAuthType: "",
		PrincipalOrgID:      nil,
		Qualifier:           nil,
		RevisionId:          nil,
		SourceAccount:       nil,
		SourceArn:           aws.String(rnARN),
	}
	_, err = c.AddPermission(context.Background(), api)

Environment

- OS: Ubuntu 20.04
- LocalStack: 1.4.0  pro

Anything else?

No response

[joe4dev]

Hi @wunderbarb Thank you for sharing this missing validation.

We implemented a fix that will become available shortly (as part of PR #7762). We will let you know when it is available in the latest Docker image.

[joe4dev]

Hi @wunderbarb The fix should be available in the latest Docker image. Can you please docker pull localstack/localstack-pro and give it a try?

[localstack-bot]

Hello 👋! It looks like this issue hasn’t been active in longer than two months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.