DEV Community: olaniyi akinkunmi

CREATING EC2 INSTANCE ON AWS AND INSTALLING IIS SERVER.

olaniyi akinkunmi — Wed, 25 Dec 2024 00:20:13 +0000

Search for EC2 on the search box

Click on Launch instance

Give your virtual machine a name and choose your image

Create new key pair login

Click on Allow HTTP traffic from the internet and Launch instance

Click on EC2 or connect instance, am clicking on EC2

Click on Instance (running)

Select the instance you created and click connect

Click RDP fill, download remote desktop file

Click on get password

Open and copy the first file we downloaded

Paste it in the box and decrypt password, the password will be generated

Copy the password and paste it on the RDP file we downloaded

You can see we are connected to a window server

Open chatGPT search for command for iis web server role and paste on your power shell in the windows server

As we can see it is instilling

Our web server has been install

Copy the public IP address to a browser and open

HOW TO CREATE A PRESIGNED URL FOR AN S3 (simple storage service)aws

olaniyi akinkunmi — Tue, 24 Dec 2024 10:34:33 +0000

After you login to aws search for s3

click create bucket

Choose the purpose of your bucket and give it a name

Give your bucket a tag

click create bucket

how bucket has been created,open the bucket

let upload on our bucket

lets add a file

our image has been uploaded

To create URL for the image
click on the image,go to action and share with presigned URL

Choose the desired minute or hour you want then click create

copy the URL and paste in a new tab

you can see the picture we uploaded

AZURE INSIGHT

olaniyi akinkunmi — Sat, 05 Oct 2024 12:52:01 +0000

Q1: kubernetes was originally designed by which company?
Kubernetes was originally designed by Google

Q2:When moving your services to Azure Kubernetes Service (AKS) for a massively multiplayer online game, several components will contribute to your monthly Azure charge:
When moving your services to Azure Kubernetes Service (AKS) for a massively multiplayer online game, several components will contribute to your monthly Azure charge:

Compute Costs: This includes the cost of the virtual machines (VMs) that run your Kubernetes nodes. The size and number of VMs will directly impact your costs.

Storage Costs: Persistent storage for your containers, such as Azure Disks or Azure Files, will also contribute to your monthly charges.

Networking Costs: This includes data transfer costs, load balancers, and virtual networks. If you use Azure Load Balancer or Azure Application Gateway, these will add to your expenses.

Azure Kubernetes Service (AKS) Management: While the AKS control plane is free, you will incur costs for the underlying infrastructure and any additional services you use.

Additional Services: Any other Azure services you integrate with your AKS cluster, such as Azure Monitor for monitoring and logging, Azure Security Center for security, or Azure DevOps for CI/CD pipelines, will also contribute to your overall costs

AZURE INSIGHT

olaniyi akinkunmi — Fri, 27 Sep 2024 22:41:28 +0000

Q1:what is the most important common pattern for auto scaling in cloud environments?
One of the most important and common patterns for auto-scaling in cloud environments is horizontal scaling. This pattern involves adding or removing instances of a resource, such as virtual machines or containers, to match the current demand. Here are some key aspects of horizontal scaling:
Scale Based on Metrics: Resources are scaled based on performance metrics like CPU usage, memory usage, or request rates. For example, if the CPU usage of a virtual machine exceeds a certain threshold, additional instances can be added to handle the load.
Scheduled Scaling: Resources are scaled based on a predefined schedule. This is useful for predictable workloads, such as scaling up during business hours and scaling down during off-hours.
Event-Driven Scaling: Resources are scaled in response to specific events, such as a sudden spike in traffic due to a marketing campaign or a special event.
Minimum and Maximum Limits: Setting minimum and maximum limits ensures that there are always enough resources to handle the load, but not so many that costs become excessive.
Health Monitoring: Automatically replacing unhealthy instances to maintain the overall health and performance of the application

Q2:what are some characteristics of cloud native applications

Cloud-native applications are designed to fully leverage the capabilities of cloud computing environments. Here are some key characteristics:

