Hello, and welcome to this presentation of the STM32F7 safety support. It covers the requirements for compliance with safety standards and how ST microelectronics helps customers targeting safety for their projects. Safety requirements for electronic devices increase permanently as the use of electronic control systems expands into the huge range of human activities. The massive expansion of these devices requires their compliance with specific safety standards. The primary goal is to prevent human death or injury, as well as environmental damage. But there are many other important factors at a lower level, such as the devaluation of an industrial process, including the loss of important data, connections, power or control, and many others. The process for developing harmonized standards at both national and international levels is rather complex, sometimes involving completely opposite efforts, such as local market protection versus its globalization. In any case, the main influencing factors come from field experience, market requirements, insurance issues, and the globalization of trade and business. The standards are produced by specific legislative and executive bodies, while specific worldwide recognized testing houses inspect and verify all the required appliances to ensure their compliance. Applications targeting safety can benefit from the acceleration of software development. Efficient and early diagnostics using specific hardware features, together with the application of proper hardware and software methods, decrease the probability of hazardous events due to possible component malfunctions. Applying certain hardware design and manufacturing methods can even increase component reliability. ST supports two basic general safety standards, a specific one targeting household appliances known as a Class B or Class C standard, and a more common industrial standard targeting safety integrity levels called SIL. The latter is a generic standard, which produces a large number of derivative standards dedicated to different fields of application. ST, in compliance with these standards, cares about both systematic and random failures. Systematic failures are predictable, and their avoidance and monitoring are based on practical experience gained in the industry. Specific failures can be avoided mainly by applying correct internal processes throughout a product's life cycle. These requirements are defined in specific internal quality documentation. Regular inspections and audits ensure that these internal rules are applied and comply with the recognized standards. To ensure integrity against random failures, specific software methods and hardware design techniques must be applied as described in the following slides will give you an overview of the main safety concepts to be taken into account when working with microcontrollers. Not all random failures result in a hazardous event, and they may even be considered as safe from a safety point of view. Basically, safety standards require monitoring to detect dangerous failures that may be directly or indirectly related to safety, and have the potential to cause a dangerous situation. Both safe and dangerous errors can either be detected or stay hidden and undetected by the system. The more often dangerous errors are discovered and prevented in time, the more the probability of a failure propagating into a hazardous event decreases. The time needed to detect dangerous errors and prevent hazardous events must fit into the overall process safety time, or PST, available, which includes all the possible delays and reaction times for the system, such as on sensors or actuators. For quantification purposes, safety standards recognize a safe failure fraction and diagnostic coverage. The safe failure fraction, or SSF, is the ratio of the rate of safe failures, including the rate of detected dangerous failures to the total failure rate of safe failures as well as detected and undetected dangerous failures. The diagnostic coverage, or DC, is the ratio of the probability of detected dangerous failures to the probability of all the dangerous failures. Random failures can cause permanent or recoverable errors. Hard failures cause permanent physical damage to the component, and the system is no longer able to operate normally. If no compensation is possible, the system has to be put into a safe state until it is repaired. Random soft latch-up and transient failures are returnable, and some kind of recovery process is usually applicable. In addition to being detected, these failures can also be compensated for in certain cases. Transient failures can be managed by both hardware and software, while transient failures need fast hardware methods exclusively. Software tests can never compensate for these temporary and short-lived errors efficiently, as they are considerably slower and limited by their execution time. From a cross-product point of view, we can recognize single-point, latent, or common types of failure causes. Random causes of failure require a special focus, especially as they can potentially destroy even quite complex safety structures. When random failures are detected and cannot be compensated for, especially after a dangerous error is detected, the system has to be stopped and placed into a safe state or go through a recovery process like reset, rollback, or a specific check function. Common methods usually allow the system to continue operating normally, while using error correction, passivation, or masking functions. Generally, a sure voting process is used to identify the damaged part or incorrect data which is then replaced by the correct one. Standards recognize hard fault tolerance, or the maximum number of errors which a system can absorb, while it still can continue at normal operation. In addition to specific functional testing, redundancy is the essential diagnostic principle here. Both detection and compensation techniques always require a sure level of redundancy to be efficient. Compensation is considerably more demanding than detection, as not only discrepancies, but the correct state has to be identified as well. To do so, specific comparison and voting mechanisms have to be additionally applied. The required level of redundancy can be achieved using a wide range of different software or hardware methods and techniques. Some of them are listed here, and others will be highlighted later in this presentation. The techniques can usually be achieved either by hardware or software, or a combination of both. From a safety point of view, a microcontroller is a relatively complex programmable electronic component, which has to comply with specific requirements determined by the applicable standards. In regards to support safety for a microcontroller, a vendor considers the product as a component out of context as its final application purpose and safety tasks are not known in advance. This is why we can speak about component ready or suitable for a determined common level of safety tasks. The effort is always to cover the component's overall reliability and fulfill the overall budget of diagnostic coverage, defined by the standard for the given safety integrity level required by the final application. A complex component like a microcontroller can be considered as a set of partial components involved in various safety tasks, each with a different diagnostic coverage and weight in the overall component safety budget. An effective way to ensure the required overall safety budget has to be focused on crucial and generic parts of the microcontroller, especially those commonly used by most applications. Any small improvement in the safety of these fundamental and significant parts of the design always brings the biggest gain in the overall safety budget of the component, which is beneficial for each application. Once a microcontroller is included in an application design and the safety task is specified, then the safety support can be deployed much more efficiently and cover just the very specific parts of the microcontroller involved in the required safety case. Many efficient methods can then be applied based on detailed knowledge of the application requirements, its design, the process, and the equipment under control. Redundancy and knowledge of the system behavior are crucial principles applied either separately or together. Inputs and outputs can be multiplied or checked by feedback, tested for logical state, value or expected response in trends or time intervals. The processes can be monitored for correct timing and flow order. Correct decisions can be made based on the comparison of results coming from redundant and independent flows, analysis, calculations, or data. The following slides are devoted to the STM32F7's features dedicated for safety support. STM32F7 microcontrollers feature specific hardware for efficient diagnostic testing and to quickly react to failures with the potential to cover a wide range of lower level safety applications. The hardware tests are autonomous with minimal or no software control. This is especially helpful in detecting transient errors and consumes the least amount of time of the overall process safety time. Nevertheless, all the tests listed here with the exception of ECC are exclusively dedicated to the detection of failures. This is why additional software tests must be added when compensation or an additional check is required, for example, to achieve a higher level of SIL. In this case, the user must ensure that the software testing period takes into account the process safety time. This slide lists application-specific safety features. A secure level of safety integrity can be achieved with an STM32F7XX microcontroller if the specific conditions and limitations described in dedicated documentation are respected. This slide lists the software checks included in the ST self-test firmware solution with a brief summary of why they are applicable. Generally, the firmware focuses on generic parts of the microcontroller based on in-depth knowledge of the design, while packages dedicated to achieving SIL standards use more extensive testing methods proved by specific methodology for their efficiency. The packages are not available for free download. Users should ask their local ST representative for the firmware. Clock cross-reference measurements can use dedicated timer interconnections. The ratio between two independent clock sources has to stay within an expected range. One frequency is used as timer input, while the other gates the timer input and raises timer capture events. A specific sequence of instructions can verify the CPU unit and its registers. For peripherals, it is suggested to verify the correct configuration at regular intervals. No parity or ECC bits are defined for memories in STM32F7. If the user needs to store safety-critical information, he should apply a March X algorithm functional test. This test additionally checks the data and address buses, but it is destructive towards the memory content. It is suitable as an initial functional test of all the SRAM space. It is not available for flash memory. At runtime, it has to be done for each part and in a transparent way to prevent corruption of the actual memory content. In principle, self-test procedures are included as an additional task when initializing the application main loop during system startup. This runtime self-test task provides periodic testing of the CPU, clock system, stack boundary, program flow, and both volatile and non-volatile memories. The watchdog timeout is refreshed upon completion if everything goes correctly. The memory areas are tested step-by-step per parts within the task. The test is synchronized by time-based ticks derived from timer interrupts. The interval required to complete the test depends mainly on the size of the memory areas under test, frequency of the task calls, and sizes of the blocks tested in a single step. Optionally, a one-time initial startup overall self-test can be additionally implemented at PowerOn or after application reset. Whenever a malfunction or discrepancy is found during these tests, the failsafe routine is called. It should put the application into safe state and determine the next recovery possibilities. Safety is spread in the full STM32F7 product range. You will find a detailed description of the aforementioned features in the different peripherals chapters. For more details, please refer to the dedicated documentation and contact your local ST representatives for the availability, status, and possible delivery of the firmware and associated documentation.


