Skip to main content

A Technical Talk on Microservices and Cloud Deployment

This is a full-length session of microservices development using Microsoft .Net Core WebAPI(C#.Net) and Mongo DB as backend. The session presentation available below   The source code of session available in GitHub , feel free to share your feedback and contribute to this project Full session video Prerequisites for development MongoDB (you can download from here ) Visual Studio 2019 DotNet Core 3.1.x SDK Postman (for API Testing)

AWS S3 in C#.Net (Amazon Web Services, Simple Storage Services)

I hope this article will help for better understanding of  AWS (Amazon Web Services) S3 (Simple Storage Services) in C#.Net SDK implementation.

AWS (Amazon Web Services)
The AWS Cloud services provided by Amazon (pioneer in cloud service)

S3 (Simple Storage Services)
This is storage service provided in AWS, this will helps us to store and retrieve the files in the Amazon cloud storage.
Bucket - Like local drive in our system (here located cloud server)
Object - File/Folder actually stored in the bucket, each object has object data & metadata

for more information about S3 services click here.

Prerequisites
1. Active AWS subscription
2. AWS .Net SDK
3. Visual Studio

Prepare for the code
Before start the sample application you need to be ready with Bucket Name and your AWS Secret Key, Access Key for the development. We should aware of the region of service (S3 does not require region selection).

Ready for Develop

1. Sign-in AWS console and open S3 Services


2. Create Bucket in S3


3. Ensure the permission, we should have the read/write and list permissions for our sample application


4. Open visual studio, create new windows application project (C#.Net)

5. Add "AWS SDK for .Net" from NuGet Package Manager



6. Form design


7. Code




 8. Run the application



source available in GitHub AWS-S3-Sample, provide the feedback and share this article with your friends

Comments

Blogger said…
DreamHost is one of the best web-hosting provider with plans for all of your hosting requirments.

Popular posts from this blog

A Technical Talk on Microservices and Cloud Deployment

This is a full-length session of microservices development using Microsoft .Net Core WebAPI(C#.Net) and Mongo DB as backend. The session presentation available below   The source code of session available in GitHub , feel free to share your feedback and contribute to this project Full session video Prerequisites for development MongoDB (you can download from here ) Visual Studio 2019 DotNet Core 3.1.x SDK Postman (for API Testing)

Know more about Azure Website KUDU?

KUDU  is the web tool for analyzing and troubleshooting azure websites. Benefits of Kudu Know about operating system Environment variables Processors & cores Applications settings Connection strings Process explorer (running instances) Debugging console (Command prompt & PowerShell) Diagnostics Log (view & download) Site extensions management and more Environment details Command prompt Are your wondering to use KUDU?, its very simple open browser and type https://{ your azure website name }.scm.azurewebsites.net . To access KUDU you need to have your azure deployment credentials! Example Your azure website : https://textingwebsite.azurewebsites.net/ Kudu URL : https://textingwebsite.scm.azurewebsites.net/ for more information about Kudu click here

How to check the Hybrid Connection in Azure Website (Webapp)

Introduction Hi, this article will helpful for you to check the hybrid connection in Azure Website (Web App). Scenario Lets assume we have 2 Web Apps and 2 On-Premises database servers, Both the webapps required on-premises database access, for this scenario we can use Azure Hybrid connection . Architecture of Web apps and Hybrid connection Website 1 : Wants to access DB Server 1 & DB Server 2 Website 2 : Wants to access DB Server 1 only To achieve this we need to create two hybrid connections for each db and we can share it with websites. Troubleshooting Once you successfully created hybrid connection and configured listener setup. we need to ensure whether our website connected to our DB Server or not. So open the Azure portal (old or new). 1. Select the website 2. Click Browse website       * Lets assume our website URL is https://myweb.azurewebsites.net       * Change the URL to https://myweb.scm.azurewebsites.net 3. Now you will enter into