![]() ![]() Once you’re in, just copy the S3 thumbnail sample code from AWS docs and shove it down Sigma’s throat. ![]() (Flattery aside, you do need a Sigma account in order to access the IDE.) Have a look at this small guide to get going. If you haven’t already, now is a great time to sign up for Sigma so that we could start inspiring you with the awesomeness of serverless. So all we have to do is to grab the original source, paste it into Sigma, and make some adjustments and drag-and-drop configuration stuff-and Sigma will understand and handle the rest. This relies on certain syntactic guidelines being followed in the code, which-luckily-are quite simple and ordinary. In this discussion, let’s take a more hands-on approach: grabbing the code from the original thumbnailing sample, pasting it into Sigma, and deploying it into AWS-the exact same thing that got me running around the block, the last time I tried.Īs you may know, Sigma manages much of the “behind the scenes” stuff regarding your app-including function permissions, trigger configurations and related resources-on your behalf. Deploying it should take just a few minutes, as per the Readme, if you dare. Sigma already comes with a ready-made version of the S3 thumbnailing sample. Let’s see what Sigma could do, to make your serverless life easy. And they built Sigma to make it a reality. While the blame for most of those stupid mistakes is on my own laziness, over-esteem and lack of attention to detail, I personally felt that getting started with a leading serverless provider should not have been that hard.Īnd so did my team at SLAppForge. In case you hadn’t noticed already, I have been recently babbling about the pitfalls I suffered when trying to get started with the official AWS lambda-S3 example.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |