Adrian Cantrill is a technical course creator who focuses currently on AWS certifications. He's a passionate technical architect and places high importance on actual learning and understanding IT, in particular cloud technology for entrants and veterans in the industry alike. He has high pass-rates from students whom have taken his courses and occasionally publishes lessons for the general public to allow greater access to fundamental tech knowledge that every aspiring or experienced engineer should know.
His full course portfolio can be found here: learn.cantrill.io
Adrian, does this mean that in the previous video, the "writeable layer" that is created would be the tmpfs shown here? Thanks! Also, do you plan to release an EKS Course?
I follow your video from the physical layer until the transport layer and then there were no continuation to the session and application layer which I feel a bit disappointed. The reasons why I follow you through all the videos is they are all very good videos which explains very clearly all the fundamental concepts of the 7 layers of the OSI models. Thanks for your contribution. Maybe you can produce some other cybersecurity subjects. I look forward in seeing you producing the videos concerned. 🤓💙🙇💆♂🦃🍋🍬
Hi Adrian, What does the actual syntax look like on a Fortinet switch (or even a Cisco router)? I have two Direct Connect Links into the same Region from two Fortiswitch Layer 3 switches doing BGP and NO ONE can give me the syntax to accomplish what Amazon said I should apply (based on this below). Both Links come from same Data Center in California to same region in Seattle Washington and subnets are exactly the same when taking either path on both sides. I want to do active/active To control route preferences, Direct Connect supports local preference BGP community tags for private virtual interfaces and transit virtual interfaces. Local preference BGP communities You can use local preference BGP community tags to achieve load balancing and route preference for incoming traffic to your network. For each prefix that you advertise over a BGP session, you can apply a community tag to indicate the priority of the associated path for returning traffic. The following local preference BGP community tags are supported: 7224:7100-Low preference 7224:7200-Medium preference 7224:7300-High preference Local preference BGP community tags are mutually exclusive. To load balance traffic across multiple AWS Direct Connect connections (active/active) homed to the same or different AWS Regions, apply the same community tag; for example, 7224:7200 (medium preference) across the prefixes for the connections. If one of the connections fails, traffic will be then load balance using ECMP across the remaining active connections regardless of their home Region associations . To support failover across multiple AWS Direct Connect connections (active/passive), apply a community tag with a higher preference to the prefixes for the primary or active virtual interface and a lower preference to the prefixes for the backup or passive virtual interface. For example, set the BGP community tags for your primary or active virtual interfaces to 7224:7300 (high preference) and 7224:7100 (low preference) for your passive virtual interfaces. Local preference BGP community tags are evaluated before any AS_PATH attribute, and are evaluated in order from lowest to highest preference (where highest preference is preferred). docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#bgp-communities-private-transit
Thanks !⭐🔥🎊🎉✨ Theory : There are two modes of Docker Networking that you need to understand: ₪ Host Networking ₪ Bridge Networking Host Networking • Let’s start with two Docker Hosts one on the left and one on the right. Inside each host are two containers, all running the same containerized application. Each container uses TCP Port 1337. • In the middle, there’s a person trying to access the containers, and let’s call him Heisenberg. • On the right, we're using Host Networking, where the containers share the network of the host. When you run a container this way, the Host Port is the same as the Container's Port. • For example: • When we run the top container, the application in the container uses Port TCP 1337, and the same port is consumed on the Docker Host. • Heisenberg can access it using the Host IP and Port TCP 1337. • However, problems arise when you attempt to run another container on the same host using the same Docker image and networking mode. It will fail because Port TCP 1337 is already in use on the host. • Host Networking is great if you want to run different containers on a host that use different ports. However, problems start if you need to run multiple versions of the same container. You need to scale horizontally or run multiple versions of the same service for different clients. Bridge Networking • This issue is solved with the second mode of networking, known as Bridge Networking. • In this mode, a bridge network is created separately, and containers can connect to it. Each container gets its own unique IP address on the network. As a result, each container can use the same port because their IP addresses are unique. • For example: • Container 1 has its own IP on the bridge network (IP1). It runs the application on TCP Port 1337. • Container 2 also has its own IP (IP2), and it runs the same application on TCP Port 1337. • Both containers can communicate directly with each other since they're on the same bridge network, but they can't be reached from outside the Docker host unless we publish them. • To make the containers accessible from outside, we publish a container port to a host port, often written as Host Port: Container Port • For example: • Running Container 1 using -P 1337:1337 publishes Container 1's Port 1337 to Host Port 1337, making it accessible to Heisenberg. • We can also publish Container 2, but we can't use Host Port 1337 since it's already used. Instead, we could use -P 1338:1337, which publishes Container 2's Port 1337 to Host Port 1338. KEY POINTS ₪ Host Networking: You don't choose the port mappings, as they aren't needed. Whatever a container uses for its application port is used on the host. It’s simple with no configuration needed but limits you to one of each container on one host. You can run many different containers on the same host as long as they use different ports. ₪ Bridge Networking: Overcomes the limitation of host networking. Your need to publish a port mapping for every container. Each container's port must be mapped to a unique host port.
I rarely comment but this time I can't just go away without saying something. Absolutely cool content. It is like finding a course that teaches hidden knowledge. I rarely see videos go so deep while trying to ensure the viewers do not forget the general view of things. I can see you were doing your best to help people not get confused in the videos with all the acronyms and relationships between different parts of the dns. Thank you for your service!!!
Hi I have one question as what if I want to have a failover to another region in case the primary region fails. So can create a transit gateway peering connection and then can use route 53 private hosted zone for the failover but then the communication between the resources can’t be done via ip address but dns names. Or can I use the floating ip address with two different EC2 instance in different regions. Or I should use simple BGP to failover to different regions in case a IPsec tunnel goes down?? Please reply.
Thanks so much! After watching bunch of videos from other channels, only this playlist helped me to bring all info together and now i start to understand this topic
This guy's AWS courses are dope too. Probably the most thorough and useful course I've taken, they're not free but without a doubt worth every cent. Thanks for helping me get a nice job and out of helldesk Adrian.
This is the best Docker course I've ever seen. I'm just lost for words. If you ever consider creating your Patreon-like community, I will be honoured to be part of it.
I want to first say that I love these videos, and they're helping me so much. But I have a question: How do you determine if the host ID is the second number on the right or the first number on the right in the IP address?