Microservices Architecture: These applications are composed of small, independent services that communicate over APIs. This allows for greater flexibility and scalability.
Containers: Cloud-native apps often use containers to package and run services. Containers provide consistency across different environments and help in scaling applications efficiently.
DevOps and Continuous Delivery: They embrace DevOps practices and continuous integration/continuous delivery (CI/CD) pipelines to ensure rapid and reliable deployment of new features and updates.
Scalability and Elasticity: Cloud-native applications can automatically scale up or down based on demand, optimizing resource usage and cost.
Resilience and Fault Tolerance: These applications are designed to handle failures gracefully, ensuring high availability and reliability.
API-Driven:_ APIs are crucial for communication between microservices and for integrating with other services and platforms_.
Automation: Automation is key in cloud-native environments, from infrastructure provisioning to application deployment and monitoring.
Stateless and Stateful Services: They can manage both stateless and stateful services, optimizing performance and resource utilization

Q3:How would you describe a monolithic application

A monolithic application is a type of software architecture where all the components of the application are tightly integrated into a single, self-contained unit. Here are some key characteristics:

Single Codebase: All the functionality of the application, including the user interface, business logic, and data access layers, is contained within one codebase.
Unified Deployment: The entire application is deployed as a single unit. This means that any changes or updates require redeploying the whole application.
Tightly Coupled Components: Components within a monolithic application are tightly coupled, meaning they are highly dependent on each other. This can make the application less flexible and harder to scale.
Centralized Data Management: Typically, a monolithic application uses a single database to manage all its data.

CONTAINER

olaniyi akinkunmi — Fri, 20 Sep 2024 22:14:21 +0000

Q1: How do you start a container ?????
* Install Docker: Ensure Docker is installed on your system. You can download it from the official Docker website.
* Pull an Image: Use the docker pull command to download the image you want to use. For example, to pull the latest Ubuntu image, you would run
* Run the Container: Use the docker run command to create and start a container from the image. For example, to start a container with the Ubuntu image.
* Start a Stopped Container: If you have a stopped container that you want to restart, use the docker start command followed by the container ID or name.

Q2: What type of editor can be used to build a docker file list any.
* Visual Studio Code (VS Code): A powerful, open-source code editor with extensions for Docker support, syntax highlighting, and IntelliSense.
* Sublime Text: A lightweight, fast editor with a wide range of plugins, including Dockerfile syntax highlighting.
* Atom: An open-source editor from GitHub, which also supports Dockerfile syntax highlighting through community packages.
* Notepad++: A free source code editor for Windows that supports various programming languages and file types, including Dockerfiles.
* Vim: A highly configurable text editor built to enable efficient text editing. It can be used within a terminal or as a standalone application.
* Nano: A simple, easy-to-use text editor for Unix-like systems, often used directly in the terminal.
* IntelliJ IDEA: An integrated development environment (IDE) that supports Docker through plugins, providing advanced features like code completion and debugging.

Q3: How do you build and download a container image
* Create a Dockerfile: This file contains the instructions for building the image
* Build the Image: Use the docker build command to create the image from your Dockerfile. Run this command in the directory containing your Dockerfile
* Verify the Image: List the images to verify that your image has been created

Q4: Where can container image can be stored and give examples
Container images can be stored in various types of repositories, both public and private. Here are some common options:

* Docker Hub: The most popular public registry for Docker images. It allows you to store and share container images with the community.
Example: docker pull ubuntu:latest pulls the latest Ubuntu image from Docker Hub.
* Amazon Elastic Container Registry (ECR): A fully managed Docker container registry that makes it easy to store, manage, and deploy Docker container images.
Example: aws ecr create-repository --repository-name my-repo creates a new repository in ECR.
* Azure Container Registry (ACR): A managed, private Docker registry service based on the open-source Docker Registry 2.0.
Example: az acr create --resource-group myResourceGroup --name myRegistry --sku Basic creates a new container registry in Azure.
* Google Container Registry (GCR): A private container image registry that supports Docker images.
Example: gcloud container images list-tags gcr.io/my-project/my-image lists tags for a specific image in GCR.
* Harbor: An open-source container image registry that secures images with role-based access control, scans images for vulnerabilities, and signs images as trusted.
Example: docker login harbor.mycompany.com logs into a Harbor registry.
* JFrog Artifactory: A universal repository manager that supports Docker images along with other package types.
Example: docker push mycompany.jfrog.io/my-repo/my-image:latest pushes an image to Artifactory.
* Red Hat Quay: A container registry that provides secure storage, distribution, and deployment of container images.

