Serverless, Seamless, Secure: Payment Integration with Razorpay & Serverless Framework! 🔒💸

Поделиться
HTML-код
  • Опубликовано: 23 окт 2022
  • Serverless Payment Integration | Razorpay | Serverless Framework | S3, Cloudfront, Secrets, Lambda
    In this video, we will look a Payments Integration flow with Razorpay.
    We will build APIs using Lambda (with Serverless Framework). For the frontend, we will build a React UI with Chakra UI.
    All of these resources will be deployed via Serverless Framework. This is PURELY serverless and is a true pay go.
    As a bonus, we will also see how to use secrets from AWS Secrets Manager within the Serverless Framework yml.
    GitHub Repo:
    Frontend: github.com/imdurgadas/serverl...
    Server: github.com/imdurgadas/serverl...
    React UI is inspired by video published by '6 Pack Programmer'.
    Notice:
    Logo's used are trademarks or registered trademarks of AWS, Razorpay, Serverless. This video is not accredited, certified, affiliated with, nor endorsed by the community.
    #serverless #razorpay #payment #paymentintegration #lambda #s3 #staticwebsite #cloudfront #secretsmanager #payasyougo #developers #upskill #cloud #tutorial #javascript
  • НаукаНаука

Комментарии • 4

  • @rishushrivastav4591
    @rishushrivastav4591 Год назад

    What have you done for cloudformation? I found it difficult as to what permissions are needed for it.

    • @durgadaskamath
      @durgadaskamath  Год назад

      What issues are you getting ? In the video setup, I have iam user which has admin access which is used by serverless framework to create the cloud formation resources.

    • @rishushrivastav4591
      @rishushrivastav4591 Год назад

      @@durgadaskamath yeah if you give admin it works what i wanted to do was create a serverless framework policy which has limited access to only what is needed eg: cloudformation accesses etc.. also serverless doesn't mention what permissions are precisely required.

    • @durgadaskamath
      @durgadaskamath  Год назад

      @@rishushrivastav4591 Reason is - the resources that needs to be configured depends on what you define in the yaml. For eg you may have dynamodb requirement so its all dependent on one's workload.