{"id":32504,"date":"2025-10-22T14:01:27","date_gmt":"2025-10-22T11:01:27","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/"},"modified":"2025-10-22T14:01:27","modified_gmt":"2025-10-22T11:01:27","slug":"aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/","title":{"rendered":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f"},"content":{"rendered":"<p><body><\/p>\n<style>\n        \/* Genel stil ayarlar\u0131 *\/\n        body {\n            font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;\n            line-height: 1.6;\n            color: #333;\n            max-width: 1000px;\n            margin: 0 auto;\n            padding: 20px;\n            background-color: #f9f9f9;\n        }\n        h2 {\n            color: #2c3e50;\n            border-bottom: 2px solid #3498db;\n            padding-bottom: 10px;\n            margin-top: 40px;\n        }\n        h3 {\n            color: #34495e;\n            margin-top: 30px;\n        }\n        p {\n            margin-bottom: 15px;\n        }\n        ul {\n            list-style-type: disc;\n            margin-left: 20px;\n            margin-bottom: 15px;\n        }\n        ol {\n            list-style-type: decimal;\n            margin-left: 20px;\n            margin-bottom: 15px;\n        }\n        li {\n            margin-bottom: 8px;\n        }\n        pre {\n            background-color: #ecf0f1;\n            padding: 15px;\n            border-radius: 5px;\n            overflow-x: auto;\n            font-family: 'Consolas', 'Monaco', monospace;\n            font-size: 0.9em;\n            margin-bottom: 20px;\n        }\n        code {\n            font-family: 'Consolas', 'Monaco', monospace;\n            background-color: #e0e6e7;\n            padding: 2px 4px;\n            border-radius: 3px;\n        }\n        .uzman-ipucu {\n            background-color: #e8f6f3;\n            border-left: 5px solid #1abc9c;\n            padding: 15px 20px;\n            margin: 25px 0;\n            border-radius: 5px;\n            font-style: italic;\n            color: #219d7d;\n        }\n        table {\n            width: 100%;\n            border-collapse: collapse;\n            margin-bottom: 20px;\n        }\n        th, td {\n            border: 1px solid #ddd;\n            padding: 10px;\n            text-align: left;\n        }\n        th {\n            background-color: #f2f2f2;\n            font-weight: bold;\n        }<\/p>\n<p>        \/* Mobil uyumluluk i\u00e7in medya sorgular\u0131 *\/\n        @media (max-width: 768px) {\n            body {\n                padding: 15px;\n            }\n            h2 {\n                font-size: 1.8em;\n            }\n            h3 {\n                font-size: 1.4em;\n            }\n            pre {\n                white-space: pre-wrap; \/* Uzun kod sat\u0131rlar\u0131n\u0131 sarar *\/\n            }\n            .uzman-ipucu {\n                padding: 10px 15px;\n            }\n        }<\/p>\n<p>        @media (max-width: 480px) {\n            h2 {\n                font-size: 1.5em;\n            }\n            h3 {\n                font-size: 1.2em;\n            }\n            ul, ol {\n                margin-left: 15px;\n            }\n        }\n    <\/style>\n<p>AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway&#8217;in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.<\/p>\n<p>Modern bulut mimarilerinde \u015firketler genellikle birden fazla Amazon Sanal \u00d6zel Bulut (VPC) kullan\u0131r. Bu VPC&#8217;ler; farkl\u0131 departmanlar, uygulama ortamlar\u0131 (geli\u015ftirme, test, \u00fcretim), farkl\u0131 g\u00fcvenlik seviyeleri veya hatta farkl\u0131 projeler i\u00e7in ayr\u0131labilir. Ancak, bu VPC&#8217;ler aras\u0131nda g\u00fcvenli ve verimli bir \u015fekilde ileti\u015fim kurmak, \u00f6zellikle VPC say\u0131s\u0131 artt\u0131\u011f\u0131nda ciddi bir karma\u015faya yol a\u00e7abilir. Geleneksel olarak, her VPC aras\u0131nda birebir VPC peering ba\u011flant\u0131lar\u0131 kurmak zorundayd\u0131k. Bu y\u00f6ntem, birka\u00e7 VPC i\u00e7in y\u00f6netilebilir olsa da, a\u011f\u0131n\u0131z b\u00fcy\u00fcd\u00fck\u00e7e bir &#8220;\u00f6r\u00fcmcek a\u011f\u0131&#8221; halini alarak y\u00f6netimi adeta bir kabusa \u00e7evirebilir. D\u00fc\u015f\u00fcnsenize, on adet VPC&#8217;niz varsa, tam ba\u011flant\u0131 i\u00e7in tam <code>N * (N-1) \/ 2<\/code> form\u00fcl\u00fcyle 45 farkl\u0131 peering ba\u011flant\u0131s\u0131 kurman\u0131z gerekir! Bu sadece konfig\u00fcrasyon y\u00fck\u00fcn\u00fc art\u0131rmakla kalmaz, ayn\u0131 zamanda g\u00fcvenlik politikalar\u0131n\u0131 y\u00f6netmeyi ve sorun gidermeyi de zorla\u015ft\u0131r\u0131r.<\/p>\n<p>Buna ek olarak, \u015firket i\u00e7i veri merkezleriniz ile AWS bulutu aras\u0131ndaki ba\u011flant\u0131lar, yani hibrit bulut yap\u0131lar\u0131 da devreye girdi\u011finde durum daha karma\u015f\u0131k hale gelir. Her VPC&#8217;nin ayr\u0131 ayr\u0131 VPN ba\u011flant\u0131lar\u0131 kurmas\u0131 veya AWS Direct Connect \u00fczerinden eri\u015fim sa\u011flamas\u0131 hem maliyetli hem de y\u00f6netim a\u00e7\u0131s\u0131ndan verimsizdir. A\u011f trafi\u011finin merkezi bir noktadan denetlenmesi, g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131n uygulanmas\u0131 ve a\u011f topolojisinin \u015feffaf bir \u015fekilde y\u00f6netilmesi, bu da\u011f\u0131n\u0131k yap\u0131da neredeyse imkans\u0131z hale gelir. A\u011f m\u00fchendisleri ve DevOps ekipleri, s\u00fcrekli olarak ba\u011flant\u0131 sorunlar\u0131, g\u00fcvenlik a\u00e7\u0131klar\u0131 ve performans darbo\u011fazlar\u0131yla u\u011fra\u015fmak zorunda kalabilir. \u0130\u015fte tam da bu noktada, AWS Transit Gateway devreye girerek bu karma\u015f\u0131k bulut a\u011f yap\u0131s\u0131n\u0131 basitle\u015ftiren, \u00f6l\u00e7eklenebilir ve merkezi bir \u00e7\u00f6z\u00fcm sunar. Transit Gateway, a\u011f y\u00f6netimine yepyeni bir bak\u0131\u015f a\u00e7\u0131s\u0131 getirir, geleneksel hub-and-spoke mimarisini buluta ta\u015f\u0131yarak verimlili\u011fi ve g\u00fcvenli\u011fi art\u0131r\u0131r.<\/p>\n<p>Transit Gateway, t\u00fcm a\u011f trafi\u011fini merkezi bir noktadan y\u00f6nlendirerek, her VPC&#8217;nin di\u011fer her VPC ile do\u011frudan ba\u011flant\u0131 kurma zorunlulu\u011funu ortadan kald\u0131r\u0131r. Bu, hem konfig\u00fcrasyon karma\u015fas\u0131n\u0131 azalt\u0131r hem de a\u011f topolojisinin \u00e7ok daha anla\u015f\u0131l\u0131r ve y\u00f6netilebilir olmas\u0131n\u0131 sa\u011flar. G\u00fcvenlik politikalar\u0131 da art\u0131k merkezi bir noktadan uygulanabilir hale gelir, bu da tutarl\u0131l\u0131\u011f\u0131 ve denetlenebilirli\u011fi art\u0131r\u0131r. Dolay\u0131s\u0131yla, e\u011fer da\u011f\u0131n\u0131k VPC yap\u0131n\u0131z\u0131n getirdi\u011fi y\u00f6netim y\u00fck\u00fcnden, g\u00fcvenlik endi\u015felerinden ve \u00f6l\u00e7eklenebilirlik k\u0131s\u0131tlamalar\u0131ndan muzdaripseniz, AWS Transit Gateway sizin i\u00e7in kurtar\u0131c\u0131 bir \u00e7\u00f6z\u00fcm olabilir. Bu ara\u00e7 sayesinde, AWS \u00fczerindeki a\u011f altyap\u0131n\u0131z\u0131 \u00e7ok daha sa\u011flam, esnek ve gelece\u011fe haz\u0131r hale getirebilirsiniz. \u015eimdi gelin, bu g\u00fc\u00e7l\u00fc servisin temel \u00f6zelliklerine daha yak\u0131ndan bakal\u0131m ve neden bu kadar \u00f6nemli oldu\u011funu anlamaya \u00e7al\u0131\u015fal\u0131m.<\/p>\n<h2>AWS Transit Gateway Temel Kavramlar\u0131 Nelerdir ve Neden \u00d6nemlidir?<\/h2>\n<p>AWS Transit Gateway, ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi, a\u011f trafi\u011fini farkl\u0131 a\u011flar aras\u0131nda &#8220;ge\u00e7iren&#8221; merkezi bir a\u011f ge\u00e7ididir. Geleneksel bir &#8220;hub-and-spoke&#8221; (merkez-ve-jant) mimarisini AWS bulutuna ta\u015f\u0131yarak, t\u00fcm a\u011f ba\u011flant\u0131lar\u0131n\u0131z i\u00e7in tek bir merkezi eri\u015fim noktas\u0131 sa\u011flar. Peki, bu tam olarak ne anlama geliyor ve neden bu kadar \u00f6nemli?<\/p>\n<p>\u00d6ncelikle, Transit Gateway, farkl\u0131 AWS Sanal \u00d6zel Bulutlar\u0131 (VPC&#8217;ler), \u015firket i\u00e7i veri merkezleri (VPN veya AWS Direct Connect arac\u0131l\u0131\u011f\u0131yla) ve hatta farkl\u0131 AWS hesaplar\u0131ndaki VPC&#8217;ler aras\u0131nda bir k\u00f6pr\u00fc g\u00f6revi g\u00f6r\u00fcr. Her bir a\u011f segmentini (VPC, VPN ba\u011flant\u0131s\u0131 vb.) do\u011frudan di\u011ferleriyle e\u015fle\u015ftirmek yerine, her birini Transit Gateway&#8217;e ba\u011flars\u0131n\u0131z. Transit Gateway daha sonra bu ba\u011flant\u0131lar aras\u0131nda trafi\u011fi y\u00f6nlendirir. Bu, a\u011f topolojinizi \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirir ve &#8220;N&#8217;ye N&#8221; (N-to-N) ba\u011flant\u0131 karma\u015fas\u0131n\u0131 &#8220;N&#8217;ye 1&#8221; (N-to-1) ba\u011flant\u0131 modeline d\u00f6n\u00fc\u015ft\u00fcr\u00fcr.<\/p>\n<p>Transit Gateway&#8217;in kalbinde birka\u00e7 temel kavram yatar:<\/p>\n<ul>\n<li><strong>Attachment (Eklenti):<\/strong> Bir VPC&#8217;yi, VPN ba\u011flant\u0131s\u0131n\u0131, AWS Direct Connect a\u011f ge\u00e7idini veya ba\u015fka bir Transit Gateway&#8217;i (peering) Transit Gateway&#8217;e ba\u011flaman\u0131n yoludur. Her bir a\u011f kayna\u011f\u0131, bir &#8220;attachment&#8221; arac\u0131l\u0131\u011f\u0131yla merkezi Transit Gateway&#8217;e ba\u011flan\u0131r. Bu attachment&#8217;lar, farkl\u0131 a\u011f segmentlerinin Transit Gateway ile ileti\u015fim kurmas\u0131n\u0131 sa\u011flayan temel yap\u0131 ta\u015flar\u0131d\u0131r. \u00d6rne\u011fin, bir VPC attachment&#8217;\u0131, VPC&#8217;nizin alt a\u011flar\u0131ndan Transit Gateway&#8217;e giden ve gelen trafi\u011fi y\u00f6netir.<\/li>\n<li><strong>Transit Gateway Route Table (Transit Gateway Y\u00f6nlendirme Tablosu):<\/strong> T\u0131pk\u0131 VPC&#8217;lerde oldu\u011fu gibi, Transit Gateway&#8217;in de kendi y\u00f6nlendirme tablolar\u0131 vard\u0131r. Bu tablolar, gelen trafi\u011fin nereye y\u00f6nlendirilece\u011fini belirler. Her attachment bir veya daha fazla y\u00f6nlendirme tablosuyla ili\u015fkilendirilebilir (association) ve bu tablolara rotalar yay\u0131labilir (propagation). Bu sayede, a\u011f\u0131n\u0131zda \u00e7ok daha gran\u00fcler bir kontrol sa\u011flayabilir ve farkl\u0131 a\u011f segmentleri aras\u0131nda farkl\u0131 y\u00f6nlendirme politikalar\u0131 uygulayabilirsiniz. \u00d6rne\u011fin, geli\u015ftirme ortam\u0131ndan gelen trafi\u011fi \u00fcretim ortam\u0131na y\u00f6nlendirmemek i\u00e7in ayr\u0131 bir y\u00f6nlendirme tablosu kullanabilirsiniz.<\/li>\n<li><strong>Association (\u0130li\u015fkilendirme):<\/strong> Bir attachment&#8217;\u0131 belirli bir Transit Gateway Y\u00f6nlendirme Tablosu ile ili\u015fkilendirme i\u015flemidir. Gelen trafik, ili\u015fkili oldu\u011fu y\u00f6nlendirme tablosundaki kurallara g\u00f6re i\u015flenir. Bu sayede, her attachment i\u00e7in hangi rotalar\u0131n ge\u00e7erli olaca\u011f\u0131n\u0131 net bir \u015fekilde belirleyebilirsiniz.<\/li>\n<li><strong>Propagation (Yay\u0131lma):<\/strong> Attachment&#8217;lar\u0131n rotalar\u0131n\u0131 otomatik olarak bir Transit Gateway Y\u00f6nlendirme Tablosuna yayma \u00f6zelli\u011fidir. Bu, \u00f6zellikle dinamik a\u011f ortamlar\u0131nda \u00e7ok kullan\u0131\u015fl\u0131d\u0131r, \u00e7\u00fcnk\u00fc manuel rota ekleme ihtiyac\u0131n\u0131 azalt\u0131r ve a\u011f de\u011fi\u015fikliklerine h\u0131zl\u0131 adaptasyon sa\u011flar. \u00d6rne\u011fin, yeni bir VPC attachment&#8217;\u0131 ekledi\u011finizde, rotalar\u0131 otomatik olarak belirli bir y\u00f6nlendirme tablosuna yayabilirsiniz.<\/li>\n<li><strong>Transitivity (Ge\u00e7i\u015flilik):<\/strong> Transit Gateway&#8217;in en \u00f6nemli \u00f6zelliklerinden biridir. Bu, bir attachment arac\u0131l\u0131\u011f\u0131yla ba\u011fl\u0131 olan t\u00fcm a\u011flar\u0131n, di\u011fer t\u00fcm ba\u011fl\u0131 a\u011flarla do\u011frudan ileti\u015fim kurabilmesi anlam\u0131na gelir. \u00d6rne\u011fin, VPC A, Transit Gateway&#8217;e ba\u011fl\u0131ysa ve Transit Gateway de VPC B&#8217;ye ba\u011fl\u0131ysa, VPC A ve VPC B do\u011frudan ileti\u015fim kurabilir. Bu, VPC peering&#8217;de olmayan bir \u00f6zelliktir; VPC peering yaln\u0131zca do\u011frudan ba\u011fl\u0131 iki VPC aras\u0131nda \u00e7al\u0131\u015f\u0131r.<\/li>\n<\/ul>\n<p>AWS Transit Gateway&#8217;in \u00f6nemini \u00f6zetlemek gerekirse, a\u011f karma\u015fas\u0131n\u0131 azalt\u0131r, y\u00f6netim y\u00fck\u00fcn\u00fc hafifletir, \u00f6l\u00e7eklenebilirli\u011fi art\u0131r\u0131r ve tutarl\u0131 bir g\u00fcvenlik duru\u015fu sa\u011flaman\u0131za olanak tan\u0131r. A\u011f\u0131n\u0131z\u0131 b\u00fcy\u00fct\u00fcrken veya hibrit bulut ortamlar\u0131na ge\u00e7erken, Transit Gateway, a\u011f altyap\u0131n\u0131z\u0131n esnek ve sa\u011flam kalmas\u0131n\u0131 sa\u011flar. Art\u0131k VPC&#8217;leriniz, VPN&#8217;leriniz ve Direct Connect ba\u011flant\u0131lar\u0131n\u0131z aras\u0131nda karma\u015f\u0131k ve da\u011f\u0131n\u0131k ba\u011flant\u0131lar kurmak yerine, hepsini merkezi bir &#8220;hub&#8221; olan Transit Gateway&#8217;e ba\u011flayabilirsiniz. Bu, a\u011f\u0131n\u0131z\u0131n kontrol\u00fcn\u00fc elinize alman\u0131z\u0131 ve operasyonel verimlili\u011fi art\u0131rman\u0131z\u0131 sa\u011flar.<\/p>\n<h2>Transit Gateway Nas\u0131l Kurulur ve \u0130lk Ba\u011flant\u0131lar Nas\u0131l Yap\u0131l\u0131r? (Ad\u0131m Ad\u0131m K\u0131lavuz)<\/h2>\n<p>AWS Transit Gateway&#8217;i kurmak ve ilk ba\u011flant\u0131lar\u0131n\u0131z\u0131 yapmak, karma\u015f\u0131k gibi g\u00f6r\u00fcnse de asl\u0131nda olduk\u00e7a basittir. A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 izleyerek merkezi a\u011f altyap\u0131n\u0131z\u0131 h\u0131zla olu\u015fturabilirsiniz. Bu b\u00f6l\u00fcmde AWS Konsolu \u00fczerinden ilerleyecek olsak da, ayn\u0131 i\u015flemler AWS CLI (Komut Sat\u0131r\u0131 Aray\u00fcz\u00fc) veya Infrastructure as Code ara\u00e7lar\u0131 (Terraform, CloudFormation) ile de ger\u00e7ekle\u015ftirilebilir.<\/p>\n<h3>1. Transit Gateway Olu\u015fturma<\/h3>\n<p>\u0130lk ad\u0131m, AWS hesab\u0131n\u0131zda bir Transit Gateway kayna\u011f\u0131 olu\u015fturmakt\u0131r:<\/p>\n<ol>\n<li>AWS Y\u00f6netim Konsolu&#8217;nda oturum a\u00e7\u0131n ve VPC hizmetine gidin.<\/li>\n<li>Sol navigasyon panelinden &#8220;Transit Gateways&#8221; alt\u0131nda &#8220;Transit Gateways&#8221; se\u00e7ene\u011fine t\u0131klay\u0131n.<\/li>\n<li>&#8220;Create Transit Gateway&#8221; d\u00fc\u011fmesine t\u0131klay\u0131n.<\/li>\n<li>A\u015fa\u011f\u0131daki bilgileri girin:\n<ul>\n<li><strong>Name tag:<\/strong> Transit Gateway&#8217;inize kolayca tan\u0131yabilece\u011finiz bir isim verin (\u00f6rne\u011fin, <code>Kurumsal-TGW<\/code>).<\/li>\n<li><strong>Description (\u0130ste\u011fe ba\u011fl\u0131):<\/strong> Bir a\u00e7\u0131klama ekleyebilirsiniz.<\/li>\n<li><strong>Amazon side Autonomous System Number (ASN):<\/strong> BGP y\u00f6nlendirmesi i\u00e7in kullan\u0131l\u0131r. Varsay\u0131lan de\u011feri b\u0131rakabilir veya 64512-65534 aral\u0131\u011f\u0131ndan \u00f6zel bir de\u011fer girebilirsiniz. Genellikle varsay\u0131lan de\u011fer yeterlidir.<\/li>\n<li>Di\u011fer ayarlar\u0131 (DNS Support, VPN ECMP Support, Default route table association, Default route table propagation) varsay\u0131lan olarak b\u0131rakabilir veya ihtiya\u00e7lar\u0131n\u0131za g\u00f6re yap\u0131land\u0131rabilirsiniz. \u00c7o\u011fu durumda, &#8220;Default route table association&#8221; ve &#8220;Default route table propagation&#8221; se\u00e7eneklerini etkin b\u0131rakmak ba\u015flang\u0131\u00e7 i\u00e7in daha kolayd\u0131r. Daha sonra ayr\u0131nt\u0131l\u0131 rota tablolar\u0131 olu\u015fturabilirsiniz.<\/li>\n<\/ul>\n<\/li>\n<li>&#8220;Create Transit Gateway&#8221; d\u00fc\u011fmesine t\u0131klayarak Transit Gateway&#8217;i olu\u015fturun. Bu i\u015flem birka\u00e7 dakika s\u00fcrebilir.<\/li>\n<\/ol>\n<p>CLI ile olu\u015fturma \u00f6rne\u011fi:<\/p>\n<pre><code>aws ec2 create-transit-gateway \\\n  --description \"Kurumsal Transit Gateway\" \\\n  --options '{\"AmazonSideAsn\": 64512, \"AutoAcceptSharedAttachments\": \"enable\", \"DefaultRouteTableAssociation\": \"enable\", \"DefaultRouteTablePropagation\": \"enable\", \"DnsSupport\": \"enable\", \"VpnEcmpSupport\": \"enable\"}' \\\n  --tag-specifications 'ResourceType=transit-gateway,Tags=[{Key=Name,Value=Kurumsal-TGW}]'<\/pre>\n<p><\/code><\/p>\n<h3>2. VPC'leri Transit Gateway'e Ekleme (Attachment)<\/h3>\n<p>Transit Gateway'iniz haz\u0131r oldu\u011funda, VPC'lerinizi ona ba\u011flaman\u0131z gerekir:<\/p>\n<ol>\n<li>VPC konsolunda, sol navigasyon panelinden \"Transit Gateways\" alt\u0131nda \"Transit Gateway Attachments\" se\u00e7ene\u011fine t\u0131klay\u0131n.<\/li>\n<li>\"Create Transit Gateway Attachment\" d\u00fc\u011fmesine t\u0131klay\u0131n.<\/li>\n<li>A\u015fa\u011f\u0131daki bilgileri girin:\n<ul>\n<li><strong>Name tag:<\/strong> Attachment i\u00e7in bir isim verin (\u00f6rne\u011fin, <code>App-VPC-Attachment<\/code>).<\/li>\n<li><strong>Transit Gateway ID:<\/strong> Az \u00f6nce olu\u015fturdu\u011funuz Transit Gateway'i se\u00e7in.<\/li>\n<li><strong>Attachment type:<\/strong> <code>VPC<\/code> se\u00e7ene\u011fini i\u015faretleyin.<\/li>\n<li><strong>VPC ID:<\/strong> Ba\u011flamak istedi\u011finiz VPC'yi se\u00e7in.<\/li>\n<li><strong>Subnet IDs:<\/strong> Ba\u011flamak istedi\u011finiz VPC'deki her Kullan\u0131labilirlik Alan\u0131 (AZ) i\u00e7in en az bir alt a\u011f se\u00e7in. Bu alt a\u011flar, Transit Gateway ENI'lerinin konu\u015fland\u0131r\u0131laca\u011f\u0131 yerlerdir. Genellikle her AZ'den bir alt a\u011f se\u00e7mek en iyi uygulamad\u0131r.<\/li>\n<\/ul>\n<\/li>\n<li>\"Create Transit Gateway Attachment\" d\u00fc\u011fmesine t\u0131klay\u0131n. Her bir VPC i\u00e7in bu ad\u0131m\u0131 tekrarlay\u0131n.<\/li>\n<\/ol>\n<p>CLI ile VPC attachment olu\u015fturma \u00f6rne\u011fi:<\/p>\n<pre><code>aws ec2 create-transit-gateway-vpc-attachment \\\n  --transit-gateway-id tgw-0123456789abcdef0 \\\n  --vpc-id vpc-0abcdef0123456789 \\\n  --subnet-ids subnet-0123456789abcdef0 subnet-0fedcba9876543210 \\\n  --tag-specifications 'ResourceType=transit-gateway-attachment,Tags=[{Key=Name,Value=App-VPC-Attachment}]'<\/pre>\n<p><\/code><\/p>\n<h3>3. VPC Y\u00f6nlendirme Tablolar\u0131n\u0131 G\u00fcncelleme<\/h3>\n<p>VPC'leriniz Transit Gateway'e eklendikten sonra, VPC i\u00e7indeki alt a\u011flar\u0131n d\u0131\u015f d\u00fcnyaya veya di\u011fer VPC'lere trafik g\u00f6ndermesi i\u00e7in y\u00f6nlendirme tablolar\u0131n\u0131 g\u00fcncellemeniz gerekir:<\/p>\n<ol>\n<li>AWS Konsolu'nda VPC hizmetine gidin.<\/li>\n<li>Sol navigasyon panelinden \"Route Tables\" se\u00e7ene\u011fine t\u0131klay\u0131n.<\/li>\n<li>Transit Gateway \u00fczerinden eri\u015fim sa\u011flamas\u0131n\u0131 istedi\u011finiz her alt a\u011f\u0131n y\u00f6nlendirme tablosunu se\u00e7in.<\/li>\n<li>\"Routes\" sekmesine ve ard\u0131ndan \"Edit routes\" d\u00fc\u011fmesine t\u0131klay\u0131n.<\/li>\n<li>\"Add route\" d\u00fc\u011fmesine t\u0131klay\u0131n.\n<ul>\n<li><strong>Destination:<\/strong> Eri\u015filmek istenen hedef a\u011f\u0131 belirtin (\u00f6rne\u011fin, <code>0.0.0.0\/0<\/code> t\u00fcm internet trafi\u011fi i\u00e7in veya di\u011fer VPC'lerin CIDR bloklar\u0131).<\/li>\n<li><strong>Target:<\/strong> \"Transit Gateway\" se\u00e7ene\u011fini se\u00e7in ve ard\u0131ndan olu\u015fturdu\u011funuz Transit Gateway'i se\u00e7in (<code>tgw-xxxxxxxxxxxxxxxxx<\/code>).<\/li>\n<\/ul>\n<\/li>\n<li>\"Save changes\" d\u00fc\u011fmesine t\u0131klay\u0131n. Bu ad\u0131m\u0131, Transit Gateway \u00fczerinden ileti\u015fim kuracak her alt a\u011f\u0131n y\u00f6nlendirme tablosu i\u00e7in tekrarlay\u0131n.<\/li>\n<\/ol>\n<p>VPC rota tablosu g\u00fcncelleme \u00f6rne\u011fi (CLI):<\/p>\n<pre><code>aws ec2 create-route \\\n  --route-table-id rtb-0123456789abcdef0 \\\n  --destination-cidr-block 0.0.0.0\/0 \\\n  --transit-gateway-id tgw-0123456789abcdef0<\/pre>\n<p><\/code><\/p>\n<h3>4. Transit Gateway Y\u00f6nlendirme Tablolar\u0131n\u0131 Yap\u0131land\u0131rma (\u0130ste\u011fe Ba\u011fl\u0131 ama \u00d6nemli)<\/h3>\n<p>E\u011fer varsay\u0131lan y\u00f6nlendirme tablosu yerine \u00f6zelle\u015ftirilmi\u015f y\u00f6nlendirme tablolar\u0131 kullanacaksan\u0131z, bunlar\u0131 yap\u0131land\u0131rman\u0131z gerekir:<\/p>\n<ol>\n<li>VPC konsolunda, \"Transit Gateways\" alt\u0131nda \"Transit Gateway Route Tables\" se\u00e7ene\u011fine t\u0131klay\u0131n.<\/li>\n<li>Varsay\u0131lan tabloyu kullanabilir veya \"Create Transit Gateway Route Table\" ile yeni bir tane olu\u015fturabilirsiniz.<\/li>\n<li>Se\u00e7ti\u011finiz y\u00f6nlendirme tablosuna t\u0131klay\u0131n.<\/li>\n<li>\"Associations\" sekmesine gidin ve \"Create association\" diyerek attachment'lar\u0131 bu tabloyla ili\u015fkilendirin.<\/li>\n<li>\"Propagations\" sekmesine gidin ve \"Create propagation\" diyerek attachment'lar\u0131n rotalar\u0131n\u0131 otomatik olarak bu tabloya yaymas\u0131n\u0131 sa\u011flay\u0131n.<\/li>\n<li>\"Routes\" sekmesinden, manuel olarak statik rotalar ekleyebilir veya yay\u0131lm\u0131\u015f rotalar\u0131 g\u00f6rebilirsiniz.<\/li>\n<\/ol>\n<p>Bu ad\u0131mlar\u0131 tamamlad\u0131\u011f\u0131n\u0131zda, VPC'leriniz art\u0131k Transit Gateway \u00fczerinden birbirleriyle ve potansiyel olarak di\u011fer a\u011f kaynaklar\u0131yla ileti\u015fim kurmaya ba\u015flayacakt\u0131r. Bu merkezi hub-and-spoke mimarisi, a\u011f\u0131n\u0131z\u0131n y\u00f6netilebilirli\u011fini ve \u00f6l\u00e7eklenebilirli\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131racakt\u0131r. Art\u0131k \u00e7ok daha karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 dahi kolayca y\u00f6netebilirsiniz.<\/p>\n<div class=\"uzman-ipucu\">\n      Uzman \u0130pucu: Transit Gateway'i farkl\u0131 hesaplardaki VPC'lerle payla\u015fmak i\u00e7in AWS Resource Access Manager (RAM) kullan\u0131n. Bu, merkezi bir a\u011f ekibinin Transit Gateway'i y\u00f6netmesini, di\u011fer ekiplerin ise kendi VPC'lerini kolayca ba\u011flamas\u0131n\u0131 sa\u011flar.\n    <\/div>\n<h2>Ger\u00e7ek D\u00fcnya Senaryolar\u0131nda Transit Gateway: Vaka Analizleri<\/h2>\n<p>AWS Transit Gateway'in teorik faydalar\u0131n\u0131 anlad\u0131k, peki ger\u00e7ek d\u00fcnya senaryolar\u0131nda bu g\u00fc\u00e7l\u00fc ara\u00e7 bize nas\u0131l yard\u0131mc\u0131 oluyor? \u0130\u015fte farkl\u0131 i\u015fletmelerin kar\u015f\u0131la\u015ft\u0131\u011f\u0131 yayg\u0131n zorluklar\u0131 ele alan \u00fc\u00e7 vaka analizi:<\/p>\n<h3>Vaka 1: \u00c7oklu VPC Uygulama Mimarisi ve Ortam Ayr\u0131m\u0131<\/h3>\n<p><strong>Senaryo:<\/strong> B\u00fcy\u00fck bir yaz\u0131l\u0131m geli\u015ftirme \u015firketi olan \"TechInnovate\", birden fazla \u00fcr\u00fcn geli\u015ftiriyor ve her \u00fcr\u00fcn i\u00e7in farkl\u0131 uygulama ortamlar\u0131na (Geli\u015ftirme, Test, \u00dcretim) sahip. Her ortam ve \u00fcr\u00fcn ayr\u0131 bir VPC'de bar\u0131nd\u0131r\u0131l\u0131yor. Ba\u015flang\u0131\u00e7ta, bu VPC'ler aras\u0131nda sadece birka\u00e7 VPC peering ba\u011flant\u0131s\u0131 vard\u0131. Ancak zamanla, \u00fcr\u00fcn say\u0131s\u0131 artt\u0131k\u00e7a ve ekiplerin farkl\u0131 ortamlar aras\u0131nda ileti\u015fim kurmas\u0131 gerekti\u011finde, peering ba\u011flant\u0131lar\u0131n\u0131n say\u0131s\u0131 h\u0131zla artt\u0131 (50'den fazla VPC peering ba\u011flant\u0131s\u0131 olu\u015ftu). Bu durum, a\u011f y\u00f6netimi ekibi i\u00e7in b\u00fcy\u00fck bir karma\u015fa yaratt\u0131. G\u00fcvenlik politikalar\u0131n\u0131 her peering ba\u011flant\u0131s\u0131 i\u00e7in ayr\u0131 ayr\u0131 uygulamak, sorun giderme ve yeni bir VPC eklemek her seferinde saatler s\u00fcr\u00fcyordu.<\/p>\n<p><strong>Transit Gateway \u00c7\u00f6z\u00fcm\u00fc:<\/strong> TechInnovate, t\u00fcm bu VPC'leri merkezi bir AWS Transit Gateway'e ba\u011flamaya karar verdi. Her ortam (Geli\u015ftirme, Test, \u00dcretim) ve her \u00fcr\u00fcn VPC'si, kendi Transit Gateway attachment'\u0131n\u0131 olu\u015fturdu. \u015eirket, \u00fc\u00e7 farkl\u0131 Transit Gateway Y\u00f6nlendirme Tablosu olu\u015fturdu: <code>Dev-Route-Table<\/code>, <code>Test-Route-Table<\/code> ve <code>Prod-Route-Table<\/code>. Geli\u015ftirme VPC'leri <code>Dev-Route-Table<\/code> ile ili\u015fkilendirildi ve sadece Test VPC'lerine veya belirli payla\u015f\u0131ml\u0131 hizmetlere (\u00f6rne\u011fin, merkezi bir Active Directory VPC'si) eri\u015fime izin verildi. \u00dcretim VPC'leri ise <code>Prod-Route-Table<\/code> ile ili\u015fkilendirildi ve kesinlikle di\u011fer ortam VPC'lerine eri\u015fime izin verilmedi, sadece payla\u015f\u0131ml\u0131 g\u00fcvenlik hizmetleri VPC'sine veya kendi i\u00e7 servislerine eri\u015febildi. Bu sayede, a\u011f izolasyonu ve g\u00fcvenlik seviyeleri net bir \u015fekilde belirlendi.<\/p>\n<p><strong>Faydalar\u0131:<\/strong><\/p>\n<ul>\n<li><strong>Basitle\u015ftirilmi\u015f A\u011f Topolojisi:<\/strong> 50'den fazla peering ba\u011flant\u0131s\u0131 yerine, her VPC sadece bir Transit Gateway'e ba\u011fl\u0131. Bu, a\u011f topolojisini \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirdi.<\/li>\n<li><strong>Geli\u015ftirilmi\u015f G\u00fcvenlik:<\/strong> Farkl\u0131 ortamlara y\u00f6nelik ayr\u0131 y\u00f6nlendirme tablolar\u0131 sayesinde, ortamlar aras\u0131 istenmeyen trafi\u011fin \u00f6n\u00fcne ge\u00e7ildi. \u00dcretim ortam\u0131, di\u011fer ortamlardan izole edildi.<\/li>\n<li><strong>Kolay Y\u00f6netim ve \u00d6l\u00e7eklenebilirlik:<\/strong> Yeni bir \u00fcr\u00fcn veya ortam VPC'si eklendi\u011finde, sadece bir attachment olu\u015fturup uygun y\u00f6nlendirme tablosuyla ili\u015fkilendirmek yeterli oldu. Bu, a\u011f ekibinin i\u015f y\u00fck\u00fcn\u00fc azaltt\u0131 ve yeni projelerin devreye al\u0131nma s\u00fcresini h\u0131zland\u0131rd\u0131.<\/li>\n<li><strong>Operasyonel Maliyet Azalmas\u0131:<\/strong> Y\u00f6netim y\u00fck\u00fcn\u00fcn azalmas\u0131yla operasyonel maliyetler de d\u00fc\u015ft\u00fc.<\/li>\n<\/ul>\n<h3>Vaka 2: Hibrit Bulut Ba\u011flant\u0131s\u0131 ve Merkezi VPN\/Direct Connect<\/h3>\n<p><strong>Senaryo:<\/strong> Finansal bir kurulu\u015f olan \"SecureBank\", hem \u015firket i\u00e7i veri merkezlerinde (on-premises) kritik sistemlere sahip hem de yeni nesil uygulamalar\u0131n\u0131 AWS bulutunda geli\u015ftiriyor. Kurulu\u015fun AWS'de birden fazla VPC'si (Uygulama VPC'leri, Veritaban\u0131 VPC'leri, Ortak Hizmetler VPC'si) bulunuyor ve bu VPC'lerin \u015firket i\u00e7i veri merkeziyle g\u00fcvenli ve y\u00fcksek h\u0131zl\u0131 bir \u015fekilde ileti\u015fim kurmas\u0131 gerekiyor. Ba\u015flang\u0131\u00e7ta her VPC, kendi Site-to-Site VPN ba\u011flant\u0131s\u0131n\u0131 kurarak \u015firket i\u00e7i a\u011fa eri\u015fiyordu. Bu, hem \u00e7ok say\u0131da VPN t\u00fcneli anlam\u0131na geliyordu hem de Direct Connect ba\u011flant\u0131s\u0131n\u0131n verimli kullan\u0131lmas\u0131n\u0131 engelliyordu. Ayr\u0131ca, a\u011f g\u00fcvenlik duvar\u0131 ve denetim mekanizmalar\u0131n\u0131 her VPC i\u00e7in ayr\u0131 ayr\u0131 y\u00f6netmek gerekiyordu.<\/p>\n<p><strong>Transit Gateway \u00c7\u00f6z\u00fcm\u00fc:<\/strong> SecureBank, \u015firket i\u00e7i veri merkezinden AWS'ye gelen t\u00fcm trafi\u011fi tek bir merkezi noktadan y\u00f6netmek i\u00e7in AWS Transit Gateway'i benimsedi. Bir AWS Direct Connect Gateway (veya y\u00fcksek kapasiteli Site-to-Site VPN ba\u011flant\u0131lar\u0131) Transit Gateway'e ba\u011fland\u0131. Ard\u0131ndan, t\u00fcm AWS VPC'leri de Transit Gateway'e attachment olarak eklendi. \u015eirket i\u00e7i a\u011fdan gelen trafik art\u0131k Direct Connect \u00fczerinden Transit Gateway'e ula\u015f\u0131yor ve buradan uygun VPC'lere y\u00f6nlendiriliyor. Benzer \u015fekilde, AWS VPC'lerinden \u015firket i\u00e7i kaynaklara giden trafik de Transit Gateway \u00fczerinden tek bir Direct Connect ba\u011flant\u0131s\u0131n\u0131 kullanarak hedefine ula\u015f\u0131yor.<\/p>\n<p><strong>Faydalar\u0131:<\/strong><\/p>\n<ul>\n<li><strong>Merkezi Eri\u015fim Noktas\u0131:<\/strong> T\u00fcm hibrit trafik i\u00e7in tek bir \"hub\" olu\u015fturuldu. Bu, Direct Connect veya VPN kaynaklar\u0131n\u0131n daha verimli kullan\u0131lmas\u0131n\u0131 sa\u011flad\u0131.<\/li>\n<li><strong>Basitle\u015ftirilmi\u015f Routing:<\/strong> \u015eirket i\u00e7i a\u011fda sadece tek bir AWS CIDR blo\u011fu (Transit Gateway'in kendi rotalar\u0131) duyurmak yeterli oldu. Ayn\u0131 \u015fekilde, AWS'de de \u015firket i\u00e7i rotalar\u0131 tek bir yerden y\u00f6netmek m\u00fcmk\u00fcn hale geldi.<\/li>\n<li><strong>Geli\u015ftirilmi\u015f G\u00fcvenlik ve Denetim:<\/strong> T\u00fcm \u015firket i\u00e7i-bulut trafi\u011fi tek bir noktadan ge\u00e7ti\u011fi i\u00e7in, bu noktada g\u00fcvenlik duvar\u0131 (\u00f6rne\u011fin, ayr\u0131 bir g\u00fcvenlik VPC'sinde konu\u015fland\u0131r\u0131lm\u0131\u015f bir sanal g\u00fcvenlik duvar\u0131 appliance'\u0131) kurallar\u0131 uygulamak, trafik ak\u0131\u015f\u0131n\u0131 izlemek ve denetlemek \u00e7ok daha kolay hale geldi.<\/li>\n<li><strong>Y\u00fcksek Eri\u015filebilirlik ve Felaket Kurtarma:<\/strong> Birden fazla VPN ba\u011flant\u0131s\u0131 veya Direct Connect ba\u011flant\u0131s\u0131 yedekli bir \u015fekilde Transit Gateway'e ba\u011flanarak y\u00fcksek eri\u015filebilirlik sa\u011fland\u0131.<\/li>\n<\/ul>\n<h3>Vaka 3: Payla\u015f\u0131ml\u0131 Hizmetler VPC'si ve G\u00fcvenlik Merkezile\u015ftirme<\/h3>\n<p><strong>Senaryo:<\/strong> Bir e-ticaret platformu olan \"GlobalShop\", mikroservis mimarisini kullan\u0131yor ve her mikroservis kendi VPC'sinde ya\u015f\u0131yor (Auth VPC, Inventory VPC, Payment VPC vb.). Ayr\u0131ca, t\u00fcm bu servislerin ihtiya\u00e7 duydu\u011fu ortak hizmetler (Active Directory, izleme ara\u00e7lar\u0131, merkezi log toplama, g\u00fcvenlik duvarlar\u0131) ayr\u0131 bir \"Shared Services VPC\" i\u00e7inde bar\u0131nd\u0131r\u0131l\u0131yor. Geleneksel VPC peering ile, her uygulama VPC'sinin Shared Services VPC'sine ayr\u0131 ayr\u0131 ba\u011flanmas\u0131 gerekiyordu, bu da hem y\u00f6netim y\u00fck\u00fc hem de g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131n karma\u015f\u0131kl\u0131\u011f\u0131 a\u00e7\u0131s\u0131ndan sorunlara yol a\u00e7\u0131yordu.<\/p>\n<p><strong>Transit Gateway \u00c7\u00f6z\u00fcm\u00fc:<\/strong> GlobalShop, t\u00fcm uygulama VPC'lerini ve Shared Services VPC'sini tek bir AWS Transit Gateway'e ba\u011flad\u0131. Daha sonra, her uygulama VPC'sinin Shared Services VPC'sine eri\u015fimi i\u00e7in \u00f6zel rotalar yap\u0131land\u0131r\u0131ld\u0131. Ayr\u0131ca, t\u00fcm d\u0131\u015fa giden internet trafi\u011finin Shared Services VPC'si i\u00e7indeki merkezi bir g\u00fcvenlik duvar\u0131ndan ge\u00e7mesi i\u00e7in Transit Gateway \u00fczerinde \u00f6zel y\u00f6nlendirme tablolar\u0131 olu\u015fturuldu. Bu, t\u00fcm uygulama VPC'lerinin internete eri\u015fimini ve i\u00e7 a\u011f trafi\u011fini tek bir noktadan denetleyebilme imkan\u0131 sa\u011flad\u0131.<\/p>\n<p><strong>Faydalar\u0131:<\/strong><\/p>\n<ul>\n<li><strong>Merkezi G\u00fcvenlik Denetimi:<\/strong> T\u00fcm d\u0131\u015fa giden ve i\u00e7 a\u011f trafi\u011fi, Shared Services VPC'sindeki merkezi g\u00fcvenlik duvar\u0131ndan ge\u00e7irildi\u011fi i\u00e7in g\u00fcvenlik politikalar\u0131 tek bir noktadan y\u00f6netilebildi. Bu, g\u00fcvenlik duru\u015funu g\u00fc\u00e7lendirdi ve uyumluluk s\u00fcre\u00e7lerini kolayla\u015ft\u0131rd\u0131.<\/li>\n<li><strong>Kaynak Payla\u015f\u0131m\u0131 Kolayl\u0131\u011f\u0131:<\/strong> Ortak hizmetlerin t\u00fcm uygulama VPC'leri taraf\u0131ndan kolayca eri\u015filebilir olmas\u0131 sa\u011fland\u0131, b\u00f6ylece her VPC'de ayr\u0131 ayr\u0131 hizmet da\u011f\u0131tma ihtiyac\u0131 ortadan kalkt\u0131.<\/li>\n<li><strong>A\u011f Basitle\u015ftirmesi:<\/strong> Her uygulama VPC'si, Shared Services VPC'sine do\u011frudan peering yapmak yerine sadece Transit Gateway'e ba\u011fland\u0131. Bu, a\u011f topolojisini \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirdi.<\/li>\n<li><strong>Maliyet Optimizasyonu:<\/strong> G\u00fcvenlik duvar\u0131 gibi kaynaklar\u0131n merkezi olarak da\u011f\u0131t\u0131lmas\u0131, lisanslama ve y\u00f6netim maliyetlerini d\u00fc\u015f\u00fcrd\u00fc.<\/li>\n<\/ul>\n<p>Bu vaka analizleri, AWS Transit Gateway'in karma\u015f\u0131k ve \u00f6l\u00e7eklenebilir bulut a\u011flar\u0131 olu\u015fturmada ne kadar esnek ve g\u00fc\u00e7l\u00fc bir ara\u00e7 oldu\u011funu a\u00e7\u0131k\u00e7a g\u00f6stermektedir. Geli\u015ftiriciden finans kurulu\u015funa kadar bir\u00e7ok farkl\u0131 senaryoda operasyonel verimlili\u011fi, g\u00fcvenli\u011fi ve \u00f6l\u00e7eklenebilirli\u011fi art\u0131rma potansiyeline sahiptir.<\/p>\n<h2>Transit Gateway Optimizasyonu ve \u0130leri D\u00fczey \u0130pu\u00e7lar\u0131 Nelerdir?<\/h2>\n<p>AWS Transit Gateway, a\u011f\u0131n\u0131z\u0131 basitle\u015ftirmek ve \u00f6l\u00e7eklendirmek i\u00e7in harika bir ara\u00e7 olsa da, en iyi performans\u0131 ve maliyet verimlili\u011fini elde etmek i\u00e7in baz\u0131 optimizasyon teknikleri ve ileri d\u00fczey ipu\u00e7lar\u0131 mevcuttur. Deneyimli kullan\u0131c\u0131lar i\u00e7in bu ipu\u00e7lar\u0131, Transit Gateway kurulumunuzu bir sonraki seviyeye ta\u015f\u0131yabilir.<\/p>\n<h3>1. A\u011f Segmentasyonu \u0130\u00e7in \u00c7oklu Transit Gateway Y\u00f6nlendirme Tablolar\u0131<\/h3>\n<p>Ba\u015flang\u0131\u00e7ta t\u00fcm attachment'lar\u0131 tek bir varsay\u0131lan Transit Gateway y\u00f6nlendirme tablosuyla ili\u015fkilendirmek kolayd\u0131r. Ancak, a\u011f\u0131n\u0131z b\u00fcy\u00fcd\u00fck\u00e7e ve farkl\u0131 g\u00fcvenlik gereksinimleri ortaya \u00e7\u0131kt\u0131k\u00e7a, a\u011f segmentasyonu vazge\u00e7ilmez hale gelir. Birden fazla Transit Gateway y\u00f6nlendirme tablosu kullanarak farkl\u0131 a\u011f segmentleri olu\u015fturabilirsiniz. \u00d6rne\u011fin:<\/p>\n<ul>\n<li><strong>G\u00fcvenlik Alanlar\u0131:<\/strong> Geli\u015ftirme, Test ve \u00dcretim ortamlar\u0131 i\u00e7in ayr\u0131 tablolar. Her tablonun sadece kendi ortam\u0131ndaki VPC'lere ve belirli payla\u015f\u0131ml\u0131 hizmetlere eri\u015fimine izin verin.<\/li>\n<li><strong>Ortak Hizmetler Tablosu:<\/strong> T\u00fcm VPC'lerin eri\u015fmesi gereken Active Directory, DNS, g\u00fcvenlik duvarlar\u0131 gibi hizmetlerin bar\u0131nd\u0131\u011f\u0131 VPC i\u00e7in \u00f6zel bir tablo olu\u015fturun ve di\u011fer tablolar\u0131 bu tabloya rota ekleyerek ortak hizmetlere eri\u015fimi sa\u011flay\u0131n.<\/li>\n<li><strong>\u0130zolasyon:<\/strong> Hassas verilerin bulundu\u011fu VPC'leri, sadece belirli ve denetlenmi\u015f rotalara sahip \u00f6zel bir y\u00f6nlendirme tablosuyla ili\u015fkilendirin.<\/li>\n<\/ul>\n<p>Bu y\u00f6ntem, a\u011f trafi\u011fini daha gran\u00fcler bir \u015fekilde kontrol etmenizi, g\u00fcvenlik duru\u015funuzu g\u00fc\u00e7lendirmenizi ve olas\u0131 g\u00fcvenlik ihlallerinin yay\u0131lmas\u0131n\u0131 s\u0131n\u0131rlaman\u0131z\u0131 sa\u011flar.<\/p>\n<h3>2. \u00c7apraz Hesap Payla\u015f\u0131m\u0131 ve AWS Resource Access Manager (RAM)<\/h3>\n<p>Kurumsal ortamlarda genellikle farkl\u0131 departmanlar\u0131n veya projelerin ayr\u0131 AWS hesaplar\u0131 olur. AWS Transit Gateway'i bu hesaplar aras\u0131nda payla\u015fmak, merkezi bir a\u011f ekibinin Transit Gateway'i y\u00f6netmesini ve di\u011fer hesap sahiplerinin kendi VPC'lerini kolayca ba\u011flamas\u0131n\u0131 sa\u011flar. Bu, AWS Resource Access Manager (RAM) arac\u0131l\u0131\u011f\u0131yla yap\u0131l\u0131r. RAM kullanarak, Transit Gateway'i di\u011fer AWS hesaplar\u0131 veya AWS Kurulu\u015funuz i\u00e7indeki kurulu\u015f birimleri ile payla\u015fabilirsiniz. Payla\u015f\u0131lan hesaplar, kendi VPC'lerini Transit Gateway'e attachment olarak ekleyebilir. Bu, merkezi a\u011f y\u00f6netimini sa\u011flarken hesaplar aras\u0131 ba\u011f\u0131ms\u0131zl\u0131\u011f\u0131 korur.<\/p>\n<h3>3. Geli\u015fmi\u015f G\u00fcvenlik ve A\u011f Kontrol\u00fc<\/h3>\n<p>Transit Gateway seviyesinde routing kontrol\u00fc sa\u011flasa da, VPC'lerinizdeki Network Access Control List'leri (NACL'ler) ve G\u00fcvenlik Gruplar\u0131 (Security Groups) a\u011f g\u00fcvenli\u011finizin temel ta\u015flar\u0131 olmaya devam eder. Bu katmanl\u0131 g\u00fcvenlik yakla\u015f\u0131m\u0131 \u00e7ok \u00f6nemlidir. Ayr\u0131ca, t\u00fcm internete \u00e7\u0131kan veya \u015firket i\u00e7i a\u011fdan gelen trafi\u011fi merkezi bir \"Inspection VPC\" \u00fczerinden y\u00f6nlendirebilirsiniz. Bu VPC, sanal g\u00fcvenlik duvar\u0131 appliance'lar\u0131n\u0131 (\u00f6rne\u011fin, Palo Alto, FortiGate, Check Point) bar\u0131nd\u0131r\u0131r. T\u00fcm uygulama VPC'lerinden gelen giden trafi\u011fi Transit Gateway y\u00f6nlendirme tablolar\u0131 arac\u0131l\u0131\u011f\u0131yla bu Inspection VPC'ye y\u00f6nlendirerek, geli\u015fmi\u015f g\u00fcvenlik denetimi ve tehdit alg\u0131lama yetenekleri elde edebilirsiniz.<\/p>\n<h3>4. Performans ve Maliyet Optimizasyonu<\/h3>\n<ul>\n<li><strong>Subnet Se\u00e7imi:<\/strong> Transit Gateway attachment'lar\u0131 i\u00e7in her Availability Zone'da (AZ) \u00f6zel bir alt a\u011f kullanmak, a\u011f trafi\u011fini en uygun AZ'de tutarak gecikmeyi azalt\u0131r ve bant geni\u015fli\u011fi maliyetlerini optimize eder.<\/li>\n<li><strong>Bant Geni\u015fli\u011fi \u0130zleme:<\/strong> Amazon CloudWatch metriklerini kullanarak Transit Gateway attachment'lar\u0131n\u0131z\u0131n bant geni\u015fli\u011fi kullan\u0131m\u0131n\u0131 d\u00fczenli olarak izleyin. Anormal trafik desenlerini veya potansiyel darbo\u011fazlar\u0131 tespit etmek i\u00e7in bu verilere ihtiyac\u0131n\u0131z olacakt\u0131r.<\/li>\n<li><strong>Gereksiz Rotlardan Ka\u00e7\u0131nma:<\/strong> Transit Gateway y\u00f6nlendirme tablolar\u0131n\u0131zda sadece gerekli rotalar\u0131 tutmaya \u00f6zen g\u00f6sterin. Gereksiz rotalar, karma\u015f\u0131kl\u0131\u011f\u0131 art\u0131rabilir ve istenmeyen trafi\u011fe neden olabilir.<\/li>\n<li><strong>Veri Aktar\u0131m Maliyetleri:<\/strong> Transit Gateway, her gigabayt veri aktar\u0131m\u0131 i\u00e7in maliyet yans\u0131t\u0131r. A\u011f tasar\u0131m\u0131n\u0131z\u0131 yaparken, \u00f6zellikle b\u00f6lgeler aras\u0131 (inter-region) Transit Gateway peering kullan\u0131l\u0131yorsa, bu maliyetleri g\u00f6z \u00f6n\u00fcnde bulundurun ve trafik ak\u0131\u015flar\u0131n\u0131 optimize edin. Ayn\u0131 AZ i\u00e7indeki trafik genellikle daha uygun maliyetlidir.<\/li>\n<\/ul>\n<p>Transit Gateway, karma\u015f\u0131k y\u00f6nlendirme senaryolar\u0131nda, \u00f6zellikle Direct Connect veya Site-to-Site VPN ba\u011flant\u0131lar\u0131nda BGP (Border Gateway Protocol) rotalar\u0131n\u0131 destekler. Bu, \u015firket i\u00e7i a\u011f\u0131n\u0131zdaki rotalar\u0131n Transit Gateway'e otomatik olarak duyurulmas\u0131n\u0131 sa\u011flayarak dinamik ve hataya dayan\u0131kl\u0131 bir routing yap\u0131s\u0131 olu\u015fturman\u0131za olanak tan\u0131r.<\/p>\n<h3>5. \u0130zleme ve Sorun Giderme<\/h3>\n<p>AWS CloudWatch, Transit Gateway performans\u0131n\u0131 ve trafi\u011fini izlemek i\u00e7in kritik bir ara\u00e7t\u0131r. Attachment ba\u015f\u0131na paket say\u0131lar\u0131, bayt say\u0131lar\u0131 ve b\u0131rak\u0131lan paketler gibi metrikleri izleyebilirsiniz. Ayr\u0131ca, Amazon VPC Flow Logs'u etkinle\u015ftirerek, Transit Gateway \u00fczerinden ge\u00e7en t\u00fcm IP trafik ak\u0131\u015flar\u0131 hakk\u0131nda ayr\u0131nt\u0131l\u0131 bilgiler toplayabilirsiniz. Bu loglar, a\u011f sorunlar\u0131n\u0131 gidermek, g\u00fcvenlik ihlallerini tespit etmek ve a\u011f kullan\u0131m modellerini analiz etmek i\u00e7in son derece de\u011ferlidir.<\/p>\n<p>Transit Gateway, a\u011f topolojinizi \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirirken, do\u011fru yap\u0131land\u0131rma ve optimizasyon teknikleriyle maksimum fayda sa\u011flayacakt\u0131r. Bu ileri d\u00fczey ipu\u00e7lar\u0131, a\u011f\u0131n\u0131z\u0131n daha g\u00fcvenli, verimli ve maliyet etkin olmas\u0131n\u0131 sa\u011flaman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<div class=\"uzman-ipucu\">\n      Uzman \u0130pucu: \u00c7oklu AWS b\u00f6lgelerinde \u00e7al\u0131\u015fan uygulamalar\u0131n\u0131z varsa, b\u00f6lgeler aras\u0131 ba\u011flant\u0131 i\u00e7in Transit Gateway Inter-Region Peering \u00f6zelli\u011fini kullan\u0131n. Bu, k\u00fcresel bir a\u011f olu\u015fturman\u0131za ve veri aktar\u0131m\u0131n\u0131 basitle\u015ftirmenize olanak tan\u0131r, ancak veri aktar\u0131m maliyetlerini dikkatle izlemeniz gerekir.\n    <\/div>\n<h2>Sonu\u00e7: AWS Transit Gateway ile Gelece\u011fin A\u011f\u0131na Ad\u0131m At\u0131n + S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<p>AWS Transit Gateway, modern bulut a\u011f mimarilerinin karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 gidermek ve kurulu\u015flara \u00f6l\u00e7eklenebilir, g\u00fcvenli ve y\u00f6netilebilir bir a\u011f omurgas\u0131 sunmak i\u00e7in tasarlanm\u0131\u015f devrim niteli\u011finde bir hizmettir. Geleneksel VPC peering'in getirdi\u011fi \"\u00f6r\u00fcmcek a\u011f\u0131\" karma\u015fas\u0131n\u0131 ortadan kald\u0131rarak, t\u00fcm AWS VPC'lerinizi, \u015firket i\u00e7i veri merkezinizi ve di\u011fer AWS hesaplar\u0131n\u0131z\u0131 merkezi bir \"hub\" \u00fczerinden ba\u011flaman\u0131za olanak tan\u0131r. Bu sayede, a\u011f topolojiniz basitle\u015fir, y\u00f6netim y\u00fck\u00fc azal\u0131r ve operasyonel verimlili\u011finiz \u00f6nemli \u00f6l\u00e7\u00fcde artar. \u00d6zellikle \u00e7oklu VPC ortamlar\u0131nda, hibrit bulut senaryolar\u0131nda ve merkezi g\u00fcvenlik denetimi gerektiren durumlarda Transit Gateway, oyunun kurallar\u0131n\u0131 de\u011fi\u015ftiren bir \u00e7\u00f6z\u00fcm sunar. G\u00fcvenli\u011fi, performans\u0131 ve maliyet etkinli\u011fini art\u0131rma potansiyeliyle, AWS \u00fczerindeki a\u011f altyap\u0131n\u0131z\u0131 gelece\u011fe haz\u0131r hale getirmek i\u00e7in vazge\u00e7ilmez bir ara\u00e7t\u0131r.<\/p>\n<p>Bu makalede, Transit Gateway'in temel kavramlar\u0131ndan, ad\u0131m ad\u0131m kurulumuna, ger\u00e7ek d\u00fcnya vaka analizlerine ve ileri d\u00fczey optimizasyon ipu\u00e7lar\u0131na kadar her \u015feyi ele ald\u0131k. Art\u0131k da\u011f\u0131n\u0131k a\u011f yap\u0131lar\u0131n\u0131z\u0131n neden oldu\u011fu ba\u015f a\u011fr\u0131lar\u0131ndan kurtulabilir ve daha esnek, g\u00fcvenli ve verimli bir a\u011f altyap\u0131s\u0131 in\u015fa edebilirsiniz. AWS Transit Gateway'i a\u011f stratejinizin merkezine alarak, bulut yolculu\u011funuzda \u00f6nemli bir avantaj elde edeceksiniz. \u015eimdi, ak\u0131llardaki baz\u0131 s\u0131k\u00e7a sorulan sorulara yan\u0131t vererek konuyu daha da peki\u015ftirelim.<\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular<\/h3>\n<h4>1. Transit Gateway ile VPC peering aras\u0131ndaki temel fark nedir?<\/h4>\n<p><strong>Cevap:<\/strong> Temel fark \"ge\u00e7i\u015flilik\" (transitivity) kavram\u0131nda yatar. VPC peering, yaln\u0131zca do\u011frudan ba\u011fl\u0131 iki VPC aras\u0131nda \u00e7al\u0131\u015f\u0131r; \u00fc\u00e7\u00fcnc\u00fc bir VPC'ye do\u011frudan rota sa\u011flayamaz. Yani, VPC A ile VPC B aras\u0131nda peering varsa ve VPC B ile VPC C aras\u0131nda peering varsa, VPC A do\u011frudan VPC C ile ileti\u015fim kuramaz. Transit Gateway ise, ba\u011fl\u0131 t\u00fcm VPC'ler aras\u0131nda ge\u00e7i\u015flili\u011fi destekler. T\u00fcm VPC'ler Transit Gateway'e ba\u011fland\u0131\u011f\u0131nda, herhangi bir ba\u011fl\u0131 VPC di\u011fer t\u00fcm ba\u011fl\u0131 VPC'lerle do\u011frudan ileti\u015fim kurabilir. Bu, a\u011f topolojisini \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirir ve \"hub-and-spoke\" mimarisini m\u00fcmk\u00fcn k\u0131lar.<\/p>\n<h4>2. Transit Gateway'in maliyetleri nas\u0131l hesaplan\u0131r?<\/h4>\n<p><strong>Cevap:<\/strong> Transit Gateway maliyetleri iki ana bile\u015fenden olu\u015fur:<\/p>\n<ol>\n<li><strong>Transit Gateway Attachment (Eklenti) \u00dccreti:<\/strong> Transit Gateway'e ba\u011fl\u0131 her attachment (VPC, VPN, Direct Connect vb.) i\u00e7in saatlik bir \u00fccret al\u0131n\u0131r.<\/li>\n<li><strong>Transit Gateway Veri \u0130\u015fleme \u00dccreti:<\/strong> Transit Gateway \u00fczerinden ge\u00e7en her GB veri i\u00e7in bir veri i\u015fleme \u00fccreti al\u0131n\u0131r. Bu \u00fccret, verinin nereden geldi\u011fine veya nereye gitti\u011fine bak\u0131lmaks\u0131z\u0131n uygulan\u0131r. B\u00f6lgeler aras\u0131 (inter-region) Transit Gateway peering kullan\u0131l\u0131yorsa, ayr\u0131ca b\u00f6lgeler aras\u0131 veri aktar\u0131m \u00fccretleri de eklenir.<\/li>\n<\/ol>\n<p>        Bu maliyetleri g\u00f6z \u00f6n\u00fcnde bulundurarak, a\u011f trafi\u011finizi optimize etmek ve gereksiz veri aktar\u0131mlar\u0131ndan ka\u00e7\u0131nmak \u00f6nemlidir.<\/p>\n<h4>3. Farkl\u0131 AWS b\u00f6lgeleri aras\u0131nda Transit Gateway ile ba\u011flant\u0131 kurabilir miyim?<\/h4>\n<p><strong>Cevap:<\/strong> Evet, kurabilirsiniz. AWS Transit Gateway, \"Inter-Region Peering\" \u00f6zelli\u011fini destekler. Bu \u00f6zellik sayesinde, farkl\u0131 AWS b\u00f6lgelerinde konu\u015fland\u0131r\u0131lm\u0131\u015f Transit Gateway'leri birbirine ba\u011flayarak k\u00fcresel bir a\u011f omurgas\u0131 olu\u015fturabilirsiniz. Bu, k\u00fcresel olarak da\u011f\u0131t\u0131lm\u0131\u015f uygulamalar\u0131n\u0131z veya felaket kurtarma senaryolar\u0131n\u0131z i\u00e7in kritik \u00f6neme sahiptir. Ancak, b\u00f6lgeler aras\u0131 veri aktar\u0131m \u00fccretlerinin daha y\u00fcksek olabilece\u011fini unutmamal\u0131s\u0131n\u0131z.<\/p>\n<h4>4. Transit Gateway \u00fczerinde g\u00fcvenlik duvar\u0131 \u00e7al\u0131\u015ft\u0131rabilir miyim?<\/h4>\n<p><strong>Cevap:<\/strong> Transit Gateway do\u011frudan bir g\u00fcvenlik duvar\u0131 hizmeti de\u011fildir, ancak merkezi bir g\u00fcvenlik duvar\u0131 \u00e7\u00f6z\u00fcm\u00fcn\u00fc entegre etmek i\u00e7in kullan\u0131labilir. Genellikle, t\u00fcm d\u0131\u015fa giden internet trafi\u011fini veya \u00f6nemli dahili trafi\u011fi denetlemek i\u00e7in \u00f6zel bir \"Inspection VPC\" olu\u015fturulur. Bu Inspection VPC, \u00fc\u00e7\u00fcnc\u00fc taraf sanal g\u00fcvenlik duvar\u0131 appliance'lar\u0131n\u0131 (\u00f6rne\u011fin, Palo Alto Networks, FortiGate, Check Point vb.) bar\u0131nd\u0131r\u0131r. Transit Gateway y\u00f6nlendirme tablolar\u0131 kullan\u0131larak, t\u00fcm ilgili trafik bu Inspection VPC'ye y\u00f6nlendirilir, orada g\u00fcvenlik duvar\u0131 kurallar\u0131ndan ge\u00e7irilir ve ard\u0131ndan hedefine y\u00f6nlendirilir. Bu yakla\u015f\u0131m, a\u011f\u0131n\u0131z i\u00e7in merkezi ve kapsaml\u0131 bir g\u00fcvenlik duru\u015fu sa\u011flar.<\/p>\n<h4>5. Mevcut bir a\u011f yap\u0131s\u0131n\u0131 Transit Gateway'e nas\u0131l ta\u015f\u0131r\u0131m?<\/h4>\n<p><strong>Cevap:<\/strong> Mevcut bir a\u011f\u0131 Transit Gateway'e ta\u015f\u0131mak genellikle a\u015famal\u0131 bir yakla\u015f\u0131mla yap\u0131l\u0131r:<\/p>\n<ol>\n<li><strong>Planlama:<\/strong> Mevcut a\u011f topolojinizi analiz edin, hangi VPC'lerin ve ba\u011flant\u0131lar\u0131n Transit Gateway'e ta\u015f\u0131naca\u011f\u0131n\u0131 belirleyin. IP adresi \u00e7ak\u0131\u015fmalar\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li><strong>Transit Gateway Olu\u015fturma:<\/strong> Yukar\u0131daki ad\u0131mlar\u0131 izleyerek bir Transit Gateway olu\u015fturun.<\/li>\n<li><strong>VPC Attachment'lar\u0131n\u0131 Olu\u015fturma:<\/strong> Mevcut VPC'leriniz i\u00e7in Transit Gateway attachment'lar\u0131 olu\u015fturun. Ancak, bu a\u015famada VPC y\u00f6nlendirme tablolar\u0131n\u0131 hen\u00fcz g\u00fcncellemeyin.<\/li>\n<li><strong>Test ve Ge\u00e7i\u015f:<\/strong> \u00d6nce kritik olmayan veya test VPC'lerinden ba\u015flayarak, VPC y\u00f6nlendirme tablolar\u0131n\u0131 Transit Gateway'e i\u015faret edecek \u015fekilde g\u00fcncelleyin. Trafi\u011fin beklenen \u015fekilde ak\u0131p akmad\u0131\u011f\u0131n\u0131 dikkatlice test edin. Her VPC'yi ayr\u0131 ayr\u0131 veya k\u00fc\u00e7\u00fck gruplar halinde ta\u015f\u0131yarak riskleri minimize edin.<\/li>\n<li><strong>Eski Ba\u011flant\u0131lar\u0131n Kald\u0131r\u0131lmas\u0131:<\/strong> T\u00fcm trafik Transit Gateway \u00fczerinden akmaya ba\u015flad\u0131\u011f\u0131nda, eski VPC peering ba\u011flant\u0131lar\u0131n\u0131 veya ba\u011f\u0131ms\u0131z VPN ba\u011flant\u0131lar\u0131n\u0131 kald\u0131rabilirsiniz.<\/li>\n<\/ol>\n<p>        Bu s\u00fcre\u00e7, kesintiyi minimize etmek i\u00e7in dikkatli planlama ve test gerektirir.<\/p>\n<p><\/body><br \/>\n<\/html><\/p>\n","protected":false},"excerpt":{"rendered":"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede,&hellip;","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1406],"tags":[],"class_list":{"0":"post-32504","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-aws","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f<\/title>\n<meta name=\"description\" content=\"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway&#039;in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f\" \/>\n<meta property=\"og:description\" content=\"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway&#039;in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-22T11:01:27+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"26 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f\",\"datePublished\":\"2025-10-22T11:01:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\"},\"wordCount\":5135,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"AWS\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\",\"name\":\"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-22T11:01:27+00:00\",\"description\":\"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway'in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f","description":"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway'in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/","og_locale":"tr_TR","og_type":"article","og_title":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f","og_description":"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway'in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.","og_url":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-22T11:01:27+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"26 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f","datePublished":"2025-10-22T11:01:27+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/"},"wordCount":5135,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["AWS"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/","url":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/","name":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-22T11:01:27+00:00","description":"AWS Transit Gateway, karma\u015f\u0131k a\u011f yap\u0131lar\u0131n\u0131 basitle\u015ftiren, g\u00fcvenli\u011fi art\u0131ran ve maliyetleri d\u00fc\u015f\u00fcren merkezi bir a\u011f \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Bu makalede, \u00e7oklu VPC ortamlar\u0131nda ve hibrit bulut senaryolar\u0131nda Transit Gateway'in nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 ke\u015ffedeceksiniz.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/aws-transit-gateway-ile-guvenli-ve-olceklenebilir-ag\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"AWS Transit Gateway ile G\u00fcvenli ve \u00d6l\u00e7eklenebilir A\u011f"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32504","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=32504"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32504\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=32504"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=32504"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=32504"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}