Provide private storage for internal company documents(Steps)

olaniyi akinkunmi — Sat, 14 Sep 2024 18:20:57 +0000

Storage Plan

Task
*Create a storage account.
*Create a storage container with restricted access.
*Configure a shared access signature for partners.
*Back up the public website storage.
*Implement lifecycle management to move content to the cool
tier.
Exercise instructions

Create a storage account and configure high availability.
1.Create a storage account for the internal private company documents.
*In the portal, search for and select Storage accounts.

*Select + Create.

*Select the Resource group created in the previous lab.

*Set the Storage account name to private. Add an identifier to the name to ensure the name is unique.

*Select Review, and then Create the storage account.

*Wait for the storage account to deploy, and then select Go to resource.

2.This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy.

*In the storage account, in the Data management section, select the Redundancy blade.

*Ensure Geo-redundant storage (GRS) is selected.

*Refresh the page.

*Review the primary and secondary location information.

*Save your changes.

Create a storage container, upload a file, and restrict access to the file.

1.Create a private storage container for the corporate data.

*In the storage account, in the Data storage section, select the Containers blade.

*Select + Container.

*Ensure the Name of the container is private.

*Ensure the Public access level is Private (no anonymous access).
*As you have time, review the Advanced settings, but take the defaults.
*Select Create.

2.For testing, upload a file to the private container. he type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publically accessible.

*Select the container.

*Select Upload.

*Browse to files and select a file.

*Upload the file.

*Select the uploaded file.

*On the Overview tab, copy the URL.

*Paste the URL into a new browser tab.

3.An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS). Learn more about Shared Access Signatures.

*Select your uploaded blob file and move to the Generate SAS tab.

*In the Permissions drop-down, ensure the partner has only Read permissions.

*Verify the Start and expiry date/time is for the next 24 hours.

*Select Generate SAS token and URL.

*Copy the Blob SAS URL to a new browser tab.

*Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded.

Configure storage access tiers and content replication.
1 To save on costs, after 30 days, move blobs from the hot tier to the cool tier. Learn more how manage the Azure Blob storage lifecycle.

*Return to the storage account.

*In the Overview section, notice the Default access tier is set to Hot.

*In the Data management section, select the Lifecycle management blade.

*Select Add rule.

*Set the Rule name to movetocool.

*Set the Rule scope to Apply rule to all blobs in the storage account.

*Select Next.

*Ensure Last modified is selected.

*Set More than (days ago) to 30.

*In the Then drop-down select Move to cool storage.

*As you have time, review other lifecycle options in the drop-down.
*Add the rule.

