Author Spotlight: Margaret O’Toole, WW Tech Leader in Sustainability at Amazon

{"value":"*The Author Spotlight series pulls back the curtain on some of AWS’s most prolific authors. Read on to find out more about our very own Margaret O’Toole’s journey, in her own words!*\n\nMy favorite part of working at AWS is collaborating with my peers. Over the last five years, I’ve had the pleasure to work with a wide range of smart, passionate, curious people. Many of whom have been co-authors of the blogs we’ve written together.\n\nWhen I joined AWS in 2017, I joined as a Cloud Support Associate in Northern Virginia. My team focused on DevOps, and while I focused on Containers mostly, I was also pushed to expand my knowledge. With that, I started to invest time with [AWS OpsWorks](https://aws.amazon.com/opsworks/) (in large part thanks to Darko Mesaroš (Sr Developer Advocate), who many of you may know and love!). Although I was really excited about the agile, scalable nature of containers, I knew that it was important to understand how to manage configuration changes more broadly.\n\nIn 2019, I decided to leave AWS Support and become a Solutions Architect (SA) in Berlin. I’ve always been really interested in systems and how different components of a system worked together—in fact, this is exactly why I studied computer science and biology at university. My role as an SA pushed me to look at customer challenges from completely new perspectives. Now, instead of helping customers with a single component of their workload, I worked with customers on massive, multi-component workloads. I was exposed to new technology that I hadn’t worked with in my Support role, like [AWS Control Tower](https://aws.amazon.com/controltower/), [Amazon SageMaker](https://aws.amazon.com/sagemaker/), and [AWS IoT](https://aws.amazon.com/iot/). In many ways, I was learning alongside my customers, and we were bouncing ideas around together to make sure we were architecting the best possible solutions for their needs.\n\nHowever, I always had a passion for [sustainability](https://aws.amazon.com/sustainability/). When I was in university, I was mostly interested in the intersection between natural systems and synthetic systems—I really wanted to understand how I could combine my passion for sustainability with the power of the AWS Cloud. And, as it turned out, so did many others at AWS! We spent most of 2020 working on experiments and writing narratives (the Amazonian version of a pitch), to better understand if customers wanted to work with AWS on sustainability related challenges, and if so, on what topics. My work today comes directly from the results of those initial customer interactions.\n\nThese events also marked a big change in my career! In 2020, I transitioned to a full-time sustainability role, becoming a Sustainability Solutions Architect—a novel function at the time. Today, I’m based in Copenhagen, and my focus is to help customers globally build the most energy-efficient and sustainable workloads on AWS. Every day, I find ways for customers to leverage AWS to solve challenges within their sustainability strategy.\n\n\n#### **Favorite blog posts**\n\n\n##### **[Perform Continuous cookbook integration testing and delivery for AWS OpsWorks for Chef Automate](https://aws.amazon.com/blogs/mt/perform-continuous-cookbook-integration-testing-and-delivery-for-aws-opsworks-for-chef-automate/)**\n\n\nMy very first blog at AWS was on how to do Continuous Integration / Continuous Delivery with [AWS OpsWorks](https://aws.amazon.com/opsworks/). A group of us in AWS Support were asked to build out a lab that could be used at [ChefConf](https://www.chef.io/chefconf), which we turned into a blog post.\n\nMany customers are using tools like Chef Automate and Puppet to manage large sets of infrastructure, but finding cloud-native approaches to these tools was not always super obvious. My favorite part of writing this blog post was combining cloud-native ideas with traditional infrastructure management tools.\n\n\n##### **[How to setup and use AWS OpsWorks for Chef Automate or Puppet Enterprise in an isolated subnet](https://aws.amazon.com/blogs/mt/how-to-setup-and-use-aws-opsworks-for-chef-automate-or-puppet-enterprise-in-an-isolated-subnet/)**\n\n\nWe also saw that customers wanted to understand how to leverage cloud network security in their OpsWorks environment, and so we decided to build a walkthrough on how to use OpsWorks for Chef Automate or Puppet Enterprise in an isolated subnet.\n\n##### **[How to set up automatic failover for AWS OpsWorks for Chef Automate](https://aws.amazon.com/blogs/mt/failover-for-aws-opsworks-for-chef-automate/)**\n\n\nIn addition to wanting to move fast and be secure, our customers also wanted to have reliability baked into their workloads. For many customers, their Chef Automate Server is a critical component, and they cannot afford downtime.\n\n\n#### **Sustainability content**\n\n\n[Ask an Expert – Sustainability](https://aws.amazon.com/blogs/architecture/ask-an-expert-sustainability/)\n\nIn August 2021, Joe Beer, WW Technology Leader, and I worked on Architecture Monthly discussing the overlap between sustainability and technology.\n\nSustainability is a really broad topic, so in order to help scope conversations, we broke the topic down into three main categories: **sustainability of, in, and through the Cloud:**\n\n- **Sustainability of the Cloud** is AWS’s responsibility, and it covers things like our renewable energy projects, continuous work to increase the energy efficiency of our data centers, and all work that supports our goal of operating as environmentally friendly as possible.\n- **Sustainability in the Cloud** is the customers’ responsibility. AWS is committed to sustainable operations, but builders also need to consider sustainability as a core non-functional requirement. To make this clearer, a set of best practices have been published in the Well Architected Sustainability Pillar.\n- **Sustainability through the Cloud** covers all of the ways that the cloud solutions support sustainability strategies. Smart EV charging, for example, uses the AWS Cloud and AI/ML to lessen the aggregate impact to the grid that may occur because of EV charging peaks and ramp ups.\n\nThroughout 2021, we worked with customers in almost all industries on both sustainability in and through the cloud, putting together a lineup of various [sustainability talks at re:Invent 2021](https://aws.amazon.com/blogs/architecture/deepen-your-knowledge-of-architecting-for-sustainability-at-reinvent/).\n\nA highlight for me, personally, was seeing the [AWS Well-Architected Framework Sustainability Pillar whitepaper](https://docs.aws.amazon.com/wellarchitected/latest/sustainability-pillar/wellarchitected-sustainability-pillar.pdf#sustainability-pillar) released. After spending most of my AWS writing career on internal documentation or blog posts, leading the development of a full whitepaper was a completely new experience. I’m proud of the result and excited to continue to work on improving the content. Today, you can find the pillar in the Well-Architected tool and also explore some [labs](https://www.wellarchitectedlabs.com/sustainability/).\n\n[Architecting for sustainability: a re:Invent 2021 recap](https://aws.amazon.com/blogs/architecture/architecting-for-sustainability-a-reinvent-2021-recap/)\n\nWe also did a deep dive into one of the sessions to highlight some of the key themes from the Well-Architected Pillar and the unique actions Starbucks took to reduce their footprint.\n\n\n\n\n\n#### **Elise Chahine**\n\n\nElise is Senior Program Manager for AWS Architecture Content, where she manages the Architecture Blog channel. Elise works with authors to develop succinct, technically accurate posts that help customers architect. When she's not rubbing shoulders with the brilliant minds of AWS, Elise enjoys a quiet life with her family in New England.","render":"<p><em>The Author Spotlight series pulls back the curtain on some of AWS’s most prolific authors. Read on to find out more about our very own Margaret O’Toole’s journey, in her own words!</em></p>\n<p>My favorite part of working at AWS is collaborating with my peers. Over the last five years, I’ve had the pleasure to work with a wide range of smart, passionate, curious people. Many of whom have been co-authors of the blogs we’ve written together.</p>\n<p>When I joined AWS in 2017, I joined as a Cloud Support Associate in Northern Virginia. My team focused on DevOps, and while I focused on Containers mostly, I was also pushed to expand my knowledge. With that, I started to invest time with <a href=\"https://aws.amazon.com/opsworks/\" target=\"_blank\">AWS OpsWorks</a> (in large part thanks to Darko Mesaroš (Sr Developer Advocate), who many of you may know and love!). Although I was really excited about the agile, scalable nature of containers, I knew that it was important to understand how to manage configuration changes more broadly.</p>\n<p>In 2019, I decided to leave AWS Support and become a Solutions Architect (SA) in Berlin. I’ve always been really interested in systems and how different components of a system worked together—in fact, this is exactly why I studied computer science and biology at university. My role as an SA pushed me to look at customer challenges from completely new perspectives. Now, instead of helping customers with a single component of their workload, I worked with customers on massive, multi-component workloads. I was exposed to new technology that I hadn’t worked with in my Support role, like <a href=\"https://aws.amazon.com/controltower/\" target=\"_blank\">AWS Control Tower</a>, <a href=\"https://aws.amazon.com/sagemaker/\" target=\"_blank\">Amazon SageMaker</a>, and <a href=\"https://aws.amazon.com/iot/\" target=\"_blank\">AWS IoT</a>. In many ways, I was learning alongside my customers, and we were bouncing ideas around together to make sure we were architecting the best possible solutions for their needs.</p>\n<p>However, I always had a passion for <a href=\"https://aws.amazon.com/sustainability/\" target=\"_blank\">sustainability</a>. When I was in university, I was mostly interested in the intersection between natural systems and synthetic systems—I really wanted to understand how I could combine my passion for sustainability with the power of the AWS Cloud. And, as it turned out, so did many others at AWS! We spent most of 2020 working on experiments and writing narratives (the Amazonian version of a pitch), to better understand if customers wanted to work with AWS on sustainability related challenges, and if so, on what topics. My work today comes directly from the results of those initial customer interactions.</p>\n<p>These events also marked a big change in my career! In 2020, I transitioned to a full-time sustainability role, becoming a Sustainability Solutions Architect—a novel function at the time. Today, I’m based in Copenhagen, and my focus is to help customers globally build the most energy-efficient and sustainable workloads on AWS. Every day, I find ways for customers to leverage AWS to solve challenges within their sustainability strategy.</p>\n<h4><a id=\"Favorite_blog_posts_13\"></a><strong>Favorite blog posts</strong></h4>\n<h5><a id=\"Perform_Continuous_cookbook_integration_testing_and_delivery_for_AWS_OpsWorks_for_Chef_Automatehttpsawsamazoncomblogsmtperformcontinuouscookbookintegrationtestinganddeliveryforawsopsworksforchefautomate_16\"></a><strong><a href=\"https://aws.amazon.com/blogs/mt/perform-continuous-cookbook-integration-testing-and-delivery-for-aws-opsworks-for-chef-automate/\" target=\"_blank\">Perform Continuous cookbook integration testing and delivery for AWS OpsWorks for Chef Automate</a></strong></h5>\n<p>My very first blog at AWS was on how to do Continuous Integration / Continuous Delivery with <a href=\"https://aws.amazon.com/opsworks/\" target=\"_blank\">AWS OpsWorks</a>. A group of us in AWS Support were asked to build out a lab that could be used at <a href=\"https://www.chef.io/chefconf\" target=\"_blank\">ChefConf</a>, which we turned into a blog post.</p>\n<p>Many customers are using tools like Chef Automate and Puppet to manage large sets of infrastructure, but finding cloud-native approaches to these tools was not always super obvious. My favorite part of writing this blog post was combining cloud-native ideas with traditional infrastructure management tools.</p>\n<h5><a id=\"How_to_setup_and_use_AWS_OpsWorks_for_Chef_Automate_or_Puppet_Enterprise_in_an_isolated_subnethttpsawsamazoncomblogsmthowtosetupanduseawsopsworksforchefautomateorpuppetenterpriseinanisolatedsubnet_24\"></a><strong><a href=\"https://aws.amazon.com/blogs/mt/how-to-setup-and-use-aws-opsworks-for-chef-automate-or-puppet-enterprise-in-an-isolated-subnet/\" target=\"_blank\">How to setup and use AWS OpsWorks for Chef Automate or Puppet Enterprise in an isolated subnet</a></strong></h5>\n<p>We also saw that customers wanted to understand how to leverage cloud network security in their OpsWorks environment, and so we decided to build a walkthrough on how to use OpsWorks for Chef Automate or Puppet Enterprise in an isolated subnet.</p>\n<h5><a id=\"How_to_set_up_automatic_failover_for_AWS_OpsWorks_for_Chef_Automatehttpsawsamazoncomblogsmtfailoverforawsopsworksforchefautomate_29\"></a><strong><a href=\"https://aws.amazon.com/blogs/mt/failover-for-aws-opsworks-for-chef-automate/\" target=\"_blank\">How to set up automatic failover for AWS OpsWorks for Chef Automate</a></strong></h5>\n<p>In addition to wanting to move fast and be secure, our customers also wanted to have reliability baked into their workloads. For many customers, their Chef Automate Server is a critical component, and they cannot afford downtime.</p>\n<h4><a id=\"Sustainability_content_35\"></a><strong>Sustainability content</strong></h4>\n<p><a href=\"https://aws.amazon.com/blogs/architecture/ask-an-expert-sustainability/\" target=\"_blank\">Ask an Expert – Sustainability</a></p>\n<p>In August 2021, Joe Beer, WW Technology Leader, and I worked on Architecture Monthly discussing the overlap between sustainability and technology.</p>\n<p>Sustainability is a really broad topic, so in order to help scope conversations, we broke the topic down into three main categories: <strong>sustainability of, in, and through the Cloud:</strong></p>\n<ul>\n<li><strong>Sustainability of the Cloud</strong> is AWS’s responsibility, and it covers things like our renewable energy projects, continuous work to increase the energy efficiency of our data centers, and all work that supports our goal of operating as environmentally friendly as possible.</li>\n<li><strong>Sustainability in the Cloud</strong> is the customers’ responsibility. AWS is committed to sustainable operations, but builders also need to consider sustainability as a core non-functional requirement. To make this clearer, a set of best practices have been published in the Well Architected Sustainability Pillar.</li>\n<li><strong>Sustainability through the Cloud</strong> covers all of the ways that the cloud solutions support sustainability strategies. Smart EV charging, for example, uses the AWS Cloud and AI/ML to lessen the aggregate impact to the grid that may occur because of EV charging peaks and ramp ups.</li>\n</ul>\n<p>Throughout 2021, we worked with customers in almost all industries on both sustainability in and through the cloud, putting together a lineup of various <a href=\"https://aws.amazon.com/blogs/architecture/deepen-your-knowledge-of-architecting-for-sustainability-at-reinvent/\" target=\"_blank\">sustainability talks at re:Invent 2021</a>.</p>\n<p>A highlight for me, personally, was seeing the <a href=\"https://docs.aws.amazon.com/wellarchitected/latest/sustainability-pillar/wellarchitected-sustainability-pillar.pdf#sustainability-pillar\" target=\"_blank\">AWS Well-Architected Framework Sustainability Pillar whitepaper</a> released. After spending most of my AWS writing career on internal documentation or blog posts, leading the development of a full whitepaper was a completely new experience. I’m proud of the result and excited to continue to work on improving the content. Today, you can find the pillar in the Well-Architected tool and also explore some <a href=\"https://www.wellarchitectedlabs.com/sustainability/\" target=\"_blank\">labs</a>.</p>\n<p><a href=\"https://aws.amazon.com/blogs/architecture/architecting-for-sustainability-a-reinvent-2021-recap/\" target=\"_blank\">Architecting for sustainability: a re:Invent 2021 recap</a></p>\n<p>We also did a deep dive into one of the sessions to highlight some of the key themes from the Well-Architected Pillar and the unique actions Starbucks took to reduce their footprint.</p>\n<p><img src=\"https://dev-media.amazoncloud.cn/1906ad65a21545db8baa09f4e672b5a2_image.png\" alt=\"image.png\" /></p>\n<h4><a id=\"Elise_Chahine_60\"></a><strong>Elise Chahine</strong></h4>\n<p>Elise is Senior Program Manager for AWS Architecture Content, where she manages the Architecture Blog channel. Elise works with authors to develop succinct, technically accurate posts that help customers architect. When she’s not rubbing shoulders with the brilliant minds of AWS, Elise enjoys a quiet life with her family in New England.</p>\n"}