Again, going to the reports on the left-hand side, closing up the buggy, holding control, scrolling down a bit to one, two, five, so I can go down to my sales areas. There they are. I'm looking for the sales by item. So I want the sales by item. And I just want the summary. There it is, sales by product service summary. And so there it is. Let's run it for 010122 tab, 123122 tab, and run it. Now, this one's a little bit more detailed because there's more stuff in it because we've got a couple different columns up top. What we're really focused in on is just the amount of the sales is what I'm focused in on to make our pie chart and our graphs. So I could just delete the other stuff once I export it to Excel. We also have some subcategories we'll have to deal with. Before I get into that, though, note that the total down here adds up to $10,280, which doesn't tie out exactly to what's on the income statement, which ties out to $10,277 for total income. That could be the case. And remember that this sales by item will only work if you're entering your data into the system in such a way that it's going to populate the subledger accounts. Quick recap, if I hit the plus button, your revenue cycle could differ depending on the type of industry you're in. If you're in gig work, you're getting paid by YouTube, you're getting paid by Amazon, some platform, then as you get the money, you might just be using a deposit form with the use of the bank feeds possibly to record the revenue. So that's great, but you're not going to have the same detail for the service subledger item because you're not entering items that way because the deposit form doesn't have the capacity to do so because it's not usually the form we use for the sales side of things. If, however, you have a cash-based business where you have a cash register, you're using the sales receipts. And as you populate the sales receipts, you're going to be populating the inventory and revenue items, service items in there. And therefore, the subledgers should be generated. Same with the invoices. If you're using invoices, the subledger should be generated because you're going to be using the items within the subledgers. So that's the general idea. Also, just remember, if I go to this first tab over here, we're going to go to the Sales tab. And then you can find your items in the products and services. And these are the things that we sell that we populate the invoices for. So these would be our inventory items, our service items. Now we have a bit more complexity because here they set up their items to have subgroups. So now we've got items and subgroup of items that we'll be showing up on our items reports as well. OK, so let's go back on over to our items reports. So when I export this, maybe I just want to group this stuff by category. If that was the case, I can collapse the tabs here and I can export just by the categories and then make my pie chart by the category. Or possibly I want all the items and not just by category. So if I want all of my items this way, then I can do it this way. Maybe I just remove the subcategories. So now I've got a category and another subcategory. So I'm going to minimize these ones. And I'm just going to have the major categories. So I'm going to minimize this. So I have like two layers, the major categories, and then everything within it. So when I export this, this gets a little bit messy because now I'm going to have to remove these kind of subtotals. So I just have a set of data and a total at the bottom. Not too bad, but it's a little bit more of a challenge to deal with it to get our pie chart. So let's do our pie chart based on this information. So I'm going to export it now by going to the dropdown up top. And I'm going to export to Excel as we've done in prior presentation. You do need Excel in order to open stuff in it. There it is. I'm going to enable the editing. I'm going to copy this and put it on our other worksheet that has all of our statements on it. You don't have to do this. If you don't have the other worksheet, you can work here. But I'm going to show you how to do it if you want to do that. We're going to hit the triangle, right click, copy. I'm going to go into my other Excel worksheet that has all our reports on it, go to the last tab within it, add another tab, and then put this in A1 or select the triangle and paste it down right then and there.


Hi, I'm Jesper, and I'm part of the ST TouchDFX team. In this video I'll show you some of the basic features of the new static graph that has been added to TouchDFX 4.19. For this I'll create a new application, like this. For starters I'll add a background, we'll just take a one-color single-color box here, make it all white, and that's it. Then let me add a static graph, you see we have a dynamic graph and a static graph. Here I add the static graph, since that is what I want to talk about. I'll expand it to fill up the entire display. As you might know from dynamic graph, the static graph has also a set of grid lines or labels that you can put on the X and Y axis. To use that you have to make space for it, so a graph has a margin that you can put up. If we want the graph to be having space for this, we could change these parameters like this. Now we have the lines of the graph in this position, and then let's see if we add some grid lines like this. And we have the X axis as well here. Then all of a sudden our graph looks like this. Let's try just to compile, run the simulator, see that everything is as it is shown here on the canvas in the designer. Here's the application and it looks similar. It has some random points inserted just as in this here, but you can disable that if you do not want that to happen in a real application. Just as for dynamic graph you can have a lot of options for grid lines and the labels to match your needs. For example this interval, so if you do not want all these grid lines to show up, you can change it to be each 40th instead. You have minor and major divisions of the grid lines, so you can add a second one. Let's change the color so we can see the difference. It has its own interval and so on. The reason why this is a minor is that if they coincide, so have the same X value in this case, then it is the major one that will be shown. The same goes for the labels, so you can change them. You can set up the interval to match your need and the way you want it to look. You can change the typography and so on. Now we have our static graph, so let me explain to you what is a static graph, what is a dynamic graph, what is the difference. To do that I will show you the documentation side of the dynamic graph. If I add a dynamic graph here I have a link to the web page of the documentation. Here you see a dynamic graph. Here is one way of the dynamic part of the graph. In a dynamic graph you add a point to the end of this graph and these points are equally divided on the X axis. There are different ways the dynamic graph can behave. If we scroll down here we see some example on the dynamic part. This one just clears when it reaches the end. This one like scrolls and this one has this final line when it overrides again. That is the dynamic part of it. The static graph as it says is a static. The view is static so you specify the range where you want to see this graph. In this case minus 100 to 100 in the X axis and minus 100 to 100 in the Y axis. The static graph is static in the sense that it does not change the axis on your view on the dataset as you insert points. You can insert points. You can specify how many points you want to allocate for. In this case you have 100 so you can add 100 points. They do not need to be inside of this range. You can plug them outside and you will see the line go towards that point. You can later change the view you have on this so you can change what part of the X axis you see and what part of the Y axis you see. You can override points in the dataset. If you have added a point 0.10 if you later on add 0.11 the graph will update with this new override the 10 and write 11 and then update the graph accordingly. An extra thing is that if you do not want integers on your X and Y axis you can set a precision. What precision you want for your X axis in this case and then when you enter numbers it can be in this range. For this example I will just leave them to be integers. Let's try to add some points to the graph. For that let me add a button so let's make space for it. Let's do like this and then add a button over here like this. Create an interaction so when the button is clicked this one we will call a virtual function. Let's just add a point and leave it with that. We generate the code. In this case we also run the simulator just to see that everything is as expected. We have a button nothing happens of course. Let's open the files that has been generated like this. I use Visual Studio of course you can use whatever editor you like. I have my code here. I have screen 1. If I go to the view base class we see my add point. We see all my elements that I put into the screen so the graph is here. We can see it has the 100 data points and we see we have a lot of elements for the grid lines. As such we don't want to do anything with those. Let me just grab this function here and add it to my view so that I can override it. I'll move it to the C file and ready to implement. Let's try to add a data point like this. It either takes flows or integers in our case. Let's just add an integer so 2.5. That's it. If we want a line to be shown let's do like this. Let's try to compile and see if we will add these points when we press the button. Hopefully we will. We saw a change here and that was probably our new two data points. One thing to notice is that you have a lot of help of functions in a graph. Here if we go to get there is a getGraph area padding range. If you want to know the range that the graph has right now you can get it here. The max value for the x-axis and the minimum value for the x-axis as well. Same for y. This can be used if you want to normalize data points or something like that when you insert them into your graph. All of these functions can be seen in the API for the graph and also the description of the static graph itself in the documentation. You can play around yourself with adding data points to your graph. Or you can go and have a look at the static graph example which inserts some random points whenever you press a button. The final thing I would like to show you is for some other interactions for the graph. If you add an interaction here you can say when you click the graph then you can also have a function called here GraphClicked. Let's generate the code here and see the base class. Now I have a graph clicked. Let's add that to my view and do something with this value here. This function is called when the graph is clicked. The value here contains an index which is an index in the array of your data points. From an index you can do a lot of things. You can get the x-value. There is a method in the graph called index to data point where you can do the conversion. You can also get something like this screen coordinate. If you want to put something on top of your graph like a circle or something where you have pressed. Let me just show you how to get a hold of it. If I include touch-the-effects utilities like this I have the touch-the-effects-print-f method. Let me show you so I can say graph1.index to screen x. From the value I will retrieve the index where I pressed again. The point in my array of data points or the index in the array of data points for the point where I pressed. If we go ahead and compile here we should see the output of the x-coordinates in which I pressed or the point in the graph where I pressed closes to. We have the console here and you can see the number getting out. Of course you can play around with all of this also. So get the index, convert it to an x-value if you need that to get the x and the y-value or you do like I did here to get the screen coordinate from where you pressed. So that concludes my short run-through of the static graph for touch-the-effects 4.19. I hope that you will try it out, play around with it and see what kind of things you can do and what applications you can do with all of this. Thank you for listening. Bye-bye.


