<\/div>\n

Merhaba,<\/p>\n

Amazon EC2(Elastic Compute Cloud), Amazon Web Service’leri taraf\u0131ndan sunulan y\u00fcksek oranda \u00f6l\u00e7eklenebilir ve esnek bir cloud servisidir. Bu servis \u00fczerinde kendi uygulamalar\u0131m\u0131z\u0131 \u00e7al\u0131\u015ft\u0131rabilece\u011fimiz, uygulaman\u0131n bellek veya CPU gibi gereksinimlerine uygun \u00e7e\u015fitli t\u00fcrler \u00fczerinden se\u00e7im yapabilecek olan instance ad\u0131nda sanal sunucular kiralanabilmekte ve ihtiya\u00e7 do\u011frultusunda da scale-up ya da scale-down \u00f6l\u00e7eklendirme yakla\u015f\u0131mlar\u0131 uygulanabilmektedir. Bizler, bu i\u00e7eri\u011fimizde bir Asp.NET Core Web API uygulamas\u0131n\u0131 Amazon EC2’de host etme s\u00fcrecini ad\u0131m ad\u0131m inceleyecek ve b\u00f6ylece DevOps ile ilgili \u00e7e\u015fitli uygulamalar\u0131n anla\u015f\u0131lmas\u0131na yard\u0131mc\u0131 olacak pek \u00e7ok etkili kavram\u0131 ele al\u0131yor olaca\u011f\u0131z.<\/p>\n

