Love your analogy of reaching VPC endpoints is analogous to having a backdoor connection to next house (as opposed to going all the way out of the house, out of neighborhood, into the city and reaching the next door house). Kudos to the analogyMaN!
Just when i was thinking abt how to decide between gw ep vs interface ep for aws s3 , you answered it , thank you.. hopefully the exam does not give both in the same query.🤔🧐
Something that I did not understand is, why they "invent" two type of interface ? Suppose that they "invent" Gateway interface first, what does its problems or limitations that pushed them to create/invent the interface endpoint ?
Was hunting for this video..lol i understand ENI's are setup for EC2's but here ENI's are configured at subnet level .. Multiple eni's can be attached to a single ec2? is there a limit or any dependency on the ec2 capacity or configuration? a little confused, going through the shared links now..
Thank you Mr.Ashish for the great, simple and easily understandable explanation
Love your analogy of reaching VPC endpoints is analogous to having a backdoor connection to next house (as opposed to going all the way out of the house, out of neighborhood, into the city and reaching the next door house).
Kudos to the analogyMaN!
Thank You ! This is Very easy to remember!
Just when i was thinking abt how to decide between gw ep vs interface ep for aws s3 , you answered it , thank you.. hopefully the exam does not give both in the same query.🤔🧐
Something that I did not understand is, why they "invent" two type of interface ? Suppose that they "invent" Gateway interface first, what does its problems or limitations that pushed them to create/invent the interface endpoint ?
Liked it👍
Was hunting for this video..lol
i understand ENI's are setup for EC2's but here ENI's are configured at subnet level ..
Multiple eni's can be attached to a single ec2? is there a limit or any dependency on the ec2 capacity or configuration? a little confused, going through the shared links now..