And now for your strong Europe spotlight. Tax centers across Army Europe will begin taking appointments to follow your 2017 tax return. But it is important that you bring all the appropriate documents to your appointment. Please bring your DOD ID, your Social Security card, any W-2s you have, any 1098 or 1099 forms, your prior year's tax returns, and any bank account information that you have for direct deposits. Military retirees living in the area without a NATO SOFA status are asked to make an appointment or check with their local legal office for information. Given the unique tax issues faced by our military retirees who are living in Germany, we're asking our retirees to stop by the legal assistance office to get their tax returns prepared. To ensure you are fully prepared to follow your 2017 taxes this year, contact your local tax center. Thank you.


Hi Peggy, this is Ashley from Oxford Toyota. I wanted to send you a quick video greeting that way you can see who you'll be working with. I noticed that your lease on your 2013 RAF4 is coming to an end. In this email, I have provided a little bit more information about what you have to look forward to with the lease coming to an end. When you get a moment, please give me a call. My number is<PHONE_NUMBER> or you can also email me back. Thanks, bye.


If one were to mention the incredible feats of engineering undertaken by our now lost ancient ancestors, in particular, gigantic walls, some may lean towards the impressive sheer enormity of the megalithic stones within the wall of Gornaya Shoria. Or more commonly, the Great Wall of China is the more popular choice, or the more obscure, lesser known Great Wall of India. Undoubtedly, the Great Wall of China was a feat of monstrous proportions, having been built to such a scale it's visible from space. Yet what many more are unaware of is an ancient kingdom once located in southwestern Nigeria. Known as the Walls of Benin, they dwarf the Walls of China, a series of defensively constructed earthworks called Aya in Edo. They consist of 9.3 miles of inner-city walls and an estimated 9,900 miles of outer wall. The Walls of Benin City were described as, quote, the world's largest earthwork carried out prior to the mechanical era, end quote, by the Guinness Book of Records. The Benin City Walls have been known of by Westerners since around the 1500s. Portuguese explorer Duarte Pacheco Pereira briefly described the Walls during his travels. Another description was given around 1600 by the Dutch explorer Derrick Reiders. Reiders' account of the Walls is as follows, quote, at the gate where I entered on horseback, I saw very high, very thick walls of earth with a very deep broad ditch around. They were dry and full of high trees. Who built these walls? Or indeed, how did they accomplish such a mind-boggling feat? Traditional accounts suggested that assuming a 10-hour workday, with a labor force of some 5,000 men, it could have been completed within just 97 days. However, these estimates have been criticized over the years in many ways, one in particular, being a lack of account for the time it would have taken to extract earth from ever-deepening holes. Yet, regardless of these discrepancies in opinion, regarding the challenge in its creation, or indeed, their age or origin, we find these walls highly compelling. There are many enigmatic, unexplained, ancient mysteries which we have covered here on our channel. Many mysterious ruins which are slowly revealing their secrets to us. However, what must be the most intriguing of the historical sub-categories has to be the O-parts, out-of-place artifacts that have been found all over earth. These mystifying items are the only subject within the field which can shed their own very unique lights upon the distant past, and sometimes hard to believe possibilities attached to their ages. The island of Samos within Greece is home to a number of these particular artifacts. 1.5 km off the coast of Turkey, this small island has a big history. Within the island's capital museum is a wide range of very impressive artifacts. The most interesting among the collection is undoubtedly the strange bronze artifact which according to academia, merely depicts a strange form of unknown carriage that would have once been pulled by horses. However, some also believe that the strange animals are actually depicting a form of periscope in that the entire artifact is actually that of an ancient submarine. Additionally, there also exists another amazing artifact that we felt was worth a mention found within private collection. Originally a religious idol, what do you think this wooden artifact is depicting? Could it actually be that of modern day paragliders? Somehow sent back in time, seen and depicted by this once ancient people as a religious vision? It's an incredible, if rather imaginative thought, but it is testament to such artifacts' intriguing nature. There are many incredible out-of-place artifacts that can be found all over Earth. Each one just weighed to spark our interest. Thanks for watching guys and until next time, take care. Thanks for watching guys and until next time, take care. During the naval operation known as Deep Freeze, men aboard a Russian icebreaker would later testify to witnessing a craft, surged through 10-foot thick ice, flinging huge chunks in all directions, a silver vessel then shooting off into the atmosphere. Dr. Reumann's Dizviela, a famous arctic explorer, was among those who testified to witnessing the terrifying event. Upon exiting the ice cold waters, he stated that steam erupted from the body of the craft, indicating the huge amount of energy these mysterious USOs possess. In 1997, pre-Codeco said, Billings-Gausen depression near the Antarctic area was examined by the Australian army at a depth of over 6 kilometers, where cameras recorded strange oval objects which emitted an intense interior light. The film was reviewed by experts from the Royal Institute of Oceanology. Their conclusions were that the structures were of artificial origin. Russian naval vessels also report off and tracking submerged dishes, traveling in excess of 150 knots or 280 miles per hour underwater. Former USSR Captain Vladimir Azaza, head of the navigational section of the Oceanographic Commission said one questioned that about 50% of encounters with UFOs are connected with the oceans, and 15% are connected with lakes, making a huge portion of close encounters in the form of unidentified submerged objects rather than flying. What these mysterious events are caused by, or indeed what the mysterious craft are beneath the ice cap, remains a closely guarded secret, with only handfuls of whistleblowers ever coming forward, yet they all stress the same thing, that we are not alone on this planet. There are many things found throughout history which cast doubt onto the modern chronological paradigm in regards to the ages of man. We have often wondered how many of these proofs have been unearthed over the years, only to disappear again into the ether without even a mention. With a caption from one of the many source books of the notorious William R. Coralus, adding some light onto the numbers of these proofs, found and discarded over the years, specifically drawn out deep from within the minds of Earth. Quote, Dr. Perez Snell of Sonora had in his collection a human jaw, which was brought out in a carload of paydirt from a shaft stretching far beneath the Table Mountain, and with it were several stone implements. The specimen was given to him by a miner. It is only fair to state that there could not well have been found a miner in all that region who would have thought it worth his while to attempt a deception, nor even one who had any doubt in his mind as to the point we are considering. For they saw the products of man's work come out with the gravel too often to pay commonly any attention to them. The only wonder, he even took the trouble to pick out the bone at all. There can be no question that for one such that has been preserved, dozens and perhaps hundreds have gone down in the current of water in the sluice. The bones in question had come from a depth of 180 feet below prehistoric lava flows. Colonel Hubs, state superintendent of instruction, had in his possession in 1857 portions of a human skull himself, which itself came from an impossibly old mine. It would seem the presence of these artifacts be predictably rife, yet ignored due to already established paradigms of history. The Calaveras Skull, also known as the Pliocene Skull, being one such artifact. A human skull found by miners in Calaveras County, California, dated to as early as the Pliocene, thus it supports the idea that humans, mastodons, and mammoths coexisted, but also pushed the timeline of man back an unacceptably long way that in regards to modern paradigms. Predictably the remains due to miners' lack of collecting them has been heavily argued as a fake. In February 25, 1866, miners found the human skull in a mine, again beneath a layer of prehistoric and easily dated lava flow at a depth of 130 feet. The skull made it into the hands of Josiah Whitney, then the state geologist of California, as well as a professor of geology at Harvard University. A year before the skull came to his attention, Whitney had also published the belief that humans, mastodons, and mammoths coexisted. Thus he became an instant advocate for its popularization. The skull served as proof of his convictions. After careful study, he officially announced its discovery at a meeting of the California Academy of Sciences on July 16, 1866, declaring it evidence of the existence of Pliocene Age Man in North America, which would easily make it the oldest known record of humans on the continent. We find the skull, and indeed William Corliss' research, incredibly compelling. During our research, we have stumbled across countless legends and accounts from history, which tell of ancient giants. Not only legends, but photographic evidence, and an equal amount of initial newspaper reports of their discovery. This often accompanied with the mention of the Smithsonian Institutes, insatiable interest in such finds, and then an inevitable erasure of said finds from future research. Rarely has an ancient giant been allegedly found, with the remains seemingly slipping the net of said institute's attention, making it into mainstream research and an ally's collection, before the Smithsonian was able to make said discovery vanish from history. Captua, being one of these particular finds, which not only matches the initial claims, but has remained in mainstream historical research. Tales of a two-headed, 11-foot-tall giant are not only corroborated by photographic evidence, but the actual mummified corpse of the giant himself. The initial discovery of this incredible being was made back in 1673. An ogre, or two-headed giant, is said to have assaulted a party of Spanish sailors, who fortunately overcame said giant with cunning. After trapping the giant, the sailors planned on killing it, fearing repercussions if released. The cause of the giant's death, however, has long been debated, but what cannot be denied is the astonishing remains which eventually made their way to London. The mummy then vanishes from the history books for nearly 400 years, reappearing in 1914 on the shores of the Birnbeck Harbor in the UK. The mummy inevitably became an extremely popular attraction, with people traveling from thousands of miles away to come and peer at this once monstrous two-headed giant. It remained in the public eye until 1959, a rare exhibit which escaped the clutches of those who would wish to hide it, with many photographs and other research projects allowed to be undertaken on the giant's remains by Lord Howard. This incredible giant, thanks to the Lord's dedication to said curiosity, remains in existence within the public's domain. An undeniable verification of a lost race of giants, which we have long claimed to have had first-hand experience of in their past discovery. A magnificent three-meter-tall mummified corpse of an ancient giant does indeed exist, and due to its age and primitive technologies available to said-claimed sailors, when initially discovered, the possibility of it being an elaborate, stitched-together hoax has been seemingly debunked, but also ignored by mainstream media due to the controversial nature of said finds. Who was Captua? Was he part of a race of beings in Patagonia? A race we have merely seen these remains of? Is the corpse authentic? If not, how was he constructed to such an astonishing detail so far back in history? Captua is undoubtedly highly compelling.


