fix: add lambda:InvokeFunction permission for function URLs

[dongwonnn]

Summary

Hello! While running the SST example, I encountered a 403 Forbidden error when accessing the deployed CloudFront URL.

After investigation, I found that starting October 2025, AWS Lambda function URLs require both lambda:InvokeFunctionUrl and lambda:InvokeFunction permissions in the resource-based policy.

The current implementation only grants lambda:InvokeFunctionUrl, which causes AccessDeniedException when invoking the function URL.

Changes

• Added lambda:InvokeFunction permission alongside the existing lambda:InvokeFunctionUrl permission
• Added AnyPrincipal to the existing IAM imports for cleaner code

Reference

• AWS Documentation: Control access to Lambda function URLs

Starting in October 2025, new function URLs will require both lambda:InvokeFunctionUrl and lambda:InvokeFunction permissions.

Test

• Deployed the example using npx sst deploy
• Verified the CloudFront URL returns 200 OK instead of 403 Forbidden

[changeset-bot]

⚠️ No Changeset found

Latest commit: a252f40

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR