This is a great presentation for engineers to execs to really understand what's happening behind the AWS console. This type of content should be in your docs. Most of what I know about AWS I have to get from video presentations.
Not necessarily. All that gwlb needs is an endpoint for vpc to vpc traffic. If the traffic is flowing from internet to your AWS workloads then you need an ingress available to route them into gwlb appliances.
This used to be not true - where you couldn't configure a more specific route than the local route in a subnet's route table (the local route is the VPC CIDR route via Local). In April 2021 AWS released "routing enhancements" where you can now configure more specific routes than the local route, and direct traffic destined from one subnet to another subnet in the same VPC to a middle box, or like the diagram, a GWLB..
AES-256 is great, unless your chips have been deliberately been diminished in capacity whereas generating random numbers is concerned ... Also, Prism ...
Trn1 - impressive. How about giving back a bit to your certified consultants? They spend hundreds of hours for exams, and on additional training every year promoting your products and services and they don't even get a proper lan yard, sticker, mug or AWS credits to try out new things ... unacceptable and ungreatful for such a big company ... It is like giving a 50c pencil as a bonus to your best sales person ...
This is a great presentation for engineers to execs to really understand what's happening behind the AWS console.
This type of content should be in your docs. Most of what I know about AWS I have to get from video presentations.
Superb presentation! As someone who deals with networking every day, the progress you show through the presentation is amazing.
Great talk
Great sir ! I have learned that are new to me about AWS .....Content and step by step presentation both are very useful .......
31:54 is this a mistake? Without ingress routing, GWLB can not re-direct traffic within a VPC from one subnet to another.
Not necessarily. All that gwlb needs is an endpoint for vpc to vpc traffic. If the traffic is flowing from internet to your AWS workloads then you need an ingress available to route them into gwlb appliances.
This used to be not true - where you couldn't configure a more specific route than the local route in a subnet's route table (the local route is the VPC CIDR route via Local). In April 2021 AWS released "routing enhancements" where you can now configure more specific routes than the local route, and direct traffic destined from one subnet to another subnet in the same VPC to a middle box, or like the diagram, a GWLB..
AES-256 is great, unless your chips have been deliberately been diminished in capacity whereas generating random numbers is concerned ...
Also, Prism ...
Trn1 - impressive. How about giving back a bit to your certified consultants? They spend hundreds of hours for exams, and on additional training every year promoting your products and services and they don't even get a proper lan yard, sticker, mug or AWS credits to try out new things ... unacceptable and ungreatful for such a big company ... It is like giving a 50c pencil as a bonus to your best sales person ...