AWS Serverless Demo - Resizing S3 Images With AWS Lambda Trigger

แชร์
ฝัง
  • เผยแพร่เมื่อ 4 ต.ค. 2024
  • Images stored using Amazon S3 are often processed into multiple sizes to fit within the design constraints of a website or mobile application. It’s a common approach to use S3 event notifications and AWS Lambda for eager processing of images when a new object is created in a bucket.
    I have created a hands on exercise to create image thumbnails on the fry using JIMP and AWS Serverless.
    Instead of processing and resizing images into all necessary sizes upon upload, the approach of processing images on the fly has several upsides:
    Increased agility
    Reduced storage costs
    Resilience to failure
    You may download the source code used this this demo from below link
    github.com/abr...
    Have a look at JIMP package documentation below,
    www.npmjs.com/...
    Watch my below video if you want to configure AWS CLI.
    • How to configure AWS C...
    AWS Serverless Demo
    S3 Image Resize
    Lambda Function Demo
    JIMP Image Manipulation
    AWS CloudWatch
    S3 Event Notification
    AWS Tutorials

ความคิดเห็น • 20

  • @d1nonlystalker
    @d1nonlystalker 3 หลายเดือนก่อน +1

    Save my day in less that 30 minutes...!!
    Nice one...!!

    • @w3cloudstudio
      @w3cloudstudio  3 หลายเดือนก่อน

      Glad to hear that!

  • @vishnuvijayan3459
    @vishnuvijayan3459 หลายเดือนก่อน

    Thank You Very Much.. !! I was looking for this type of tutorials .. !! You are a real life saver.. !! I expect more from your side... !!

  • @danielugot
    @danielugot 5 หลายเดือนก่อน +1

    Great learning on this hands-on. Many thanks.
    Please I could not complete the hands-on because I did not get the complete line of code to push to my lambda function.
    I will appreciate getting the remaining line of code. Thank

    • @w3cloudstudio
      @w3cloudstudio  5 หลายเดือนก่อน +1

      Sorry for the inconvenience where I did not notice part of my commands are not visible due to my cam position, please find below my complete command.
      aws lambda update-function-code --function-name ImageManipulator --s3-bucket studio-bkt-7 --s3-key index.zip --publish
      pls refer below article to know more on this,
      awscli.amazonaws.com/v2/documentation/api/latest/reference/lambda/update-function-code.html

    • @danielugot
      @danielugot 5 หลายเดือนก่อน

      @@w3cloudstudio I really appreciate. Thank you for the link to read up on update-function-code.

  • @harshal_joshi
    @harshal_joshi 6 หลายเดือนก่อน +1

    .easy to understanding Thanks

    • @w3cloudstudio
      @w3cloudstudio  6 หลายเดือนก่อน

      Thank you for your feedback.

    • @harshal_joshi
      @harshal_joshi 6 หลายเดือนก่อน

      @@w3cloudstudio plz Shere more like this video

    • @w3cloudstudio
      @w3cloudstudio  6 หลายเดือนก่อน +1

      ​@@harshal_joshi sure, you may please subscribe to this channel in order to keep informed on new videos.

    • @harshal_joshi
      @harshal_joshi 6 หลายเดือนก่อน

      @@w3cloudstudio can you made video like docker and kubernetes and some AWS vide

    • @harshal_joshi
      @harshal_joshi 6 หลายเดือนก่อน

      @@w3cloudstudio yes definitely your video information and easy to understand

  • @hardeepshiyani
    @hardeepshiyani 2 หลายเดือนก่อน

    Why you are putting nodemodules of awe-sdk where it doesn’t require lambda?

  • @R.Yuvashri
    @R.Yuvashri 3 หลายเดือนก่อน

    I didn't got error in your code but then I didn't got the resized image in my destination bucket why?

  • @krishnawaghmode2120
    @krishnawaghmode2120 4 หลายเดือนก่อน +1

    nice explain👌 please explain video mp4 upload to convert multi bitrate eg. video-720.mp4,video-480.mp4 save s3 bucket

    • @w3cloudstudio
      @w3cloudstudio  4 หลายเดือนก่อน

      Thanks, we shall look into it soon!

  • @R.Yuvashri
    @R.Yuvashri 3 หลายเดือนก่อน

    I got invoke error, access denied error why?

    • @w3cloudstudio
      @w3cloudstudio  3 หลายเดือนก่อน

      Hi, it will work fine if you follow exactly, i think you might have missed some lambda permissions, please review the policy and role and ensure buckets have read write permissions.