<\/div>\n

Merhaba,<\/p>\n

Bu i\u00e7eri\u011fimizde, bir Asp.NET Core API uygulamas\u0131n\u0131n Amazon Elastic Container Services(Amazon ECS)<\/em>‘a nas\u0131l deploy edilece\u011fini ve uygulamay\u0131 dockerize etmeyi detayl\u0131ca inceleyecek ve bu s\u00fcre\u00e7te Amazon a\u00e7\u0131s\u0131ndan ihtiya\u00e7 duyulacak olan servisleri ele al\u0131yor olaca\u011f\u0131z. O halde buyurun ba\u015flayal\u0131m…<\/p>\n

Amazon Elastic Container Services(Amazon ECS) Nedir?<\/h5>\n
Amazon Elastic Container Services<\/em>, Amazon Web Services(AWS) taraf\u0131ndan sunulan, Docker container’lar\u0131n\u0131n y\u00f6netilmesi ve \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131ndan sorumlu olan bir servistir. ECS, kullan\u0131c\u0131lara y\u00fcksek \u00f6l\u00e7eklenebilir ve g\u00fcvenli bir \u015fekilde uygulamalar\u0131 \u00e7al\u0131\u015ft\u0131rma ve y\u00f6netme i\u00e7in gerekli altyap\u0131y\u0131 sa\u011flamaktad\u0131r.<\/p>\n
ECS, bir docker container’\u0131n\u0131 \u00f6zelle\u015ftirilmi\u015f bir bilgisayar sunucusuna yerle\u015ftirir, ayr\u0131ca y\u00fcksek performans ve \u00f6l\u00e7eklenebilirlik sa\u011flamak i\u00e7in otomatik olarak kaynaklar\u0131n y\u00f6netimini \u00fcstlenir. Bu, uygulamalar\u0131n daha h\u0131zl\u0131 ba\u015flat\u0131lmas\u0131n\u0131 ve kullan\u0131c\u0131lar\u0131n ihtiya\u00e7lar\u0131na g\u00f6re esnek bir \u015fekilde \u00f6l\u00e7eklendirilmesini sa\u011flar.<\/p>\n
ECS, AWS’nin di\u011fer hizmetleriyle de entegre olabilir. Misal olarak; Amazon Elastic Load Balancer(ELB) ile birlikte kullan\u0131larak load balancing operasyonu ger\u00e7ekle\u015ftirilebilir yahut Amazon CloudWatch Logs ile birlikte kullan\u0131larak container log’lar\u0131 takip edilebilir.<\/p>\n
AWS Fargate Nedir?<\/h5>\n
AWS Fargate, AWS taraf\u0131ndan sunulan bir container servisidir. Amazon Elastic Container Service(Amazon ECS)<\/em> ve Amazon Elastic Kubernetes Service(Amazon EKS)<\/em> ile entegre edilebilmektedir. Fargate, container’lar\u0131n \u00e7al\u0131\u015ft\u0131rmas\u0131 i\u00e7in kullan\u0131c\u0131 a\u00e7\u0131s\u0131ndan gerekli olan sunucu y\u00f6netimini tamamen ortadan kald\u0131rmakta ve container’lar\u0131 do\u011frudan bir sanal \u00f6zel bulut(VPC) i\u00e7erisinde \u00e7al\u0131\u015ft\u0131rmaktad\u0131r.<\/p>\n
Fargate, kullan\u0131c\u0131lar\u0131n ECS veya EKS arac\u0131l\u0131\u011f\u0131yla y\u00f6netilen container servislerini kullan\u0131rken, sunucular\u0131 y\u00f6netme yahut \u00f6l\u00e7eklendirme gibi konularda endi\u015felenmelerine gerek duyulmaks\u0131z\u0131n uygulama container’lar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmalar\u0131na olanak sa\u011flamakta ve t\u00fcm bunlar\u0131n yan\u0131nda otomatik bir \u015fekilde \u00f6l\u00e7eklendirme(automatic scaling), load balancing, service discovery ve g\u00fcvenlik(security) gibi pek \u00e7ok \u00f6zellik sunmaktad\u0131r.<\/p>\n
Ayr\u0131ca Fargate, kullan\u0131c\u0131lar\u0131n uygulamalar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmak i\u00e7in sadece gerekti\u011fi kadar kaynak kullanmalar\u0131na olanak tan\u0131yan bir kaynak y\u00f6netimi modeli sunmakta ve b\u00f6ylece uygulama performans\u0131n\u0131 art\u0131rmak i\u00e7in gereksiz yere kaynaklar\u0131n bo\u015fa harcanmas\u0131 durumunu ortadan kald\u0131rmaktad\u0131r.<\/p>\n
Amazon ECS \u0130le \u0130lgili Bilinmesi Gereken Baz\u0131 Terminolojiler<\/h5>\n\n\n\n\n\n\n
Task<\/th>\n Service<\/th>\n Cluster<\/th>\n<\/tr>\n<\/thead>\n
Bir veya birden fazla container i\u00e7erebilen uygulama \u00e7al\u0131\u015ft\u0131rma bile\u015fenidir. Task, \u00e7al\u0131\u015ft\u0131raca\u011f\u0131 container’a dair image, port, protokol vs. gibi bilgileri bar\u0131nd\u0131rmakta ve bu yap\u0131land\u0131rmalar do\u011frultusunda container’\u0131 aya\u011fa kald\u0131rmaktad\u0131r.<\/td>\n Birden fazla task instance’\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmak i\u00e7in kullan\u0131lan yap\u0131land\u0131rmad\u0131r. Task’lar\u0131n i\u015flemlerini koordine ederek y\u00fck dengelemesi, y\u00fcksek kullan\u0131labilirlik, \u00f6l\u00e7eklenebilirlik ve performans sa\u011flar. Bir task ba\u015far\u0131s\u0131z oldu\u011fu taktirde di\u011fer task’lar\u0131n hizmet sa\u011flamaya devam etmesinden, ayr\u0131ca otomatik olarak yeni task’lar\u0131n olu\u015fturulup \u00f6l\u00e7eklendirilmesinden sorumludur. B\u00f6ylece kaynak y\u00f6netimini olduk\u00e7a kolayla\u015ft\u0131rmaktad\u0131r. Ayr\u0131ca container’\u0131n s\u00fcr\u00fcm kontrol\u00fc servis sayesinde sa\u011flanmaktad\u0131r.<\/td>\n Bir grup kaynaklar\u0131n(instance’lar\u0131n) k\u00fcmesidir. Cluster, container’lar\u0131n tek bir mant\u0131ksal birimde, y\u00fcksek performansl\u0131 ve \u00f6l\u00e7eklenebilir bir \u015fekilde y\u00f6netilmesine ve koordine edilmesine olanak tan\u0131r.<\/td>\n<\/tr>\n
$\"Asp.NET$ <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\u0130\u00e7erik Rotam\u0131z Nas\u0131l Olacak?<\/h5>\n
Bu i\u00e7er\u011fimizde temelde bir Asp.NET Core API uygulamas\u0131 i\u00e7in olu\u015fturulan docker image’inin Amazon Elastic Container Registry(ECR)<\/em>‘e y\u00fcklenmesini ve AWS ECS’de nas\u0131l bar\u0131nd\u0131r\u0131labilece\u011fini ele al\u0131yor olaca\u011f\u0131z. Bu nedenle, \u00f6ncelikle .NET API uygulamas\u0131n\u0131 olu\u015fturacak ve local’deki MongoDB \u00f6rne\u011fiyle gerekli test i\u015flemlerini ger\u00e7ekle\u015ftirece\u011fiz. Akabinde bu uygulama i\u00e7in bir Dockerfile dosyas\u0131 haz\u0131rlayacak ve olu\u015fturdu\u011fumuz docker image’ini Amazon ECR’ye y\u00fckleyece\u011fiz. ECR’de tan\u0131mlanm\u0131\u015f olan docker image’ini \u00e7ekmek(pull) ve \u00e7al\u0131\u015ft\u0131rmak(run) i\u00e7in g\u00f6rev tan\u0131mlar\u0131(task definition) olan bir ECS Cluster olu\u015fturaca\u011f\u0131z.<\/p>\n
ESC’nin temel mant\u0131\u011f\u0131, her ECS Cluster’\u0131n “n”<\/em> task definition’a sahip olaca\u011f\u0131d\u0131r ve buradaki her bir task definition, uygulama deploy yakla\u015f\u0131m\u0131m\u0131za ba\u011fl\u0131 olarak birden fazla docker container’\u0131 i\u00e7erebilir. Task definition olu\u015fturulduktan sonra bir servis bu g\u00f6rev tan\u0131m\u0131na dayal\u0131 olarak olu\u015fturulabilmektedir. Haliyle biz, bir cluster olu\u015fturacak ve daha sonra biri MongoDB image’ini di\u011feri de ECR’den .NET uygulamas\u0131n\u0131 \u00e7eken iki task tan\u0131m\u0131nda bulunacak ve sonras\u0131nda da bu task’lar\u0131 \u00e7al\u0131\u015ft\u0131racak olan servislerin olu\u015fturulmas\u0131n\u0131 ger\u00e7ekle\u015ftirip, uygulamay\u0131 deploy etmi\u015f olaca\u011f\u0131z.<\/p>\n
\u015eimdi gelin t\u00fcm bu s\u00fcreci hep beraber tecr\u00fcbe edelim…<\/p>\n
\u00d6rnek \u00c7al\u0131\u015fma<\/h5>\n
\u015eimdi gelin i\u00e7eri\u011fimizde hedefledi\u011fimiz konular\u0131 ad\u0131m ad\u0131m \u00f6rneklendirmeye ba\u015flayal\u0131m.<\/p>\n
\n
1. Ad\u0131m (API Olu\u015fturma ve MongoDB Entegrasyonunu Sa\u011flama)<\/span><\/em>
\n\u00d6rneklendirmeyi ger\u00e7ekle\u015ftirebilmek i\u00e7in bir Asp.NET Core Web API uygulamas\u0131 olu\u015fturunuz ve ard\u0131ndan MongoDB \u00e7al\u0131\u015fmalar\u0131n\u0131 y\u00fcr\u00fctebilmek i\u00e7in MongoDB.Driver<\/a> k\u00fct\u00fcphanesini kurunuz. Devam\u0131nda ise ‘BooksController’ isminde bir controller s\u0131n\u0131f\u0131 olu\u015fturunuz ve a\u015fa\u011f\u0131daki entity e\u015fli\u011finde controller’\u0131n i\u00e7eri\u011fini tasarlay\u0131n\u0131z.<\/p>\n
\n
\r\n public class Book\r\n {\r\n [BsonId]\r\n [BsonRepresentation(BsonType.ObjectId)]\r\n public string? Id { get; set; }\r\n public string? Name { get; set; }\r\n public string? Author { get; set; }\r\n public string? PublishedYear { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n
\n
\r\n [Route("api\/[controller]")]\r\n [ApiController]\r\n public class BooksController : ControllerBase\r\n {\r\n readonly IMongoCollection<Book> _bookCollection;\r\n public BooksController(IConfiguration configuration)\r\n {\r\n MongoClient mongoClient = new(configuration["MongoDBConfigurations:ConnectionString"]);\r\n IMongoDatabase database = mongoClient.GetDatabase(configuration["MongoDBConfigurations:Database"]);\r\n _bookCollection = database.GetCollection<Book>(configuration["MongoDBConfigurations:BookCollection"]);\r\n }\r\n\r\n [HttpGet]\r\n public async Task<IActionResult> Get()\r\n => Ok(await _bookCollection.Find(b => true)\r\n .ToListAsync());\r\n\r\n [HttpPost]\r\n public async Task<IActionResult> Post(Book book)\r\n {\r\n await _bookCollection.InsertOneAsync(book);\r\n return Ok(book.Id);\r\n }\r\n }\r\n<\/pre>\n<\/div>\n
Evet, g\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere local olarak yap\u0131land\u0131r\u0131lm\u0131\u015f, MongoDB altyap\u0131s\u0131nda, veritaban\u0131na kitap ekleyen ve t\u00fcm kitaplar\u0131 sorgulayarak elde etmemizi sa\u011flayan bir API kurgulanm\u0131\u015f bulunmaktad\u0131r. Tabi burada isterseniz, best practices a\u00e7\u0131s\u0131ndan controller’da ki business logic’i farkl\u0131 bir servise al\u0131p oradan y\u00fcr\u00fctmeyi ger\u00e7ekle\u015ftirebilir ve Options Pattern<\/a>‘\u0131 kullanarak konfig\u00fcrasyonlar\u0131 y\u00fcr\u00fctebilirsiniz. Bizler i\u00e7eri\u011fi \u00e7ok fazla \u015fi\u015firmemek i\u00e7in bu sadelik seviyesinde seyre devam edece\u011fiz.<\/p>\n
Ayr\u0131ca konfig\u00fcrasyonel de\u011ferleri ‘appsettings.json’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi tutabilirsiniz:<\/p>\n
\n
\r\n{\r\n "Logging": {\r\n "LogLevel": {\r\n "Default": "Information",\r\n "Microsoft.AspNetCore": "Warning"\r\n }\r\n },\r\n "AllowedHosts": "*",\r\n "MongoDBConfigurations": {\r\n "ConnectionString": "mongodb:\/\/localhost:27017",\r\n "Database": "AmazonESCDB",\r\n "BookCollection": "Books"\r\n }\r\n}\r\n<\/pre>\n<\/div>\n<\/li>\n
2. Ad\u0131m (Uygulamay\u0131 Dockerize Etme)<\/span><\/em>
\n\u015eimdi olu\u015fturdu\u011fumuz uygulamay\u0131 dockerize edebilmek i\u00e7in \u00f6ncelikle Dockerfile’\u0131 olu\u015ftural\u0131m. Bunun i\u00e7in uygulaman\u0131n ana dizinine(root) ‘Dockerfile’ isminde bir dosya ekleyiniz ve i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi doldurunuz.<\/p>\n
\n
\r\nFROM mcr.microsoft.com\/dotnet\/sdk:7.0 AS build\r\nWORKDIR \/src\r\n\r\nCOPY . .\r\nRUN dotnet restore\r\n\r\nCOPY . .\r\nRUN dotnet publish -c release -o \/app\/publish\r\n\r\nFROM mcr.microsoft.com\/dotnet\/aspnet:7.0\r\nWORKDIR \/app\/publish\r\nCOPY --from=build \/app\/publish .\/\r\n\r\nEXPOSE 80\r\n\r\nENTRYPOINT ["dotnet", "Amazon.ESC.AspNETCore.WebAPI.Deploy.Example.API.dll"]\r\n<\/pre>\n<\/div>\n
Ve ard\u0131ndan uygulaman\u0131n ana dizinine odaklanm\u0131\u015f bir powershell ya da cmd a\u00e7arak a\u015fa\u011f\u0131daki talimat e\u015fli\u011finde bu Dockerfile \u00fczerinden bir docker image olu\u015fturunuz.<\/p>\n
docker build -t amazon-esc-aspnetcore-webapi-deploy-example-api .<\/strong><\/div>\n $\"Asp.NET$ <\/a>Bu talimat neticesinde Dockerfile i\u00e7erisindeki talimatlar\u0131n s\u0131ras\u0131yla i\u015flendi\u011fini ve ilgili image’\u0131n a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi Docker Desktop \u00fczerinden de g\u00f6zlemlenebildi\u011fi \u015fekliyle ba\u015far\u0131yla olu\u015fturuldu\u011funu g\u00f6r\u00fcyoruz. $\"Asp.NET$ <\/a>Art\u0131k olu\u015fturdu\u011fumuz uygulaman\u0131n local’de image’\u0131n\u0131 ald\u0131\u011f\u0131m\u0131za g\u00f6re bunu Amazon ECS’nin de eri\u015febilece\u011fi \u015fekilde internete g\u00f6ndermemiz gerekmektedir. Bunun i\u00e7in ilgili image’\u0131 Amazon ECR’ye yani Amazon Elastic Container Registry<\/em>‘e g\u00f6nderiyor olaca\u011f\u0131z.\n<\/li>\n
3. Ad\u0131m (Image’i Amazon ECR’ye Push’lama)<\/span><\/em>
\nYukar\u0131daki ad\u0131mda bahsedildi\u011fi gibi taraf\u0131m\u0131zca olu\u015fturulan docker image’lerine Amazon ECS’den eri\u015fim g\u00f6sterilebilmesi i\u00e7in g\u00fcvenli bir \u015fekilde depolanmas\u0131n\u0131 ve da\u011f\u0131t\u0131lmas\u0131n\u0131 sa\u011flayan bir havuza g\u00f6ndermemiz gerekmektedir. Bunun i\u00e7in y\u00fcksek performansl\u0131 bar\u0131nd\u0131rma hizmeti sunan Amazon ECR’yi kullanaca\u011f\u0131z. Tabi sizler isterseniz Amazon ECR’ye alternatif olarak Docker Hub’\u0131 da kullanabilirsiniz.<\/p>\n
Bunun i\u00e7in \u00f6ncelikle AWS Console \u00fczerinden ECR servisini a\u00e7\u0131n\u0131z ve a\u015fa\u011f\u0131daki gibi bir repository olu\u015fturunuz. $\"Asp.NET$ <\/a> $\"Asp.NET$ <\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bizler ‘amazon-ecs-aspnetcore-webapi-deploy-example’ ad\u0131nda bir repository olu\u015fturmu\u015f bulunuyoruz. Bu i\u015flemin ard\u0131ndan olu\u015fturulan docker image’\u0131 Amazon ECR’de olu\u015fturulan bu repository’e g\u00f6ndermek i\u00e7in Dockerfile’\u0131n bulundu\u011fu dizini tekrardan powershell yahut cmd ile a\u00e7\u0131n\u0131z ve a\u015fa\u011f\u0131daki talimatlar\u0131 veriniz.<\/p>\n
\n
\r\naws ecr get-login-password | docker login --username AWS --password-stdin 567921601443.dkr.ecr.ap-south-1.amazonaws.com\r\ndocker tag amazon-esc-aspnetcore-webapi-deploy-example-api 567921601443.dkr.ecr.ap-south-1.amazonaws.com\/amazon-esc-aspnetcore-webapi-deploy-example\r\ndocker push 567921601443.dkr.ecr.ap-south-1.amazonaws.com\/amazon-esc-aspnetcore-webapi-deploy-example\r\n<\/pre>\n<\/div>\n
E\u011fer ki, login s\u00fcrecinde problem ya\u015f\u0131yorsan\u0131z a\u015fa\u011f\u0131daki talimat\u0131 deneyiniz.<\/p>\n
\n
powershell 'docker login --username AWS -p $(aws ecr get-login-password --region <<region>> ) ****.dkr.ecr.<<region>>.amazonaws.com'<\/pre>\n<\/div>\n
<\/em><\/p><\/blockquote>\n
$\"Asp.NET$ <\/a>Bu i\u015flem neticesinde AWS Console’dan ECR servisine gidip g\u00f6nderilen image’i a\u015fa\u011f\u0131daki gibi do\u011frulaman\u0131zda fayda vard\u0131r. $\"Asp.NET$ <\/a>\n<\/li>\n
4. Ad\u0131m (Docker Image’i Local’de Test Etme)<\/span><\/em>
\n\u015eimdi uygulamam\u0131z\u0131n image’ini AWS ECR’ye g\u00f6nderdi\u011fimize g\u00f6re, ufaktan local’de bir test ger\u00e7ekle\u015ftirmekte fayda vard\u0131r. Bunun i\u00e7in a\u015fa\u011f\u0131daki docker talimat\u0131n\u0131 vermeniz yeterli olacakt\u0131r;<\/p>\n
\n
\r\naws ecr get-login-password | docker login --username AWS --password-stdin 567921601443.dkr.ecr.ap-south-1.amazonaws.com\r\ndocker run -p 8080:80 -e MongoDBConfigurations:ConnectionString='mongodb:\/\/host.docker.internal:27017' -e ASPNETCORE_ENVIRONMENT=Development amazon-esc-aspnetcore-webapi-deploy-example-api\r\n<\/pre>\n<\/div>\n
Burada ilk olarak yine docker’da oturum a\u00e7\u0131yor ard\u0131ndan ‘8080’ portunda olu\u015fturdu\u011fumuz image’dan bir container aya\u011fa kald\u0131r\u0131yoruz. Ayr\u0131ca container’da kullan\u0131lacak olan MongoDB connection string de\u011ferini environment olarak verdi\u011fimize dikkatinizi \u00e7ekerim. $\"Asp.NET$ <\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere ilgili talimat \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131 taktirde uygulama aya\u011fa kalkmakta ve http:\/\/localhost:8080\/api\/books<\/a> adresine yap\u0131lan istek neticesinde a\u015fa\u011f\u0131daki g\u00f6r\u00fcnt\u00fcde oldu\u011fu gibi kay\u0131tl\u0131 kitaplar taraf\u0131m\u0131za d\u00f6nd\u00fcr\u00fclmektedir. $\"Asp.NET$ <\/a>Evet, uygulamam\u0131z\u0131n gayet sa\u011fl\u0131kl\u0131 bir \u015fekilde \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6zlemlemi\u015f olduk. \u015eimdi s\u0131ra uygulamay\u0131 Amazon ECS’ye deploy etmeye geldi.\n<\/li>\n
5. Ad\u0131m (Amazon ECS’ye Cluster’\u0131n\u0131n Olu\u015fturulmas\u0131)<\/span><\/em>
\n\u0130lk olarak Amazon ECS’yi kullanabilmek, MongoDB ve dotnet uygulamalar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rabilmek i\u00e7in bir ECS Cluster olu\u015fturulmas\u0131 gerekmektedir. Bunun i\u00e7in a\u015fa\u011f\u0131daki g\u00f6rselde oldu\u011fu gibi AWS Console \u00fczerinden ECS servisine aratarak gidiniz. $\"Asp.NET$ <\/a>Ard\u0131ndan a\u015fa\u011f\u0131daki gibi cluster’\u0131 olu\u015fturunuz. $\"Asp.NET$ <\/a> $\"Asp.NET$ <\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere ‘amazon-esc-aspnetcore-webapi-deploy-example-api-cluster’ isminde bir cluster olu\u015fturulmu\u015ftur.<\/p>\n
\u015eimdi bu i\u015flemi yapt\u0131ktan sonra olu\u015fturulan cluster’a servis ve task(g\u00f6rev) ekleme i\u015flemlerini ger\u00e7ekle\u015ftirmemiz gerekmektedir.\n<\/li>\n
6. Ad\u0131m (MongoDB Task’\u0131 Olu\u015fturma ve AWS ECS Cluster’\u0131yla \u0130li\u015fkilendirme)<\/span><\/em>
\n $\"Asp.NET$ <\/a>\u00d6ncelikle cluster’da biri servis g\u00f6revi g\u00f6recek di\u011feri ise MongoDB’yi y\u00fcr\u00fctecek task tan\u0131m\u0131nda bulunmam\u0131z gerekmektedir. Bunun i\u00e7in ECS servisinin men\u00fcs\u00fcnden yandaki gibi ‘Task definitions’ sayfas\u0131na geliniz ve a\u00e7\u0131lan sayfada ‘Create new task definition’ butonuna t\u0131klay\u0131n\u0131z.<\/p>\n
\u0130lk olarak a\u015fa\u011f\u0131daki gibi MongoDB task’\u0131n\u0131 yap\u0131land\u0131ral\u0131m. $\"Asp.NET$ <\/a>Bu yap\u0131land\u0131rmada container ve image ad\u0131yla birlikte ba\u011flant\u0131 noktalar\u0131 \u00f6nem arz etmektedir. Image ad\u0131n\u0131n ‘mongo’ olmas\u0131na dikkat ediniz. Bu \u015fekilde yap\u0131land\u0131rma neticesinde ilgili image’\u0131 Docker Hub’dan \u00e7ekecektir.<\/p>\n
\u015eimdi task tan\u0131mlama s\u00fcrecinin bir sonraki ad\u0131m\u0131nda ise task’\u0131n boyutunu ve \u00e7al\u0131\u015faca\u011f\u0131 i\u015fletim sistemini belirleyiniz. $\"Asp.NET$ <\/a>G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bizim \u00e7al\u0131\u015fmam\u0131zda y\u00fcksek trafik s\u00f6z konusu olmayaca\u011f\u0131 i\u00e7in minimum de\u011ferlerde CPU ve RAM de\u011ferlerini se\u00e7mi\u015f bulunuyoruz. Tabi ki de sizler yaz\u0131l\u0131m\u0131n\u0131z\u0131n i\u015flem hacmine g\u00f6re buradaki de\u011ferleri belirlemeniz gerekti\u011finin fark\u0131ndas\u0131n\u0131z.<\/p>\n
Velhas\u0131l, bu temel yap\u0131land\u0131rmalar e\u015fli\u011finde MongoDB task’\u0131n\u0131 olu\u015fturunuz ve ‘Task definitions’ sayfas\u0131nda a\u015fa\u011f\u0131daki gibi listelendi\u011fini g\u00f6rerek, olu\u015fturuldu\u011fundan emin olunuz. $\"Asp.NET$ <\/a>Evet, MongoDB task’\u0131 olu\u015fturuldu\u011funa g\u00f6re art\u0131k cluster ile ili\u015fkilendirebiliriz. Bunun i\u00e7in ‘Clusters’ sayfas\u0131ndan ilgili cluster’a t\u0131klayarak, a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi sayfan\u0131n hemen a\u015fa\u011f\u0131s\u0131ndaki ‘Tasks’ sekmesine geliniz ve ‘Run new task’ butonuna t\u0131klay\u0131n\u0131z. $\"Asp.NET$ <\/a>A\u00e7\u0131lan sayfada cluster ile a\u015fa\u011f\u0131daki yap\u0131land\u0131rmalar e\u015fli\u011finde ilgili task’\u0131 ili\u015fkilendiriniz. $\"Asp.NET$ <\/a>Bu i\u015flemin ard\u0131ndan cluster \u00fczerinden ‘Tasks’ sekmesine tekrar gelirsek e\u011fer olu\u015fturulan task’\u0131n cluster ile ili\u015fkilendirildi\u011fini ve biraz bekleyince \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6zlemleyebiliriz. $\"Asp.NET$ <\/a>\n<\/li>\n
7. Ad\u0131m (AWS ECS Cluster’\u0131na MongoDB Servisi Ekleme)<\/span><\/em>
\n\u015eimdi de cluster’a MongoDB servisi eklememiz gerekmektedir. Bunun i\u00e7in ilgili cluster \u00fczerinden a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi ‘Services’ sekmesine geliniz ve ‘Create’ butonuna t\u0131klay\u0131n\u0131z. $\"Asp.NET$ <\/a>Devam\u0131nda ise a\u00e7\u0131lan sayfada a\u015fa\u011f\u0131daki yap\u0131land\u0131rmalar e\u015fli\u011finde servisi olu\u015fturunuz. $\"Asp.NET$ <\/a>Ayr\u0131ca bu servise bir load balancer ba\u011flayarak endpoint olu\u015fturabilmek i\u00e7in ayn\u0131 sayfada hafif a\u015fa\u011f\u0131da bulunan ‘Load balancing’ k\u0131sm\u0131nda da a\u015fa\u011f\u0131daki yap\u0131land\u0131rmalar\u0131 ger\u00e7ekle\u015ftiriniz. $\"Asp.NET$ <\/a>Bu i\u015flemden sonra ‘Services’ sekmesinde olu\u015fturulan servisi g\u00f6zlemleyerek, emin olunuz. $\"Asp.NET$ <\/a>\n<\/li>\n
8. Ad\u0131m (27017 Portuna Trafik \u0130zninin Verilmesi)<\/span><\/em>
\n\u015eimdi 27017 portuna trafik izninin verilmesini ger\u00e7ekle\u015ftirelim. Bunun i\u00e7in ilgili cluster i\u00e7erisinde a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi servise t\u0131klay\u0131n\u0131z, a\u00e7\u0131lan sayfada ‘Networking’ sekmesi \u00fczerinden ‘Security groups’ ba\u011flant\u0131s\u0131na t\u0131klayarak VPC yap\u0131land\u0131rmalar\u0131na geliniz. $\"Asp.NET$ <\/a>Ard\u0131ndan a\u015fa\u011f\u0131daki ‘Inbound rules’ listesinden ilk rule’u se\u00e7erek sa\u011f taraftaki ‘Edit inbound rules’ butonuna t\u0131klay\u0131n\u0131z. $\"Asp.NET$ <\/a>Ve a\u00e7\u0131lan sayfada a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rmay\u0131 ger\u00e7ekle\u015ftiriniz. $\"Asp.NET$ <\/a>\n<\/li>\n
9. Ad\u0131m (Uygulamay\u0131 ECS’ye Deploy Etme)<\/span><\/em>
\nVe son olarak uygulamay\u0131 ECS’ye deploy edelim. Bunun i\u00e7in ilk olarak MongoDB task’\u0131n\u0131n IP’sini almam\u0131z gerekmektedir. Bunu da a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi edinebilirsiniz. $\"Asp.NET$ <\/a>\u015eimdi ‘Task definitions’dan a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcndeki gibi uygulama ayarlar\u0131n\u0131 bar\u0131nd\u0131racak olan bir task olu\u015fturunuz. $\"Asp.NET$ <\/a> $\"Asp.NET$ <\/a>Burada dikkat ederseniz ‘book-manager-task’\u0131n\u0131n ba\u011flant\u0131 sa\u011flayaca\u011f\u0131 MondoDB’nin connection string’i environment olarak verilmekte ve biraz \u00f6nce edindi\u011fimiz IP bu noktada kullan\u0131lmaktad\u0131r. Ayr\u0131ca container image’\u0131 olarak ECR’ye g\u00f6ndermi\u015f oldu\u011fumuz repository’nin kullan\u0131ld\u0131\u011f\u0131na dikkatinizi \u00e7ekerim. Velhas\u0131l kelam, olu\u015fturulan bu task’\u0131 cluster’da aya\u011fa kald\u0131r\u0131n\u0131z. $\"Asp.NET$ <\/a>Malumunuz az bekledi\u011finiz taktirde task’\u0131n ‘Running’ stat\u00fcs\u00fcne geldi\u011fini g\u00f6receksiniz.<\/p>\n
Ayn\u0131 \u015fekilde cluster \u00fczerinden uygulama i\u00e7in a\u015fa\u011f\u0131daki gibi service olu\u015fturunuz. $\"Asp.NET$ <\/a>A\u015fa\u011f\u0131daki gibi load balancer tan\u0131mlamas\u0131n\u0131 da ger\u00e7ekle\u015ftiriniz. $\"Asp.NET$ <\/a>Ve b\u00f6ylece her iki servisimiz de hizmete haz\u0131r… $\"Asp.NET$ <\/a>\n<\/li>\n
10. Ad\u0131m (Test Etme)<\/span><\/em>
\nYukar\u0131daki ad\u0131mlar do\u011fru bir \u015fekilde uyguland\u0131\u011f\u0131 taktirde API’\u0131n ECS’ye ba\u015far\u0131l\u0131 bir \u015fekilde deploy edildi\u011fini varsayabiliriz. Tabi ki de bunu do\u011frulayabilmek i\u00e7in son olarak test yapmak en makuludur. Testi ger\u00e7ekle\u015ftirebilmek i\u00e7in ise uygulama servisi \u00fczerinden endpoint’e eri\u015fmemiz gerekmektedir. Bunun i\u00e7in de a\u015fa\u011f\u0131daki gibi ‘Networking’ sekmesinden ‘DNS names’ alt\u0131ndaki ba\u011flant\u0131 \u00fczerinden uygulaman\u0131n endpoint’ine eri\u015febilirsiniz. $\"Asp.NET$ <\/a>Uygulamam\u0131zda swagger aktif oldu\u011fu i\u00e7in yukar\u0131daki g\u00f6rselde oldu\u011fu gibi endpoint sonuna ‘\/swagger’ yaz\u0131p request’te bulundu\u011fumuz taktirde swagger aray\u00fcz\u00fc taraf\u0131ndan kar\u015f\u0131lan\u0131yorsan\u0131z her \u015fey yolundad\u0131r demektedir.<\/p>\n
Son olarak API’\u0131n swagger aray\u00fcz\u00fc sayesinde testini ger\u00e7ekle\u015ftirip veritaban\u0131na ba\u015far\u0131yla eri\u015febildi\u011fini tecr\u00fcbe ettiyseniz art\u0131k makaleyi burada noktayalabilirsiniz \ud83d\ude42 $\"Asp.NET$ <\/a>\n<\/li>\n<\/ul>\n
Nihai olarak yapt\u0131klar\u0131m\u0131z\u0131 \u00f6zetlememiz gerekirse e\u011fer;<\/p>\n
\n
ASP.NET Core API uygulamas\u0131 olu\u015fturarak Docker image’\u0131n\u0131 olu\u015fturduk.<\/li>\n
Olu\u015fturulan Docker image’\u0131n\u0131 depolamak ve y\u00f6netebilmek i\u00e7in AWS Container Registry(ECR)’ye y\u00fckledik.<\/li>\n
Amazon ECS’de bu uygulamaya ait container’lar\u0131 y\u00f6netip, koordine edece\u011fimiz cluster tan\u0131m\u0131nda bulunduk.<\/li>\n
Veritaban\u0131(MongoDB) container’\u0131 i\u00e7in bir task olu\u015fturduk ve cluster’da aya\u011fa kald\u0131rd\u0131k.<\/li>\n
Yine veritaban\u0131(MongoDB) container’\u0131n\u0131\/task’\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rabilmek i\u00e7in bir servis olu\u015fturduk ve bu servise IP tan\u0131mlayabilmek i\u00e7in load balancer ekledik.<\/li>\n
Olu\u015fturulan MongoDB servisinin 27017 portuna eri\u015fim i\u00e7in trafik izni verdik.<\/li>\n
Uygulamay\u0131 Amazon ECS’ye deploy edebilmek i\u00e7in uygulamaya dair bir container bar\u0131nd\u0131racak task olu\u015fturduk ve bunu da cluster’da aya\u011fa kald\u0131rd\u0131k. Burada uygulaman\u0131n image’\u0131n\u0131 2. ad\u0131mda depolad\u0131\u011f\u0131m\u0131z AWS Container Registry’den \u00e7ektik.<\/li>\n
Ve son olarak uygulama task’\u0131n\u0131 \u00e7al\u0131\u015ft\u0131racak olan servisi olu\u015fturup yine IP tan\u0131mlayabilmek i\u00e7in bu servise de load balancer ekledik.<\/li>\n<\/ol>\n
\u0130\u015fte bu kadar… \ud83d\ude42<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…
\n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n
Kaynaklar;
\nhttps:\/\/aws.amazon.com\/tr\/ecs\/features\/
\nhttps:\/\/codewithmukesh.com\/blog\/deploy-aspnet-core-web-api-to-amazon-ecs\/<\/p>\n
Not : \u00d6rnek projeyi a\u015fa\u011f\u0131daki github adresinden edinebilirsiniz.
\n https:\/\/github.com\/gncyyldz\/Amazon.ESC.AspNETCore.WebAPI.Deploy.Example<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, Bu i\u00e7eri\u011fimizde, bir Asp.NET Core API uygulamas\u0131n\u0131n Amazon Elastic Container Services(Amazon ECS)‘a nas\u0131l deploy edilece\u011fini ve uygulamay\u0131 dockerize etmeyi detayl\u0131ca inceleyecek ve bu s\u00fcre\u00e7te Amazon a\u00e7\u0131s\u0131ndan ihtiya\u00e7 duyulacak olan servisleri ele al\u0131yor olaca\u011f\u0131z....<\/p>\n","protected":false},"author":1,"featured_media":26316,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4778,4730],"tags":[4779,4785,4786,4783,4780,4784,4781,4731,4787,4782],"class_list":["post-26238","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-amazon-ecs","category-aws","tag-amazon-ecs","tag-amazon-eks","tag-amazon-elastic-container-registry","tag-amazon-elastic-container-service","tag-amazon-elastic-container-services","tag-amazon-elastic-kubernetes-service","tag-amazon-elastic-load-balancer","tag-aws","tag-ecr","tag-elb"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=26238"}],"version-history":[{"count":20,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26238\/revisions"}],"predecessor-version":[{"id":26317,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26238\/revisions\/26317"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/26316"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}