<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: ChloeMouret</title>
    <description>The latest articles on Forem by ChloeMouret (@chloemouret).</description>
    <link>https://forem.com/chloemouret</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1112833%2F1c1778e8-3698-4d41-910f-78e1c10da5de.png</url>
      <title>Forem: ChloeMouret</title>
      <link>https://forem.com/chloemouret</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/chloemouret"/>
    <language>en</language>
    <item>
      <title>Search your AWS resources blazingly fast ⚡️</title>
      <dc:creator>ChloeMouret</dc:creator>
      <pubDate>Wed, 20 Sep 2023 08:57:58 +0000</pubDate>
      <link>https://forem.com/slsbytheodo/search-your-aws-resources-blazingly-fast-42h8</link>
      <guid>https://forem.com/slsbytheodo/search-your-aws-resources-blazingly-fast-42h8</guid>
      <description>&lt;h2&gt;
  
  
  It's so annoying to find your resources in AWS ...
&lt;/h2&gt;

&lt;p&gt;I don't know about you, but I find it really annoying to find my resources in AWS. I always have to click through the different services and then search for my resource.&lt;/p&gt;

&lt;p&gt;If I need to find my &lt;code&gt;myLambda&lt;/code&gt; function, I have to click on the &lt;code&gt;Lambda&lt;/code&gt; service, then click on &lt;code&gt;Functions&lt;/code&gt; and then search for my function.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ffind_lambda_in_lamdba_service.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ffind_lambda_in_lamdba_service.png" title="Find my lambda in Lambda service" alt="Find my lambda in Lambda service"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In fact, there is a global search bar in the top left corner of the AWS console. But it's not really helpful. It only searches for services, not for resources. So if I search for &lt;code&gt;myLambda&lt;/code&gt; in the search bar, I get a list of all the services that contain the word &lt;code&gt;myLambda&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🚀🚀 In this article, let me show you how to use this search bar to find your resources directly.🚀🚀&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Use AWS Resource Explorer directly in the search bar
&lt;/h2&gt;

&lt;p&gt;AWS Resource Explorer is a service that is used to efficiently search and discover your AWS resources across AWS Regions and accounts. It provides a single view of your resources and enables you to search and filter by resource type, region, tags, and other key attributes. You can also view resource details, including resource configuration, metadata, and related resources.&lt;/p&gt;

&lt;p&gt;The best thing about it is that you can combine with the search bar and &lt;strong&gt;it is free&lt;/strong&gt; !! 🤯&lt;/p&gt;

&lt;h3&gt;
  
  
  Enable AWS Resource Explorer
&lt;/h3&gt;

&lt;p&gt;To enable AWS Resource Explorer, you need to go to the &lt;a href="https://resource-explorer.console.aws.amazon.com/resource-explorer/home#/home" rel="noopener noreferrer"&gt;AWS Resource Explorer console&lt;/a&gt; and click on &lt;code&gt;Turn on Resource Explorer&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Then, you just have a small form to fill in. You just have to specify the Aggregator Index Region, a quick rule of thumb is to choose the region where you have the most resources.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftuto_step3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftuto_step3.png" title="Turn on Resource Explorer" alt="Turn on Resource Explorer"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then click on &lt;code&gt;Turn on Resource Explorer&lt;/code&gt; and you are done! 🎉 You will have to wait a few minutes for the service to be index all your resources in the background.&lt;/p&gt;

&lt;h3&gt;
  
  
  Use AWS Resource Explorer in the search bar
&lt;/h3&gt;

&lt;p&gt;From now on, it is so easy, just type the name of your resource in the search bar, scroll a little bit if needed and you will find your resource that match your input.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftuto_step4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftuto_step4.png" title="Use AWS Resource Explorer in the search bar" alt="Use AWS Resource Explorer in the search bar"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What is so powerful with that is that you can find associated resources like log groups and IAM roles.&lt;/p&gt;

&lt;h3&gt;
  
  
  Last trick 🌟
&lt;/h3&gt;

&lt;p&gt;Filter only your resources in the search bar by typing &lt;code&gt;/resources&lt;/code&gt; before your resource name. This will filter only your resources and not the AWS services.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftrick.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FChloeMouret%2Fkumo-articles%2Fmaster%2Fblog-posts%2Faws-search-bar%2Fassets%2Ftrick.png" title="Quick trick for your AWS search bar" alt="Quick trick for your AWS search bar"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Also, if you want to be blazingly faster, you can use &lt;code&gt;OPT + S&lt;/code&gt; for Mac or &lt;code&gt;ALT + S&lt;/code&gt; for Windows to focus directly on the search bar.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://twitter.com/ChloeMrt1" class="ltag_cta ltag_cta--branded" rel="noopener noreferrer"&gt;Follow me on twitter 🚀&lt;/a&gt;
&lt;/p&gt;

</description>
      <category>aws</category>
      <category>tutorial</category>
      <category>serverless</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
