AWS Managed Prefix Lists | DEMO | Usage with Transit Gateway | Customer-managed Prefix Lists

[@ravipapetla]

Good video and very clear explanation

[@teehammed9580]

Great video! The explanation is really clear and easy to understand. Just to note that you can now refer to a prefix list in your transit gateway route table. It probably wasn't an option when this video was recorded, but it is now.

[@sagarsriva]

great video

[@amitrockstar4676]

Good sir thank you so much

[@christianibiri]

Great video!

[@knowledgeindia]

Thank you 👍I hope you continue to learn from our videos.

[@indrajitg4729]

Another great video thanks a lot. One question - if I have multiple accounts connecting to a central account (through TGW) where a server is hosted and it needs to be accessed over say port 22 from other spoke accounts -- then creating only 1 prefix list with all those source IP addresses from spoke accounts will be enough ? as long as I share the prefix list with all the accounts (central as well as spoke).

[@meghagn4553]

can u upload a video on setting up of EKS on AWS or AKS on Azure ?

[@ZampGaming]

I created a security group and a prefixed list, when I am trying to add that prefix list to an inbound rule in my security group I get this error: The maximum number of rules per security group has been reached. I do not have any other rules in the security group and neither in any other group. I made prefix list with one entry and also tried without any entry but still getting same error.

[@jamesren4949]

The Security Group has a default limit of 60 entries. If you have more than 60 entries in your prefix list or your prefix list is set to have max more than 60, I think it might explain why you had this error.