This was one of the best presentation that I ever saw at re:Invent. Thank you Pratibha for sharing this bunch of information in a simple way that everybody could understand.
Pratibha , The way you explained the concept is pretty clear and even without any computer background person can understand , Thank you for presenting very nicely.
I was lucky enough to have attended this session in-person. The presenter, Pratibha (GM at AWS), was awesome. I got to ask here some questions after the session too about their intention to add UDP to the ALB. Wow, Pratibha left AWS and went to Google. Shocking.
So in a way @15:10 you are saying that having 2 classic load balancers architecture for content based routing is great taking blast radius in consideration
Layer 4 is the transport layer of the OSI model, but it deals in network protocols rather than application protocols. You are correct, but I guess they are flexible with the naming of the load balancer rather than calling it a transport load balancer.
can some one answer why there is no single public IP or single private ip .. when you have ec2s are in different available zones... unlike Azure... this is a big big big limitation...
@@subhashgangidi we have a situation , lets say you want to host a landing page (hosted on s3 as static site) with abc.com domain , you also want to host another application that needs to be accessible at abc.com/console (hosted using containers) , any solution for this use case ? currently I am using nginx container to proxy pass to S3 , this helps me to host Static page and application under same domain name abc.com
There is no architecture visibility and no troubleshooting tools like ping, trace route and packet capture. Also ip overlapping does not work in vpc peering.
@AWS at minute 3:44, on the slide, it says "Layer 4 network" I believe you meant to type "layer 4 Transport", hopefully no one who created the OSI model is watching this video, otherwise they would probably kick your behind.
good presentation but it was quite distressing to listen to this lady for almost an hour. It seemed to me that she has some respiratory issues. She went through the whole presentation fighting for a breath, as it were her last one...
![AWS re:Invent 2018: [REPEAT 1] Deep Dive and Best Practices for Amazon Redshift (ANT401-R1)](http://i.ytimg.com/vi/TJDtQom7SAA/mqdefault.jpg)
![AWS re:Invent 2018: [REPEAT 1] Deep Dive and Best Practices for Amazon Redshift (ANT401-R1)](/img/tr.png)
This was one of the best presentation that I ever saw at re:Invent. Thank you Pratibha for sharing this bunch of information in a simple way that everybody could understand.
@Davina Gasiorowski op h my in
she has the knowledge on the technology and the skills to teach, I want to learn more with her. Super helpful
Pratibha , The way you explained the concept is pretty clear and even without any computer background person can understand , Thank you for presenting very nicely.
I was lucky enough to have attended this session in-person. The presenter, Pratibha (GM at AWS), was awesome. I got to ask here some questions after the session too about their intention to add UDP to the ALB. Wow, Pratibha left AWS and went to Google. Shocking.
Great presentation Parthiba. Crisp, succinct and down to the detail without boring the audience.
You remind me my engineering teacher, whom i respect a lot.
simplicity with knowledge at its height.
Pratibha, this presentation has significantly improved my understanding of ALB/NLB's. Much appreciated.
Awesome presentation Pratibha and Will. So much information in such a short span of time.
Absolutely amazing, full of knowledge and to the point and on top of that she is GM.
This is what I needs. Thanks for explaing in the simplest way possible. Nice presentation slids too
Awesome presentaion , very clear and in-depth knowledge of ALB
This was one of the best presentation I have ever seen.Thank you for sharing !
Very nice presentation Pratibha and thank you aws for sharing such deep information in a very simple way.
Great information for us budding AWS solutions architects.
Amazing video. Thank you so much Pratibha for sharing this.
Brilliant. Really enjoying the re:Invent videos.
I think I need to attend an AWS Summit!
This was an excellent presentation. You were like one of my professors back in the college. Thank you :)
Very detailed presentation, worth watching.
So in a way @15:10 you are saying that having 2 classic load balancers architecture for content based routing is great taking blast radius in consideration
Amazing video. Thank you so much Pratibha Maam .
Awesome presentation. Thanks Pratibha
Hello, Nice presentation but at 3:37 says Layer 4 as Network but it should be Transport, might be a Typo.(hope am not wrong :) )
No, it's correct, it should be Network.
Layer 4 is the transport layer of the OSI model, but it deals in network protocols rather than application protocols. You are correct, but I guess they are flexible with the naming of the load balancer rather than calling it a transport load balancer.
Thanks a lot madam ... it's easy to understand
can alb be used for url rewriting urls, similar to what an apache or nginx rewrite does?
big kudos on support for dual stack on ALB
Excellent presentation and content
can some one answer why there is no single public IP or single private ip .. when you have ec2s are in different available zones... unlike Azure... this is a big big big limitation...
Awesome. Thanks!
What's missing with ALB is setting up s3-based websites as targets.
S3 hosted sites are highly available by nature. Curious, what's the possible use case to use ELB with S3 hosted website?
@@subhashgangidi we have a situation , lets say you want to host a landing page (hosted on s3 as static site) with abc.com domain , you also want to host another application that needs to be accessible at abc.com/console (hosted using containers) , any solution for this use case ? currently I am using nginx container to proxy pass to S3 , this helps me to host Static page and application under same domain name abc.com
Namaste! 🙏🏽
There is no architecture visibility and no troubleshooting tools like ping, trace route and packet capture. Also ip overlapping does not work in vpc peering.
Good presenation
Great Job except when she introduces the Netflix guy as the Facebook guy. LOL
GREAT MA'AM THANKS ...
Best video
First time I heard someone telling "es kee-u el" (SQL) and not "si kee-u el" (CQL) that I consider incorrect!
But admit that she has immense knowledge
Cringe when she introduced the guy from Netflix as from Facebook. Was a really good presentation though!
@AWS at minute 3:44, on the slide, it says "Layer 4 network" I believe you meant to type "layer 4 Transport", hopefully no one who created the OSI model is watching this video, otherwise they would probably kick your behind.
good presentation but it was quite distressing to listen to this lady for almost an hour. It seemed to me that she has some respiratory issues. She went through the whole presentation fighting for a breath, as it were her last one...
randsonian I did not notice anything