Hi, everyone. All right. So just to make sure there is no feedback. OK, fantastic. All right. So good afternoon, everyone. And first of all, thank you, everyone, for joining the community today. And the topic for the presentation here, basically, is that building an enterprise-grade multi-account AWS environment. So before we begin the presentation, and here is the quick introduction about myself. And I'm Badri. I work for Macking and Financial Services. I myself am a cloud architect or cloud engineer. And I'm one of the AWS Singapore user group leader. I'm myself a community builder. I'm also very passionate towards the cloud and distributed systems in very general. I also wanted to make it clear. So this talk, what I'm delivering here, is on my personal capacity. So any of my opinions, what I express here, is personally on my own, not that of my organization. Yeah? Right. So here is the agenda for this event today. So what we will do, we will start by decoding this multi-AWS accounts with a proper design structure and the management to operate on top of it. And then we look at managing the access control across the distributed AWS accounts. We'll then discuss about managing the network connectivity across the distributed AWS accounts. And finally, we'll conclude this presentation by managing the security detection and assessment across the distributed AWS accounts. Before I dive specifically into this multi-AWS accounts, well, let's just have a quick understanding about why single-AWS account is just not enough. Well, there are a lot of these concerns boiling down to this isolation. Starting with the security, it is difficult to isolate the different parts of your infrastructure. Like, how are we going to write down the IAM policy to identify the respective teams' AWS resources? How are we going to segment different parts of the workload if it is being hosted in the single VPC in the shared environment? Or how are we going to apply a resource policy on top of the S3 buckets, perhaps if you are creating in the common AWS accounts? So it will become increasingly challenging from a security perspective. And it's also very natural that different teams have different compliance and different regulations. And especially in a shared environment, if you're hosting different teams' AWS resources, it will be extremely challenging for you to track, identify, and apply the respective compliance and the regulation on top of it. And it's also very natural that different teams have different governance requirements and different management requirements. And especially in a shared environment, and in a single AWS account, it is again, it's going to be difficult for you to track, identify, and apply that specific governance and management methodologies on those shared resources. And finally, two specific concerns. We also have challenges with the cost. And different teams have different budgets and resources. And the most vast majority of the resources, you can apply the tax and to have the cost managed. And perhaps there are resources like data transfer, but you cannot apply the tax. And you have to be very systematic in terms of allocating the charges to the different teams. And we also have increasingly challenging environment when you operate in the shared AWS account itself. And finally, so you'll also have all this quotas. We have various functional and non-functional limitations on single AWS accounts. And all these constraints, it points us towards this multi AWS account structure. Now, let's try to decode this multi AWS accounts with a proper design structure. And we'll see how to manage those multi AWS accounts, what we create in AWS. And when you're adapting this multi AWS account strategy, the very natural question what you basically have is, how many accounts you basically need. And the truth is basically is that there isn't any hard answer. It really depends on your size and the complexity of your organization. You can go about creating a different AWS accounts for different environments. Say for example, AWS account for Dell, AWS accounts for QA, AWS accounts for Prod. In that way, you have a higher, good segregation between the different resources, different nature of AWS resources in each of those AWS accounts. You can also have different AWS accounts created for each of the team in your organization. So in that way, you have a better cost tracking, better ownership, and better access control, which is dedicated for each of those teams. And you can also have AWS accounts created for each of your project initiatives. And again, that will go about having you with a better cost tracking and better access control, better ownership for that respective project in terms of operating that specific AWS account. And you can also be even more granular, right? So you can go about having this AWS accounts created by application per environment. Say for example, AppA Dev on its own AWS account, AppA QA on its own AWS account, likewise for different applications. And perhaps with this basically approach, it is basically very secure and you have a better cost tracking for each of the applications, better isolation of this AWS resources between different environments for different applications. And you will also have a better ownership and it's also easy to decommission the resources. So when the specific application is not in use, you can go ahead and scrap those resources and close the AWS account. I highlighted in green, not because this is the only valid principle, perhaps this is one of the principle what I practiced in one of my working organizations where security and the ownership and the account release lifecycle of a very priority concern, yeah? Now, boiling down all this multi-accounts what we have just discussed, if you notice like you will be ultimately ending up in two nature of AWS accounts. One, the management account, the please value create all your organization AWS accounts. Another one, what you broadly call it as subordinate accounts or a member accounts, yeah? And in the member accounts, you will be having a two nature of member accounts, one which is of very sad services in nature and another one which is self-contained which is for a specific application use case, yeah? Shared services say for example, networking. Networking is responsible for providing a network connectivity for all the AWS accounts. Security services, logging services, so those are specific things. So, now basically once you decide on your, once you decide on your account principles and once you've put out the solid principles for creating the AWS accounts, the next question what you have to answer is how are you going to group those AWS accounts? So when I say group those AWS accounts, basically is that you try to group your AWS account which are similar in nature and this similar is a very broad word and it's very subjective and it really, it basically is that each of the organization priority, you go ahead and define the similar principle. Say for example, you can group all the dev accounts into one organization unit or you can group all the QA accounts into one organization unit. Perhaps you can also consider grouping dev and QA together into non-pro-organization unit and perhaps it really depends on your maturity and how you want to group those AWS accounts together to apply this organization unit benefits on top of it. So basically is that all this grouping will provide you the benefit of managing these accounts which are similar in nature where you have a better resource segregation and you will have a centralized management on top of those grouping. Perhaps you can easily manage this compliance and governance on all those AWS accounts which are similar in nature. Say for example, you can apply the compliance policies for the specific organization unit which are similar in nature. You can have a better cost management. So when you group those AWS accounts, say for example, dev AWS accounts, so you can easily identify with that specific organization unit what is basically the charge which is consumed for all your dev AWS accounts. So cost management is going to be very simpler and finally it is basically is that you will have an automated resource creation on top of it. So let's say if you're grouping the AWS accounts which are for your dev use cases, perhaps you can automate by taking advantage of this AWS organization unit where you can systematically go ahead and have that resource created when the new account joins your dev organization unit or likewise for different organization unit as well. So it helps you with all this automation when you group those similar accounts together and you can apply all those similar automation what is needed for you to get the job done. So this is one such example like we have practiced in one of my working organizations. Perhaps you can notice that we have a high level categorization of broad and non-prod accounts. And in broad you have two different OUs, one for your accounts which are shared services in nature another one for application accounts which are self-contained in nature and likewise for non-prod. And also you can notice like there are two additional OUs which is for your innovation use cases. Basically is that there are not necessarily that innovation use cases will naturally naturally follows that level of vetting what is needed for your organization AWS accounts recommend or AWS services recommends. So perhaps you can consider providing a bit more flexibility on top of those innovation OUs to isolate that from your rest of your organization and perhaps them to have the flexibility by way of allocating that by way of categorizing them as a separate OU and you can apply all those compliance policies or the innovation related compliance policies on top of it. And likewise suspended OUs. So basically is that the whole idea is once when the specific AWS account or the specific application use cases it's done with its life cycle. You move that to the suspended OU and you apply this resource control policy in a service control policy you explicitly block all the accents what is going to take place in that specific AWS accounts. So this is one such example. So you can apply, you can basically have this thought process in trying to understand what benefits this OU provides and try to group those accounts which are similar in nature which matches your best interest for your organization itself. Now fantastic. So we have decided with this organization structure and how are we going to manage this multi AWS accounts? So one where basically we are very fortunate from the perspective that the level of ambiguity in terms of this multi-account management is greatly reduced unlike other scenarios in AWS where you will be ending up and fighting between SNS, SQS or same services providing the same use cases competing between each other. So but we are fortunate that for this multi-account management the level of ambiguity is greatly reduced, right? So you only have two options. You either use control-tevo or you self-manage this organization AWS accounts. Well, I would basically recommend perhaps if you as an organization which are very small in size and if you don't have any strong opinions right away go ahead and have this control-tevo used, right? Because it handles with all this primitive guardrails which are provided out of the box and it matches with all the best practices and it also helps you with all the automations in terms of providing you with the service catalogs and basically it offloads you all this management over here what is required for your multi AWS account management itself. So whereas the other extreme is self-manage the AWS organization accounts. Why it is really needed, right? So AWS control-tevo it comes up with its own opinions. It comes up with its own opinions when it comes to the primitive guardrails or it comes with its own opinions when it comes to how do you want to have this organization units structured, right? How are you going to group those similar AWS accounts together? So it comes with its own opinion which mostly meets across I would say like a 90% of the needs. Perhaps if you as an organization which are heavily customized, right? Which is basically, you know, fortunately or unfortunately all my working experience we have a heavy customization recommend where we try to do all the lot of account orchestration related activities in terms of like onboarding, creating appropriate IAM roles provisioning all the networking resources to have this connected across your distributed AWS accounts providing a connectivity to your on-prem accounts or providing a DevOps related accesses. So this sort of customization which not necessarily meets the control-tevo out of the box provided solution. So for such use cases you can consider using your self-managed way of doing that AWS automation accounts, yeah? Perhaps one of the things is like, you know, if you already have hundreds of AWS accounts, right? And you have self-managing perhaps you already have a well-established process. So migration effort might not be worth it, right? So if you're moving to control-tevo by the time itself. So with this, we will be moving on and once you have this, once you basically establish this multi AWS account structure the next big question is basically is that how are we going to address this access control across this distributed AWS accounts, yeah? Because creating an AWS accounts is a very cheap activity and, you know, perhaps when you start to have this hundreds of AWS accounts and what are some of the distributed distributed account challenges what you possibly have, right? So let's say if you are sticking with this very classical way, yeah? Very classical way of creating the IAM users in your own AWS account in all this distributed AWS accounts. You can imagine the complexity, right? So you can imagine the complexity what it creates. You know, in you self-managing all those hundred different AWS accounts with all the users what you're creating on top of it, yeah? So it will become increasingly difficult to manage and track the user access across the distributed accounts and it is definitely not scalable. Perhaps you will be linearly increasing your effort, right? So all the operations are fit. What is, you know, when you keep adding the, when you keep adding a new accounts when you keep adding a new users you will be basically, you know linearly increasing the efforts as and when you scale it. So this approach is definitely not scalable if you're sticking into the classical way, yeah? And you will also definitely have issues when it comes to visibility, right? So you, what is the single source of truth you could leverage on, right? So to understand how are you, how are you, you know, what different users you have created across those distributed accounts? You will definitely lack of visibility in terms of, you know, in terms of the distributed AWS accounts if you're leveraging on a very classical way, yeah? And finally, of course, we'll be having those, you know, auditing and reporting challenges. Perhaps if you're coming from a financial enterprise you will understand the seriousness behind it. So, you know, as it is going to be that there is no single point of contact for you to get you that auditing and reporting done, right? So you will be basically relying on some form on automation or to get all those, you know, all those user accesses and the required, whatever the permissions what is applied across those distributed accounts in a very some, you know, very, very imperative way, right, very imperative way of providing an automation on top of it. So all these challenges that comes with the distributed AWS accounts if you're leveraging on a very classical way. So now what is really needed for us, you know, into manage this access control across all the distributed accounts? Of course, we expect a central management, central management of all the user and access to the distributed AWS accounts. You will expect a role-based access control. Of course, for sure you will be also expecting an attribute-based access control, but very classical way, we will be relying on the role-based access control and you will be expecting a multi-factor authentication and for sure if you're coming from enterprise you already have established, you know, your own credentials, you have your own identity provider, you will naturally expect your, you know, you won't use the credentials what you've created on your own identity provider to use on top of those AWS accounts. And basically, you know, you also expect since you have already grouped those AWS accounts and you have created those AWS accounts under the AWS organization, it is natural for us to expect some sort of an integration, you know, for us to cascade it across all those accounts what you've created part of your organization. So some form of an integration is also what is naturally expected, you know, from managing the user access control for all your distributed accounts. And finally, the compliance and auditing reporting all have to happen at a one single place, right? So that's something what I feel which is very specific and which is, you know, effectively needed for managing the user access across all the distributed accounts, yeah? So now what different ways is available? Yes, of course, one is an IAM user which is very classical way, which is what we just discussed. Another thing is basically the IAM roles. What do you basically do? Like, you know, in each of AWS accounts, you associate the IAM roles for the users with the identity provider, you know, by way of doing a SAML assistant. Again, that is not manageable. You know, even if you rely on heavy automation in terms of associating that part of your account orchestration related activities in associating an IAM role for the SAML identity provider, that is also very distributed in nature. And the third option is basically is that IAM identity center, right? So this IAM identity center, which is previously called AWS Singles, I know. And this effectively, you know, this is an effective service which is put out to meet all this, you know, all this what we want, you know, in terms of centralized management for the users across the distributed accounts. And we expect identity federation with the existing identity provider. And we expect a single sign on across all those AWS accounts. So IAM identity center perhaps comes as a, you know, very specific choice from a distributed AWS account management perspective in terms of the user access itself, which you can consider using it. So ideally how it will be looking like, you will be creating an identity center in one of your management account. I believe now you can delegate this identity center into NFM member account. So so far now, so you'll be creating this identity center in your management account. And that is your central point of contact where you will be creating the users by way of integrating with the existing identity provider. And from there, you cascade it, whatever the users that has been created and what about the users being created, you will be associating a role on the management account and that gets naturally cascaded into all the distributed accounts by way of associating in the management account itself. So this basically provides us a path where we have a centralized management for all the user accesses for all of our distributed accounts. And it also naturally integrates with the AWS organization where all whatever the users and the roles what we are creating in the management account gets automatically cascaded into the member accounts. And you will be also having an integration to the existing identity provider, which is very common in all of our enterprise. And you will be also applying a role-based access control. So this is one of the natural choice when it comes to access control management for your distributed AWS account itself. So the third topic, just give me a minute. Right. So the third topic is about managing the network connectivity across all your distributed accounts. Now, if I boil down all this network connectivity that you recommend from our AWS accounts perspective. So what is something which is needed? When you create all this distributed AWS accounts, it is natural for you to expect different applications or different AWS accounts to talk between each other, yeah? So which is basically the connectivity between the VPCs. And you will also naturally expect the VPC to communicate to the data center. And you will expect the VPC to communicate to the internet. And of course, you will be having all the branches from an enterprise perspective. It is very natural that you expect the VPC to communicate between the branches, yeah? So this is some of the connectivity requirements. We'll look at the patterns later. And so what I would consider as a tenets when it comes to the network connectivity for distributed AWS accounts. You need a centralized management where you have a single point of contact to manage all your routings and your networking decisions and the visibility in terms of the routing. And of course, it needs to be very scalable because it will be ultimately creating hundreds of AWS accounts for any enterprise use case. You naturally expect a multi-region connectivity for all those distributed VPCs. And basically is that when you connect multiple VPCs, it is natural that we will expect the VPC to communicate between each other, not necessarily one-to-one, but if you are grouping three different VPCs, you naturally expect three different VPCs to communicate between each other to have a free flow of network connectivity itself. You basically expect a transitivity in terms of your traffic moment here. And finally, of course, we'll be expecting a multicast and broadcast network traffic, network packet moments across all of our distributed VPCs. And end points because not necessarily all the, okay, for those resources which are hosted outside the VPCs, perhaps it can be your partner resources or even the AWS resources, AWS resources like S3, which operates in the AWS public IP address space, which means you need to have some form of a connectivity, network connectivity to those AWS resources which are not running in your own VPC and likewise for all the partner resources which are not operating in your own VPC. So these are some of the connectivity recommends on the connectivity core tenants, whatever would be expecting in a distributed AWS account management. Yeah. Now let's try to understand what different choices they have. So I'll be talking about the VPC pairing with VPC pairing. You basically connect two different VPCs together. But of course, if you are using this VPC pairing for your distributed account use cases, you'll be ultimately creating a mess network with the VPC pairing, which is definitely not scalable. And you will lack all the single point of contact. And you will lack of transitivity. It is that VPCA can communicate to VPCB and not necessarily VPCA to VPCC by providing both connectivitys together. So transitivity is missing. And also direct kind of gateway. I'll just exclude that option. Direct kind of gateway has its own limitation in terms of it is scalable up up to 10 AWS accounts, which means when you create hundreds of AWS accounts with the hundreds of VPCs, this is definitely not a scalable approach. But it has its own merits. It has its own merits for a connectivity use case. Perhaps we will just conclude now that this is something which is not necessarily scalable from a distributed AWS account perspective with the hundreds of AWS accounts or hundreds of VPCs. So the natural choices what we have is transit gateway is basically provides you the hub and spokes out of a management. And private link, we'll look at connectivity patterns very shortly. The transit gateway, private link for you to connect for your resources in the VPC to connect to the resources, you're hosted outside the VPC. It is necessarily that AWS resources or your partner resources. So private link is needed across all your distributed accounts. Direct connectors needed for you to communicate back to the on-prem. And perhaps RAM. RAM what you can do is this is not a random access memory. This is resource access manager. Perhaps if you're using this AWS organization, the RAM allows you to share the resources necessarily like say for example, transit gateway. So you can share the transit gateway submits across distributed accounts by way of associating this resource access manager. So it helps you with all the sharing for your organization AWS accounts. Now, we put this into perspective like what is, we basically, we have a transit gateway, private link, direct connect and RAM for our network connectivity use cases for our distributed account management, yeah. Now with this in picture, basically this is a gist of it where what we naturally expect from a network connectivity perspective is sort of a hub and spoke architecture where with the hub, you create all your networking resources where it can provide you with the routing decisions and your network security bag, and a centralized management for all your network traffic moments across your distributed VPCs. And all the member accounts which communicate back to the hub, you know, which by the form of associating back to the hub account to facilitate the connectivity or the network packet moments between the distributed VPCs itself, yeah. So you can put this into picture.   So you can basically create this endpoints in the shared services account as opposed to creating those endpoints across all the distributed accounts. Say for example, if you're creating an endpoint for S3, you know, if you're creating this endpoints for S3 across all your 100 AWS accounts, you can imagine the charges what it's going to take because ultimately it is all providing you the gateway to the underlying AWS infrastructure by way of exposing your private IP by associating elastic network interface. And then it provides you the, you know, the network connectivity path to the underlying AWS infrastructure itself. So it provides no value for us to associate into each of the AWS accounts, perhaps if effectively just the proxy. So what you basically do, like you create all those endpoints in a common AWS account, the hub account, and use the transit gateway, you know, as a transit gateway as a mechanism to expose all those, you know, expose all the traffic moments for those resources which are hosted outside of APC by way of associating the transit gateway together, yeah? So now this in picture, we'll see, we'll quickly go through some of the patterns. So we basically, you know, from a connectivity between VPC perspective. Now we, you know, we just discussed, we will be using the transit gateway, transit gateway for our hub and spoke related architecture. Now we can see for your multi-region recommends. Say for example, in this case, each of the apps will be associated part of the transit gateway, likewise for your app's portion in the different region itself. And perhaps for you to have the inter-region connectivity, what you will basically do, you will be basically doing a transit gateway pairing for it. So and this is really scalable from the perspective that you can associate hundreds of VPCs into a common transit gateway, yeah? And now let's try to expand this, you know, on top of this transit gateway. So once you establish this transit gateway as a connectivity pattern, you can basically expand the transit gateway for further use cases, you know, from a VPC to an internet. Say for example, if you wanted to communicate to, you know, internet from all your distributed VPCs, me coming in from spending most of the time and most of the time in financial services, the security is basically a main consideration, main priority, so security comes in for every topic. So what you naturally expect is basically is that you wanted to monitor the traffic moments or perhaps you wanted to whitelist the traffic moments for the, you know, for those traffic but just communicating back to the internet. So, you know, you can associate the transit gateway and from there it communicates to the common egress path and you can apply the network access firewall, you know, on top of it for you to have the host-based firewall sort of thing, yeah? And then, you know, if we expand this transit gateway pattern, you know, to our data connect use case. So now the beauty is basically is that since we have this transit gateway as pattern, you basically expand this, you know, transit gateway pattern for some of the, you know, other use cases as well like twice for, you know, on-prem. So say for example, in this case, you basically associate the direct connect, you know, into the transit gateway by way of creating a transit virtual interface. So which means this transit gateway as a pattern, it solves all the connectivity related requirements for all your distributed AWS account management, yeah? So, consideration that I have only two minutes left, we'll be just quickly going through the security at a scale for, you know, for our distributed AWS accounts perspective. So the final thing is basically managing the security at scale, you know, for our distributed AWS accounts, yeah? Again, from a security, you know, from a security at a scale, what is something which you naturally expect, right? So again, you wanted to automate the security checks and you wanted to have some intelligent threat detection, intelligent threat detection for various data sources, you know, from AWS, let's say the DNS queries, what you're still seeing to round 53 for some of the communication what is happening to, you know, happening out of your, happening out of the host, you wanted to have that monitored, you wanted to have some intelligent threat detection on top of it, or you wanted to have intelligent threat detection on top of your X3 access logs to identify any, you know, outliers or any exceptions, or you wanted to have, you wanted to have, you wanted to monitor your cloud trial logs for any outliers, for any exceptions from your natural trends itself. So that effect, you know, intelligent threat detection is something which is naturally expected for all this multitude of use cases across all of our distributed accounts. And we'll also expect a vulnerability management. We expect to track API activity and the API usage because everything happens in AWS is by way of interacting with the AWS APIs. And that's basically the beauty of AWS as well, no? So since everything happens via the API, you know, you naturally expect to monitor the API activity to understand if it is deviating from the natural, you know, your ongoing trends. And if there are any outliers, you wanted to capture, you know, on the fly. And of course, we expect to protect data at scale. You know, we wanted to preserve the data sensitivity at scale for all you distributed our AWS accounts use cases. Now, boiling down all this recommends into different services what we have in AWS which supports it. Sorry, I'll just conclude this with that. So, yeah, just one minute. Again, we expect some sort of a hub and spoke architecture, you know, like what we discussed for the network connectivity itself, yeah? So that you expect to run all your security related services into one common AWS account and try to cascade that down, you know, into all your distributed AWS accounts, you know, for you to manage those, all the security related recommends itself. So some of the services are quickly, quickly, you know, highlight, you know, what you notice here is basically the security hub, which is running all the security services AWS account. And I can also see the event bus.  So you can use the event bridge as a service to funnel down all your events, you know, your cloud watch events, your API activity, your conflict events. You can funnel down all those events into a security hub to take advantage of those.  You can also group those controls and, you know, manage this vulnerability management with the automated security response by way of associating into the security hub itself. You can also have your own customization, you know, on top of this event bridge events, what is being funneled down across the distributed AWS accounts itself. And that concludes my talk. And I thank everyone for joining my presentation today. Yeah. Okay. Thank you to the last speaker of the day is Badri. So next up.