2 The public website files need to be backed up to another storage account.[Learn more about object replication.

*In your storage account, create a new container called backup. Use the default values. Refer back to Lab 02a if you need detailed instructions.

*Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.

*In the Data management section, select the Object replication blade.

*Select Create replication rules.

*Set the Destination storage account to the private storage account.

*Set the Source container to public and the Destination container to backup.

*Create the replication rule.

*Optionally, as you have time, upload a file to the public container. Return to the private storage account and refresh the backup container. Within a few minutes your public website file will appear in the backup folder.

YES WE DID IT

AZURE INSITE

olaniyi akinkunmi — Sat, 14 Sep 2024 13:01:47 +0000

Q1. An o organization wants to implement a serverless workflow to solve problem.one of the requirements is the solution needs to use a designer first (declarative) deployment model. which of the choices below meets the requirements
ANS:For implementing a serverless workflow with a designer-first (declarative) deployment model, Azure Logic Apps and Power Automate are excellent choices. Both services provide a visual designer to create workflows and integrate with various SaaS and enterprise applications

Q2. which azure hosting plain is the best when predictive scaling and cost are required????
For predictive scaling and cost optimization, Azure Virtual Machine Scale Sets with Predictive Autoscale is a great option. Predictive Autoscale uses machine learning to forecast CPU load based on historical usage patterns, allowing you to scale out before demand spikes1
Additionally, consider the Azure Consumption Plan for serverless functions, which automatically scales based on demand and charges only for compute resources used2. This can be particularly cost-effective for applications with variable workloads.

Provide storage for the public website

olaniyi akinkunmi — Fri, 13 Sep 2024 14:08:46 +0000

Skilling tasks
1 Create a storage account with high availability.
2 Ensure the storage account has anonymous public access.
3 Create a blob storage container for the website documents.
4 Enable soft delete so files can be easily restored.
5 Enable blob versioning

Create a storage account with high availability.

Create a storage account to support the public website.
In the portal, search for and select Storage accounts.

Select + Create.

*For resource group select new. Give your resource group a name and select OK.

*Set the Storage account name to publicwebsite. Make sure the storage account name is unique by adding an identifier.

*Take the defaults for other settings.

*Select Review and then Create.

Wait for the storage account to deploy, and then select Go to resource.

This storage requires high availability if there’s a regional outage. Additionally, enable read access to the secondary region, Learn more about storage account redundancy.

*In the storage account, in the Data management section, select the Redundancy blade.

*Ensure Read-access Geo-redundant storage is selected.

*Review the primary and secondary location information

Information on the public website should be accessible without requiring customers to login. *In the storage account, in the Settings section, select the Configuration blade.

*Ensure the Allow blob anonymous access setting is Enabled.

*Be sure to Save your changes.

Create a blob storage container with anonymous read access
1 The public website has various images and documents. Create a blob storage container for the content. Learn more about storage containers.
*in your storage account, in the Data storage section, select the Containers blade.

*Select + Container.

*Ensure the Name of the container is public.

*Select Create.

2 Customers should be able to view the images without being authenticated. Configure anonymous read access for the public container blobs. Learn more about configuring anonymous public access.

*Select your public container.

*On the Overview blade, select Change access level.

*Ensure the Public access level is Blob (anonymous read access for blobs only).

*Select OK.

Practice uploading files and testing access.
1 For testing, upload a file to the public container. The type of file doesn’t matter. A small image or text file is a good choice
*Ensure you are viewing your container.

*Select Upload.

*Browse to files and select a file. Browse to a file of your choice.

*Select Upload.

*Close the upload window, Refresh the page and ensure your file was uploaded.
2. Determine the URL for your uploaded file. Open a browser and test the URL.
*Select your uploaded file.

*On the Overview tab, copy the URL.

*Paste the URL into a new browser tab.
*If you have uploaded an image file it will display in the browser. Other file types should be downloaded.

Configure soft delete

It’s important that the website documents can be restored if they’re deleted. Configure blob soft delete for 21 days. Learn more about soft delete for blobs. *Go to the Overview blade of the storage account.

*On the Properties page, locate the Blob service section.

*Select the Blob soft delete setting.

*Ensure the Enable soft delete for blobs is checked.
*Change the Keep deleted blobs for (in days setting is 21.

*Notice you can also Enable soft delete for containers.

*Don’t forget to Save your changes.

2. If something gets deleted, you need to practice using soft delete to restore the files.
*Navigate to your container where you uploaded a file.

*Select the file you uploaded and then select Delete.

*Select OK to confirm deleting the file.

*On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.

*Select your deleted file, and use the ellipses on the far right, to Undelete the file.

*Refresh the container and confirm the file has been restored.

Configure blob versioning

It’s important to keep track of the different website product document versions. Learn more about blob versioning. *Go to the Overview blade of the storage account.

*In the Properties section, locate the Blob service section.

*Select the Versioning setting.

*Ensure the Enable versioning for blobs checkbox is checked.

*Notice your options to keep all versions or delete versions after.

*Don’t forget to Save your changes.

As you have time experiment with restoring previous blob versions. *Upload another version of your container file. This overwrites your existing file.

*Your previous file version is listed on Show deleted blobs page.

Provide storage for the IT department testing and training

olaniyi akinkunmi — Wed, 11 Sep 2024 17:27:39 +0000

Step 1: Create and deploy a resource group to hold all your project resources. Learn more about
*In the Azure portal, search for and select Resource groups

*Give your resource group a name.

select a region

*Select Review and create to validate the resource group.

*Select Create to deploy the resource group.

Step 2 Create and deploy a storage account to support testing and training. Learn more about the types of storage accounts

*In the Azure portal, search for and select Storage accounts.
*Select + Create.

*On the Basics tab, select your Resource group.

*Provide a Storage account name.

*Set the Performance to Standard.

*Select Review, and then Create.

*Wait for the storage account to deploy and then Go to resource.

Configure simple settings in the storage account.

1 The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired. Learn more about storage account redundancy.

*In your storage account, in the Data management section, select the Redundancy blade.

*Select Locally-redundant storage (LRS) in the Redundancy drop-down.

*Be sure to Save your changes

Refresh the page and notice the content only exists in the primary location.

2 The storage account should only accept requests from secure connections. Learn more about requiring secure transfer from secure connections
*In the Settings section, select the Configuration blade.

*Ensure Secure transfer required is Enabled.

3 Developers would like the storage account to use at least TLS version 1.2
*In the Settings section, select the Configuration blade.

*Ensure the Minimal TLS version is set to Version 1.2

4 Until the storage is needed again, disable requests to the storage account.
*In the Settings section, select the Configuration blade.

*Ensure Allow storage account key access is Disabled

*Be sure to Save your changes.

5 Ensure the storage account allows public access from all networks

In the Security + networking section, select the Networking blade.

*Ensure Public network access is set to Enabled from all networks.

*Be sure to Save your changes.

NEED FOR DEPLOYMENT SLOTS

olaniyi akinkunmi — Sat, 07 Sep 2024 09:15:51 +0000

Q1: Describe The Benefit of Deployment Slot

Deployment slots provide the following benefits:
Flexibility: Manage and test multiple versions of your app simultaneously.
Reliable Deployment Process: Maximizes user satisfaction and minimizes disruptions.
Zero-Downtime Deployments: Test new versions before putting them into production.
Seamless Rollbacks: Easily roll back to a previous version if anything goes wrong.
Robust Testing Environments: Mitigate risks associated with updating live applications.
Q2: BY Default, all clint request to the app production URL
(http://.azurewebsites.net)are routed to the production slot. one can automatically route a portion of the traffic to another slot. what is the default routing rule applied to new deployment slots??
By default, when you create a new deployment slot in Azure App Service, the traffic routing percentage for the new slot is set to 0%. This means that all client requests are initially routed to the production slot, and no traffic is automatically directed to the new slot.

If you want to route a portion of the traffic to the new slot, you can manually adjust the traffic percentage settings in the Azure portal.

Databases-Database Type, SQL Use Cases

olaniyi akinkunmi — Wed, 28 Aug 2024 02:55:21 +0000

Q1: Which of the deployment is Iaas or Paas
Azure SQL: Azure SQL is a family of managed, secure, and intelligent products that use the SQL Server database engine in the Azure cloud (Iaas)
SQL Managed Instance: is a Platform-as-a-Service (PaaS) service that has near 100% compatibility with the latest Enterprise Edition SQL Server database engine (Paas)
SQL Database:is a cloud-based database service that provides a relational SQL database in the cloud (Paas)
Azure SQL Managed Instance: including its Instance Pool feature, is considered a Platform as a Service (PaaS)
Azure SQL Database: elastic pools are a simple, cost-effective solution for managing and scaling multiple databases with varying and unpredictable usage demands. The databases in an elastic pool are on a single server and share a set number of resources at a set price. Elastic pools in SQL Database enable software-as-a-service (SaaS)
Q2: What is a manage service??????
Managed Services offers a comprehensive suite of services and tools that can help organizations manage and scale their IT infrastructure on the cloud. Compared to other cloud service providers, Azure has a strong focus on enterprise-level features, such as compliance management, security, and hybrid cloud integration.
Q3: You are moving an application and data base to your azure, but your data base is currently 62TB and will continue to grow.which azure SQL deployment option will be easiest to use???
For a large and growing database like yours (62TB and increasing), the Azure SQL Database Hyperscale option would be the most suitable. Hyperscale is designed to handle large-scale databases and offers the following benefits:
Scalability: It can scale up to 100TB per database, which accommodates your current size and future growth.
Performance: It provides high performance with rapid scaling of storage and compute resources.
Flexibility: You can scale storage and compute independently, allowing for cost-effective management1.
Backup and Restore: Fast backup and restore capabilities, which are crucial for large database

Pushing Code From Local Environment(Gitbash) to Github

olaniyi akinkunmi — Mon, 26 Aug 2024 23:16:19 +0000

We need to differentiate and know the function between gitbash and github
Git Bash
Git Bash is a command-line interface (CLI) application for Windows that provides a Bash emulation environment to run Git commands. It allows users to interact with Git, the version control system, using a Unix-like command-line experience12.
Here are some key features of Git Bash:
Bash Emulation: It behaves like the Bash shell found in Linux and Unix environments, making it familiar for users who are accustomed to those systems13.
Git Commands: You can perform various Git operations such as cloning repositories, committing changes, pushing and pulling updates, and more2.
Unix Utilities: Git Bash includes several Unix utilities like SSH, SCP, and CAT, which can be useful for various tasks
.Type: Command-line interface
Purpose: Provides a Unix-like terminal environment on Windows to use .Git commands
.Functionality: Allows you to interact with Git repositories locally
.Installation: Installed locally on your system
.Usage: Primarily used for executing Git commands and managing version control
GitHub
GitHub is a platform for version control and collaboration that allows developers to store, manage, and share their code. It uses Git, the distributed version control system, to track changes in code and facilitate collaboration among multiple developers.
Here are some key features of GitHub:
Repository Hosting: Store and manage your code in repositories.
.Version Control: Track changes and revert to previous versions if needed.
.Collaboration Tools: Work with others through pull requests, code reviews, and issues.
Continuous Integration/Continuous Deployment (CI/CD): Automate testing and deployment of your code.
.Project Management: Use tools like project boards and task lists to manage your work.
.Security Features: Identify and fix vulnerabilities in your code
.Type: Web-based platform
.Purpose: Hosts Git repositories and provides tools for collaboration, version control, and project management
.Functionality: Offers a graphical user interface (GUI) for managing repositories, issues, pull requests, and more
.Installation: Accessed via the web; no local installation required
.Usage: Used for hosting repositories, collaborating with others, and managing projects online
Walkthrough to push from your local environment(github)
1. Download Git Bash
2.configure Git bash
3.work with the configure evvironment
4.clone your github repo
5.push to github
to download gitbash
Step 1 download git

_this is how our gitbah looks like _

Step 2 configure your environment
use the command git config --global user.name "name" press enter

configure your email
use the command git config --global user.email "email"

Step 3 work with the configure environment
you will create a directory
mkdir website

cd website

create a local repository with the command git init

create a file; touch index.html

**Step 4 **clone your repository

Click on code

Click on http and copy url

paste the code,the command is git remote add origin and the url

**Step **5 push to git hub
use this command git add . to push everything or git add index.html for index.html alone

take a snap shoot using this command with a nice message
git commit -m "nice message"

push it finally to git hub using this code
git push origin master

confirm your login

it has been push to git hub then open

Now you compare and pull request

The file has been push

Go to settings click on page

go to branch choose master then click on save

You can see we have a web page

THANK YOU FOR FOLLOWING THROUGH