AWS, bir y\u0131l boyunca orta \u00f6l\u00e7ekli uygulamalar\u0131 host edebilmek i\u00e7in her ay 750 saate kadar Linux ve Windows instance’\u0131n\u0131 \u00fccretsiz olarak sunmaktad\u0131r.<\/em><\/p><\/blockquote>\n
$\"\"$ <\/a>EC2 ismindeki 2, Amazon’un ikinci nesil bulut bili\u015fim hizmetini ifade etmektedir. Bu hizmet, ilk nesil sabit ve esnek olamayan \u00e7\u00f6z\u00fcmlerden farkl\u0131 olarak; dinamik ve elastik bir yap\u0131da tasarlanm\u0131\u015ft\u0131r ve kullan\u0131c\u0131lara daha fazla esneklik, \u00f6l\u00e7eklenebilirlik ve maliyet optimizasyonu sa\u011flamaktad\u0131r. Bu nedenle 2 say\u0131s\u0131, EC2’nin teknolojik geli\u015fimini ve sundu\u011fu yenilikleri vurgulamak i\u00e7in kullan\u0131lm\u0131\u015ft\u0131r.<\/em><\/p>\n
Uygulamay\u0131 Geli\u015ftirelim<\/h4>\n
\u00d6ncelikle bir Asp.NET Core Web API uygulamas\u0131 geli\u015ftirerek i\u00e7eri\u011fimize giri\u015f yapal\u0131m. Bizlerin geli\u015ftirece\u011fi uygulama basit bir \u00fcr\u00fcn y\u00f6netim sistemi olacakt\u0131r. \u015eimdi ad\u0131m ad\u0131m bu uygulamay\u0131 geli\u015ftirmeye odaklanal\u0131m;<\/p>\n
\n
Ad\u0131m 1 (Product Entity’sini Olu\u015ftural\u0131m)<\/span><\/em>\n
\n
\r\n public record Product(Guid Id)\r\n {\r\n public string Name { get; set; }\r\n public string? Description { get; set; }\r\n public decimal Price { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n<\/li>\n
Ad\u0131m 2 (Veritaban\u0131 & Migration \u0130\u015flemlerini Yapal\u0131m)<\/span><\/em>
\nVeritaban\u0131 olarak PostgreSQL’i tercih ediyorum. Tabi ki de sizler, uygulamay\u0131 \u00f6zelle\u015ftirebilece\u011finiz gibi veritaban\u0131n\u0131 da kendinize \u00f6zel se\u00e7ebilirsiniz.<\/p>\n
\u00d6ncelikle a\u015fa\u011f\u0131daki gibi bir DbContext nesnesi olu\u015ftural\u0131m.<\/p>\n
\n
\r\n public class ApplicationDbContext : DbContext\r\n {\r\n public ApplicationDbContext(DbContextOptions options) : base(options)\r\n {\r\n }\r\n\r\n public DbSet<Product> Products { get; set; }\r\n }\r\n<\/pre>\n<\/div>\n
Ve ‘Program.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi veritaban\u0131 tan\u0131mlamas\u0131nda bulunal\u0131m.<\/p>\n
\n
\r\nbuilder.Services.AddDbContext<ApplicationDbContext>(options => options.UseNpgsql(builder.Configuration.GetConnectionString("PostgreSQL")));\r\n<\/pre>\n<\/div>\n
Ard\u0131ndan Package Manager Console<\/em> \u00fczerinden add-migration mig_1<\/code> talimat\u0131 e\u015flinde bir migration olu\u015ftural\u0131m. \u015eimdi bu migration’\u0131 ister update-database<\/code> komutuyla migrate edebilirsiniz, isterseniz de a\u015fa\u011f\u0131daki gibi dinamik bir yakla\u015f\u0131m sergileyebilirsiniz.<\/p>\n
\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.Services.AddDbContext<ApplicationDbContext>(options => options.UseNpgsql(builder.Configuration.GetConnectionString("PostgreSQL")));\r\n\r\nvar app = builder.Build();\r\n\r\n#region Dynamic Migration\r\nusing IServiceScope scope = app.Services.CreateScope();\r\nApplicationDbContext dbContext = scope.ServiceProvider.GetRequiredService<ApplicationDbContext>();\r\nif (dbContext.Database.GetPendingMigrations().Any())\r\n await dbContext.Database.MigrateAsync();\r\n#endregion\r\n\r\n.\r\n.\r\n.\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\n<\/li>\nAd\u0131m 3 (Operasyonel Endpoint’leri Olu\u015ftural\u0131m)<\/span><\/em> \nTemel \u00fcr\u00fcn i\u015flemlerini y\u00fcr\u00fctecek operasyonlara sahip endpoint’leri a\u015fa\u011f\u0131daki gibi minimal api olarak olu\u015ftural\u0131m.<\/p>\n\n\r\n.\r\n.\r\n.\r\n\r\napp.MapGet("\/products", async (ApplicationDbContext dbContext) =>\r\n{\r\n return await dbContext.Products.ToListAsync();\r\n});\r\n\r\napp.MapGet("\/products\/{id}", async (ApplicationDbContext dbContext, string id) =>\r\n{\r\n Product? product = await dbContext.Products.FindAsync(id);\r\n if (product is null)\r\n return Results.NotFound();\r\n return Results.Ok(product);\r\n});\r\n\r\napp.MapPost("\/products", async (ApplicationDbContext dbContext, CreateProductVM createProductVM) =>\r\n{\r\n Product product = new(Guid.NewGuid())\r\n {\r\n Name = createProductVM.Name,\r\n Description = createProductVM.Description,\r\n Price = createProductVM.Price\r\n };\r\n\r\n await dbContext.Products.AddAsync(product);\r\n await dbContext.SaveChangesAsync();\r\n});\r\n<\/pre>\n<\/div>\n<\/li>\n<\/ul>\n\u0130\u015fte bu kadar… Bu ad\u0131mlar s\u00fcrecinde kullan\u0131lan viewmodel gibi teferruatlara ve istifade edilen k\u00fct\u00fcphanelere i\u00e7eri\u011fimizin sonunda payla\u015fm\u0131\u015f oldu\u011fumuz github adresinden g\u00f6z atabilirsiniz. Makalenin hacmini art\u0131k yersiz \u015fi\u015firmemek i\u00e7in bu detaylar\u0131 sizlere b\u0131rak\u0131yorum.<\/p>\n Dockerizing<\/h4>\nAyr\u0131ca .NET’te gelen built-in container<\/a> deste\u011finden de istifade edelim istiyorum. Bunun i\u00e7in a\u015fa\u011f\u0131daki tan\u0131mlar\u0131 uygulaman\u0131n ‘.csproj’ dosyas\u0131ndaki ilgili alana ekleyelim.<\/p>\n \n\r\n\t<PropertyGroup>\r\n\t\t.\r\n\t\t.\r\n\t\t.\r\n\r\n\t\t<ContainerImageName>products-api<\/ContainerImageName>\r\n\t\t<ContainerImageTags>latest<\/ContainerImageTags>\r\n\t\t<PublishProfile>DefaultContainer<\/PublishProfile>\r\n\t\t<RuntimeIdentifier>linux-x64<\/RuntimeIdentifier>\r\n\t<\/PropertyGroup>\r\n<\/pre>\n<\/div>\nBu yap\u0131land\u0131rmadan sonra uygulaman\u0131n Docker image’\u0131n\u0131 olu\u015fturmak i\u00e7in a\u015fa\u011f\u0131daki talimat\u0131n verilmesi yeterli olacakt\u0131r.<\/p>\ndotnet publish -c Release --self-contained<\/code><\/div>\n\u0130\u00e7eri\u011fimizin devam\u0131nda Amazon EC2 instance’\u0131nda da ayn\u0131 i\u015flemleri ger\u00e7ekle\u015ftirecek ve orada da bir Docker image’\u0131 olu\u015fturaca\u011f\u0131z. \u015eimdi Docker Compose ile bu olu\u015fturdu\u011fumuz uygulamay\u0131 PostgreSQL ile aya\u011fa kald\u0131racak bir talimat dizisi olu\u015fturarak devam edelim.<\/p>\nPostgreSQL Container’\u0131 \u0130le Docker Compose<\/h4>\n\n\r\nversion: '3.8'\r\nservices:\r\n api:\r\n container_name: product-api\r\n image: products-api:latest\r\n environment:\r\n - ASPNETCORE_ENVIRONMENT=docker\r\n - ASPNETCORE_URLS=http:\/\/+:80\r\n ports:\r\n - 80:80\r\n depends_on:\r\n postgres:\r\n condition: service_healthy\r\n postgres:\r\n container_name: postgres\r\n image: postgres:15-alpine\r\n environment:\r\n - POSTGRES_USER=postgres\r\n - POSTGRES_PASSWORD=123456\r\n ports:\r\n - 5432:5432\r\n volumes:\r\n - postgres-data:\/data\/db\r\n healthcheck:\r\n test: ["CMD-SHELL", "pg_isready -U postgres"]\r\n interval: 10s\r\n timeout: 5s\r\n retries: 5\r\nvolumes:\r\n postgres-data:\r\n<\/pre>\n<\/div>\nYukar\u0131daki docker compose i\u00e7eri\u011fine g\u00f6z atarsan\u0131z e\u011fer iki adet servisin yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6receksiniz. \u0130lki, biraz \u00f6nce olu\u015fturdu\u011fumuz product-api<\/em> isimli built-in container’d\u0131r. Bu ilk etapta local docker instance’\u0131ndan \u00e7ekilecektir. \u0130\u00e7eri\u011fimizin devam\u0131nda Amazon EC2 instance’lar\u0131nda da \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6rece\u011fiz. \u0130kinci servis ise PostgreSQL yap\u0131land\u0131rmas\u0131n\u0131 bar\u0131nd\u0131rmaktad\u0131r.<\/p>\nappsettings.docker.json<\/h4>\nBu i\u015flem tamamland\u0131ktan sonra uygulamam\u0131z i\u00e7in docker’a uygun yap\u0131land\u0131rmay\u0131 bar\u0131nd\u0131racak appsettings.docker.json<\/em> dosyas\u0131n\u0131 ekleyerek devam edelim.<\/p>\n\n\r\n{\r\n "ConnectionStrings": {\r\n "PostgreSQL": "Host=postgres;Port=5432;Database=ProductDB;Username=postgres;Password=123456;Include Error Detail=true"\r\n }\r\n}\r\n<\/pre>\n<\/div>\nB\u00f6ylece ASPNETCORE_ENVIRONMENT<\/code> de\u011feri docker olarak ayarland\u0131\u011f\u0131 taktirde uygulama bu dosya \u00fczerinden yap\u0131land\u0131r\u0131lacakt\u0131r.<\/p>\n \u015eimdi ise s\u0131ra EC2 container’\u0131 olu\u015fturmaya gelmi\u015ftir.<\/p>\n Amazon EC2 Linux Instance Olu\u015fturma<\/h4>\nArt\u0131k her\u015fey haz\u0131r oldu\u011funa g\u00f6re bir Amazon EC2 Linux instance’\u0131n\u0131 aya\u011fa kald\u0131rabiliriz. Bunun i\u00e7in AWS Management Console \u00fczerinden EC2’yi aratal\u0131m. \n<\/a>Ard\u0131ndan a\u00e7\u0131lan sayfada ‘Launch instance’ butonuna t\u0131klayal\u0131m.<\/a>Ve ard\u0131ndan ilgili instance’\u0131 a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131ral\u0131m.<\/a><\/a>Burada Key pair<\/em> alan\u0131nda ‘Create new key pair’ diyerek a\u015fa\u011f\u0131daki gibi yeni bir tane olu\u015ftural\u0131m.<\/a>Burada key pair name olarak ‘admin’ de\u011ferini veriyoruz. Ayr\u0131ca dosya bi\u00e7imi olarak .ppk’y\u0131 se\u00e7iyoruz. ‘Create key pair’ butonuna t\u0131klad\u0131\u011f\u0131m\u0131zda admin.ppk ad\u0131nda bir dosya indirilecektir. Bu daha sonradan taraf\u0131m\u0131zca Amazon EC2 instance’\u0131na uzaktan ba\u011flanmak i\u00e7in kullan\u0131laca\u011f\u0131ndan dolay\u0131 bu dosyan\u0131n g\u00fcvenli bir \u015fekilde tutuldu\u011fundan emin olunmal\u0131d\u0131r.<\/p>\n Devam\u0131nda ise instance yap\u0131land\u0131rmas\u0131n\u0131 a\u015fa\u011f\u0131daki gibi yap\u0131p, ard\u0131ndan ‘Launch instance’ butonuna t\u0131klayal\u0131m.<\/a><\/a>Evet, t\u00fcm bu i\u015flemlerden sonraki ad\u0131m\u0131m\u0131z ise makinemizden bu EC2 instance’\u0131na ba\u011flanmakt\u0131r. Bizler bunun i\u00e7in PuTTY’i kullan\u0131yor olaca\u011f\u0131z. O halde buyurun devam edelim.<\/p>\n PuTTY \u0130le EC2 Instance’\u0131na SSH<\/h4>\n\u00d6ncelikle bilmeyenler i\u00e7in PuTTY ne la?<\/em><\/strong> sorusunu cevapland\u0131rarak devam edelim.<\/p>\nPuTTY, \u00e7e\u015fitli a\u011f protokolleri i\u00e7in bir client yaz\u0131l\u0131m\u0131d\u0131r ve \u00f6zellikle SSH(Secure Shell), Telnet, rlogin ve seri port ba\u011flant\u0131lar\u0131 gibi protokoller i\u00e7in kullan\u0131lmaktad\u0131r.<\/em><\/p><\/blockquote>\nPuTTY’i kullanabilmek i\u00e7in https:\/\/www.putty.org<\/a> adresinden indirilip, kurulmas\u0131 gerekmektedir.<\/p>\n PuTTY’i kurduktan sonra a\u00e7al\u0131m ve ‘Connection’ -> ‘SSH’ -> ‘Auth’ -> ‘Credentials’ sekmesinden PPK dosyas\u0131n\u0131 y\u00fckleyerek gerekli kimlik bilgileri yap\u0131land\u0131rmas\u0131nda bulunal\u0131m.<\/a>Devam\u0131nda ise ‘Session’ sekmesinden host bilgisini yazal\u0131m ve ‘Open’ diyerek ba\u011flant\u0131y\u0131 ba\u015flatal\u0131m.<\/a>Bu i\u015flemden sonra a\u015fa\u011f\u0131daki gibi ‘login as’ k\u0131sm\u0131 gelecektir.<\/a>Burada ‘ec2-user’ de\u011ferini yazal\u0131m ve enter diyelim.<\/p>\n Vee g\u00f6z\u00fcm\u00fcz ayd\u0131n \ud83d\ude42 Art\u0131k Linux Instance’\u0131na giri\u015f yapm\u0131\u015f bulunuyoruz… \n<\/a>\u015eimdi bu instance’a Git, Docker, .NET Runtime vs. gibi ihtiyac\u0131m\u0131z olan t\u00fcm ortam kurulumlar\u0131n\u0131 ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n Bunun i\u00e7in \u00f6ncelikle sudo su<\/code> talimat\u0131 e\u015fli\u011finde super user’a ge\u00e7i\u015f yapal\u0131m.<\/p>\n Ard\u0131ndan yum install git<\/code> talimat\u0131yla git’in kurulumunu ba\u015flatal\u0131m.<\/p>\n yum install docker<\/code> \nsudo systemctl start docker.service<\/code> \ndocker ps<\/code> talimatlar\u0131 e\u015fli\u011finde Docker’\u0131 kural\u0131m.<\/p>\n sudo yum install aspnetcore-runtime-7.0<\/code> \nsudo yum install dotnet-sdk-7.0<\/code> \ndotnet tool install --global dotnet-ef --version 7.0.19<\/code> \n. \/etc\/profile.d\/dotnet-cli-tools-bin-path.sh<\/code> \ndotnet sdk check<\/code> talimatlar\u0131 e\u015fli\u011finde de .NET 7 runtime’\u0131 ve SDK’yi kural\u0131m.<\/p>\n Burada e\u011fer ki y\u00fcklenen paketlerde bir hata, eri\u015fememe ya da tan\u0131mama durumu s\u00f6z konusu olursa, Microsoft paket deposunu a\u015fa\u011f\u0131daki talimatla eklemeli; \nsudo rpm -Uvh https:\/\/packages.microsoft.com\/config\/centos\/7\/packages-microsoft-prod.rpm<\/code> \nve ard\u0131ndan depo listesini sudo yum update<\/code> talimat\u0131yla g\u00fcncellemelisiniz. \n<\/em><\/p><\/blockquote>\n Devam\u0131nda ise docker-compose dosyas\u0131n\u0131n \u00e7al\u0131\u015fmas\u0131 i\u00e7in a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde gerekli ara\u00e7lar\u0131 y\u00fckleyelim. \nsudo curl -L https:\/\/github.com\/docker\/compose\/releases\/latest\/download\/docker-compose-$(uname -s)-$(uname -m) -o \/usr\/local\/bin\/docker-compose<\/code> \nsudo chmod +x \/usr\/local\/bin\/docker-compose<\/code> \ndocker-compose version<\/code><\/p>\n Evet, \u015fu ana kadar gerekli olan t\u00fcm ara\u00e7lar y\u00fcklenmi\u015ftir. \u015eimdi s\u0131rada Github repository’sini instance volume i\u00e7erisine klonlamak var. Bunun i\u00e7in yukar\u0131daki sat\u0131rlarda geli\u015ftirdi\u011fimiz \u00fcr\u00fcn y\u00f6netim sistemi uygulamas\u0131n\u0131 github’da yeni bir repository olu\u015fturarak depolayal\u0131m. (bknz: https:\/\/github.com\/gncyyldz\/Amazon.EC2.Hosting.Example<\/a>)<\/span> Ard\u0131ndan a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde hem uygulamay\u0131 github’dan \u00e7ekelim hem de docker image’\u0131n\u0131 olu\u015ftural\u0131m. \nmkdir repos<\/code> \ncd repos<\/code> \ngit clone https:\/\/github.com\/gncyyldz\/Amazon.EC2.Hosting.Example<\/code> \ncd Amazon.EC2.Hosting.Example<\/code> \ndotnet publish -c Release --self-contained<\/code> \ndocker images<\/code> \nBurada yapt\u0131\u011f\u0131m\u0131z \u00e7al\u0131\u015fmay\u0131 \u00f6zetlememiz gerekirse e\u011fer; \u00f6ncelikle ‘repos’ ad\u0131nda bir klas\u00f6r olu\u015fturduk ve ard\u0131ndan repository’mizi bu klas\u00f6re kopyalad\u0131k. Klonlama tamamland\u0131ktan sonra proje klas\u00f6r\u00fcne giderek uygulamay\u0131 publish ettik. Hat\u0131rlarsan\u0131z e\u011fer \u00f6nceki sat\u0131rlarda .csproj dosyas\u0131nda uygulama yay\u0131nland\u0131\u011f\u0131nda docker image’\u0131n\u0131 olu\u015fturacak spesifikasyonlarda bulunmu\u015ftuk. Haliyle bu i\u015flem neticesinde gerekli docker image’\u0131n\u0131 olu\u015fturmu\u015f olduk.<\/a>Bu a\u015famadan sonra art\u0131k uygulama i\u00e7erisindeki docker-compose dosyas\u0131n\u0131 \ndocker-compose up -d<\/code> talimat\u0131yla \u00e7al\u0131\u015ft\u0131rabiliriz. Tabi bunun i\u00e7in uygulaman\u0131n dizinine tam gelindi\u011finden emin olmal\u0131y\u0131z…<\/a><\/p>\n Uygulamay\u0131 Herkes Taraf\u0131ndan Eri\u015fime A\u00e7\u0131k Hale Getirme<\/h4>\nBu a\u015famadan sonra art\u0131k yap\u0131lmas\u0131 gereken uygulaman\u0131n herkes taraf\u0131ndan eri\u015fime a\u00e7\u0131k hale getirilmesidir. Bunun i\u00e7in a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi AWS Management Console \u00fczerinden EC2 instance’\u0131na gelelim ve ‘Security’ \u00fczerinden 80 portuna gelecek olan trafi\u011fe izin verelim.<\/a><\/p>\n Dikkat!<\/p>\n Github’dan uygulamay\u0131 klonlama a\u015famas\u0131nda a\u015fa\u011f\u0131dakine benzer hata al\u0131yorsan\u0131z e\u011fer;<\/p>\n unable to access ‘https:\/\/github.com\/gncyyldz\/Amazon.EC2.Hosting.Example\/’: Failed to connect to github.com port 443 after 131206 ms: Couldn’t connect to server<\/div>\n\u0130lgili EC2 instance’\u0131n\u0131n security groups alan\u0131ndan ‘Outbound rules’ sekmesine gelerek gelen t\u00fcm trafi\u011fe a\u015fa\u011f\u0131daki gibi rule tan\u0131m\u0131nda bulunulmas\u0131 gerekmektedir! \n<\/a> \n<\/em><\/p><\/blockquote>\n Test Etme<\/h4>\nArt\u0131k yapt\u0131\u011f\u0131m\u0131z bu \u00e7al\u0131\u015fmay\u0131 test edebiliriz. Bunun i\u00e7in EC2 instance’\u0131n\u0131n public adresini kopyalayal\u0131m ve Postman \u00fczerinden endpoint’lere testlerimizi ger\u00e7ekle\u015ftirelim.<\/a><\/a><\/a>Burada \u00f6zellikle dikkat edilmesi gereken nokta \u015fudur ki, request ataca\u011f\u0131n\u0131z public adresin https de\u011fil http protokol\u00fcne sahip olmas\u0131na \u00f6zen g\u00f6sterilmelidir. Aksi taktirde istek neticesinde connect ECONNREFUSED hatas\u0131 al\u0131rs\u0131n\u0131z.<\/p>\n Nihai olarak; \nBu i\u00e7eri\u011fimizde Asp.NET Core Web API mimarisinde geli\u015ftirdi\u011fimiz bir uygulamay\u0131 Amazon EC2 Linux instance’\u0131nda host etmi\u015f ve bunun i\u00e7in gerekli olan yap\u0131land\u0131rmalar\u0131 ele alm\u0131\u015f bulunuyor ve bunlar\u0131n yan\u0131nda .NET 7’de gelmi\u015f olan built-in container deste\u011fini de tecr\u00fcbe etmi\u015f oluyoruz.<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n Not : \u00d6rnek projeye a\u015fa\u011f\u0131daki github adresinden eri\u015febilirsiniz. \nhttps:\/\/github.com\/gncyyldz\/Amazon.EC2.Hosting.Example\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Amazon EC2(Elastic Compute Cloud), Amazon Web Service’leri taraf\u0131ndan sunulan y\u00fcksek oranda \u00f6l\u00e7eklenebilir ve esnek bir cloud servisidir. Bu servis \u00fczerinde kendi uygulamalar\u0131m\u0131z\u0131 \u00e7al\u0131\u015ft\u0131rabilece\u011fimiz, uygulaman\u0131n bellek veya CPU gibi gereksinimlerine uygun \u00e7e\u015fitli t\u00fcrler \u00fczerinden...<\/p>\n","protected":false},"author":1,"featured_media":27033,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5059,4730],"tags":[5054,5055,5060,5056,5058,5057],"class_list":["post-26999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-amazon-ec2","category-aws","tag-amazon-ec2","tag-amazon-ec2-hosting","tag-elastic-compute-cloud","tag-putty","tag-putty-nedir","tag-ssh"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26999","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=26999"}],"version-history":[{"count":13,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26999\/revisions"}],"predecessor-version":[{"id":27035,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26999\/revisions\/27035"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/27033"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}