Don't be holding, this is their starting lineup. Damian Hyatt in goal. They have a back four of Sadiki, Burton Devonte, Hodges, Zakia Wilson, Shevon James, playing at right back. Fabian McCarty, good to see him in the starting lineup. Shaqeem Powell, Donovan Sikri, completed in the middle of the park. Stephen Williams, Nicholas Nelson. Boy, hasn't he shot of the goals for his chop. Ten strikes to his name so far this season, hoping to be on the score sheet tonight. Dwight Merrick, of course, one of the players coming on loan from Mount Pleasant with this Don't Be Holding team coach by Lenny Hyatt. 4-3-3 is what they are playing here. Nelson, don't forget that it was a hat-trick last time out as well against Mullines for Nicholas Nelson, his first of the season. And here's the starting lineup for Harbour View, the 33-year-old Glenmore. Samuel, making his 13th appearance for Harbour View. Odell and Harding, of course, the captain, the side guard, Stuart, who's back in the island and immediately in the Harbour View, starting now to remain wrecking rage, and O'Kima Jones complete the back forth. Seem priestly, Anglain as well as Trey Bennett in the middle of the park. Omar Thompson, Andre Faken with four goals and Rowan Brown, the Trey up front. Yeah, goal scoring, a problem. Has to take a look at the full-time highlights. And there was a real lack of quality in the first half, especially from the stars of the East, Anglain's effort well over the top. And then Merrick with the effort from distance, beating Samuel at the near post. Would have seen it laid, went through the legs, and won the defenders. But it was a good hit, you know, it really was from Merrick. And that was the lead for Don Beholden. Harbour View tried to get back into this contest. That effort well over the top, couldn't quite get over it. But again, they didn't offer a lot going forward, the stars of the East. But they were methodical, they were surgical, they were clinical. Look at that ball from Segri. And look at the finish from Blackwood. It's first this season. That was just wonderful. 16 passes, they stringed. Before that finish from Blackwood. Wonderful stuff. Two nil, Don Beholden. Samuel's night was about to get worse. We'll show you that bit of inaction, so to speak in a little while. Segri's effort though had to be parried over by Samuel who had a moment of madness. In fact, probably a couple of moments of madness. Birket with the assist, Smith against his old club, Rajesh Smith. With the finish, not sure exactly what Samuel was thinking there. Birket knew exactly what he was doing. Well, Jay Smith applied the finish there. And that was three nil for the Don Beholden team. It was full-time too. Don Beholden with six shots, four of which were on target. Half of you didn't break the shot on target. 13,000, they committed three more than Don Beholden. They also had three at a cart. Half of you, two more than Don Beholden. Two corner kicks a piece. And Don Beholden with the majority of the possession as one would have suspected, would have occurred with this Lenny Hyde coach team at 55%. Devante, just celebrating your 19th birthday just over a month ago. How does it feel at your age to put together a performance like this? Well, me, you know, in me, I've just stayed focused right through the 90s. Keep my discipline from my teammates working with me. It's out there, out from there. Cree sheets have been hard to come by for Don Beholden this season. So how important was it to keep your concentration right throughout the 90 minutes? Well, from week in the training session, we are working on defense car. Every game we play, we give up two goals or a goal. So we work on that and we pay it off on the pitch. We work very hard tonight, out of the lads. Let's talk about personal as well. How worried was it for you to see your team at Nicholas Nelson going out, knowing the kind of season you was having so far and against a half of you team who has gotten the better of you earlier this season? Well, it was hard, but we know what the bench can do. The players and the bench can do. And you come on and you did very well. Are you going to make the playoffs? For sure, for sure, for sure. Congrats on your man of the match performance, Devante. Get some rest. I will look forward to seeing you next week. Thanks. Devante Hodges, our player to...


