2 Answers
- Newest
- Most votes
- Most comments
1
When configuring the S3 Object Lambda Access Point, it was confirmed that an error occurred when the optional Lambda version was specified.
So I solved the problem without specifying the version.
answered a year ago
0
Not specifying Lambda version indeed solved our problem too! The UI is so buggy that, even without choosing the Lambda version, the UI summary still shows version as '$LATEST', however, as long as user did not check the optional version box and did not type the word '$LATEST', it seems to work properly.
answered a year ago
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago