{"id":32505,"date":"2025-10-22T14:31:54","date_gmt":"2025-10-22T11:31:54","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/"},"modified":"2025-10-22T14:31:54","modified_gmt":"2025-10-22T11:31:54","slug":"amazon-eks-ve-kalici-depolama-ihtiyaci-nedir","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/","title":{"rendered":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?"},"content":{"rendered":"

Amazon EFS ve EKS Entegrasyonu: Terraform ile Kal\u0131c\u0131 Depolama<\/span><\/p>\n

Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS’yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.<\/p>\n

G\u00fcn\u00fcm\u00fcz\u00fcn bulut tabanl\u0131 uygulamalar\u0131, dinamik ve \u00f6l\u00e7eklenebilir altyap\u0131lar \u00fczerinde \u00e7al\u0131\u015fmay\u0131 gerektiriyor. Bu altyap\u0131lar\u0131n ba\u015f\u0131nda \u015f\u00fcphesiz Kubernetes geliyor. Amazon Elastic Kubernetes Service (EKS), AWS bulutunda y\u00f6netilen Kubernetes k\u00fcmeleri sunarak, geli\u015ftiricilerin uygulamalar\u0131n\u0131 daha verimli bir \u015fekilde da\u011f\u0131tmas\u0131na ve y\u00f6netmesine olanak tan\u0131r. Ancak, konteyner tabanl\u0131 uygulamalar\u0131n do\u011fas\u0131 gere\u011fi, pod’lar genellikle k\u0131sa \u00f6m\u00fcrl\u00fcd\u00fcr ve yeniden ba\u015flat\u0131ld\u0131klar\u0131nda veya farkl\u0131 d\u00fc\u011f\u00fcmlere ta\u015f\u0131nd\u0131klar\u0131nda \u00fczerlerindeki verileri kaybederler. \u0130\u015fte bu noktada kal\u0131c\u0131 depolama (persistent storage)<\/strong> ihtiyac\u0131 ortaya \u00e7\u0131kar.<\/p>\n

Pek \u00e7ok uygulama, \u00e7al\u0131\u015fabilmek i\u00e7in verilerini kal\u0131c\u0131 olarak saklamaya ihtiya\u00e7 duyar. \u00d6rne\u011fin, bir veritaban\u0131, bir i\u00e7erik y\u00f6netim sistemi (CMS) veya bir e-ticaret platformu d\u00fc\u015f\u00fcn\u00fcn. Bu t\u00fcr stateful uygulamalar<\/strong>, pod’lar\u0131n \u00f6mr\u00fcnden ba\u011f\u0131ms\u0131z olarak verilerin korunmas\u0131n\u0131 ve eri\u015filebilir olmas\u0131n\u0131 bekler. Aksi takdirde, her pod yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda, uygulama t\u00fcm verilerini kaybeder ve ba\u015ftan ba\u015flamak zorunda kal\u0131r ki bu, i\u015f s\u00fcreklili\u011fi a\u00e7\u0131s\u0131ndan kabul edilemez bir durumdur. Kubernetes’in kal\u0131c\u0131 depolama mekanizmalar\u0131, PersistentVolume (PV) ve PersistentVolumeClaim (PVC) sayesinde bu soruna \u00e7\u00f6z\u00fcm sunar. Ancak, bu mekanizmalar\u0131n alt\u0131nda yatan depolama \u00e7\u00f6z\u00fcm\u00fcn\u00fcn do\u011fru se\u00e7ilmesi b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r.<\/p>\n

Peki, Amazon EKS ortam\u0131nda kal\u0131c\u0131 depolama i\u00e7in en uygun se\u00e7eneklerden biri neden Amazon Elastic File System (EFS)? \u00c7\u00fcnk\u00fc EFS, birden fazla EKS pod’u taraf\u0131ndan ayn\u0131 anda eri\u015filebilen, \u00f6l\u00e7eklenebilir, esnek ve tam olarak y\u00f6netilen bir NFS dosya sistemi sa\u011flar. Bu, mikro hizmet tabanl\u0131 mimarilerde, \u00f6zellikle de birden fazla pod’un ayn\u0131 dosya sistemine yazma\/okuma yapmas\u0131 gereken senaryolarda kritik bir avantajd\u0131r. EKS ile entegre edildi\u011finde, EFS, uygulamalar\u0131n\u0131z\u0131n y\u00fcksek eri\u015filebilirlik ve veri tutarl\u0131l\u0131\u011f\u0131 gereksinimlerini kar\u015f\u0131lamalar\u0131na yard\u0131mc\u0131 olur. Ayr\u0131ca, Terraform<\/strong> gibi bir Altyap\u0131 olarak Kod (IaC) arac\u0131 kullanarak bu entegrasyonu otomatikle\u015ftirmek, hem h\u0131z\u0131 art\u0131r\u0131r hem de insan hatas\u0131 riskini en aza indirir. Bu kombinasyon, DevOps pratiklerini benimsemi\u015f ekipler i\u00e7in vazge\u00e7ilmez bir \u00e7\u00f6z\u00fcm sunar. Dolay\u0131s\u0131yla, bu makale boyunca, bu g\u00fc\u00e7l\u00fc \u00fc\u00e7l\u00fcy\u00fc – EKS, EFS ve Terraform’u – bir araya getirerek, konteynerize uygulamalar\u0131n\u0131z i\u00e7in sa\u011flam ve s\u00fcrd\u00fcr\u00fclebilir bir depolama altyap\u0131s\u0131 nas\u0131l olu\u015fturaca\u011f\u0131n\u0131z\u0131 detayl\u0131 bir \u015fekilde inceleyece\u011fiz.<\/p>\n

Temel Ta\u015flar: Amazon EFS, EKS ve Terraform’a Yak\u0131ndan Bak\u0131\u015f<\/h2>\n

Modern bulut altyap\u0131lar\u0131nda ba\u015far\u0131l\u0131 entegrasyonlar ger\u00e7ekle\u015ftirebilmek i\u00e7in, kullan\u0131lan temel bile\u015fenleri derinlemesine anlamak elzemdir. Bu b\u00f6l\u00fcmde, entegrasyonumuzun temelini olu\u015fturan Amazon EFS, Amazon EKS ve Terraform’a yak\u0131ndan bakacak, her birinin neden bu senaryoda kritik rol oynad\u0131\u011f\u0131n\u0131 anlayaca\u011f\u0131z.<\/p>\n

Amazon EFS Nedir ve Neden \u00d6nemlidir?<\/h3>\n

Amazon Elastic File System (EFS), AWS bulutunda kolayca \u00f6l\u00e7eklenebilen, sunucusuz, tam olarak y\u00f6netilen bir NFS (Network File System) dosya depolama hizmetidir<\/strong>. EFS’nin en b\u00fcy\u00fck avantajlar\u0131ndan biri, ayn\u0131 anda binlerce EC2 \u00f6rne\u011fi veya konteyner taraf\u0131ndan eri\u015filebilmesidir. Bu \u00f6zellik, \u00f6zellikle \u00e7ok say\u0131da pod’un ayn\u0131 veri setine eri\u015fmesi gereken EKS ortamlar\u0131 i\u00e7in onu ideal bir se\u00e7enek haline getirir. EFS, verilerinizin y\u00fcksek oranda dayan\u0131kl\u0131 olmas\u0131n\u0131 sa\u011flar; AWS’nin belirtti\u011fine g\u00f6re, verileri birden fazla Availability Zone’da (AZ) depolayarak %99.999999999 (11 adet 9) dayan\u0131kl\u0131l\u0131k sunar. Ayr\u0131ca, depolama alan\u0131n\u0131z\u0131 manuel olarak sa\u011flaman\u0131za gerek kalmadan, uygulama ihtiya\u00e7lar\u0131n\u0131za g\u00f6re otomatik olarak \u00f6l\u00e7eklenir, bu da maliyet etkinli\u011fi ve operasyonel kolayl\u0131k sa\u011flar.<\/p>\n

EFS’nin di\u011fer \u00f6nemli \u00f6zellikleri aras\u0131nda \u015funlar bulunur:<\/p>\n

    \n
  • Payla\u015f\u0131ml\u0131 Eri\u015fim:<\/strong> Birden fazla EC2 \u00f6rne\u011fi veya EKS pod’u ayn\u0131 anda ayn\u0131 dosya sistemine okuma\/yazma eri\u015fimi sa\u011flayabilir.<\/li>\n
  • Esneklik:<\/strong> Dosya sistemleri terabaytlarca veriye kadar \u00f6l\u00e7eklenebilir ve sadece kulland\u0131\u011f\u0131n\u0131z depolama alan\u0131 i\u00e7in \u00f6deme yapars\u0131n\u0131z.<\/li>\n
  • Y\u00fcksek Performans:<\/strong> Farkl\u0131 performans modlar\u0131 (General Purpose, Max I\/O) ve \u00e7\u0131k\u0131\u015f tipleri (Bursting, Provisioned) ile uygulaman\u0131z\u0131n gereksinimlerine uygun performans\u0131 sa\u011flayabilirsiniz.<\/li>\n
  • G\u00fcvenlik:<\/strong> Veri aktar\u0131m\u0131 s\u0131ras\u0131nda ve depoda \u015fifreleme, AWS IAM ile entegrasyon ve a\u011f eri\u015fimi i\u00e7in g\u00fcvenlik gruplar\u0131 gibi \u00f6zelliklerle g\u00fcvenlik sa\u011flan\u0131r.<\/li>\n<\/ul>\n

    K\u0131sacas\u0131, EFS, EKS \u00fczerinde \u00e7al\u0131\u015fan stateful uygulamalar i\u00e7in esneklik, \u00f6l\u00e7eklenebilirlik ve y\u00fcksek eri\u015filebilirlik sunan kritik bir depolama \u00e7\u00f6z\u00fcm\u00fcd\u00fcr.<\/p>\n

    Amazon EKS Neden Tercih Edilmeli?<\/h3>\n

    Amazon Elastic Kubernetes Service (EKS), geli\u015ftiricilerin ve operasyon ekiplerinin Kubernetes’i AWS bulutunda kolayca da\u011f\u0131tmas\u0131na, y\u00f6netmesine ve \u00f6l\u00e7eklendirmesine olanak tan\u0131yan tam olarak y\u00f6netilen bir hizmettir. EKS, Kubernetes kontrol d\u00fczleminin (master node’lar) y\u00f6netimini AWS’ye b\u0131rakarak, kullan\u0131c\u0131lar\u0131n yaln\u0131zca i\u015f y\u00fcklerini (worker node’lar) y\u00f6netmeye odaklanmas\u0131n\u0131 sa\u011flar. Bu, operasyonel y\u00fck\u00fc \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r ve altyap\u0131 y\u00f6netiminden ziyade uygulama geli\u015ftirmeye daha fazla zaman ayr\u0131lmas\u0131na imkan tan\u0131r.<\/p>\n

    EKS’nin tercih edilmesinin ba\u015fl\u0131ca nedenleri \u015funlard\u0131r:<\/p>\n

      \n
    • Y\u00f6netilen Hizmet:<\/strong> Kontrol d\u00fczlemi i\u00e7in otomatik yamalama, y\u00fckseltmeler ve y\u00fcksek eri\u015filebilirlik sunar.<\/li>\n
    • G\u00fcvenlik:<\/strong> AWS IAM ile derin entegrasyon, a\u011f izolasyonu ve g\u00fcvenlik gruplar\u0131 ile g\u00fc\u00e7l\u00fc g\u00fcvenlik mekanizmalar\u0131 sa\u011flar.<\/li>\n
    • \u00d6l\u00e7eklenebilirlik:<\/strong> Hem kontrol d\u00fczlemi hem de worker node’lar\u0131 i\u00e7in kolay \u00f6l\u00e7eklenebilirlik sunar.<\/li>\n
    • Entegrasyon:<\/strong> AWS hizmetleriyle (VPC, IAM, CloudWatch, ELB gibi) sorunsuz entegrasyon sa\u011flar.<\/li>\n<\/ul>\n

      EKS, \u015firketlerin modern, konteynerize uygulamalar\u0131n\u0131 g\u00fcvenilir, \u00f6l\u00e7eklenebilir ve y\u00fcksek performansl\u0131 bir ortamda \u00e7al\u0131\u015ft\u0131rmalar\u0131 i\u00e7in g\u00fc\u00e7l\u00fc bir temel olu\u015fturur. Bu da onu kal\u0131c\u0131 depolama \u00e7\u00f6z\u00fcmleriyle entegrasyon i\u00e7in m\u00fckemmel bir platform yapar.<\/p>\n

      Terraform ile Altyap\u0131 Y\u00f6netimi Nas\u0131l Kolayla\u015f\u0131r?<\/h3>\n

      Terraform, HashiCorp taraf\u0131ndan geli\u015ftirilen a\u00e7\u0131k kaynakl\u0131 bir Altyap\u0131 olarak Kod (Infrastructure as Code – IaC)<\/strong> arac\u0131d\u0131r. Kullan\u0131c\u0131lar\u0131n bulut veya \u015firket i\u00e7i kaynaklar\u0131n\u0131 tan\u0131mlamalar\u0131n\u0131 ve sa\u011flamalar\u0131n\u0131 sa\u011flayan bildirimsel bir yap\u0131land\u0131rma dili (HashiCorp Configuration Language – HCL) kullan\u0131r. Terraform’un temel avantaj\u0131, altyap\u0131y\u0131 kod olarak y\u00f6netme yetene\u011fidir; bu da altyap\u0131n\u0131n versiyonlanabilmesini, test edilebilir olmas\u0131n\u0131 ve da\u011f\u0131t\u0131mlar\u0131n tutarl\u0131 ve tekrarlanabilir olmas\u0131n\u0131 sa\u011flar. Bu sayede, EKS k\u00fcmesi olu\u015fturmaktan EFS dosya sistemi yap\u0131land\u0131rmaya, hatta Kubernetes kaynaklar\u0131n\u0131 bile tan\u0131mlamaya kadar t\u00fcm altyap\u0131n\u0131z\u0131 tek bir ara\u00e7la y\u00f6netebilirsiniz.<\/p>\n

      Terraform’un bu entegrasyon senaryosunda kritik olmas\u0131n\u0131n nedenleri:<\/p>\n

        \n
      • Otomasyon:<\/strong> T\u00fcm AWS ve Kubernetes kaynaklar\u0131n\u0131n otomatik olarak sa\u011flanmas\u0131n\u0131 ve g\u00fcncellenmesini sa\u011flar.<\/li>\n
      • Tutarl\u0131l\u0131k:<\/strong> Altyap\u0131n\u0131n her da\u011f\u0131t\u0131m\u0131nda ayn\u0131 \u015fekilde olu\u015fturulmas\u0131n\u0131 garanti eder, bu da “konfig\u00fcrasyon kaymas\u0131” (configuration drift) riskini azalt\u0131r.<\/li>\n
      • Versiyon Kontrol\u00fc:<\/strong> Altyap\u0131 tan\u0131mlar\u0131n\u0131 Git gibi bir versiyon kontrol sisteminde saklayarak de\u011fi\u015fiklikleri izleme ve geri alma imkan\u0131 sunar.<\/li>\n
      • Mod\u00fclerlik:<\/strong> Tekrar kullan\u0131labilir mod\u00fcller arac\u0131l\u0131\u011f\u0131yla altyap\u0131 kodunu d\u00fczenlemeyi ve payla\u015fmay\u0131 kolayla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n

        Terraform, bu entegrasyon s\u00fcrecini basitle\u015ftirir, h\u0131zland\u0131r\u0131r ve hatalar\u0131 minimize eder. Bu \u00fc\u00e7l\u00fcn\u00fcn birle\u015fimi, modern bir bulut altyap\u0131s\u0131 i\u00e7in sa\u011flam, \u00f6l\u00e7eklenebilir ve y\u00f6netilebilir bir temel olu\u015fturur.<\/p>\n

        Ad\u0131m Ad\u0131m Entegrasyon: Terraform ile EFS ve EKS Nas\u0131l Yap\u0131land\u0131r\u0131l\u0131r?<\/h2>\n

        Amazon EFS’yi Amazon EKS ile entegre etmek, \u00f6zellikle Terraform kullanarak, sistematik bir s\u00fcre\u00e7 gerektirir. Bu b\u00f6l\u00fcmde, gerekli \u00f6nko\u015fullar\u0131 belirledikten sonra, EFS dosya sistemi olu\u015fturma, EKS k\u00fcmesini kurma ve EFS CSI s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc yap\u0131land\u0131rma ad\u0131mlar\u0131n\u0131 detayl\u0131 Terraform kod \u00f6rnekleriyle a\u00e7\u0131klayaca\u011f\u0131z. Unutmay\u0131n, bu ad\u0131mlar\u0131 takip etmeden \u00f6nce AWS CLI, kubectl<\/span> ve Terraform’un sisteminizde kurulu ve yap\u0131land\u0131r\u0131lm\u0131\u015f oldu\u011fundan emin olmal\u0131s\u0131n\u0131z.<\/p>\n

        EFS Dosya Sistemi Olu\u015fturma ve Yap\u0131land\u0131rma Ad\u0131mlar\u0131 Nelerdir?<\/h3>\n

        EKS k\u00fcmenizin kullanaca\u011f\u0131 EFS dosya sistemini olu\u015fturmak i\u00e7in \u00f6ncelikle gerekli a\u011f altyap\u0131s\u0131n\u0131 (VPC, alt a\u011flar, g\u00fcvenlik gruplar\u0131) tan\u0131mlamam\u0131z gerekiyor. EFS, EC2 \u00f6rneklerinin veya EKS pod’lar\u0131n\u0131n ona ba\u011flanabilmesi i\u00e7in bir veya daha fazla Mount Target’a ihtiya\u00e7 duyar. Her Mount Target, EFS dosya sistemine bir alt a\u011fda a\u011f aray\u00fcz\u00fc sa\u011flar.<\/p>\n

        A\u015fa\u011f\u0131daki Terraform kodu, bu ad\u0131mlar\u0131 otomatikle\u015ftirmek i\u00e7in kullan\u0131labilir:<\/p>\n

        <\/p>\n

        \nresource \"aws_vpc\" \"main\" {\n  cidr_block = \"10.0.0.0\/16\"\n  enable_dns_hostnames = true\n  tags = {\n    Name = \"eks-efs-vpc\"\n  }\n}\n\nresource \"aws_subnet\" \"public\" {\n  count             = 2\n  vpc_id            = aws_vpc.main.id\n  cidr_block        = cidrsubnet(aws_vpc.main.cidr_block, 8, count.index)\n  availability_zone = data.aws_availability_zones.available.names[count.index]\n  tags = {\n    Name = \"eks-efs-public-subnet-${count.index}\"\n  }\n}\n\nresource \"aws_security_group\" \"efs_security_group\" {\n  name        = \"efs-sg\"\n  description = \"Allow NFS traffic to EFS\"\n  vpc_id      = aws_vpc.main.id\n\n  ingress {\n    description = \"Allow NFS from VPC CIDR\"\n    from_port   = 2049 # NFS port\n    to_port     = 2049\n    protocol    = \"tcp\"\n    cidr_blocks = [aws_vpc.main.cidr_block]\n  }\n\n  egress {\n    from_port   = 0\n    to_port     = 0\n    protocol    = \"-1\"\n    cidr_blocks = [\"0.0.0.0\/0\"]\n  }\n  tags = {\n    Name = \"efs-sg\"\n  }\n}\n\nresource \"aws_efs_file_system\" \"eks_efs\" {\n  creation_token = \"eks-efs-file-system\"\n  encrypted      = true\n  performance_mode = \"generalPurpose\" # Veya \"maxIO\"\n  throughput_mode  = \"bursting\"       # Veya \"provisioned\"\n\n  tags = {\n    Name = \"eks-efs\"\n  }\n}\n\nresource \"aws_efs_mount_target\" \"eks_efs_mount_target\" {\n  count           = length(aws_subnet.public)\n  file_system_id  = aws_efs_file_system.eks_efs.id\n  subnet_id       = aws_subnet.public[count.index].id\n  security_groups = [aws_security_group.efs_security_group.id]\n}\n<\/pre>\n
        <\/span><\/p>\n
        Yukar\u0131daki kod blo\u011fu \u00f6ncelikle bir VPC ve iki adet genel alt a\u011f olu\u015fturur. Ard\u0131ndan, EFS’ye NFS (port 2049) trafi\u011fine izin veren bir g\u00fcvenlik grubu tan\u0131mlar. Daha sonra aws_efs_file_system<\/span> kayna\u011f\u0131 ile \u015fifreli bir EFS dosya sistemi olu\u015fturulur. performance_mode<\/span> ve throughput_mode<\/span> parametreleri, uygulaman\u0131z\u0131n performans gereksinimlerine g\u00f6re ayarlanmal\u0131d\u0131r. Son olarak, her bir alt a\u011f i\u00e7in birer aws_efs_mount_target<\/span> olu\u015fturularak EFS’nin bu alt a\u011flar \u00fczerinden eri\u015filebilir olmas\u0131 sa\u011flan\u0131r. Bu, EFS’nin y\u00fcksek eri\u015filebilirlik sa\u011flamak i\u00e7in farkl\u0131 Availability Zone’larda bulunmas\u0131na olanak tan\u0131r.<\/p>\n
        Uzman \u0130pucu: \u00c7oklu Mount Target’lar, EFS dosya sisteminizi birden fazla Availability Zone’a yayarak y\u00fcksek eri\u015filebilirlik sa\u011flar. EKS k\u00fcmenizin d\u00fc\u011f\u00fcmleri hangi AZ’de olursa olsun EFS’ye ba\u011flanabilir.<\/span><\/p>\n
        EKS K\u00fcmesi Olu\u015fturma ve EFS CSI S\u00fcr\u00fcc\u00fcs\u00fc Kurulumu Nas\u0131l Ger\u00e7ekle\u015fir?<\/h3>\n
        EFS dosya sistemi haz\u0131r oldu\u011funda, bir EKS k\u00fcmesi olu\u015fturup EFS CSI (Container Storage Interface) s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc entegre etmemiz gerekiyor. CSI s\u00fcr\u00fcc\u00fcs\u00fc, Kubernetes’in EFS dosya sistemini PersistentVolume (PV) ve PersistentVolumeClaim (PVC) arac\u0131l\u0131\u011f\u0131yla kullanmas\u0131n\u0131 sa\u011flar. EKS’nin EFS’ye eri\u015febilmesi i\u00e7in gerekli IAM izinlerini ve OIDC sa\u011flay\u0131c\u0131s\u0131n\u0131 yap\u0131land\u0131rmak da bu ad\u0131m\u0131n \u00f6nemli bir par\u00e7as\u0131d\u0131r.<\/p>\n
        <\/p>\n
        \n# EKS Cluster IAM Role\nresource \"aws_iam_role\" \"eks_cluster_role\" {\n  name = \"eks-cluster-role\"\n  assume_role_policy = jsonencode({\n    Version = \"2012-10-17\"\n    Statement = [\n      {\n        Action = \"sts:AssumeRole\"\n        Effect = \"Allow\"\n        Principal = {\n          Service = \"eks.amazonaws.com\"\n        }\n      },\n    ]\n  })\n}\n\nresource \"aws_iam_role_policy_attachment\" \"eks_cluster_policy\" {\n  policy_arn = \"arn:aws:iam::aws:policy\/AmazonEKSClusterPolicy\"\n  role       = aws_iam_role.eks_cluster_role.name\n}\n\n# EKS Cluster\nresource \"aws_eks_cluster\" \"main\" {\n  name     = \"eks-efs-cluster\"\n  role_arn = aws_iam_role.eks_cluster_role.arn\n  vpc_config {\n    subnet_ids = aws_subnet.public.*.id\n  }\n  depends_on = [\n    aws_iam_role_policy_attachment.eks_cluster_policy\n  ]\n}\n\n# EKS OIDC Provider\nresource \"aws_iam_openid_connect_provider\" \"eks_oidc\" {\n  client_id_list  = [\"sts.amazonaws.com\"]\n  thumbprint_list = [data.tls_certificate.eks_cluster_thumbprint.certificates[0].sha1_fingerprint]\n  url             = aws_eks_cluster.main.identity[0].oidc[0].issuer\n}\n\ndata \"tls_certificate\" \"eks_cluster_thumbprint\" {\n  url = aws_eks_cluster.main.identity[0].oidc[0].issuer\n}\n\n# EFS CSI Driver IAM Role\nresource \"aws_iam_role\" \"efs_csi_driver_role\" {\n  name = \"efs-csi-driver-role\"\n  assume_role_policy = jsonencode({\n    Version = \"2012-10-17\"\n    Statement = [\n      {\n        Effect = \"Allow\"\n        Principal = {\n          Federated = aws_iam_openid_connect_provider.eks_oidc.arn\n        }\n        Action = \"sts:AssumeRoleWithWebIdentity\"\n        Condition = {\n          StringEquals = {\n            \"${replace(aws_iam_openid_connect_provider.eks_oidc.url, \"https:\/\/\", \"\")}:sub\" = \"system:serviceaccount:kube-system:efs-csi-controller-sa\"\n          }\n        }\n      },\n    ]\n  })\n}\n\nresource \"aws_iam_policy\" \"efs_csi_driver_policy\" {\n  name        = \"efs-csi-driver-policy\"\n  description = \"Policy for EFS CSI driver to manage EFS resources\"\n  policy = jsonencode({\n    Version = \"2012-10-17\"\n    Statement = [\n      {\n        Effect = \"Allow\"\n        Action = [\n          \"elasticfilesystem:DescribeMountTargets\",\n          \"elasticfilesystem:DescribeFileSystems\",\n          \"elasticfilesystem:DescribeAccessPoints\"\n        ]\n        Resource = \"*\"\n      },\n      {\n        Effect = \"Allow\"\n        Action = [\n          \"ec2:DescribeAvailabilityZones\"\n        ]\n        Resource = \"*\"\n      }\n    ]\n  })\n}\n\nresource \"aws_iam_role_policy_attachment\" \"efs_csi_driver_policy_attach\" {\n  policy_arn = aws_iam_policy.efs_csi_driver_policy.arn\n  role       = aws_iam_role.efs_csi_driver_role.name\n}\n\n# EKS Addon for EFS CSI Driver (recommended approach)\nresource \"aws_eks_addon\" \"efs_csi_driver\" {\n  cluster_name          = aws_eks_cluster.main.name\n  addon_name            = \"aws-efs-csi-driver\"\n  addon_version         = \"v1.5.0\" # En son s\u00fcr\u00fcm\u00fc kontrol edin\n  service_account_role_arn = aws_iam_role.efs_csi_driver_role.arn\n  resolve_conflicts     = \"OVERWRITE\"\n  depends_on = [\n    aws_iam_openid_connect_provider.eks_oidc\n  ]\n}\n<\/pre>\n
        <\/span><\/p>\n
        Bu kod blo\u011fu karma\u015f\u0131k g\u00f6r\u00fcnse de, ad\u0131m ad\u0131m incelendi\u011finde olduk\u00e7a mant\u0131kl\u0131d\u0131r. \u00d6ncelikle EKS k\u00fcmesi i\u00e7in bir IAM rol\u00fc ve gerekli politikay\u0131 tan\u0131mlar\u0131z. Ard\u0131ndan, aws_eks_cluster<\/span> kayna\u011f\u0131 ile k\u00fcmemizi olu\u015ftururuz. EKS k\u00fcmesi olu\u015fturulduktan sonra, Kubernetes hizmet hesaplar\u0131n\u0131n AWS kaynaklar\u0131na g\u00fcvenli bir \u015fekilde eri\u015fmesini sa\u011flayan bir OIDC (OpenID Connect) sa\u011flay\u0131c\u0131s\u0131 olu\u015fturulur. Bu, aws_iam_openid_connect_provider<\/span> kayna\u011f\u0131 ile yap\u0131l\u0131r ve data.tls_certificate<\/span> kullan\u0131larak k\u00fcme sertifikas\u0131n\u0131n parmak izi al\u0131n\u0131r.<\/p>\n
        Daha sonra, EFS CSI s\u00fcr\u00fcc\u00fcs\u00fc i\u00e7in \u00f6zel bir IAM rol\u00fc (efs_csi_driver_role<\/span>) olu\u015fturulur. Bu rol, EKS k\u00fcmesinin OIDC sa\u011flay\u0131c\u0131s\u0131 arac\u0131l\u0131\u011f\u0131yla kube-system<\/span> ad alan\u0131ndaki efs-csi-controller-sa<\/span> hizmet hesab\u0131na atan\u0131r. Bu, s\u00fcr\u00fcc\u00fcn\u00fcn EFS kaynaklar\u0131n\u0131 y\u00f6netmek i\u00e7in gereken AWS API \u00e7a\u011fr\u0131lar\u0131n\u0131 yapmas\u0131n\u0131 sa\u011flar. aws_iam_policy<\/span> ile EFS’ye eri\u015fim i\u00e7in gerekli izinleri i\u00e7eren bir politika tan\u0131mlan\u0131r. Son ve en kritik ad\u0131m ise, aws_eks_addon<\/span> kayna\u011f\u0131n\u0131 kullanarak EFS CSI s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc EKS k\u00fcmesine do\u011frudan bir eklenti olarak kurmakt\u0131r. Bu, AWS taraf\u0131ndan y\u00f6netilen ve \u00f6nerilen bir yakla\u015f\u0131md\u0131r ve kurulumu b\u00fcy\u00fck \u00f6l\u00e7\u00fcde basitle\u015ftirir. service_account_role_arn<\/span> parametresi ile daha \u00f6nce olu\u015fturdu\u011fumuz CSI s\u00fcr\u00fcc\u00fcs\u00fc IAM rol\u00fcn\u00fc buraya ba\u011flar\u0131z. addon_version<\/span> i\u00e7in her zaman en g\u00fcncel s\u00fcr\u00fcm\u00fc kullanmay\u0131 unutmay\u0131n.<\/p>\n
        Bu kapsaml\u0131 Terraform yap\u0131land\u0131rmas\u0131 sayesinde, EFS dosya sisteminiz ve EKS k\u00fcmeniz aras\u0131ndaki entegrasyonun temelini sa\u011flam bir \u015fekilde atm\u0131\u015f olursunuz. Art\u0131k Kubernetes uygulamalar\u0131n\u0131z, bu EFS dosya sistemini kal\u0131c\u0131 depolama olarak kullanmaya haz\u0131rd\u0131r.<\/p>\n
        Uygulamal\u0131 Senaryolar: EFS Kal\u0131c\u0131 Birim Talepleri (PVC) ve Kullan\u0131m\u0131<\/h2>\n
        EFS dosya sistemi ve EKS k\u00fcmesi ile EFS CSI s\u00fcr\u00fcc\u00fcs\u00fc ba\u015far\u0131yla yap\u0131land\u0131r\u0131ld\u0131ktan sonra, s\u0131ra Kubernetes uygulamalar\u0131n\u0131z\u0131n bu kal\u0131c\u0131 depolamay\u0131 kullanmas\u0131na geliyor. Bu b\u00f6l\u00fcmde, EFS tabanl\u0131 PersistentVolume (PV) ve PersistentVolumeClaim (PVC) olu\u015fturman\u0131n yan\u0131 s\u0131ra, bir uygulaman\u0131n (\u00f6rne\u011fin, bir web sunucusu veya WordPress gibi bir CMS) bu depolamay\u0131 nas\u0131l kullanaca\u011f\u0131n\u0131 g\u00f6steren ger\u00e7ek d\u00fcnya senaryolar\u0131na odaklanaca\u011f\u0131z. Terraform’un Kubernetes sa\u011flay\u0131c\u0131s\u0131 sayesinde, bu Kubernetes kaynaklar\u0131n\u0131 bile IaC prensipleriyle y\u00f6netebiliriz.<\/p>\n
        Stateful Uygulamalar \u0130\u00e7in Kal\u0131c\u0131 Depolama Nas\u0131l Tan\u0131mlan\u0131r?<\/h3>\n
        Kubernetes’te kal\u0131c\u0131 depolama kullanman\u0131n ilk ad\u0131m\u0131 bir StorageClass<\/span> tan\u0131mlamakt\u0131r. StorageClass<\/span>, Kubernetes k\u00fcmesindeki depolama birimlerini soyutlamak ve dinamik olarak depolama sa\u011flamak i\u00e7in kullan\u0131l\u0131r. EFS CSI s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc kurdu\u011fumuz i\u00e7in, EFS tabanl\u0131 depolama sa\u011flamak i\u00e7in \u00f6zel bir StorageClass<\/span> tan\u0131mlayabiliriz.<\/p>\n
        <\/p>\n
        \nresource \"kubernetes_storage_class\" \"efs_sc\" {\n  metadata {\n    name = \"efs-sc\"\n  }\n  provisioner          = \"efs.csi.aws.com\"\n  parameters = {\n    provisioningMode   = \"eXistingFileSysteM\" # Dinamik EFS olu\u015fturma yerine mevcut EFS'yi kullan\n    fileSystemId       = aws_efs_file_system.eks_efs.id\n    directoryPerms     = \"777\" # \u00d6rnek i\u00e7in, daha k\u0131s\u0131tlay\u0131c\u0131 olabilir\n    # accesspoint id'si belirtilirse, EFS Access Point kullan\u0131l\u0131r\n    # accessPointId      = aws_efs_access_point.example.id\n  }\n  reclaim_policy       = \"Retain\"\n  volume_binding_mode  = \"Immediate\"\n  mount_options        = [\"tls\"] # EFS'ye g\u00fcvenli ba\u011flant\u0131 i\u00e7in\n}\n<\/pre>\n
        <\/span><\/p>\n
        Yukar\u0131daki StorageClass<\/span>, efs.csi.aws.com<\/span> sa\u011flay\u0131c\u0131s\u0131n\u0131 kullanarak mevcut EFS dosya sistemimizi (fileSystemId<\/span>) i\u015faret eder. provisioningMode: eXistingFileSysteM<\/span> parametresi, Kubernetes’in mevcut bir EFS dosya sistemini kullanaca\u011f\u0131n\u0131 belirtir. reclaim_policy: Retain<\/span>, PVC silindi\u011finde EFS \u00fczerindeki verilerin korunmas\u0131n\u0131 sa\u011flar, bu da veri kayb\u0131n\u0131 \u00f6nlemek i\u00e7in \u00f6nemlidir. mount_options: [“tls”]<\/span> ise g\u00fcvenli ba\u011flant\u0131y\u0131 te\u015fvik eder.<\/p>\n
        Ard\u0131ndan, bir PersistentVolumeClaim (PVC)<\/span> olu\u015ftururuz. PVC, bir uygulaman\u0131n talep etti\u011fi depolama kaynaklar\u0131n\u0131 tan\u0131mlayan bir Kubernetes nesnesidir.<\/p>\n
        <\/p>\n
        \nresource \"kubernetes_persistent_volume_claim\" \"efs_pvc\" {\n  metadata {\n    name      = \"efs-claim\"\n    namespace = \"default\" # Uygulaman\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 namespace\n  }\n  spec {\n    access_modes       = [\"ReadWriteMany\"] # EFS i\u00e7in tipik\n    storage_class_name = kubernetes_storage_class.efs_sc.metadata[0].name\n    resources {\n      requests = {\n        storage = \"5Gi\" # Talep edilen depolama alan\u0131, EFS kapasiteye g\u00f6re otomatik \u00f6l\u00e7eklenir\n      }\n    }\n  }\n}\n<\/pre>\n
        <\/span><\/p>\n
        Bu PVC<\/span>, efs-sc<\/span> StorageClass<\/span>‘\u0131 kullanarak 5 GB depolama alan\u0131 talep eder. ReadWriteMany<\/span> eri\u015fim modu, EFS’nin anahtar \u00f6zelliklerinden biridir, \u00e7\u00fcnk\u00fc birden fazla pod’un ayn\u0131 anda depolama alan\u0131na okuma ve yazma yapmas\u0131na izin verir.<\/p>\n
        \u015eimdi, bu PVC<\/span>‘yi kullanan basit bir Nginx da\u011f\u0131t\u0131m\u0131n\u0131 inceleyelim:<\/p>\n
        <\/p>\n
        \nresource \"kubernetes_deployment\" \"nginx_deployment\" {\n  metadata {\n    name      = \"nginx-efs-app\"\n    namespace = \"default\"\n  }\n  spec {\n    replicas = 3\n    selector {\n      match_labels = {\n        app = \"nginx-efs\"\n      }\n    }\n    template {\n      metadata {\n        labels = {\n          app = \"nginx-efs\"\n        }\n      }\n      spec {\n        container {\n          name  = \"nginx\"\n          image = \"nginx:latest\"\n          port {\n            container_port = 80\n          }\n          volume_mount {\n            name       = \"efs-volume\"\n            mount_path = \"\/usr\/share\/nginx\/html\" # Nginx'in statik dosyalar\u0131n\u0131 koydu\u011fu yer\n          }\n        }\n        volume {\n          name = \"efs-volume\"\n          persistent_volume_claim {\n            claim_name = kubernetes_persistent_volume_claim.efs_pvc.metadata[0].name\n          }\n        }\n      }\n    }\n  }\n}\n<\/pre>\n
        <\/span><\/p>\n
        Bu Deployment<\/span>, \u00fc\u00e7 adet Nginx pod’u \u00e7al\u0131\u015ft\u0131r\u0131r ve her bir pod, efs-claim<\/span> adl\u0131 PVC<\/span>‘yi \/usr\/share\/nginx\/html<\/span> dizinine ba\u011flar. Bu sayede, Nginx sunucusunun servis etti\u011fi web dosyalar\u0131 EFS \u00fczerinde kal\u0131c\u0131 olarak saklan\u0131r ve t\u00fcm pod’lar taraf\u0131ndan payla\u015f\u0131l\u0131r. E\u011fer bir pod \u00f6l\u00fcrse veya yeniden planlan\u0131rsa, yeni pod ayn\u0131 EFS depolama alan\u0131na ba\u011flan\u0131r ve veriler sa\u011flam kal\u0131r. Bu yap\u0131land\u0131rma, birden fazla pod’un ayn\u0131 veriye e\u015fzamanl\u0131 olarak eri\u015fmesi gereken WordPress, Drupal gibi CMS uygulamalar\u0131 veya payla\u015f\u0131ml\u0131 konfig\u00fcrasyon dosyalar\u0131na ihtiya\u00e7 duyan mikro hizmetler i\u00e7in idealdir.<\/p>\n
        Vaka Analizi: E-ticaret Uygulamas\u0131n\u0131n Veri Tutarl\u0131l\u0131\u011f\u0131<\/h3>\n
        Bir e-ticaret uygulamas\u0131n\u0131n foto\u011fraf galerisi ve \u00fcr\u00fcn a\u00e7\u0131klamalar\u0131 gibi statik i\u00e7eriklerini depolad\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcnelim. Bu i\u00e7erikler s\u0131k\u00e7a g\u00fcncellenir ve uygulaman\u0131n birden fazla mikro hizmet pod’u taraf\u0131ndan eri\u015filmesi gerekir (\u00f6rne\u011fin, bir y\u00fckleyici servisi, bir g\u00f6sterim servisi). E\u011fer bu veriler EKS pod’lar\u0131n\u0131n ge\u00e7ici depolamas\u0131nda olsayd\u0131, pod’lar yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda i\u00e7erikler kaybolurdu. EFS’yi kal\u0131c\u0131 depolama olarak kullanarak, t\u00fcm bu i\u00e7erikler EFS’de merkezi olarak saklan\u0131r. Hem \u00fcr\u00fcn foto\u011fraflar\u0131n\u0131 y\u00fckleyen uploader-service<\/span> pod’lar\u0131 hem de web sitesinde bu foto\u011fraflar\u0131 g\u00f6steren frontend-service<\/span> pod’lar\u0131, ReadWriteMany<\/span> eri\u015fim modu sayesinde ayn\u0131 EFS alan\u0131na e\u015fzamanl\u0131 olarak eri\u015febilir. Bu, veri tutarl\u0131l\u0131\u011f\u0131n\u0131 sa\u011flar, operasyonel karma\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131r ve uygulama \u00f6l\u00e7eklenebilirli\u011fini art\u0131r\u0131r. B\u00f6ylece, kullan\u0131c\u0131lar her zaman en g\u00fcncel \u00fcr\u00fcn bilgilerini ve g\u00f6rsellerini g\u00f6r\u00fcrken, uygulama geli\u015ftiricileri depolama y\u00f6netimi yerine i\u015f mant\u0131\u011f\u0131na odaklanabilirler.<\/p>\n
        Performans ve G\u00fcvenlik \u0130pu\u00e7lar\u0131: EFS ve EKS Entegrasyonunda Nelere Dikkat Edilmeli?<\/h2>\n
        EFS ve EKS entegrasyonu, uygulamalar\u0131n\u0131za g\u00fc\u00e7l\u00fc bir kal\u0131c\u0131 depolama \u00e7\u00f6z\u00fcm\u00fc sunarken, performans\u0131 optimize etmek ve g\u00fcvenli\u011fi sa\u011flamak i\u00e7in dikkat edilmesi gereken baz\u0131 \u00f6nemli noktalar vard\u0131r. Do\u011fru yap\u0131land\u0131rmalarla hem maliyetleri d\u00fc\u015f\u00fcrebilir hem de veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve eri\u015filebilirli\u011fini art\u0131rabilirsiniz.<\/p>\n
        EFS Performans Modlar\u0131 ve \u00c7\u0131k\u0131\u015f Tipleri Nelerdir?<\/h3>\n
        EFS, uygulaman\u0131z\u0131n gereksinimlerine g\u00f6re farkl\u0131 performans modlar\u0131 ve \u00e7\u0131k\u0131\u015f (throughput) tipleri sunar. Bu se\u00e7enekleri anlamak, do\u011fru dengeyi kurman\u0131za yard\u0131mc\u0131 olacakt\u0131r:<\/p>\n
          \n
        • Performans Modlar\u0131:<\/strong>\n
            \n
          • General Purpose:<\/strong> \u00c7o\u011fu dosya tabanl\u0131 i\u015f y\u00fck\u00fc i\u00e7in tasarlanm\u0131\u015ft\u0131r ve d\u00fc\u015f\u00fck gecikme s\u00fcresi sa\u011flar. Web sunucular\u0131, CMS’ler, geli\u015ftirme ortamlar\u0131 gibi uygulamalar i\u00e7in idealdir.<\/li>\n
          • Max I\/O:<\/strong> \u00c7ok say\u0131da istemciden \u00e7ok y\u00fcksek oranda paralel i\u015flemler gerektiren i\u015f y\u00fckleri i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bu mod, daha y\u00fcksek gecikme s\u00fcresi pahas\u0131na daha fazla giri\u015f\/\u00e7\u0131k\u0131\u015f operasyonunu destekler. B\u00fcy\u00fck veri analizi, medya i\u015fleme gibi senaryolarda kullan\u0131labilir. Genellikle General Purpose<\/span> modu \u00e7o\u011fu EKS i\u015f y\u00fck\u00fc i\u00e7in yeterli olacakt\u0131r.<\/li>\n<\/ul>\n<\/li>\n
          • \u00c7\u0131k\u0131\u015f Tipleri:<\/strong>\n
              \n
            • Bursting Throughput (Varsay\u0131lan):<\/strong> Dosya sisteminin boyutuyla orant\u0131l\u0131 olarak \u00f6l\u00e7eklenen bir temel \u00e7\u0131k\u0131\u015f seviyesi sunar. Dosya sistemi b\u00fcy\u00fcd\u00fck\u00e7e temel \u00e7\u0131k\u0131\u015f seviyesi artar. Kredi sistemi kullanarak bu temel seviyenin \u00fczerinde k\u0131sa s\u00fcreli patlamalar yapabilir. \u00c7o\u011fu i\u015f y\u00fck\u00fc i\u00e7in maliyet etkin ve uygun bir se\u00e7enektir.<\/li>\n
            • Provisioned Throughput:<\/strong> Sabit ve belirli bir \u00e7\u0131k\u0131\u015f seviyesini garanti etmeniz gerekti\u011finde kullan\u0131l\u0131r. Bu, i\u015f y\u00fck\u00fcn\u00fcz\u00fcn burst kredilerine g\u00fcvenemeyecek kadar s\u00fcrekli y\u00fcksek bir \u00e7\u0131k\u0131\u015f gerektirmesi durumunda tercih edilir. Performans\u0131n tahmin edilebilirli\u011fi a\u00e7\u0131s\u0131ndan \u00f6nemlidir ancak maliyeti daha y\u00fcksektir.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
              Uzman \u0130pucu: Uygulaman\u0131z\u0131n I\/O profiline dikkatlice bak\u0131n. \u00c7o\u011fu durumda, General Purpose<\/span> performans modu ve Bursting Throughput<\/span> \u00e7\u0131k\u0131\u015f tipi yeterli olacakt\u0131r. A\u015f\u0131r\u0131 sa\u011flamadan ka\u00e7\u0131nmak maliyet tasarrufu sa\u011flar. CloudWatch metriklerini kullanarak EFS performans\u0131n\u0131 izleyerek do\u011fru karar\u0131 verebilirsiniz.<\/span><\/p>\n
              G\u00fcvenlik En \u0130yi Uygulamalar\u0131: EFS Eri\u015fimi Nas\u0131l S\u0131n\u0131rland\u0131r\u0131l\u0131r?<\/h3>\n
              EFS’ye eri\u015fimi g\u00fcvence alt\u0131na almak, EKS k\u00fcmenizdeki verilerinizi korumak i\u00e7in hayati \u00f6nem ta\u015f\u0131r:<\/p>\n
                \n
              • \u015eifreleme:<\/strong> EFS dosya sistemleri olu\u015ftururken verilerinizi \u015fifrelemeyi (encrypted = true<\/span>) her zaman etkinle\u015ftirin. Hem hareket halindeki (in-transit) hem de beklemedeki (at-rest) verilerin \u015fifrelenmesi i\u00e7in TLS ba\u011flant\u0131s\u0131 ve AWS Key Management Service (KMS) kullan\u0131labilir.<\/li>\n
              • A\u011f G\u00fcvenli\u011fi (Security Groups):<\/strong> EFS Mount Target’lar\u0131na atanan g\u00fcvenlik gruplar\u0131, hangi IP adreslerinden veya g\u00fcvenlik gruplar\u0131ndan (EKS worker node’lar\u0131n\u0131n g\u00fcvenlik grubu gibi) NFS portu (2049) \u00fczerinden eri\u015fime izin verilece\u011fini kontrol etmelidir. En az ayr\u0131cal\u0131k ilkesini uygulay\u0131n.<\/li>\n
              • IAM Yetkilendirmesi:<\/strong> EFS CSI s\u00fcr\u00fcc\u00fcs\u00fc i\u00e7in olu\u015fturdu\u011funuz IAM rol\u00fcn\u00fcn, yaln\u0131zca EFS kaynaklar\u0131n\u0131 y\u00f6netmek ve tan\u0131mlamak i\u00e7in kesinlikle gerekli olan minimum izinlere sahip oldu\u011fundan emin olun.<\/li>\n
              • EFS Eri\u015fim Noktalar\u0131 (Access Points):<\/strong> Eri\u015fim Noktalar\u0131, uygulama d\u00fczeyinde eri\u015fim denetimi sa\u011flamak i\u00e7in EFS’ye \u00f6zel giri\u015f noktalar\u0131d\u0131r. Her Eri\u015fim Noktas\u0131, belirli bir k\u00f6k dizini ve POSIX kullan\u0131c\u0131\/grup kimlikleri ile ili\u015fkilendirilebilir. Bu sayede, EKS pod’lar\u0131 belirli bir dizinden \u00f6teye ge\u00e7emez ve belirli bir kullan\u0131c\u0131 olarak i\u015flem yapar. Bu, \u00e7ok kirac\u0131l\u0131 (multi-tenant) veya s\u0131k\u0131 izin denetimi gerektiren ortamlar i\u00e7in m\u00fckemmel bir g\u00fcvenlik katman\u0131 sa\u011flar.<\/li>\n<\/ul>\n
                <\/p>\n
                \nresource \"aws_efs_access_point\" \"example\" {\n  file_system_id = aws_efs_file_system.eks_efs.id\n  posix_user {\n    gid = 1001\n    uid = 1001\n  }\n  root_directory {\n    path = \"\/app_data\" # Uygulaman\u0131n eri\u015fece\u011fi k\u00f6k dizin\n    creation_info {\n      owner_gid   = 1001\n      owner_uid   = 1001\n      permissions = \"0755\"\n    }\n  }\n  tags = {\n    Name = \"efs-access-point\"\n  }\n}\n<\/pre>\n
                <\/span><\/p>\n
                Yukar\u0131daki \u00f6rnekte, \/app_data<\/span> yolunu i\u015faret eden ve belirli bir POSIX kullan\u0131c\u0131s\u0131na (UID\/GID 1001) ait bir EFS Eri\u015fim Noktas\u0131 tan\u0131mlanm\u0131\u015ft\u0131r. Kubernetes StorageClass<\/span>‘\u0131n\u0131zda bu accessPointId<\/span>‘yi belirterek, pod’lar\u0131n\u0131z\u0131n yaln\u0131zca bu dizine bu yetkilerle eri\u015fmesini sa\u011flayabilirsiniz.<\/p>\n
                Y\u00fcksek Eri\u015filebilirlik ve Felaket Kurtarma Stratejileri<\/h3>\n
                EFS, do\u011fas\u0131 gere\u011fi y\u00fcksek eri\u015filebilirlik sunar (verileri birden fazla AZ’de \u00e7o\u011falt\u0131r). Ancak, felaket kurtarma ve daha fazla esneklik i\u00e7in ek stratejiler d\u00fc\u015f\u00fcnebilirsiniz:<\/p>\n
                  \n
                • \u00c7oklu AZ Mount Target’lar:<\/strong> Herhangi bir Availability Zone’da bir sorun olmas\u0131 durumunda EFS’ye kesintisiz eri\u015fim sa\u011flamak i\u00e7in birden fazla AZ’de Mount Target olu\u015fturdu\u011funuzdan emin olun (Terraform kodumuz bunu zaten yap\u0131yor).<\/li>\n
                • AWS Backup ile Yedekleme:<\/strong> EFS dosya sistemlerinizin d\u00fczenli olarak yedeklenmesini sa\u011flamak i\u00e7in AWS Backup’\u0131 kullan\u0131n. Bu, yanl\u0131\u015fl\u0131kla silme veya veri bozulmas\u0131 durumunda verilerinizi kurtarman\u0131z\u0131 sa\u011flar.<\/li>\n
                • Replikasyon (EFS Replication):<\/strong> EFS Replication, dosya sisteminizi ayn\u0131 AWS B\u00f6lgesi i\u00e7inde veya farkl\u0131 bir AWS B\u00f6lgesi’ne otomatik olarak kopyalayarak veri kayb\u0131 riskini daha da azalt\u0131r ve felaket kurtarma hedeflerine ula\u015fmaya yard\u0131mc\u0131 olur.<\/li>\n<\/ul>\n
                  Bu ipu\u00e7lar\u0131 ve en iyi uygulamalarla, EFS ve EKS entegrasyonunuz hem performansl\u0131 hem de g\u00fcvenli bir \u015fekilde \u00e7al\u0131\u015facakt\u0131r.<\/p>\n
                  S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h2>\n
                  EFS’yi EKS ile Terraform kullanarak entegre etme s\u00fcreci hakk\u0131nda s\u0131k\u00e7a kar\u015f\u0131la\u015f\u0131lan sorular ve yan\u0131tlar\u0131 a\u015fa\u011f\u0131dad\u0131r:<\/p>\n
                  EFS ve EBS aras\u0131ndaki temel fark nedir?<\/h3>\n
                  Cevap:<\/strong> Amazon EBS (Elastic Block Store), tek bir EC2 \u00f6rne\u011fine ba\u011fl\u0131 blok depolama birimidir ve ReadWriteOnce<\/span> eri\u015fim modunu destekler. Yani sadece bir pod taraf\u0131ndan kullan\u0131labilir. Amazon EFS ise birden fazla EC2 \u00f6rne\u011fi veya EKS pod’u taraf\u0131ndan ayn\u0131 anda eri\u015filebilen payla\u015f\u0131ml\u0131 bir dosya sistemidir ve ReadWriteMany<\/span> eri\u015fim modunu destekler. EFS, \u00f6zellikle birden fazla pod’un ayn\u0131 dosyalara e\u015fzamanl\u0131 olarak eri\u015fmesi gereken senaryolar i\u00e7in idealdir.<\/p>\n
                  EFS CSI s\u00fcr\u00fcc\u00fcs\u00fc neden gereklidir?<\/h3>\n
                  Cevap:<\/strong> EFS CSI (Container Storage Interface) s\u00fcr\u00fcc\u00fcs\u00fc, Kubernetes’in EFS dosya sistemini tan\u0131mas\u0131n\u0131 ve kullanmas\u0131n\u0131 sa\u011flayan bir arabirimdir. Bu s\u00fcr\u00fcc\u00fc olmadan, Kubernetes pod’lar\u0131n\u0131z EFS kaynaklar\u0131n\u0131 do\u011frudan talep edemez ve kullanamaz. S\u00fcr\u00fcc\u00fc, EKS k\u00fcmenizdeki PV ve PVC taleplerini EFS dosya sistemine ba\u011flamak i\u00e7in k\u00f6pr\u00fc g\u00f6revi g\u00f6r\u00fcr.<\/p>\n
                  Terraform ile EFS Access Point nas\u0131l olu\u015fturulur?<\/h3>\n
                  Cevap:<\/strong> EFS Access Point, EFS dosya sistemine \u00f6zel bir uygulama giri\u015f noktas\u0131d\u0131r. Terraform’da aws_efs_access_point<\/span> kayna\u011f\u0131n\u0131 kullanarak olu\u015fturulur. Bu kaynak, EFS dosya sistemi kimli\u011fini, bir k\u00f6k dizini (root directory) ve opsiyonel olarak POSIX kullan\u0131c\u0131\/grup kimliklerini belirtmenizi sa\u011flar. Daha sonra bu Access Point’i StorageClass<\/span> tan\u0131m\u0131n\u0131zda kullanabilirsiniz.<\/p>\n
                  EFS’de veri \u015fifrelemesi varsay\u0131lan olarak a\u00e7\u0131k m\u0131d\u0131r?<\/h3>\n
                  Cevap:<\/strong> Hay\u0131r, EFS’de veri \u015fifrelemesi varsay\u0131lan olarak a\u00e7\u0131k de\u011fildir. EFS dosya sistemi olu\u015ftururken encrypted = true<\/span> parametresini ayarlayarak \u015fifrelemeyi etkinle\u015ftirmeniz \u00f6nerilir. Bu, bekleyen verilerinizi AWS KMS anahtarlar\u0131yla \u015fifreler. Ayr\u0131ca, mount se\u00e7eneklerinde tls<\/span> kullanarak hareket halindeki verilerinizi de \u015fifreleyebilirsiniz.<\/p>\n
                  EFS performans\u0131n\u0131 nas\u0131l izleyebilirim?<\/h3>\n
                  Cevap:<\/strong> EFS performans\u0131n\u0131 Amazon CloudWatch metrikleri arac\u0131l\u0131\u011f\u0131yla izleyebilirsiniz. CloudWatch, dosya sistemi boyutunu, \u00e7\u0131k\u0131\u015f kullan\u0131m\u0131n\u0131 (throughput utilization), I\/O operasyonlar\u0131n\u0131 ve gecikme s\u00fcresi (latency) gibi kritik metrikleri sa\u011flar. Bu metrikleri d\u00fczenli olarak kontrol ederek performans sorunlar\u0131n\u0131 tespit edebilir ve EFS yap\u0131land\u0131rman\u0131z\u0131 (\u00f6rne\u011fin, performans modu veya \u00e7\u0131k\u0131\u015f tipi) optimize edebilirsiniz.<\/p>\n
                  Sonu\u00e7: Gelece\u011fe Y\u00f6nelik Ad\u0131mlar ve Entegrasyonun \u00d6nemi<\/h2>\n
                  Bu makale boyunca, Amazon EFS’yi Amazon EKS ile Terraform kullanarak entegre etmenin karma\u015f\u0131k olmayan ancak kritik s\u00fcrecini derinlemesine inceledik. Modern konteynerize uygulamalar\u0131n kal\u0131c\u0131 depolama ihtiya\u00e7lar\u0131n\u0131 kar\u015f\u0131lamak, uygulaman\u0131n sa\u011flaml\u0131\u011f\u0131 ve veri tutarl\u0131l\u0131\u011f\u0131 a\u00e7\u0131s\u0131ndan hayati \u00f6neme sahiptir. EFS’nin sundu\u011fu \u00f6l\u00e7eklenebilirlik, payla\u015f\u0131ml\u0131 eri\u015fim ve y\u00f6netilen dosya sistemi avantajlar\u0131, EKS ortam\u0131ndaki stateful uygulamalar i\u00e7in m\u00fckemmel bir temel olu\u015fturmaktad\u0131r. Terraform ile bu entegrasyonu otomatikle\u015ftirmek ise altyap\u0131 y\u00f6netimini basitle\u015ftirir, tutarl\u0131l\u0131\u011f\u0131 art\u0131r\u0131r ve DevOps ekipleri i\u00e7in paha bi\u00e7ilmez bir kolayl\u0131k sa\u011flar.<\/p>\n
                  EKS k\u00fcmelerinizin, y\u00fcksek oranda eri\u015filebilir ve dayan\u0131kl\u0131 bir dosya sistemine sahip olmas\u0131, \u00f6zellikle mikro hizmet tabanl\u0131 mimarilerde ortak veri havuzlar\u0131na ihtiya\u00e7 duyan uygulamalar i\u00e7in bir zorunluluktur. \u0130ster bir i\u00e7erik y\u00f6netim sistemi, ister bir e-ticaret platformu veya karma\u015f\u0131k bir veri analiz i\u015f y\u00fck\u00fc \u00e7al\u0131\u015ft\u0131r\u0131n, EFS ve EKS kombinasyonu, verilerinizi g\u00fcvenle ve performansla y\u00f6netmenize olanak tan\u0131r. Ayr\u0131ca, bu entegrasyonu Terraform gibi bir IaC arac\u0131yla y\u00f6netmek, altyap\u0131 de\u011fi\u015fikliklerinin versiyonlanabilir olmas\u0131n\u0131, g\u00f6zden ge\u00e7irilebilir olmas\u0131n\u0131 ve da\u011f\u0131t\u0131mlar\u0131n otomatikle\u015ftirilmesini sa\u011flar. Bu da geli\u015ftirme s\u00fcre\u00e7lerini h\u0131zland\u0131r\u0131r ve operasyonel hatalar\u0131 minimize eder.<\/p>\n
                  Gelecekte, bu entegrasyonu daha da geli\u015ftirmek i\u00e7in CI\/CD (S\u00fcrekli Entegrasyon\/S\u00fcrekli Da\u011f\u0131t\u0131m) boru hatlar\u0131na dahil etmek, otomatik testler eklemek ve g\u00f6zlem ara\u00e7lar\u0131yla (monitoring tools) performans\u0131 s\u00fcrekli izlemek gibi ad\u0131mlar atabilirsiniz. AWS EFS ve EKS entegrasyonu, bulut tabanl\u0131 uygulamalar\u0131n\u0131z\u0131n kalbinde yer alan verileri y\u00f6netmek i\u00e7in g\u00fc\u00e7l\u00fc, esnek ve g\u00fcvenilir bir yol sunarak, dijital d\u00f6n\u00fc\u015f\u00fcm yolculu\u011funuzda \u00f6nemli bir mihenk ta\u015f\u0131 olacakt\u0131r. Bu sayede, geli\u015ftiricileriniz kod yazmaya, uygulamalar\u0131n\u0131z da kesintisiz \u00e7al\u0131\u015fmaya devam edecektir.<\/p>\n","protected":false},"excerpt":{"rendered":"Amazon EFS ve EKS Entegrasyonu: Terraform ile Kal\u0131c\u0131 Depolama Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu…","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":[1],"tags":[],"class_list":{"0":"post-32505","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nAmazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?<\/title>\n<meta name=\"description\" content=\"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.\" \/>\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\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?\" \/>\n<meta property=\"og:description\" content=\"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-22T11:31:54+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=\"24 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?\",\"datePublished\":\"2025-10-22T11:31:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\"},\"wordCount\":4246,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\",\"name\":\"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-22T11:31:54+00:00\",\"description\":\"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?\"}]},{\"@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":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?","description":"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.","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\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/","og_locale":"tr_TR","og_type":"article","og_title":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?","og_description":"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.","og_url":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-22T11:31:54+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"24 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?","datePublished":"2025-10-22T11:31:54+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/"},"wordCount":4246,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/","url":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/","name":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-22T11:31:54+00:00","description":"Amazon EKS k\u00fcmeleriniz i\u00e7in kal\u0131c\u0131 depolama aray\u0131\u015f\u0131nda m\u0131s\u0131n\u0131z? Bu rehberde, Amazon EFS'yi EKS ile Terraform kullanarak nas\u0131l entegre edece\u011finizi ad\u0131m ad\u0131m ve uygulamal\u0131 \u00f6rneklerle ke\u015ffedin.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/amazon-eks-ve-kalici-depolama-ihtiyaci-nedir\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Amazon EKS ve Kal\u0131c\u0131 Depolama \u0130htiyac\u0131 Nedir?"}]},{"@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\/32505","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=32505"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32505\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=32505"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=32505"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=32505"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}