AWS Fargate Tutorial and Demo with API Gateway and Amplify | reInvent 2020 Fargate Amplify Feature

[@gymcoding]

Thank you. It was very helpful.

[@itsvikrams]

How does load balancing works with respect fargate containers with out ELB?

[@hemanthp]

@Cloud With Raj any thoughts on this ?

[@oleksandrgolovatyi8447]

That's an amazing demo. Thank you! Would be good to have it extended with an example of multi stage deployments based on cloud map discovery.

[@cloudwithraj]

Great suggestion, will keep this in mind for future videos!

[@andresgonzalezaragon5689]

Thanks!

[@cloudwithraj]

WOW! Thank YOU so much for the generous tip. I am so glad you found the content useful. Happy holidays. Keep learning and keep rocking 👊

[@VivekVhatkar-z3m]

Do you have any video that explains API Gateway(Rest API)->NLB-(with VPC Link)>ALB->ECS->Fargate

[@mzw8374]

What is the best practice, with LB or just with API GW? what if we use both to ECS?

[@vijaynaidun]

Awesome. Container is a run time term, "Image" is the packed app in ECR ?

[@cloudwithraj]

Yes, you are right Vijay

[@ameyapathak2008]

Hey Raj nice video 📸📸📸

[@cloudwithraj]

Thanks Ameya!

[@ameyapathak2008]

@@cloudwithraj sir am a mainframe guy like u... want to change to AWS devops like you.. please guide 🙏🏼🙏🏼

[@EricCanton]

Provides no details on setting up the Fargate Task + VPC + CloudMap backend, which is the only thing I wanted to know from this video.

[@dillon9347]

But how to create all of these components and infrastructure using Amplify if I already have an existing API project? Also not even a mention of the default Amplify API codebase and how to change?

[@ytuser659]

Is there TLS involved between API GW and the ECS service? If yes, where does it get terminated? If not, would using ALB+NLB or just NLB between Gateway and ECS make the communication fully TLS?

[@Bandla.Tarakesh]

I am not getting this option API Gateway + AWS Fargate (Container-based) using amplify

[@mertcancam]

Keep up the good work!

[@cloudwithraj]

Thanks brother

[@roboprofit2548]

How do you Change the ECS task definition to deploy Fargate with a custom vcpu? Editing conatainerXXXXX-cloudformation-template.json doesn't work because "amplify push" overwrites the json file back to the default

[@manasmehrotra6794]

Do we still need vpc link if api-gateway is running inside vpc ? (same as fargate)

[@cloudwithraj]

API Gateway can't be attached to your VPC, hence you need the private link for private integration.

[@altamashakhtar4719]

Hello Raj, Your lessons are amazing. It helped me a lot. I followed your API gateway lessons, and I was able to route traffic to my Fargate service(with cloud-map) with custom domain and mutual TLS enabled. All credit goes to you and your Videos. :-) :-) However in the above setup , I am stuck at a situation where I want to allow only request form a desired set of IPs , I initially thought of using AWS WAF , but apparently AWS WAF is not supported as of now for HTTPs API. I even tried adding a security group in my VPC link and Whitelist only the desired IPs but still my endpoint was publicly accessible :) It would be great if you can suggest me a way to solve this :) I am soo close of finding a great solution for my use case. Need some help . :-)

[@cloudwithraj]

You can use API Resource policy OR a more sophisticated version would be to use CloudFront with WAF in front of the HTTP API (Not API gateway managed, rather you manage the CloudFront and point to your HTTP API)

[@altamashakhtar4719]

@@cloudwithraj Thanks for the reply :) I did consider using a WAF + Cloudfront but as of now I have added a lambda Authorizer which compares the sourceIP with the desired set of IPs :) Thanks again :) Your videos genuinely helped me a lot :) Keep it up :))

[@chauhansunil0409]

Just a suggestion, try to speak clearly. Don't try to flaunt your accent. Really sucks.

[@alipatel528]

Shut up