 Hi, thanks for joining the TechSoup webinar today. Ask the expert, and we do have some experts to be with us today. It's Amazon Web Service. My name is Aretha Simons. I'm the webinar producer here at TechSoup. This is being recorded, so you'll get the recording within 48 hours. I promise you, for everybody who's registered, you'll get the recording. I wanna just show you how you can participate with us today. You already know that you're muted, right? So you're gonna use the Q&A to ask questions. You can also ask questions in the chat room. They have experts here to answer your questions here in the chat room. If you need the closed caption, please turn on the closed caption using the CC button located in your Zoom menu. Again, we will record this and you'll get the recording within 48 hours. If you hear something that you like, aha, I need to share this, go ahead and share it with us and tag us on social media. Share with all your friends because we want everybody to know this information. We're going to the cloud, so let's get ready, right? So I'm gonna move off the way and turn it over to the two experts who are here today. I'd like to introduce Jamie Gluck. He is the Global Manager for Amazon Web Services. And then Mike George, he's a Senior Solution Architect at Amazon Web Services. Mike, I'm gonna turn this over to you, take it over. All right, thank you so much, Aretha. And it's a pleasure to be here today. My name is Jamie Gluck and I am here with my colleague, Mike George. And we are both from the AWS nonprofits team. Specifically, I'm a Global Program Manager for AWS nonprofits. And today is really dedicated to connecting with you and understanding what your questions are so we can enable you and empower you to leverage AWS for mission impact. So before we get started, I just wanna set some little ground rules and talk a little bit about how you can make the best use of this webinar. So the first things first in terms of an announcement is that the links will be available in the chat. So I'm about to speak about a couple of different programs that are happening here at AWS in support of nonprofits and I'll provide you with those links in the chat. So definitely check that out. Additionally, this is your time. This is dedicated to helping you understand how AWS can support your organization. So please ask the questions. There's no such thing as a bad question. We will do our best to get to all the questions but pop those questions as they come into your head into the chat and we'll spend some time afterwards. And then last, if you want to just make sure you can see a slide a little bit better, here are some of the instructions in order to zoom in on your screen. So in terms of the agenda today, first I'll be speaking about the AWS nonprofit programs. Again, what resources and programs are available to help your organization leverage AWS permission impact. Then I'll pass the mic over to my colleague, Mike, and he'll discuss a little bit about what's currently happening with your peers in terms of the ways that they're leveraging AWS to achieve their missions. And then of course, we'll definitely save time at the end for any questions and providing answers. Again, this is your time. This should be conversational. This is an opportunity for you to learn from us, the AWS expert about the ways that you can use this technology. So jumping right into the AWS nonprofit programs, I want to spotlight four. The first one is the AWS nonprofit credit program. And this credit program works in collaboration with TechSoup to provide $1,000 in AWS promotional credits. This credit is excellent if you're just getting started on the cloud or if you're well on your way in your journey while using AWS. It's a way to lower the impact financially of your use of AWS. Additionally, we have the Imagine Grant program. And while the submissions are currently closed, they're opening in the near future. And this is a program that encourages and inspires organizations of all shapes and sizes to submit their ideas about the ways that cloud technology can help their organization succeed. And we provide credits as well as cash to a select few organizations. Additionally, definitely want to save the date and moreover even register for the upcoming in-person conference called the Imagine Nonprofit Conference. This year, it's on March 22nd and 23rd in Washington DC. And we encourage you to register not only for the in-person one if you're able to make it there, but there's also options for tuning in virtually. And then again, we pride ourselves on our ability to connect with our customers and make ourselves available to organizations no matter their question and no matter their size. So I'll put a link in the chat for a way that you can connect with someone like me or like Mike to ask your questions even beyond this webinar. So definitely have the opportunity to speak to an AWS expert directly. So with that, I'll pass the mic over to my colleague to discuss a little bit more about how nonprofits are leveraging AWS. All right. Hi everyone. So my name is Mike. I am a solutions architect with AWS working with nonprofits. And so today what we're gonna be doing is talking about how you can roadmap your journey to the cloud. And I wanna start out by first of all talking about what other nonprofits are doing in the cloud. I think this is helpful to see, again, what are others doing and that can help spur ideas for ways that you can push your organization forward by moving to the cloud. The first organization I wanna talk about is the Rock and Roll Hall of Fame. You're probably familiar with Rock Hall. They have a lot of physical and digital assets related to the history of Rock and Roll. And until recently the Rock Hall used a lot of different technologies to store its files and some of the storage mediums that they use to preserve material were outdated. They were expensive to maintain and they were prone to failure. And you think about the kind of data that the Rock Hall has. They have videos of induction ceremonies. They have B-roll. They have artists to interviews and they have live concerts from some really unique artists like Aretha Franklin, Paul McCartney, Led Zeppelin, Elton John, Prince, and many, many more. And so you've got some really valuable assets as it relates to the history of Rock and Roll. So they launched a plan in 2015 to better preserve some of these assets. And they started out small. To save these assets, they landed on using Amazon S3, which is our durable object storage in the cloud solution. And then for objects that maybe they didn't need quite so fast retrieval, they used Amazon S3 GlacierD bar archive where they could store it, still get access to it if they needed to, but it would take maybe a little bit longer, but that trade-off then was they have a much lower storage cost per object. And so that's what they landed on. They then began to, and they ended up storing some objects that are two to three terabytes in size. Once they started saving some of these objects, some of these videos that encapsulate the history of Rock music, they began to build on the success by building out a digital management platform to support the organization of these video assets. So you can see in their example, they started out small and then they built on the success that they were able to do. And since they began this process, they've been able to preserve over 2,000 different video files that equates to around 300 terabytes of video assets. Let's look at another organization, code.org. You may be familiar with code.org. And code.org operates a learning platform that allows classrooms from all over the world or basically students from K through 12 all over the world to learn about computer science concepts. And code.org runs an annual hour of code event. And they really feel like they have one chance to get it right. During their hour of code event, they oftentimes see 10 times the traffic that they see during regular, during other parts of the year. And they feel like they have this one chance to get it right because when students come to their site during the hour of code, some of those students may not wanna be there. They may not wanna learn about computer science techniques, but code.org feels like, okay, if we can get people to come in, then we can get them interested in computer science, which could literally change some of their lives. And so to make sure that they had the reliability and the scalability that they need to really get it right the first time, code.org moved their infrastructure to AWS. They found that they were able to support millions of school-aged children from hundreds of countries around the world, again, supporting 10 times the traffic that they normally see. They did this by putting their servers on Amazon EC2 and they took advantage of Amazon, I'm sorry, advantage of AWS auto-scaling so that they could adjust their capacity up or down depending on the amount of traffic they see. So during hour of code events, they scale their systems up, people access their sites as that traffic goes away, they scale back down, and they pay for only what they use. And they found that in doing this, not only were they able to support this influx of students, but they ended up saving money in the process. So that's an example of what code.org is doing. The next one I wanna talk about briefly is the Los Angeles LGBT Center. The center really wanted to build a call center and they had a couple of people on staff that had experienced building call centers and they knew it was typically a fairly complex process, a lot of upfront planning usually needed to take place. So when they wanted to build this call center, they looked at a number of solutions and ended up settling on Amazon Connect, which is our virtual call center in the cloud solution. Much to their surprise, they found that they could build a call center in literally a matter of minutes and they ended up building like fleshing out that call center and releasing it within about a week. They were surprised with how easy that was. You know, they were able to go from a simple idea to testing this out to have a fully deployed, scalable, secure solution in literally just a couple of days. So this saved them time and money and resources that they could then use in forward, pushing their mission forward. And it's important to understand that the call center that they've set up is largely the face of the center for individuals that don't come in directly. So individuals can call in and have, ask questions about upcoming appointments or things related to mental health services or really anything that the center does. The center has 50 staff members that support 30,000 clients in the clinic. One of the things that they were able to do that was pretty interesting is they ended up doing a fundraising event with KTLA, which is their local TV station. They had a live telephone and during the telephone, they were able to raise $1.3 million. As the calls came in, they were able to scale out their call center. As the telephone ended, they were able to scale in their call center. Again, paying only for what they use without any upfront costs or anything like that. And the last nonprofit I wanna talk about is Mercy Corps. And Mercy Corps has a mission of alleviating suffering, poverty and oppression by helping people build secure, productive and just communities. Mercy Corps works in over 40 countries and they have over 5,000 team members who work side by side with people who are living through poverty, disaster, violent conflict and living through the impacts of climate change. One of Mercy Corps missions was they wanted to identify the price of a food basket. And a food basket, if you're not familiar, is the basic staples that someone needs to survive. So this will include usually things like rice or flour and a number of other things. They found that as if they could predict the price of each of the items within a food basket, they would then have good indicators on when they needed to work with other NGOs to bring aid into the country. And so they actually did this in Syria. They calculated the price of a food basket through some AIML services that AWS offers. They found that they had around an 88% accuracy per food basket item. And this helped them, again, be much more responsive to the needs of the user, the needs of their community. So the needs of the people within Syria that needed aid. So that's some examples of what other nonprofits are doing with the cloud. What I wanna do now though is briefly, I just wanna pause for a second and ask where are all of you in your cloud journey? Are you asking what's the cloud? If you are, what I'd like you to do is go to the chat and put in a one. If you're aware of the cloud but not really doing anything in there, put a two. If you'd like to run something in the cloud but you're not really sure where to start, put in a three. If you're thinking of running workloads, put a four. And if you're actually running workloads, put a five in there. And let's just see where everybody is at. I just lost my Zoom, so give me a sec so I can see what everyone's response is. No worries. Jayman here, we're getting kind of a mix. Lots of ones but also seeing some fours, some fives, some two. So it sounds like we've got a good mix in terms of competency and experience using the cloud but definitely a good group of those ones and twos just learning how to get started. Okay, awesome. All right, so let's talk about some benefits of moving to the cloud. So when you think about moving to the cloud, when I talk with customers that are thinking about moving to the cloud, they typically think of AWS these things here, like kind of the core infrastructure building blocks like compute, I need servers. I need security tools. I need locations where I can deploy this. And that's definitely true. You can get that with AWS. But we also have over 200 services built on these kind of these core foundations. And one of our goals is to help push you further up the stack. And so by that we mean, if you're managing a server, that's actually distracting you from doing something with your mission. There's nothing that differentiates, if you're managing a server, there's nothing about managing that server that differentiates you as an organization or differentiates your mission. It's keeping the lights on work. And we often call that work undifferentiated heavy lifting. That's the muck of keeping the lights on. It's important muck, but it's not differentiating muck. So that's why we have these higher level services that you can leverage that allow you to move faster. And so these are things like virtual desktops in the cloud. We have services to support IoT. We have machine learning services. If you have a lot of machine learning experience, great, we have tools to support that. If you have no idea what machine learning is, great, we have tools to support that as well. We have tools to support analytics. We have media services so that you can transcode video and deploy it and broadcast and make it easy to have video on demand. We have solutions to easily build mobile applications and database platforms. Anyway, there's a lot of different services here. So part of what I wanna do is, in terms of talking about the different nonprofits, the different stories we've talked about, we gave you some really simple examples of starting out small and we had some examples that are maybe a little bit outside the box, like call center solutions and AIML solutions. So there's a lot of different things you can do by moving to the cloud. In fact, we typically see that there are five main things that nonprofits get when they move to the cloud. And the first thing that we generally see that nonprofits get is agility. What that means is you can easily spin up resources as you need them. So that means you can spin up hundreds or thousands of servers if you needed to. But this also means that you can really quickly develop and roll out new applications. So you can experiment and you can innovate more quickly and frequently and if the experiment fails, no harm, no foul, you just turn it off. The second advantage that we see nonprofits get is cost savings. Again, you're paying only for what you use and you think of it like a light switch. When you're in your home and you flip a switch, the power company sends electricity to that light bulb, right? Likewise, when you turn off the switch, the power turns off. It's the same way with cloud computing. You wanna turn on that switch, pay for the server that you're using and when you turn it off, you don't wanna pay for it anymore and that's exactly what you can do. The third advantage we see nonprofits see is elasticity and what this really means is, if you've ever had to manage an on-prem data center or otherwise have to manage capacity, you really need to buy enough servers and enough capacity to support your organization at peak levels of activity. But you don't need to worry about that in the cloud. You pay for only what you use and if you need more servers, you can spin those up and if you need less servers, you can spin those down. And again, you only pay for what you use and you can put safeguards in place so that that automatic scaling can happen for you up to a certain predefined threshold that you define and then when you want to scale down, you can scale down to a certain predefined threshold that you define. The fourth main thing that we see that nonprofits can get access to is innovation. So this is especially true with nonprofits that you can certainly innovate in IT or from an IT perspective in a nonprofit but it takes a lot of effort and it takes a lot of funding. And that's typically outside the realm of what most nonprofits want to do or are able to do. And by using AWS, you can get access to the latest services and features and you benefit from what AWS is providing and you don't have to build it yourself. And that means that you can spend more time working on your mission and trying to differentiate what you're trying to do as an organization instead of that undifferentiated heavy lifting that I mentioned earlier. The last main thing that the nonprofits get from moving to the cloud is our global footprint. So you can deploy globally literally in minutes. If you wanted to deploy servers to Singapore right now, we could, I mean, it's trivially easy to deploy servers anywhere in the world. All right, so there's a lot there. So now the natural question is, okay, how do you get started? So let me tell you, it's a very easy approach to get started. Now, with that said, keep in mind that every organization's cloud journey is unique. To succeed in your transformation, you really need to think about what are you trying to do? What is the benefit that you get from going to the cloud? That's really that envisioned phase that I have up here. In the envisioned phase, you identify the why. What are you doing and what value does it bring? Once you've done that envisioning phase, once you've identified your why of moving to the cloud, then you can move to phase two, which is aligning. Aligning is figuring out the who and the what. Once you've figured that out, you can launch. Launching is just, in many cases, as simple as deploying something to the cloud. And then once you've deployed, you can measure it, you can figure out if there are any gaps that you want to refine and then you can go to the scale phase where you again measure those gaps and you keep refining what you built or you can build new services and features. And so we really see this as a continuous process from figuring out the what that I want to do to figuring out how I'm going to do it to building and launching, to then looking at any gaps or any next steps and continuing this process over and over again. Okay, so I've explained these four steps briefly. Jamie, maybe you could help me out. What I'd like you to do is in the chat, if you're in the envision phase, I'd like you to put a one in there. If you're in the, so envision phase is figuring out the what, of what you want to do in the cloud. If you're in the alignment phase where you're trying to figure out the how and the who, put a two in the chat. If you're launching things right now in the cloud, put a three. And if you've already done these things, but you're looking back to see what we've done and you're refining and improving, put a four in there. So we're seeing a lot of ones, some twos. I see one four, Mike, but perhaps you can speak a little bit about what our audience members who are in the one phase might be able to do to move forward towards four. Yeah, so that's exactly what we're going to talk about here. So what I want to do now is I want to look at each of these four topics and talk through, okay, what does this actually mean? And let me give you some concrete examples of what a nonprofit could do. So let's start out with the Envision phase. Now in the lower right-hand corner, hopefully you can see I've got a map, so you can orient where we are. We're in the Envision phase right now. Again, the Envision phase is really identifying what do you want to do in the cloud? And having a goal is oftentimes all you need to get started. Think about what do you want to get out of moving to the cloud? Is it better efficiency? Is it cost savings? Is it organizational transformation? Maybe you want access to technology or tools or services that you don't currently have access to or maybe it's something else, but you need to identify this why of your cloud journey. And once you've identified the why, you can then align this vision among your other stakeholders. Okay, so let's give you some concrete examples here. So maybe as an example, you want to increase fundraising that's your goal and you identify that you can do that through maybe better donor management or maybe you want to have personalized email campaigns to help encourage donation among some of your more generous donors. So that would be an example of a why or maybe you don't need to worry about fundraising and well, everyone has to worry about fundraising. Maybe what you want to do is you want to worry about or you want to do a better job showing the impact that your organization has towards its mission. So your why there might be, I want to produce public dashboards to better show that impact. So those are some examples there, but again, the first phase is really figuring out that why, the value that you can get from moving to the cloud. Okay, so now once we've done that, we move on to the second phase, the alignment phase and getting alignment is probably the hardest part of any cloud journey. The reason for that is because in many cases, you're asking people to change and any change, even good change can be really hard to do. It's important in the alignment phase that you identify a single threaded leader who's responsible for your cloud adoption efforts. And this becomes even more critical, the larger the organization becomes. Now, if you are a larger organization, that single threaded leader will likely have a team. And that team will ideally oversee some sort of cloud team. You could call it a cloud center of excellence. You could call it a centralized cloud team. I mean, there's a lot of different names for it, but basically that individual in that group are responsible for helping the organization in adopting cloud services. In this phase again, you're basically identifying, okay, remember in the envision phase, I've identified what my goal is. The alignment phase, I now talk through the details of what I'm trying to do. Who's going to do the work? How am I going to do the work? When is that work going to get done? So it's really putting some meat on the bones of that goal, if that makes sense. Okay, so let's talk about some concrete things that nonprofits can do here. So really once you've identified your goal, you need to identify who owns each goal and get those stakeholders together so that you can identify requirements. Making sure that you include everyone who's going to interact with this project is going to be critical. You know, maybe you need to identify who your end users are. Who's the developer? Who's responsible for maintenance of this solution? Oh, we lost them, Damon. Are you able to- That's what I think so, yeah. Hey, Mike, if you can turn off your video, perhaps your bandwidth will be a little bit stronger. You're on a roll there, but we'll give you a couple of minutes to just pop back on, not a problem. I want to take this opportunity to answer one of the questions that came in. It's a really good question. And the question comes from PFEW asking, are there limits to what the $1,000 and AWS promotional credits can be used for? For instance, can they be used for existing AWS customers or can they be used to cover services such as LightSale and Route 53? So great question. And the answer is, no matter whether you're a new customer or not, you can absolutely leverage the $1,000 and AWS promotional credits. And while there's a little bit of nuance in terms of what they cover, the vast majority of on-demand services are covered. So absolutely to Route 53 and absolutely to LightSale. So yes, you can use the credit, no matter whether you're a brand new customer or an existing customer. And yes, they can be used for on-demand services such as LightSale and Route 53. So back to you, Mike, you're on a roll and let's pick up where we just left off. So I dropped there somewhere. Can you help me know when I dropped? Was it on this slide? Exactly right. Okay, great, great. So I wasn't talking on my own for five minutes there. No, no, no, we're with you. It's just right at this slide. Awesome, great. So again, I was talking about the example of maybe one of your concerns in moving to the cloud is that you don't have qualified staff. They don't have expertise in cloud. Great, well, we can help you with that. There are a lot of ways to help. We have training solutions. We have upskilling solutions. We can help you connect with our ProServe team or one of our partners to again, help upskill your team or help you with staff augmentation or maybe even take on the project for you and then give it back to you once it's completed. So again, there's a lot of different ways that we can help you. But it's important during this phase to get your concerns out into the open to make sure that everyone's on the same page and is ready to get started. All right. So in the envisioned phase, we figured out what our goal is in the alignment phase. We figured out how we want to achieve that goal. We've surfaced any concerns we have. We've tried to resolve those. Now we're in the launch phase. Really the launch phase is thinking about, well, it's really launching the thing that we're planning, building and launching that and then thinking through, how do we know that we were successful? Have we established any success criteria? What does the definition of done in our case? So make sure you think through those criteria and have some really clear guidance so that you know whether your project was successful or not. So let's talk about some concrete examples here. Again, I talked about how in the envisioned phase, we talk through our goal, we align on that and then we start building and deploying something. So really it's important to identify a challenge. Working with us with AWS, we can help you design a solution and build out a pilot. Your pilot should have really clear goals and metrics. Again, we can certainly help you with that. You wanna have these measurable outcomes so that you can identify whether you were successful or not and you can identify areas of improvement in the future. We talk a lot about working backwards here at AWS and by that we mean, figure out what that goal is and then trace your steps backwards to determine what steps you have to take to meet that goal that you want to achieve. And we use this process to build our services and it's how we support our customers and by doing this, this helps us stay laser focused on that opportunity that we want to achieve and it helps us maintain flexibility in how we achieve that goal. So as you go through this launch phase be thinking about where's that value that we want to achieve? What technical constraints keep us from realizing it? And again, working with AWS or with partners that we help you work with, you can identify that process. You can identify that value and make sure that you see that value in the projects that you launch. All right, and then the final phase is really the rinse and repeat phase where you've launched something, you've now measured it, you've identified if there are any gaps, if there are you can measure those gaps and go back through the envision alignment and launch phase to start closing those gaps or maybe there's a new project that you want to develop and then you just put that through the same phase again where you envision, you align, you launch and then measure. And what we found with a lot of customers is as they follow this process you'll find that that initial win that you get will spark a lot of other ideas and projects. Oftentimes that first project is gonna be the most difficult but once you begin it and start seeing some success you're almost immediately gonna see a flywheel effect here. Okay, so let's talk about some ways that we can help you and some resources that are available to you. I have some QR codes so feel free to scan these if you want. The first is our nonprofit credit program. Jayman talked about that at the beginning. This gives you access to up to $1,000 in promotional credits. Again, this allows you to begin building solutions without any upfront investment in physical infrastructure. We have our nonprofit technical hub and this is where you can go if you're just starting your cloud journey or maybe you're looking for what are other customers doing? What are the best practices for certain workloads that I'm trying to deploy? Our nonprofit technical hub has a lot of information in those areas. Maybe you need help from a partner or someone to help you be successful. So that's really where our partner program comes into play here. Our nonprofit competency partners can help by either providing end-to-end resources, staff augmentation, project work and basically help you be successful on whatever that what is that you've defined during that Envision process. And finally, we wanna help you. So that final QR code will take you to a contact us page. If you don't know who your account executive is, then let us know and we can put you in touch with who your account executive is. They can loop in a solutions architect like myself and we can help guide you on your cloud journey through these four phases that we've talked about. Keep in mind that we've helped over 7,500 different government agencies, 14,000 different academic institutions and 35,000 different nonprofit organizations. So we wanna help you be successful. So in terms of your call to action, what you can do, again, identify that what and the why of your cloud journey. Once you've identified those, then you simply align on how and who, how are you gonna do it and who's gonna do the work? You launch a pilot, you measure success and then you iterate. But that's really all there is to it. So let's open it up to Q and A. Jamie and I heard that you were answering some questions. Are there any additional questions we can help answer? Yeah, absolutely. First and foremost, thanks so much, Mike. Really appreciate that overview. Hopefully it was inspiring to the audience to get them started as well as to help them along their journey to and on the cloud. I wanna highlight one question that we got but I think might resonate a lot with our audience members. I think one second also, Mike, can you go back to the QR code? I think that would be also a good hold slide so people can kind of access these resources. But so the excellent, excellent. So the question is, this person has a simple website on WordPress and they fundraise through it, but they don't necessarily have the volume or the need for a robust call center. They don't get all that much traffic but they know that the cloud has value but they're trying to understand what might be a good kind of starting point for AWS for an organization that doesn't yet have that immediate banging on the door type of need. There are a lot of things to look at. I mean, the first thing is if you have a data center or a server in the closet or any sort of computer that's running that's supporting your mission or your membership that is probably an opportunity to consolidate and put into AWS. You'll get better resiliency, you'll get better security. One of the problems with running things in your office is you see a computer under a desk and you say, what is this? What does this thing do? And people are like, oh, I don't know, turn it off. We're kind of afraid to, we don't wanna break anything. You don't really have great visibility when you're running servers on-prem of what they're actually doing but when you put things into the cloud you have complete visibility into everything that's running. So that's one thing I would think of. I'd also think about what does your member outreach look like? We have a lot of services like Amazon Pinpoint that allows you to have targeted messaging to your end users, whether it's through email or SMS or what have you. That's something to look at. Jamie, do you have other suggestions for that? Yeah, those are excellent. And I think in my experience from working with organizations with a similar sentiment and question, really just getting started opens the doors to opportunities, to questions, to people, to knowledgeable resources that help inform your journey. It's almost about the getting started helps you decide where you're going as opposed to understanding exactly what your destination might be and then getting started. So I think a combination of this QR code on the far left which is the credit program plus the QR code on the far right which is support from our nonprofit team over here at AWS. Those two things combined can empower your organization to experiment and to dip your toes in the water, get started to a mic's point, maybe explore some member and donor engagement, maybe see what you can do with your database that you haven't yet considered. So all that combined, again, just get started. You can experiment kind of risk-free and then the rest seems to unfold from there. So excellent question. I'm gonna go on to the next question. And while I'm reading this, I wanna encourage all of our listeners to continue to ask their question. I know you're here for a reason and we have this dedicated time for you to answer those questions. So the next one comes from a viewer named Ashwin that says that they have some data and they know what kind of automation they wanna do with it but how do they know what services AWS can offer for achieving that automation? And maybe more over Mike, you can explain to our audience with so many AWS services, where and how do they navigate and what resources are available to help them understand the connection between the service and the solution they're trying to achieve. Yeah. So there are a couple of things that come to mind here. First of all, I mean, when you log into the AWS console, we have a services dropdown. If you drop down the services, you're gonna see 200 plus services and it can be overwhelming with the number of services that we have available. The first thing again, I'd recommend is by using that QR code on the far right, you can get in touch with a solutions architect like myself and we're more than happy to help you look at your workload and identify, okay, this piece right here, this should be an AWS Lambda function. This piece right here, this data transformation, this is a AWS glue job. I mean, so we can help identify what the specific services are for you. So that's one way to approach this. Another way to approach this is we have a solutions library where we have a lot of pre-built kind of vetted solutions that are common patterns we see people perform on AWS. You can go to our solutions library and in many cases, there's a template you can click that will deploy those resources in your account. So you don't really have to worry about building anything. It's pre-built for you as part of the solution and then you can just put in your data and you can go on your way. So those are two ideas that come to mind. Excellent, great. I am gonna move on to the next question. Thanks so much. I think it all comes back to leveraging the support that's out there already. Again, I can't emphasize this enough. What we hang our hat on is providing that unique customer experience and partnership experience for nonprofits. This isn't just another team that supports any type of organization but moreover we know the nuances and in and out unique to your organization. So get in touch with that QR code on the right. So this is a little bit more of a in-depth question, Mike. It comes from Justin that says does AWS offer a hybrid cloud solution that enables on-premises data storage and access that syncs with cloud storage specifically in relation to Amazon WorkDocs but maybe you can also speak about it a little bit more as a high level about kind of a hybrid cloud solution and the pros and cons and what someone might wanna do when considering that as an option. Yeah, so we wanna avoid the answer. It depends in terms of what your solution is but oftentimes we come back to that because it really does depend on the specific use case. Maybe it's latency or performance requirements you have. There are a lot of different solutions and just to talk through those briefly, yeah, there are definitely some hybrid solutions that we have. We have solutions with VMware where you can run VMware, VMs on-prem and in the cloud. We have solutions where maybe you want to run compute closer to your end users. We have solutions called AWS Outposts where you can run compute and databases really close to your users but you control them from the AWS data plane. So the servers are physically installed in your data center but you can control them through the AWS console. There are likely other solutions that we have out there that I'm just not thinking of right now but again, feel free to contact us. Let's have a deep dive on your use case and we can help you come up with a solution. Fantastic, thanks so much Mike and speaking to that point of contact us I just wanna acknowledge, we see the question from TEEEH. It's a great question. It's about elastic bean stock and the comparability between that and EC2 instances to that current viewer definitely reach out to us scan. We have the answer to that and it's just a little bit more in depth of the question. So can you talk a little bit Mike about what might be the future in terms of AI solutions for some of our nonprofit needs? In particular, we have a question from Joe who's talking about a database that collects data and some frequently asked questions from their constituents. And the question is, does AWS offer an AI solution for database to collect data or answers to questions posted in platforms like Quora or others? Once those responses are collected can they be sorted to the most relevant and researched by AWS? So I think it's just an overview of the value and potential for AI to help with questions that come in frequently to organizations as well as any other use cases you might be aware of. So yeah, great question. So first of all, I mean, let's talk about just briefly our AI ML stack. I don't wanna get into it too deeply but basically we have a couple of layers of our AI ML stack. We have kind of the DIY layer where you wanna manage everything yourself you're super comfortable with really deep ML stuff. We have a layer above that where you're deep in ML but you don't wanna manage infrastructure and we have a layer above that where I don't wanna manage anything and I may or may not know anything about ML but I wanna take advantage of ML services. So we have services like Amazon recognition which is a computer vision service. We have the ability to create chatbots. We have the ability to create forecasts. There's dozens and dozens of different services. So what I'm seeing in terms of like a trend in AI ML is continuing to lower that bar so that it's easier for people that don't have machine learning expertise to get into ML. Getting into ML without having some of these higher level services is a challenge. Like you really need like a deep background in statistics or data science or something like that but by removing some of those obstacles we've really made it a lot easier for people that literally have no knowledge of how machine learning works to take advantage of that. Now, in terms of that specific question we do have services like Amazon Kendra which is essentially a full text indexing and searching solution where it can index content that you gather. Maybe that's questions from other sites or content that you have and users can enter queries that can automatically find the most relevant content for you. But there's a lot of other things we could do as well just depending on what the specific use case is there. So it's a very deep and broad topic. Yeah, absolutely. And I think that can sometimes be scary and we wanna recognize that but at the same time, it's empowering. I mean, I'm confident in saying that it's really not about if the cloud it's really more about when. So I wanna applaud everyone who's still here with us who showed up who are really investing in understanding how this technology can bring value to your organization because this is absolutely the right first step. You are in the right place and between what Mike has provided in the past 40 or so minutes as well as these resources that are right in front of us on the screen we are here to support you in your learning and in your progress and in your journey and using AWS for mission impact. So I wanna wrap up with one last question. Oftentimes we don't have the opportunity to have an audience of nonprofits like we do currently. And I wanna ask a question I'm gonna post it in the chat as well. Give me one second, but essentially I'd like for you all to share for the sake of our understanding and to continue to provide as best of support as possible a little bit more insight into what would be most valuable in terms of support or continued support to help you use AWS. So go ahead and look in your chat and answer one, two or three. So if it's one, it's that you've already leveraged the AWS promotional credit, but you're looking for more. If it's two, you really wanna speak with peers in your community to understand how they're leveraging AWS and how you can make use of what they've done to add value to your organization. And then the third one is if you're looking for trainings you want to just explore on your own and learn on your own. So I see some answers coming in there. Thank you so much. I'm seeing some ones and threes, some twos and threes. Okay, three, so excellent. Thank you very much. This is really informative. Again, it helps Mike, myself and our entire AWS team ensure that we're providing you with those specific resources that are needed to leverage the cloud for mission impact. So thank you so much for taking the time to join us today. It's our pleasure to see you here again to restate for the sake of emphasis. You are absolutely in the right place. It's not a matter of if, but really matter of when the cloud continues to provide value for your nonprofit. So with that, I hope everyone has a great rest of your day. Please take a moment to scan some of these QR codes to get in touch and upwards and onwards. We'll see you on the cloud. Thanks so much. Thanks all.