I'm on the hunt for the greatest meme in NBA 2K history, and so far, the meme to beat is the one I posted yesterday saying this. When an Elite 3 team loses to a squad of Amateur 2 players, and it was a photo of the Dwayne Wade buzzer beater and Kevin Durant just standing there cheese. Now, after half of the internet got angry at me calling Dwayne Wade an Amateur 2, relax. It's a meme. I just want retweets, man, okay? Calm down. You began to truly recognize the accuracy of this here meme. So for all intents and purposes, this is Agent Borga, a part of 2K meme review, and this is a 10 out of 10 meme. Yes, ladies and gentlemen, this is the meme to beat, so we're going across the internet on a voyage to find one better. On a side note, underneath that tweet, LD2K responded with a laughing emoji. The random wizard responded saying, Please tell the devs to fix pushing. LD2K responded saying, I already spoke to them. So basically the whole 2K community erupted in celebration. So I don't want to be the Debbie Down or anything like that, but I'm just letting y'all know that in the past few years, even when LD2K used to be with 2K as a community manager, we've heard I've already spoken to them a lot of time. That does not translate to it's going to be fixed. Very, very different thing. But I will hold out optimism. I just watched this live, so you have to too. D-Shirt, I got you, I got you now, I got you now. Oh snap! He missed! Verified on the rebounds! Pass to the back! That's the original Malik! Oh he shoots again! And then it's the air ball! Offensive rebounds! Malik back with the ball at the top of the 3 point line. Ziggs dacking! Another one! Another one, ladies and gentlemen! And another, and another one! Sorry, S. I hope you don't have your parents in the background trying to sleep or whatever. That was the most disgusting display. That was a comp game? Hold on, who was that? Brian the kid being point guard? Brian! Brian, why? Why do I always find Brian in these garbage situations? I think we've all collectively lost about 26 IQ points watching that together. You know what? Since it was my commentary, maybe 27. Basically, the entire reply section was trying to unsee what they just saw. I put out a tweet. I said, What's the funniest 2K meme you've seen all year? Grinding responded. Grinding D.F.'s uploading schedule. You losing weight. Every video I post, it's either agent bro is getting pretty sad at this point. You better start losing weight, cause this is just not a good look. Or it's agent bro, I see you've been grinding and losing some weight.  What is wrong with y'all? My boyfriend's friends gonna call him this morning while we're sleeping telling him to get on 2K. He's gonna get up and tell me they need me. You laughing sideways emoji? Yeah, they need him. Do you know what kind of friend you'd have to be to knowingly subject your other friends to playing with randoms? So when your friends need you, they need you, you gotta get up. They gonna run in here, mic'd up, throwing me his card on phone with... Guys, what is wrong with Twitter and Grammar? Is it that hard with DoorDash on it telling me to order some to eat? I'm hungry, man. And so I did order him some food with his money. Look how helpful I am. And he moved the couch closer to the TV. What? He moved the couch closer? Wow, ladies and gentlemen, I never saw that one coming. The end. Thanks for watching The Real 2K Wives of Twitter. If you're a real girlfriend, right, and you care about your guy, then you wouldn't let him play on a TV. He has no idea what he's missing out on without playing on monitors. It doesn't even have to be... It could be a $100 monitor and he will change his life drastically. So next Christmas, next Valentine's Day, instead of putting out these... Please! Getting viral, get him a monitor. $100, 60 Hertz monitor. It just has to be 60. Agent Borga rates this one 4 out of 10. What do I have to say about this one? What is there to say? I don't think there's anything really to say about this one.  That's the best you can come up with. Are you serious right now? I'm so disappointed in y'all. I put out a tweet expecting to literally die laughing and so far, I'm just thoroughly disappointed. That's 100 likes to y'all. This is a good meme. 0 out of 10.  Peer stretch shoots contested 3. Me. That's off. Peer stretch. Green. Me. Green. Guys, let's not joke about this, okay? Because this is a very serious situation. RDC world had his whole gimmick snatched from him. Soljue was probably a big fan. He went on the breakfast club and snatched his whole gimmick and nobody's talking about it.  Me sleeping him and won. See, that's why I have a house all to myself. So at 6 a.m. in the morning, I can be just as loud as I want to be. So go out there, ladies and gentlemen, to an expensive city like Toronto and rent a house all by yourself and watch your bank account deplete. That's one of my favorite things to watch happen every month. Dodgeball and headphone bugs. 2K developer neglecting the 2K community. Oh, that's a classic. Not funny. A close attention. L2, L2. Oh my God. Your guy has zero hands, my God. Why? Oh my God. Oh my God. Oh my God. Oh my God. Guys, do you see this? This is pure joy and happiness.  Swante looking at jump shot 25 and neglecting a good jump shot, ladies and gentlemen. Stop watching all these jump shot videos. There's no point. Especially if you're not getting better. Jesus, guys. Just use 11 as your base in Kyrie as your release. It is not complicated. Somebody responded this one. I'm on TikTok now hoping to have a lot of fun. Yo, can't I do a sponsorship in peace? God, damn.  How is this a meme? This is literally a thumbnail, guys. I got fat, yes. And then I made money off my ability to get fat. Have you ever seen anybody monetize their fatness before? Guys, this is unhistorical, unprecedented behavior.  It's 2K making YouTubers fat. When did Phantom upload this? I've seen my boy AG for me.   I don't, I mean, I don't know. I might bulk up one day. Get to the point! When you go from going outside all the time to staying inside all the time and then not changing your eating habits, you get fat. That's it. How has the dudes in the neighborhood look? Ah! Agent Borger rates that a two out of 10. You could do a lot better, my guy.  And then it's a pro one, elite two and elite three being bougies. That's a decent meme right there. That's pretty decent. I can tell us the old one because there's no pro ones being bougie right now. That is a sec, six and a half, 6.9 out of 10, ladies and gentlemen. Look at this guy go. Huh? There we go. Get to the mocap for NBA 2K. I don't know why they have professionals do it.  I'm gonna keep it a thousand million with you guys, man. These are not funny at all. Somebody told me to hop on NBA 2K subreddits. Let's do that. Dynamic duo.  Probably like a cello or a big violin. I don't know. So, okay, here's the thing guys. Know my team meme is gonna make sense to me because my team died a long time ago. Yannis needs to be packed. Yo, what? Yannis got wings on his back, man. That's another my team joke though. 1 out of 10, baby. When you were waiting to play a cages game for 10 minutes and then some squad just takes your place. Place. Damn it, man. The real tragedy here is that you'd be waiting to play a cage game by yourself. Now that is very, that's a very lonely decision. The only time you go to cages is when... Can't think of a time actually where you'd want to go to the cages. So many my team memes. This is why LD2K will forever be one of the... Can finish elementary school, bro. Put sentences together, man. I don't eff with Ronnie too much because he seems so arrogant and it's like he thinks he's above a lot of people. A groupie too. He's a clown.  Most satisfying part of the game of my life. I'm glad that in a time of need we could just come together in the community in the common hatred for one guy. You'd figure opening day of the season would draw a bigger crowd. Saw this on Twitter. Caption. This man bought his PS4 with him to the hospital after his wife gave birth. Is he right or wrong? And I can tell you one million percent guys that there is a lot of time you just sit there doing absolutely nothing except staring at a cute baby, okay? And so, yeah. The real question is how on earth he's playing with hotel Wi-Fi. I mean, hospital Wi-Fi. That's the real question we should be answering because to me, this looks like a walk-on pro-amp game. You need good internet for that or else you're going to be lagging with all kinds of latency. He's playing on a TV. To me, this guy is a hero, man. He's a forward thinker. What am I going to do in the hospital room except stare at a beautiful baby? In fact, sometimes they take the baby away because they have to do all the immunization and stuff like that, right?  So yes, this is the correct thing to do. In fact, I think you'll be wrong not to do that. I'm serious. This is the verdict, ladies and gentlemen. My meme is still the meme to beat. Yeah, I'm fairly disappointed. I thought Reddit was going to come with some bangers. They didn't. I thought my mentions was going to be flooded with tweets. You guys missed the mark. And so, I mean, listen, bro, unless you guys can come up with a 10 out of 10. Hey, if you guys enjoyed the video, make sure to drop a like, subscribe to the channel, click on this video and that video, this video or that video over there, all right? Click on one of them. And we'll catch you guys later. Mount. Peace.


Oh no, anxiety creeps up on me Is this how it's supposed to feel? Tell me when it's over I got someplace that I gotta be It won't leave My friends, hey Get out of your comfort zone It's a blessing in disguise Get out of what you call home Your name is written in the sky It might feel just like baby It's not the light Remember you want me I try to work I really wanted to get it right Trying to find some balance in my life I never really put up a fight I'm losing sleep