Forem: MaryAyobami

My Cloud+Security Series

MaryAyobami — Wed, 03 Apr 2024 10:05:29 +0000

If you ever come across this, hello to you! And welcome to my blog.

I haven’t posted new articles on this blog in a while, but that is about to change. I’m starting a new series - “Cloud+Security Series,” where I intend to write articles on cloud computing, cloud security, and cybersecurity. It is not entirely structured. I plan to write on random topics around this area or any new or exciting topic I come across in my learning and hands-on projects with these areas. I will be dropping at least two articles each week. I implore you to stick around here. You will enjoy the articles whether you are a cloud enthusiast like me, a newbie, or a professional.

Cheers.

Instant Deployment Made Easy: How to Deploy Web Apps on Azure Static Web Apps.

MaryAyobami — Sat, 15 Apr 2023 08:40:49 +0000

Azure Static Web Apps is a service that deploys full-stack web apps automatically to Azure from a code repository. This service has been designed to meet the daily workflow of developers, where apps are built and deployed based on code changes. When an Azure Static Web Apps resource is created, Azure interacts directly with GitHub or Azure DevOps to monitor a branch of choice. Whenever there is a code change through push commits or acceptance of pull requests, a build automatically runs and the app and API are deployed to Azure.

This service supports popular web development frameworks such as React, Angular, Vue.js, and static site generators such as Gatsby and Hugo. In this article, I will walk you through the steps required to deploy a web app on Azure Static Web App through two different methods:

Azure Portal
Azure Static Web App CLI

Contents

Prerequisites

Deployment through the Azure Portal

Step 1: Create a new Azure Static Web App

Step 2: Configure the Static Web App

Step 3: Review and deploy the Static Web App

Step 4: Access your Static Web App

Deployment through the Azure SWA CLI

Conclusion

Prerequisites

Before we move forward in deploying our apps, we need the following:

An Azure Account, which can be created here.
A Github repository that contains the code to be deployed. You can find the repository used in this article here.

Once you are set, let's proceed!

Deployment through the Azure Portal

Step 1: Create a new Azure Static Web App

The first step is to create a new Azure Static Web App in the Azure portal. Follow these steps to create the app:

Log in to the Azure portal (https://portal.azure.com/).
Click on "Create a resource" in the top left corner of the dashboard.
Search for "Static Web Apps" in the search bar.
Click on "Static Web Apps (Preview)" from the list of results.
Click on the "Create" button to create a new static web app.

Step 2: Configure the Static Web App

Go ahead to select a subscription, resource group (or create a new one), and give a name to your app as shown in the image below:

Under Deployment Details , Select the source where your code is located. For Github, you may have to authorize Azure to connect to your Github account if you have not done so before.

Then, Select the repository where your web app code is hosted.
Select the branch that you want to deploy.

Choose the build command that will be used to build your web app. This could be a script in your package.json file or a custom command. Specify the output folder where the built files will be located.
Choose the deployment environment for your static web app. You can choose between a preview or production environment.
Click on the "Review + create" button to review your settings.

Step 3: Review and deploy the Static Web App

After configuring the static web app, you need to review the settings and deploy it. Follow these steps to review and deploy the app:

On the "Create a Static Web App" page, click on the "Review + create" button.
Review your settings and make any necessary changes. Click on the "Create" button to create and deploy your static web app.
Wait for the deployment to complete. You can view the deployment progress in the "Notifications" section.

Step 4: Access your Static Web App

Once the deployment is complete, you will receive a notification. To access your web app, click on 'Go to Resource'.

From there, you can directly access your web app by clicking on the "Browse" button. Alternatively, you can copy the URL of your web app.

Step 4: Accessing your Static Web App

Once the deployment is complete, you will receive a notification. To access your web app, click on 'Go to Resource'.

From there, you can directly access your web app by clicking on the "Browse" button. Alternatively, you can copy the URL of your web app.

And voila! Your web app is up and running.!

Deployment through the Azure SWA CLI

Another deployment option is the Azure Static Web Apps CLI, also known as SWA CLI. It is a local development tool for Azure Static Web Apps that can deploy your app to Azure Static Web Apps.

To use the SWA CLI, you need to install it first. You can install it globally using the following command:

npm install -g @azure/static-web-apps-cli

After a successful installation, navigate to the code you want to deploy and change the directory. To initialize a new static web app project, use the following command:

swa init

This command will prompt you to choose a configuration name for your app. After that, you will be shown an overview of the configuration settings. If the settings are correct, enter YES then proceed to deploying your app.

To deploy your app to Azure Static Web Apps, type the following command:

To deploy to Azure Static Web Apps, type:

swa deploy

Conclusion

Azure Static Web Apps makes it easy to deploy web apps to a secure and scalable environment. By following the steps outlined in this article, you can deploy your web app to Azure Static Web Apps in just a few minutes.

Get Started with Virtual Machines: A Step-by-Step Guide to Setting up an EC2 Instance on AWS.

MaryAyobami — Sat, 08 Apr 2023 02:31:06 +0000

A virtual machine is a software implementation of a physical machine, allowing multiple operating systems to run on the same physical hardware. In simple terms, A virtual machine is like a computer that exists within another computer. It's a software program that mimics the functions of a physical computer and can run its own operating system and applications independently of the host machine. This means that you can have multiple virtual machines running on the same physical computer, each with its own operating system and software applications. It's like having several computers in one!

What is EC2?

EC2 which stands for Elastic Compute Cloud is a web service provided by Amazon Web Services (AWS) that allows users to create and manage virtual machines on the cloud. AWS EC2 provides a scalable, reliable, and secure environment for running virtual machines with various operating systems, such as Linux, Windows, and macOS. EC2 instances can be launched and terminated on demand, allowing customers to scale their infrastructure up or down based on their needs.

In this article, I will guide you through the process of setting up an EC2 instance on AWS.

Step 1: Create an AWS Account

The first step to setting up an EC2 instance on AWS is to create an AWS account. To do this, go to the AWS website and click on the "Create a Free Account" button. Follow the prompts to create your account.

Once your account is created, log in to the AWS console. This is where you will manage all of your AWS resources, including EC2 instances.

Step 2: Launch an EC2 Instance

To launch an EC2 instance, follow these steps.

1. Type EC2 in global search box, then select EC2 from the options.

2. On the the EC2 dashboard, click on instances then the "Launch Instance" button.

You will be presented with a variety of options for configuring your instance.

3. Name your Instance and add Tags.

Give your EC2 instance a name. You can also add tags to your instance to help you organize and identify it.

4. Choose an Amazon Machine Image (AMI)

An Amazon Machine Image (AMI) is a pre-configured virtual machine image that includes the operating system, application server, and any other software required to run your application. You can choose from a variety of pre-configured AMIs provided by AWS, or you can create your own custom AMI.

5. Choose an Instance Type

The next step is to choose an instance type. An instance type defines the CPU, memory, storage, and network capacity of your EC2 instance. You can choose from a variety of instance types depending on your specific requirements.

A t2.micro instance which is selected by default, has 1 vCPU and 1 GiB Memory. The t2.micro instance type is eligible for the free tier. In Regions where t2.micro is unavailable, you can use a t3.micro instance under the free tier.

Then choose an existing key-pair, or create a new one

It is not recommended to proceed without a key-pair as it is needed to connect to your instance. If you launch an instance without a key pair, then you can't connect to it.

6. Configure Instance Details: (Network Settings, Security Group)

A security group is a set of firewall rules that control the traffic that can access your EC2 instance. You can configure your security group to allow traffic from specific IP addresses or ranges, or to allow traffic from anywhere.

Add SSH(port-22) and HTTP(port-80) rules in Inbound security groups rules to access your instance from putty(ssh) and through web browser(internet) respectively._
_ Keep the default selections for the other configuration settings.

7. Add Storage.

You can add storage volumes to your instance. AWS offers different types of storage, such as Elastic Block Store (EBS) and Instance Store.

OPTIONAL: Advanced Details
In this section, everything can be left as default. You can also configure it. You can pass user data to the instance that can be used to perform automated tasks and even run scripts after the instance starts.

8. Review and Launch Your Instance

Once you have satisfied with your instance settings, you can launch your instance.

Step 3: Connect to Your Instance
There are multiple ways to connect to your instance. After your instance is launched, you can connect to it directly using EC2 instance connect, remote desktop protocol (RDP) client or a secure shell (SSH) client. To do this, you will need to use the key pair that you created earlier.
Amazon EC2 Instance Connect provides a simple and secure way to connect to your EC2 instance using a browser-based client. To connect to your instance,

Go to the EC2 console
In the navigation pane, click on Instances
Select your instance and click the "Connect" button.

Enter the custom username (ubuntu in this case) and click on connect. And that's it! Your EC2 instance is up and running!

Once you are connected to your EC2 instance, you can install and configure your application. This may include installing any necessary software, configuring your web server, and setting up any databases or other dependencies.

Setting up an EC2 instance on AWS as a beginner can seem daunting at first, but with the right guidance, it can be a straightforward process. By following the steps outlined in this article, you can quickly set up an EC2 instance and start running your applications in the cloud.