UHD STUDIO

shots and Angles

2025-06-15T08:51:00.002+05:30

The Grammar of the Gaze: An Interactive Explorer

The Grammar of the Gaze

An Interactive Explorer of Cinematic Language

Shot Size Explorer

The proximity of the camera to a subject dictates the audience's emotional connection. Use the buttons below to see how changing the shot size alters the narrative focus from environment to emotion.

Extreme Long Shot

Extreme Long Shot (ELS)

Technical Definition:

The subject appears small, dominated by the surrounding location. Often used as an establishing shot to show context and scale.

Artistic Analysis:

Evokes feelings of isolation, awe, or vulnerability by emphasizing the environment. It sets the tone and establishes the world of the story.

Camera Angle Explorer

The vertical position of the camera is a powerful psychological tool. Select an angle to see how it alters our view of the subject and to explore its emotional impact with the chart.

●_●

Eye-Level

Psychological Effect:

Creates a sense of neutrality, equality, and direct connection. The audience relates to the character as a peer, fostering empathy.

Common Use:

The default for most naturalistic dialogue scenes, allowing the audience to focus on performance without overt psychological manipulation.

Psychological Impact Analysis

The Director's Lens

Great directors develop a unique visual grammar that becomes their signature. Select a director to explore their core philosophy and key cinematic techniques.

SCENE: 42 TAKE: 01 DIRECTOR: YOU

Advanced Visual Storytelling

Mastery of cinematography involves synthesizing framing, perspective, lens choice and camera movement to create profound psychological effects.

The Dolly Zoom (Vertigo Effect)

Achieved by moving the camera away from a subject while zooming in, this technique creates a disorienting warp. The subject stays the same size while the background appears to stretch away, visually externalizing a character's internal crisis or a sudden, world-altering realization.

Famous Use: Chief Brody witnessing the shark attack in *Jaws* (1975).

⊙▃⊙

HOVER TO FEEL THE EFFECT

The Long Take ("Oner")

A single, uninterrupted shot that continues for an extended period. It preserves the temporal and spatial integrity of a scene, immersing the audience in a real-time experience, making them feel like a present observer rather than a passive viewer.

Famous Use: The iconic Copacabana entrance shot in *Goodfellas* (1990).

Shallow vs. Deep Focus

Shallow Focus: Blurs the background (bokeh) to isolate the subject, drawing attention to their emotions. Creates a romantic or dreamlike mood.

Deep Focus: Keeps both foreground and background sharp, embedding the character in their environment and suggesting a connection between them. Allows for multiple layers of action in one frame.

2024-03-16T09:46:00.007+05:30

Dhanaseenuvasan PY01AB5657 MODEL Ford Fiesta FASTAG BAL

Tell.Me.Lies.S01E01.720p.DSNP.WEBRip.x264-GalaxyTV

2024-02-25T13:47:00.000+05:30

How to Install and Configure Docker on Different Operating Systems, Build, Run, and Manage Docker Containers with Basic Commands, Use Docker Images and Dockerfiles to Create Customized Containers ,Docker Compose to Define and Run Multi-Container Applications , Docker Networking to Connect Containers and Hosts , Docker Registries to Store and Share Images

2023-09-05T19:52:00.003+05:30

DOCKER ENGINE

Dependencies are the software or libraries that are required to install or run another software. For example, to install Jenkins, you need to install Java first. To install Ansible, you need to install Python first.

Sometimes, different software may require different versions of the same dependency. For example, some software may need Python 2, while others may need Python 3. However, you cannot have two versions of Python on the same operating system.

Docker is a software that solves this problem by creating isolated environments called containers. Each container can have its own dependencies and software without affecting the others.

Docker uses the base kernel of the operating system to create containers. Therefore, you can only run applications that are compatible with the base kernel. For example, if you have a Windows-based operating system, you can only run Windows applications in Docker containers. If you have a Linux-based operating system, you can only run Linux applications in Docker containers.

Docker has several components, such as:

Dockerfile: A text file that contains instructions to build a Docker image.
Docker image: A binary file that contains the dependencies and software for a container.
Docker container: A running instance of a Docker image.
Docker Hub: A repository of Docker images that you can download or upload.

To use Docker on Windows, you need to install Docker and Kitematic tools. Kitematic is a graphical user interface for managing Docker containers on Windows.

To create a container, follow these steps:

Launch an Ubuntu HVM LTS 64-bit x86 instance with all TCP open, 16 GB storage size, and 1 GB RAM.
Connect to the instance and switch to the root user with sudo su - root.
Update the package index files on Ubuntu with apt-get update.
Install Docker with apt install docker.io.

Docker has three main components:

Dockerfile: A text file that contains instructions to build a Docker image.
Docker image: A binary file that contains the dependencies and software for a container.
Docker container: A running instance of a Docker image.

To install an image from Docker Hub, use docker pull <image_name>.

For example, to install the httpd image, use docker pull httpd.

With the help of an image, you can launch multiple containers with different port mappings.

For example, to create a container with the httpd image and map port 7070 of the host to port 80 of the container, use docker run -itd -p "7070:80" httpd.

You can also give a name to your container with the --name option. The name should be unique for each container.

For example, to create a container named webserver with the httpd image and map port 9090 of the host to port 80 of the container, use docker run -itd --name webserver -p "9090:80" httpd.

To check the status of your containers, use docker ps. To see all containers, including the stopped ones, use docker ps -a.

To access your containers from a web browser, enter the public IP address of your instance followed by the port number of the host.

For example, if your instance has the IP address 43.205.216.140 and you have mapped port 7070 of the host to port 80 of the container, enter http://43.205.216.140:7070 in your browser.

To stop a container, use docker stop <container_name> or docker stop <container_ID>.

To start a stopped container, use docker start <container_ID>.

To delete a container, use docker rm <container_name> or docker rm <container_ID>. You need to stop the container first before deleting it.

To force remove a container without stopping it, use docker rm -f <container_ID>.

To enter into a container and execute commands inside it, use docker exec -it <container_ID> /bin/bash.

For example, to install vim inside a container, use docker exec -it <container_ID> /bin/bash and then apt install vim.

To exit from a container, use exit.

Note: When you stop the instance, all containers also stop.

To delete an image, use docker rmi <image_name>:<version>. You can only delete an image if no container is running on that image.

To see the details of a container, use docker inspect <container_name> or docker inspect <container_ID>.

To see what changes happened in a container, use docker logs <container_name> or docker logs <container_ID>.

To see the statistics of containers, use docker stats for all containers and docker stats <container_name> or docker stats <container_ID> for a specific container.

To see the processes running in a container, use docker top <container_name> or docker top <container_ID> for read-only mode or use docker exec -it <container_ID> /bin/bash and then use top for live mode.

To create an AMI from a container, follow these steps:

Create a container with the desired image and configuration. For example, to create a container with the httpd image, use docker run -itd httpd.
Enter into the container and install the software or libraries you need. For example, to install vim and git inside the container, use docker exec -it <container_ID> /bin/bash and then use apt install vim and apt install git.
Exit from the container with exit.
Commit the changes to a new image with docker commit <container_ID> <image_name>:<version>. For example, to create an image named myimage with version 1.0.1 from the container ID d90ce38d2ea5, use docker commit d90ce38d2ea5 myimage:1.0.1.

To share your image with someone else, you have two options:

Upload your image to Docker Hub (remote):

Create a Docker account on the web browser.
Log in to your Docker account on the Ubuntu machine with docker login and enter your username and password (token).
Create a tag for your image with your Docker account name and repository name. For example, to create a tag for myimage:1.0.1 with the account name alwaysdhina and the repository name httpd_vim_git, use docker tag myimage:1.0.1 alwaysdhina/httpd_vim_git.
Push your image to Docker Hub with docker push <tag_name>. For example, to push alwaysdhina/httpd_vim_git, use docker push alwaysdhina/httpd_vim_git.
You can see your image on your Docker Hub account under the repository section.
You can also see the pull command for your image under the tag section of the repository.

Save your image to a local file (local):

Save your image to a tar file with docker save -o /usr/local/<file_name_backup>.tar <image_name>:<version>. For example, to save myimage:1.0.1 to a file named myimagebackup.tar, use docker save -o /usr/local/myimagebackup.tar myimage:1.0.1.
You can share this file with someone else through any means.
To load the image from the file, use docker load -i <backup_file_name>.tar. For example, to load the image from myimagebackup.tar, use docker load -i myimagebackup.tar.
You can see the image on your local machine with docker images.

To see what commands you have used, use history.

Dockerfile and volumes are two important concepts in Docker.

Dockerfile: A text file that contains instructions to build a Docker image. You can specify the base image, the dependencies, the software, the commands, and the configuration for your image in a Dockerfile. You can use docker build command to create an image from a Dockerfile.
Volumes: A way to persist and share data between containers and the host machine. Volumes are directories or files that are mounted to a container and are not affected by the container’s lifecycle. You can use volumes to store data that you want to keep after the container is deleted, or to share data between different containers.

There are two ways to create a container with a volume attached:

Way 1: Use the -v option with docker run and specify the local directory and the container directory for syncing data. For example, to create a container with the httpd image and map port 70 of the host to port 80 of the container, and sync the data between /root/html on the host and /usr/local/apache2/htdocs on the container, use docker run -itd -p "70:80" -v "/root/html:/usr/local/apache2/htdocs" httpd. Whatever changes happen in the local directory will also be reflected in the container directory, and vice versa. If you delete data inside the container, it will also be deleted in the local directory. But if you delete the container, the data will still remain in the local directory. You can use docker volume ls to see the volumes on your machine.

Way 2: Use docker volume create command to create a volume with a name and a mount point. For example, to create a volume named my-volume, use docker volume create my-volume. You can use docker volume inspect my-volume to see the details of the volume, such as its mount point. Then, use --mount option with docker run and specify the source as the volume name and the destination as the container directory. For example, to create a container with the httpd image and map port 10 of the host to port 80 of the container, and mount the my-volume volume to /usr/local/apache2/htdocs on the container, use docker run -itd --mount source=my-volume,destination=/usr/local/apache2/htdocs -p "10:80" httpd. The data in the volume will be synced with the data in the container directory. If you delete data inside the container, it will also be deleted in the volume. But if you delete the container, the volume will still remain on your machine. You can use docker volume ls to see the volumes on your machine.

Dockerfile is a text file that contains instructions to build a Docker image. You can use a Dockerfile to specify the base image, the dependencies, the software, the commands, and the configuration for your image. You can use docker build command to create an image from a Dockerfile.

Here is an example of a Dockerfile that creates an image with CentOS as the base image, installs httpd, and labels the image with a name:

# Use CentOS as the base image

FROM centos

# Label the image with a name

LABEL Name="Dhinakran"

# Replace the mirrorlist with baseurl in yum repos

RUN sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*

RUN sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*

# Install httpd

RUN yum install httpd -y

To create an image from this Dockerfile, save it in a directory (for example, /root/test/) and run the following command:

# Create an image named Dimg with version v2 from the Dockerfile in /root/test/

docker build -t Dimg:v2 /root/test/

You can see the image on your machine with docker images command. For example, you may see something like this:

REPOSITORY TAG IMAGE ID CREATED SIZE

Dimg v2 3dff28a2a576 59 seconds ago 280MB

centos latest 5d0da3dc9764 23 months ago 231MB

The -itd option in the docker run command stands for interactive, tty, and detached.

interactive means that the container will be able to accept input from the user. This is useful if you need to run a command in the container that requires user input, such as a script that asks for the user's name.
tty means that the container will have a pseudo-terminal. This allows you to interact with the container's shell, such as by running ls or cd commands.
detached means that the container will run in the background. This means that you can run the container and then immediately exit the command prompt, without having to wait for the container to finish running.

So, the docker run -itd -name myser -p "from:to" httpd command will create a new container from the httpd image, and it will be:

Interactive, so you can enter input into the container.
TTY enabled, so you can interact with the container's shell.
Detached, so the container will run in the background.
Named myser.
Exposed on port from to port to on the host machine.

The docker exec -it CONTAINER-ID /bin/bash command will connect to an existing container and open a bash shell inside it. The CONTAINER-ID is the ID of the container that you want to connect to.

The docker container prune command will delete all stopped containers.

To access a container only through SSH, follow these steps:

Create a Dockerfile that installs SSH and configures the root login and password. For example, you can use the following Dockerfile:

# Use Ubuntu 16.04 as the base image

FROM ubuntu:16.04

# Label the image with a name

LABEL Name="Dhinakran"

# Update the package index files on Ubuntu

RUN apt-get update

# Install wget and openssh-server

RUN apt-get install wget openssh-server -y

# Replace the prohibit-password option with yes in sshd_config

RUN sed -i 's/PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config

# Set the root password to root123

RUN echo 'root:root123' | chpasswd

# Create the /var/run/sshd directory

RUN mkdir /var/run/sshd

# Run the ssh daemon in the foreground

CMD ["/usr/sbin/sshd", "-D"]

# Expose port 22 for SSH

EXPOSE 22

Build an image from this Dockerfile with docker build -t <image_name>:<version> <directory>. For example, to create an image named sshaccess with version latest from the Dockerfile in /root/test/, use docker build -t sshaccess:latest /root/test/.
Run a container from this image with docker run -itd -p "<host_port>:22" <image_name>. For example, to create a container with sshaccess image and map port 200 of the host to port 22 of the container, use docker run -itd -p "200:22" sshaccess.
Connect to the container from another machine using SSH with ssh -p <host_port> root@<public_IP>. For example, to connect to the container from a Windows machine using PuTTY, enter the public IP address of the host machine and port 200 in PuTTY. To connect to the container from a Linux machine using command prompt, use ssh -p 200 root@<public_IP>. Enter the root password (root123) when prompted.
You can now access the container as the root user and execute commands inside it.

To restrict the permission to a container like read-only access, you can use the --volumes-from option with docker run and specify the source container and the read-only mode. For example, follow these steps:

Create a new container with a volume that you want to sync with another container. For example, to create a container named WebServer with the httpd image and sync the data between /usr/local/apache2/logs on the host and /usr/local/apache2/logs on the container, use docker run -itd --name WebServer -p "100:80" -v "/usr/local/apache2/logs" httpd.
Create another container with read-only access to the volume of the source container. For example, to create a container with the sshaccess image and map port 200 of the host to port 22 of the container, and mount the volume from WebServer in read-only mode, use docker run -itd -p "200:22" --volumes-from WebServer:ro sshaccess.
Access the second container from another machine using SSH with ssh -p <host_port> root@<public_IP>. For example, to connect to the container from a Windows machine using PuTTY, enter the public IP address of the host machine and port 200 in PuTTY. To connect to the container from a Linux machine using command prompt, use ssh -p 200 root@<public_IP>. Enter the root password (root123) when prompted.
You can now access the second container as the root user, but you cannot modify the data in the volume that is mounted from the source container.

Note: In real life, you may want to use the same port number for accessing a container as the default port number for that service. For example, for httpd service, you may want to use port 80 instead of port 100. To do that, you can use -p "80:80" instead of -p "100:80" when creating the first container.

----LINK-----

By default, every container is isolated and does not interact with any other container.

------HOW TO LINK OR CONNECT CONTAINERS-------[IMPORTANT TOPIC]

First, launch a container with SQL image and name it DB:

docker run -itd -e MYSQL_ROOT_PASSWORD=DHINA123 --name DB mysql:5.5

The -e option sets the environment variable for the MySQL root password. Without this, the container will not launch.

Example:

root@ip-172-31-33-206:~# docker run -itd --name DB mysql:5.5 ERROR OCCURS

root@ip-172-31-33-206:~# docker run -itd -e MYSQL_ROOT_PASSWORD=DHINA123 --name DB mysql:5.5 7e02bcaf9a4f65987a9c6f2a7bee87aaa008c74606fa8a62ebd24201bf339452

root@ip-172-31-33-206:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7e02bcaf9a4f mysql:5.5 “docker-entrypoint.s…” 6 seconds ago Up 5 seconds 3306/tcp DB

Next, launch a container with WordPress image and name it MyWebServer. To link this container with the DB container, use the --link option:

docker run -itd --name MyWebServer --link DB:mysql -p “80:80” wordpress

The --link option creates a connection between the two containers and allows WordPress to access the MySQL database. The -p option maps the port 80 of the container to the port 80 of the host machine.

----SUMMARY-----

docker run -itd

-p (FOR PORT FORWARDING) –name (NAMING CONTAINER) -e (ENVIRONMENT LIKE MYSQL_ROOT_PASSWORD=DHINA123) -v (VOLUME CREATE) –mount (ATTACH VOLUME WITH CONTAINER) –volumes-from (CREATE CONTAINER WITH ALREADY CREATED CONTAINER NAME WITH VOLUME) –link (LINK OR CONNECT CONTAINERS (WORDPRESS CONTAINER TO SQL CONTAINER)) -t (TO TAG IMAGE FOR DOCKERFILE) –network (CHOOSE WHICH NETWORK THAT CONTAINER WILL USE LIKE BRIDGE OR HOST) imagename:version

Writing all these options for docker run command can be difficult or confusing.

|------TO AVOID THOSE KIND OF CONFUSION, WE CAN USE YAML FILE----|

-----------HOW TO LINK OR CONNECT CONTAINERS (WORDPRESS CONTAINER TO SQL CONTAINER) THROUGH YAML FILE--------------

----DOCKER COMPOSE-----

NOTE: WRITING DOCKER FILE & DOCKER COMPOSE ARE ROLES AND RESPONSIBILITIES OF DEVOPS ENGINEER ONLY IF YOU ARE WORKING IN DOCKER

YAML FORMAT IS USED FOR COMPOSING

WE CAN WRITE ALL THE OPTIONS OF DOCKER COMMAND IN A YAML FILE. IF WE NEED, WE CAN EASILY USE IT.

INSTALL DOCKER COMPOSE IN LINUX MACHINE.

YAML FILE

The YAML file format is used for docker compose, which allows us to write all the options of docker command in a single file. If we need, we can easily use it.

docker-compose.yml (DOCKER COMPOSE FILE FORMAT)

version: “3” services: #global value database: image: mysql:5.7 volumes: - ./data:/var/lib/mysql environment: MYSQL_ROOT_PASSWORD: somewordpress MYSQL_DATABASE: wordpress MYSQL_USER: wordpress MYSQL_PASSWORD: wordpress wordpress: image: wordpress depends_on: - database ports: - “8080:80” restart: always environment: WORDPRESS_DB_HOST: database:3306 WORDPRESS_DB_USER: wordpress WORDPRESS_DB_NAME: wordpress WORDPRESS_DB_PASSWORD: wordpress

Example:

root@ip-172-31-33-206:~# vi docker-compose.yaml

root@ip-172-31-33-206:~# cat docker-compose.yml

cat: docker-compose.yml: No such file or directory root@ip-172-31-33-206:~# cat docker-compose.yaml version: “3” services: #global value database: image: mysql:5.7 volumes: - ./data:/var/lib/mysql environment: MYSQL_ROOT_PASSWORD: somewordpress MYSQL_DATABASE: wordpress MYSQL_USER: wordpress MYSQL_PASSWORD: wordpress wordpress: image: wordpress depends_on: - database ports: - “8080:80” restart: always environment: WORDPRESS_DB_HOST: database:3306 WORDPRESS_DB_USER: wordpress WORDPRESS_DB_NAME: wordpress WORDPRESS_DB_PASSWORD: wordpress root@ip-172-31-33-206:~#

root@ip-172-31-33-206:~# snap install docker (INSTALL DOCKER-COMPOSE COMMANDS) docker 20.10.24 from Canonical✓ installed root@ip-172-31-33-206:~# docker-compose up -d (TO RUN YAML FILE) IT WILL CREATE CONTAINERS AND DATA WE PROVIDED IN YAML FILE

docker-compose ps (TO SHOW CONTAINERS USING DOCKER-COMPOSE)

SO, FINALLY WE LAUNCHED TWO CONTAINERS WITH LINKED USING DOCKER-COMPOSE.

-----DOCKER NETWORK------

root@ip-172-31-33-206:~# docker network ls NETWORK ID NAME DRIVER SCOPE 99dbfaab2bec bridge bridge local b51513edaba3 host host local 562ff9a09495 none null local e467761683f4 root_default bridge local

bridge

( TO CREATE ISOLATED CONTAINERS BY DEFAULT )(IF WE CREATE CONTAINERS THROUGH DOCKER RUN COMMAND, IT CHOOSES BRIDGE NETWORK FOR ISOLATION BY DEFAULT) host ( NO ISOLATION BETWEEN CONTAINERS )

docker network create --driver host Dhina ( TO CREATE OWN NETWORK )

root@ip-172-31-33-206:~# docker network rm d3 (TO DELETE NETWORK) d3 root@ip-172-31-33-206:~#

DOCKER NETWORKING TUTORIAL

https://docs.docker.com/network/network-tutorial-standalone/

-------TO LEARN DOCKER COMPOSE---------

DOCKER REFERENCE [ https://docs.docker.com/reference/

: https://docs.docker.com/network/network-tutorial-standalone/ : https://docs.docker.com/reference/

Data Warehouse Architecture in detail

2023-07-20T12:48:00.001+05:30

Data Warehouse

A data warehouse is a centralized repository of structured, organized, and historical data that is used for reporting, analysis, and business intelligence purposes.
It is a historical collection of data from different sources that is integrated, cleansed, and organized for analysis.
Data warehouses are used to support business intelligence (BI) and decision-making.

Characteristics of a Data Warehouse:

Centralized repository: A data warehouse is a centralized repository of data, which means that it is a single source of truth for all of the data that is stored in it.
Historical data: Data warehouses typically contain historical data, which means that they store data that has been collected over a period of time.
Integrated data: The data in a data warehouse is integrated, which means that it has been combined from different sources.
Cleansed data: The data in a data warehouse is cleansed, which means that it has been cleaned of errors and inconsistencies. .
Organized data: The data in a data warehouse is organized in a way that makes it easy to access and analyze.

Data warehouses are an essential tool for businesses that want to make better decisions based on data.

Architecture of Data Warehouse:

Detailed Description of data warehouse Architecture

ETL: Extract, transform, load. This process is used to load data from operational databases and external sources into the data warehouse.
Refresh: This process is used to update the data warehouse data on a regular basis, such as daily, weekly, or monthly.
Data marts typically contain a subset of the data in the data warehouse, and they are optimized for specific types of analysis.
The metadata repository is a database that stores information about the data warehouse data. This information includes the schema of the data warehouse, the lineage of the data, and the quality of the data.
OLAP servers can be used to process queries from the front-end tools. They can also be used to generate reports.
Query/report: This process is used to retrieve data from the data warehouse and to generate reports.
Analysis: This process is used to analyze the data warehouse data. Users can use analysis tools to perform various analysis tasks, such as trend analysis, forecasting, and clustering.
Data mining: This process is used to discover patterns in the data warehouse data. Users can use data mining tools to discover patterns that can be used to make predictions or to identify new opportunities.

Advantages of data warehouses:

Improved business intelligence: Data warehouses can help businesses to gain a better understanding of their data by providing a centralized repository for historical data.
Better decision-making: By providing access to a wide range of data, data warehouses can help businesses to make better decisions.
Improved data quality: Data warehouses can help to improve data quality by providing a single source of truth for data.

Disadvantages of data warehouses:

Costly setup and maintenance: Data warehouses can be expensive to set up and maintain.
Limited flexibility: Data warehouses can be limited in their flexibility.
Data silos: Data warehouses can create data silos.

Used for

Track sales trends
Analyze customer behavior.
Identify new market opportunities.
Make better strategic decisions.
Here are some examples of data warehouses:

Example Of Data Warehouse

Amazon Redshift
Google Big Query
Microsoft Azure SQL Data Warehouse

Launch Your Amazon EC2 Instance labs

2023-07-13T20:19:00.001+05:30

Task 1: Launch Your Amazon EC2 Instance

In this task, you will launch an Amazon EC2 instance with termination protection. Termination protection prevents you from accidentally terminating an EC2 instance. Your instance will include a User Data script that will install a simple web server.

From the AWS Management Console, use the AWS search bar to search for

EC2

and then choose the service from the list of results.

At the top left of the screen, if you see New EC2 Experience in the top-left of the screen, ensure New EC2 Experience is selected.

Choose the Launch instance drop down menu and choose Launch instance.

In the Name and tags section, enter

Web Server

in the Name box.

For Amazon Machine Image (AMI), select Amazon Linux 2 AMI.

This lab will only work with an Amazon Linux 2 AMI.

An Amazon Machine Image (AMI) provides the information required to launch an instance, which is a virtual server in the cloud. An AMI includes:

A template for the root volume for the instance (for example, an operating system or an application server with applications)
Launch permissions that control which AWS accounts can use the AMI to launch instances
A block device mapping that specifies the volumes to attach to the instance when it is launched

The Quick Start list contains the most commonly-used AMIs. You can also create your own AMI or select an AMI from the AWS Marketplace, an online store where you can sell or buy software that runs on AWS.

In the Instance Type section, choose the Instance type drop down menu and choose

t3.micro

Amazon EC2 provides a wide selection of instance types optimized to fit different use cases. Instance types comprise varying combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose the appropriate mix of resources for your applications. Each instance type includes one or more instance sizes, allowing you to scale your resources to the requirements of your target workload.

A t3.micro instance type has 2 virtual CPUs and 1 GiB of memory.

In the Key pair (login) section, locate the Key pair name drop down menu and choose Proceed without a key pair (Not recommended).

Amazon EC2 uses public–key cryptography to encrypt and decrypt login information. To log in to your instance, you must create a key pair, specify the name of the key pair when you launch the instance, and provide the private key when you connect to the instance.

In this lab you will not log into your instance, so you do not require a key pair.

In the Network settings section, choose the Edit button. Make the following selections:

VPC: Choose the VPC with the name that contains

Lab VPC

Subnet: Choose the Subnet with the name that contains

Public Subnet 1

The Network indicates which Virtual Private Cloud (VPC) you wish to launch the instance into. You can have multiple networks, such as different ones for development, testing and production.

The Lab VPC was created using a CloudFormation template during the setup process of your lab. This VPC includes two public subnets in two different Availability Zones.

In the Firewall (security groups) section, choose Create security group

Security group name =

Web Server security group

Description =

Security group for my web server

A security group acts as a virtual firewall that controls the traffic for one or more instances. When you launch an instance, you associate one or more security groups with the instance. You add rules to each security group that allow traffic to or from its associated instances. You can modify the rules for a security group at any time; the new rules are automatically applied to all instances that are associated with the security group.

In this lab, you will not log into your instance using SSH. Removing SSH access will improve the security of the instance.

Choose the Remove button to remove the existing SSH rule. You should have no security group rules.

The Configure storage section default choices can be left alone.

Amazon EC2 stores data on a network-attached virtual disk called Elastic Block Store.

You will launch the Amazon EC2 instance using a default 8 GiB disk volume. This will be your root volume (also known as a ‘boot’ volume).

Expand the Advanced details section. Scroll down to the Termination protection drop down menu and set to Enable.

When an Amazon EC2 instance is no longer required, it can be terminated, which means that the instance is stopped and its resources are released. A terminated instance cannot be started again. If you want to prevent the instance from being accidentally terminated, you can enable termination protection for the instance, which prevents it from being terminated.

Scroll all the way to the bottom until you see a field for User data.

When you launch an instance, you can pass user data to the instance that can be used to perform common automated configuration tasks and even run scripts after the instance starts.

Your instance is running Amazon Linux, so you will provide a shell script that will run when the instance starts.

Copy the following text and paste it into the User data field:

#!/bin/bash

yum -y install httpd

systemctl enable httpd

systemctl start httpd

echo '<html><h1>Hello From Your Web Server!</h1></html>' > /var/www/html/index.html

The script will:

Install an Apache web server (httpd)
Configure the web server to automatically start on boot
Activate the Web server
Create a simple web page

Choose Launch instance .

Expected output:

Success

Choose Instances from the collapsible menu on the left pane. You may need to expand the menu to see this option.

The instance might appear in a pending state, which means it is being launched. It will then change to running, which indicates that the instance has started booting. When creating a new instance, there will usually be a short time before you can access the instance.

Wait for your instance to display the following:

Instance state: Running .
Status check: 2/2 checks passed .

Periodically refresh the page if you don’t see a change in the Instance state or Status check values.

Select the for your newly-created Web Server and the Details tab displays detailed information about your instance.

To view more information in the Details tab, drag the window divider upwards.

Review the information displayed in the Details tab. It includes information about the instance type, security settings, network settings, and more. The instance receives a Public IPv4 DNS name that you can use to communicate with the instance from the Internet.

Congratulations! You have successfully launched your first Amazon EC2 instance.

Task 2: Monitor Your Instance

Monitoring is an important part of maintaining the reliability, availability, and performance of your Amazon Elastic Compute Cloud (Amazon EC2) instances and your AWS solutions.

Select the Status checks tab.

With instance status monitoring, you can quickly determine whether Amazon EC2 has detected any problems that might prevent your instances from running applications. Amazon EC2 performs automated checks on every running EC2 instance to identify hardware and software issues.

Notice that both the System reachability and Instance reachability checks have passed.

Select the Monitoring tab.

This tab displays CloudWatch metrics for your instance. Currently, there are not many metrics to display because the instance was recently launched.

You can choose a graph to see an expanded view.

Amazon EC2 sends metrics to Amazon CloudWatch for your EC2 instances. Basic (five-minute) monitoring is enabled by default. You can enable detailed (one-minute) monitoring.

Select the Actions menu (in the upper right of the console), choose Monitor and troubleshoot and select Get system log.

Expected output:

Note: If you do not see a system log, wait a couple of minutes and refresh the log screen until it appears.

The System Log displays the console output of the instance, which is a valuable tool for problem diagnosis. It is especially useful for troubleshooting kernel problems and service configuration issues that could cause an instance to terminate or become unreachable before its SSH daemon can be started.

Scroll through the output and note that the httpd package was installed from the user data that you added when you created the instance.

Scroll down to the bottom of the browser window and select Cancel.

Select the for Web Server, then select the Actions menu, choose Monitor and troubleshoot and select Get instance screenshot.

Expected output:

This shows you what your Amazon EC2 instance console would look like if a screen were attached to it.

If you are unable to reach your instance via SSH or RDP, you can capture a screenshot of your instance and view it as an image. This provides visibility as to the status of the instance, and allows for quicker troubleshooting.

Scroll down to the bottom of the browser window and select Cancel.

Congratulations! You have explored several ways to monitor your instance.

Task 3: Update Your Security Group and Access the Web Server

When you launched the EC2 instance, you provided a script that installed a web server and created a simple web page. In this task, you will access content from the web server.

Select the for Web Server, then choose the Details tab.

Copy the Public IPv4 address of your instance to your clipboard.

Open a new tab in your web browser, paste the IP address you just copied, then press Enter.

Consider:

Are you able to access your web server? Why not?

You are not currently able to access your web server because the security group is not permitting inbound traffic on port 80, which is used for HTTP web requests. This is a demonstration of using a security group as a firewall to restrict the network traffic that is allowed in and out of an instance.

To correct this, you will now update the security group to permit web traffic on port 80.

Keep the browser tab open, but return to the EC2 Management Console tab.

In the left navigation pane, select Security Groups.

Select the for the Security group ID with the Security group name Web Server security group.

The security group currently has no rules.

Choose the Inbound rules tab.

Choose Edit inbound rules.

Choose Add rule then configure:

Type: HTTP
Source: Anywhere-IPv4

Choose Save rules .

The new Inbound HTTP rule will create an entry for both IPV4 IP address (0.0.0.0/0) as well as IPV6 IP address (::/0).

Note: using “Anywhere”, or more specifically, using 0.0.0.0/0 or ::/0 is not a recommended best practice for production workloads.

Return to the web server tab that you previously opened and refresh the page.

Expected output:

You should see the message Hello From Your Web Server!

Congratulations! You have successfully modified your security group to permit HTTP traffic into your Amazon EC2 Instance.

Task 4: Resize Your Instance: Instance Type and EBS Volume

As your needs change, you might find that your instance is over-utilized (too small) or under-utilized (too large). If so, you can change the instance type. For example, if a t3.micro instance is too small for its workload, you can change it to an t3.small instance. Similarly, you can change the size of a disk.

STOP YOUR INSTANCE

Before you can resize an instance, you must stop it.

When you stop an instance, it is shut down. There is no charge for a stopped EC2 instance, but the storage charge for attached Amazon EBS volumes remains.

On the EC2 Management Console, in the left navigation pane, choose Instances.

If it is not already selected, select the for Web Server .

Select Instance state , then Stop instance.

Choose Stop .

Your instance will perform a normal shutdown and then will stop running. This may take a couple minutes.

Wait for the Instance State to display: Stopped .

CHANGE THE INSTANCE TYPE

If it is not already selected, select the for Web Server .

Select the Actions menu, select Instance settings and Change instance type, then configure:

Instance type: t3.small

Choose Apply .

When the instance is started again it will be a t3.small, which has twice as much memory as a t3.micro instance.

RESIZE THE EBS VOLUME

In the left navigation pane, select Volumes from the Elastic Block Store section.

Select the volume there.

In the Actions menu, select Modify volume.

The disk volume currently has a size of 8 GiB. You will now increase the size of this disk.

Change the size (GiB) to:

Choose Modify .

Choose Modify to confirm and increase the size of the volume.

START THE RESIZED INSTANCE

You will now start the instance again, which will now have more memory and more disk space.

In left navigation pane, select Instances.

Select the Web Server.

Select Instance state and then Start instance.

Note: An EBS volume being modified goes through a sequence of states: Modifying, Optimizing, and finally Complete.

Congratulations! You have successfully resized your Amazon EC2 Instance. In this task you changed your instance type from t3.micro to a t3.small. You also modified your root disk volume from 8 GiB to 10 GiB.

Task 5: Test Termination Protection

You can delete your instance when you no longer need it. This is referred to as terminating your instance. You cannot connect to or restart an instance after it has been terminated.

In this task, you will learn how to use termination protection.

In left navigation pane, select Instances.

Select the Web Server.

Select Instance state and then Terminate instance.

Choose Terminate .

At this point you see the following error message on top of the page:

Failed to terminate an instance: The instance ‘i-xxxxxxxx’ may not be terminated. Modify its ‘disableApiTermination’ instance attribute and try again.

The above error is expected, and this is a safeguard to prevent the accidental termination of an instance. If you really want to terminate the instance, you will need to disable the termination protection.

Select Actions , choose Instance settings , and Change termination protection.

Unselect Enable.

Choose Save .

You can now terminate the instance.

Refresh the instance console screen.

Select the Web Server

Choose Instance state , and Terminate instance .

Choose Terminate .

Expected output:

The Instance state of the Web Server instance should change to Terminated after about 30 seconds. You may have to refresh the page a few times

Congratulations! You have successfully tested termination protection and terminated your instance.

Conclusion

You have successfully done the following:

Launched a web server with termination protection enabled.
Monitored Your EC2 instance.
Modified the security group that your web server is using to allow HTTP access.
Resized your Amazon EC2 instance to scale.
Tested termination protection.
Terminated your EC2 instance.

End lab

Follow these steps to close the console and end your lab.

Return to the AWS Management Console.

At the upper-right corner of the page, choose AWSLabsUser, and then choose Sign out.

Choose End lab and then confirm that you want to end your lab.

Additional resources

How to Create a Key Pair in AWS

2023-07-13T20:08:00.000+05:30

How to Create a Key Pair in AWS

A key pair is a set of public and private keys that you can use to securely connect to your AWS instances. The public key is a cryptographic code that can be used by anyone to encrypt data, while the private key is a secret code that can be used to decrypt the data.

To create a key pair using the AWS Management Console:

Sign in to the AWS Management Console and open the Amazon EC2 console.
In the navigation pane, under Network & Security, choose Key Pairs.
Choose Create key pair.
In the Create key pair dialog box, enter a name for your key pair and choose the file format. You can choose PEM or PPK for Windows or Linux instances.
Choose Create key pair. The console will download the private key file to your computer. You must save this file in a secure location and never share it with anyone. You will need this file to connect to your instances later.
You can view the public key of your key pair in the console by choosing the key pair name and then choosing View public key.

To create a key pair using the AWS CLI:

Install and configure the AWS CLI on your computer.
Run the following command to create a key pair and save the private key as a file named my-key-pair.pem:

aws ec2 create-key-pair --key-name my-key-pair --query 'KeyMaterial' --output text > my-key-pair.pem

Change the permissions of the private key file to make it read-only for your user:

chmod 400 my-key-pair.pem

You can view the public key of your key pair by running the following command:

aws ec2 describe-key-pairs --key-name my-key-pair --query 'KeyPairs[0].KeyFingerprint'

To create a key pair using the AWS SDKs:

Follow the documentation for your preferred programming language. For example, you can use the Java SDK to create a key pair with the following code:

Java

// Create an EC2 client
AmazonEC2 ec2 = AmazonEC2ClientBuilder.defaultClient();

// Create a key pair request
CreateKeyPairRequest request = new CreateKeyPairRequest();
request.setKeyName("my-key-pair");

// Create a key pair
CreateKeyPairResult result = ec2.createKeyPair(request);

// Get the private key
String privateKey = result.getKeyPair().getKeyMaterial();

// Save the private key to a file
FileOutputStream out = new FileOutputStream("my-key-pair.pem");
out.write(privateKey.getBytes());
out.close();

// Get the public key
String publicKey = result.getKeyPair().getKeyFingerprint();

I hope this is helpful! Let me know if you have any other questions.

How to Create a Security Group with RDP, HTTPS, and SSH in AWS

2023-07-13T20:05:00.004+05:30

How to Create a Security Group with RDP, HTTPS, and SSH in AWS

A security group is a set of firewall rules that control the inbound and outbound traffic for your AWS instances. You can create a security group that allows RDP, HTTPS, and SSH access to your instances by following these steps:

Sign in to the AWS Management Console and open the Amazon EC2 console.
In the navigation pane, under Network & Security, select Security Groups.

Click Create Security Group.

In the Create Security Group dialog box, enter the following information:
- Name: A descriptive name for your security group.
- Description: A brief description of your security group.
- VPC: The VPC that you want to associate your security group with.
Click Add Rule to add a new inbound rule.
- Type: Select RDP from the drop-down list.
- Source: Select My IP to allow only your IP address to access your instances via RDP. Alternatively, you can select Custom and enter a range of IP addresses or a CIDR block.
- Description: (Optional) Enter a description for the rule.
Repeat step 5 to add two more inbound rules for HTTPS and SSH.
- Type: Select HTTPS from the drop-down list.
- Source: Enter 0.0.0.0/0 to allow anyone to access your instances via HTTPS.
- Description: (Optional) Enter a description for the rule.
- Type: Select SSH from the drop-down list.
- Source: Enter your IP address or a range of IP addresses in the Source column to allow SSH access to your instances.
- Description: (Optional) Enter a description for the rule.
Click Create. The console will display the details of your new security group.
To apply the security group to your instances, select the instances that you want to modify and choose Actions, then Networking, then Change security groups. In the Change security groups dialog box, select the security group that you created and choose Assign security groups.

Your security group is now created and applied to your instances. You can now access your instances via RDP, HTTPS, and SSH.

Here are some additional tips for creating security groups:

Use a descriptive name for your security group so that you can easily identify it later.
Be specific when defining the inbound rules for your security group. Only allow inbound traffic from the sources that you need to access your instance.
Use the Source list to control where the inbound traffic is coming from. You can choose to allow traffic from anywhere, from a specific IP address or range of IP addresses, or from a specific VPC.
You can also create outbound rules to control the traffic that your instance can send out to the internet.

AWS Tech Labs

2023-07-12T20:21:00.000+05:30

AWS Tech Labs

AWS Tech Labs is a YouTube channel dedicated to providing free, hands-on labs that help you learn about Amazon Web Services (AWS). Our labs cover a wide range of AWS services and topics, from beginners to advanced users.

We offer a variety of lab formats, including:

Interactive labs: These labs allow you to follow along with a guided tutorial and complete hands-on exercises.

Assessment labs: These labs test your knowledge of AWS concepts with a series of challenges.

Demo labs: These labs give you a live demonstration of an AWS service or feature.

We also offer a variety of other resources to help you learn about AWS, including:

Blog posts: Our blog posts provide in-depth tutorials and articles on AWS topics.

Documentation: Our documentation provides comprehensive reference information on AWS services and features.

Support forums: Our support forums are a great place to ask questions and get help from AWS experts.

Whether you're a beginner or an experienced AWS user, we have the resources you need to learn about AWS and build your skills. Subscribe to our YouTube channel today and start learning!

About Admin

2023-07-12T20:17:00.002+05:30

I,Dhanaseenuvasan, hereby declare that I have completed the AWS Quest Cloud Partitioner badge and the AWS Solution Architecting badge. I have completed all of the requirements for these badges, including completing the corresponding interactive role-playing games, passing the quizzes, and completing the hands-on labs.
I understand that these badges are a valuable credential that demonstrates my knowledge and skills in cloud computing. I am confident that these badges will help me to advance my career in the cloud computing industry.
I have attached screenshots of my badges as proof of completion. (Click Badge to Verify)

Dated: [12/07/2023]

What is CORBA in Distributed computing?

2023-07-09T08:42:00.003+05:30

What is CORBA in Distributed computing?

CORBA stands for Common Object Request Broker Architecture.
It enables software components to communicate with each other regardless of their programming language, operating system, or hardware platform.
CORBA is a middleware platform that provides a way for objects to communicate with each other across a network.

The CORBA architecture consists of four main components:

Object Request Broker (ORB): The ORB is the core of the CORBA architecture. It is responsible for managing the communication between objects, providing location transparency, and supporting the invocation of remote methods.
Interface Definition Language (IDL): The IDL is a language for describing the interfaces of CORBA objects. It is used to define the methods and attributes that are accessible to other objects.
Naming Service: The naming service is a directory service that provides a way for objects to find each other.
Object Adapter: The object adapter is responsible for managing the lifecycle of CORBA objects. It creates objects, destroys objects, and manages the invocation of methods on objects.

CORBA is a powerful tool for building distributed applications.

Advantages of CORBA:

Interoperability: CORBA allows objects to communicate with each other regardless of their programming language, operating system, or hardware platform. This makes it possible to build applications that are composed of objects that are scattered across different machines and written in different languages.
Location transparency: CORBA provides location transparency, which means that objects can be accessed without having to know where they are located. This makes it easier to build distributed applications that are scalable and fault tolerant.
Standardization: CORBA is a standard, which means that there are a number of different implementations available. This makes it easier to find an implementation that meets your specific needs.
Security: CORBA provides a number of security features, such as authentication and encryption. This makes it possible to build secure distributed applications.

Disadvantage of CORBA:

Complexity: CORBA is a complex architecture, which can make it difficult to learn and use.
Deployment complexity: CORBA applications can be difficult to deploy and manage.
Performance: CORBA can be slower than other distributed computing technologies, such as RMI.
Lack of adoption: CORBA is not as widely adopted as other distributed computing technologies, such as REST.

Application of CORBA:

Enterprise applications: CORBA is often used to build enterprise applications that need to be scalable, fault-tolerant, and interoperable. Example: CRM
Telecommunications: CORBA can be used to build billing systems, call routing systems, and network management systems.
Manufacturing: CORBA can be used to build production planning systems, inventory management systems, and quality control systems

HOW TO HOST APPLICATION IN (EC2)BY ENABLING IIS WEB SERVER

2023-07-04T08:30:00.000+05:30

HOW TO HOST APPLICATION IN (EC2)BY ENABLING IIS WEB SERVER

Here are the steps on how to host an application in EC2 by enabling IIS web server:

Launch an EC2 instance with Windows Server. You can choose the latest version of Windows Server 2022.
Once the instance is launched, connect to it using RDP. You can use the public DNS name of your instance to connect to it.
Open Server Manager. You can find it in the Start menu.
In Server Manager, click on Add Roles and Features.
In the Add Roles and Features wizard, select Web Server (IIS) and click Next.
In the Select Features window, select the features that you want to install. For example, you can select Static Content and Dynamic Content.
Click Next and follow the instructions to complete the installation.
Once the installation is complete, you can create a website. To do this, right-click on Sites in the IIS Manager and select Add Website.
In the Add Website window, enter the name of your website and the directory where you want to store the website files.
Click Next and configure the bindings for your website. The binding specifies the IP address and port that your website will listen on.
Click Next and review the settings.
Click Create to create your website.
Once the website is created, you can access it by entering the public DNS name of your instance and the port that you configured for your website in your web browser.

Here are some additional things to keep in mind when hosting an application in EC2 by enabling IIS web server:

You need to make sure that your security group allows traffic to the port that your website is listening on.

I hope this helps!

Video Tutorial

How to Launch Windows EC2 Instance in AWS

2023-07-04T08:27:00.000+05:30

Sure, here are the steps on how to launch a Windows EC2 instance in AWS in detail:
Go to the AWS Management Console and sign in to your account.
In the navigation pane, select EC2.
In the Launch Instance wizard, select Quick Start and then Windows.
For Amazon Machine Image (AMI), select the Windows Server AMI that you want to use.
For Instance Type, select the instance type that you want to use.
For Number of Instances, enter the number of instances that you want to launch.
For Storage, select the storage options that you want to use.
For Networking, select the VPC and subnet that you want to use.
For Security Group, select the security group that you want to use.
For Tags, enter the tags that you want to apply to your instance.
Review the settings and then click Launch.
Once your instance is launched, you can connect to it using Remote Desktop Protocol (RDP).
Here are some additional things to keep in mind when launching a Windows EC2 instance:
You need to make sure that you have a valid AWS key pair. You can create a key pair in the AWS Management Console.
You need to make sure that your security group allows traffic to the ports that you need to access your instance.
You can use a bastion host to access your Windows EC2 instance if you need to connect to it from the internet.
I hope this helps! Let me know if you have any other questions.

Video Tutorial

HOW TO BUILD LOGIN PAGE AND SIGN UP PAGE IN REACT JS AND AWS AMPLIFY

2023-06-30T12:51:00.000+05:30

STEPS TO BUILD LOGIN & SIGNUP PAGE
IN REACTJS,NODEJS USING AWS AMPLIFY IN VS CODE

SOFTWARE REQUIREMENTS

NODE JS
AWS ACCOUNT
VISUAL STUDIO CODE

PLEASE BE FOLLOW THESE STEPS

1. INSTALL NODEJS

2. CHECK VERSION OF NODEJS IN CMD -node --version

3. CREATE AWS ACCOUNT(IF NOT HAVE OR TEMPORARY NEEDED,Dm me BUT,ITS COST)

4. INSTALL VISUAL STUDIO CODE ( install Extension-Live server,AWS Toolkit)

5. RUN THESE COMMAND IN VS CODE TERMINAL-NPM UPDATE-npm install npm -g

6. INSTALL -AWSTOOLKIT EXTENSION IN VSCODE

7. ENABLE SCRIPTING IN VS CODE -Set-ExecutionPolicy -Scope CurrentUser Unrestricted(paste these higlighted cmd in vs code Terminal)

8. RUN THESE CMD IN TERMINAL-npx create-react-app projectname(Procedure)

9. RUN IN VSCODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-amplify configure(AWS ACCOUNT NECESSARY)TO PERFORM THESE CMD

10. RUN IN VSCODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-amplify init

11. RUN IN VS CODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-amplify add auth

12. RUN IN VS CODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-amplify push

13. PASTE THESE PROGRAM IN APP.JS FILE-import React from 'react';

import logo from './logo.svg';

import './App.css';

import { Amplify } from 'aws-amplify';

import awsconfig from './aws-exports';

import "@aws-amplify/ui-react/styles.css";

import {

withAuthenticator,

Button,

Heading,

Image,

View,

Card,

} from "@aws-amplify/ui-react";

Amplify.configure(awsconfig);

function App({ signOut }) {

return (

<Card>

</Card>

</View>

);

}

export default withAuthenticator(App);

14. RUN IN VS CODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-npm install --save aws-amplify @aws-amplify/ui-react

15. RUN IN VS CODE TERMINAL(INSIDE PROJECTNAME DIRECTORY)-npm start

Video Procedure below

ENABLE MULTI-FACTOR AUTHENTICATION IN LOGIN PAGE

2023-06-30T12:49:00.003+05:30

ENABLE MULTI-FACTOR AUTHENTICATION IN LOGIN PAGE

1. Login Into The Amplify Console

2. Setup Amplify Studio

3. Enable Amplify Studio

4. Open Coginito - Choose Userpool,then click SIGN-IN-EXPERIENCE (Scrool Down) And Edit MFA,And Switch To Require MFA,Then Choose Authentication apps and Click SAVE CHANGES

5. Backend Environment-Launch Studio

6. In Authentication -Click MULTI-FACTOR AUTHENTICATION-Choose OPTIONAL and AUTHENTICATION APPLICATION

7. Then ,Click Deploy-Confirm Deployment

8. Copy the cmd and Paste it into the terminal of Visual Studio Code[That File Directory]

9. Again go,Cognito

10. In SIGN-IN-EXPERIENCE-(Scrool Down) And Edit MFA,it shows optional.change To Require MFA,Then Choose Authentication apps and Click SAVE CHANGES

11. Then back to AMPLIFY STUDIO-In Authentication -Click MULTI-FACTOR AUTHENTICATION-Choose ENFORCED and AUTHENTICATION APPLICATION

12. Then ,Click Deploy-Confirm Deployment

13. Copy the cmd and Paste it into the terminal of Visual Studio Code[That File Directory]

AWS Amplify

2023-04-08T18:54:00.002+05:30

AWS Amplify is a development platform provided by Amazon Web Services (AWS) that enables developers to build scalable, secure, and high-performance cloud-powered mobile and web applications. It provides a comprehensive set of tools and services that help developers to build and deploy applications quickly and efficiently, with features such as authentication, analytics, storage, APIs, and more.

AWS Amplify consists of three main components:

1. Amplify CLI: Amplify CLI is a command-line interface tool that allows developers to easily create, configure, and deploy cloud-powered applications and backend services. It provides a simple and intuitive way to create AWS resources such as AWS Lambda, Amazon API Gateway, AWS AppSync, Amazon Cognito, Amazon DynamoDB, and others. Developers can also use the Amplify CLI to manage their AWS resources, including creating and configuring authentication and authorization, storage, and APIs.

2. Amplify Libraries: Amplify Libraries are pre-built libraries and UI components for popular front-end frameworks such as React, Angular, Vue, and Ionic. The libraries provide developers with easy-to-use components that can be used to build applications quickly. These libraries are customizable, extensible, and offer built-in support for key features such as authentication, storage, and APIs.

3. Amplify Console: Amplify Console is a continuous deployment and hosting service for web applications. It provides a simple and intuitive way to build, test, and deploy web applications to AWS. Developers can use Amplify Console to manage their web application's code, deploy it to a cloud-based hosting environment, and monitor its performance.

The core features of AWS Amplify include:

1. Authentication: AWS Amplify provides built-in authentication and authorization features that enable developers to secure their applications with various authentication providers such as Amazon Cognito, OAuth, and Social providers such as Google, Facebook, and Twitter. This feature allows developers to easily manage user sign-up, sign-in, and access control for their applications.

2. Analytics: AWS Amplify provides built-in analytics features that enable developers to track user behavior, application performance, and other important metrics. This feature allows developers to gain insights into their applications and improve their performance.

3. Storage: AWS Amplify provides built-in support for cloud storage with Amazon S3 and Amazon DynamoDB. This feature enables developers to easily store and retrieve files and data from the cloud, providing secure and scalable storage for their applications.

4. APIs: AWS Amplify provides a simple and easy-to-use API feature that enables developers to create and deploy APIs with AWS AppSync or Amazon API Gateway. This feature allows developers to create and manage APIs that are scalable, secure, and easy to use.

5. In summary, AWS Amplify is a powerful development platform that enables developers to build, test, and deploy cloud-powered mobile and web applications quickly and efficiently. With built-in support for authentication, analytics, storage, and APIs, AWS Amplify simplifies the process of developing, deploying, and managing cloud-powered applications.

AWS Toolkit Extension for Visual Studio Code (VS Code)

2023-04-08T18:50:00.001+05:30

AWS Toolkit Extension for Visual Studio Code (VS Code) is a plugin that enables developers to work with Amazon Web Services (AWS) services directly from within the VS Code editor. This extension provides several features and functionalities that can be used to develop, deploy, and debug applications on AWS.

The AWS Toolkit Extension provides a set of tools and functionalities that make it easier for developers to build, test, and deploy serverless applications on AWS. It also provides an integrated development environment (IDE) for developing applications with AWS services, which includes support for AWS Lambda, AWS Step Functions, Amazon API Gateway, Amazon S3, and other AWS services.

Some of the key features and functionalities of the AWS Toolkit Extension for VS Code include:

Ø AWS Explorer: A graphical user interface (GUI) that enables developers to view and manage their AWS resources from within VS Code. Developers can browse and navigate through their AWS accounts, create, update, and delete resources, and view resource details.

Ø AWS CloudFormation: The AWS Toolkit Extension for VS Code provides support for AWS CloudFormation, which is a service that enables developers to define and manage their AWS infrastructure as code. The extension allows developers to create, update, and delete CloudFormation stacks, view stack details, and preview stack changes.

Ø AWS SAM: The AWS Toolkit Extension for VS Code provides support for AWS Serverless Application Model (SAM), which is an open-source framework for building serverless applications on AWS. The extension allows developers to create, test, and deploy SAM applications, view and update application details, and debug SAM applications locally.

Ø AWS Lambda: The AWS Toolkit Extension for VS Code provides support for AWS Lambda, which is a service that enables developers to run code without provisioning or managing servers. The extension allows developers to create, update, and delete Lambda functions, view function details, and test functions locally.

Ø AWS Step Functions: The AWS Toolkit Extension for VS Code provides support for AWS Step Functions, which is a service that enables developers to build serverless workflows using AWS services. The extension allows developers to create, update, and delete Step Functions, view state machine details, and test state machines locally.

In summary, the AWS Toolkit Extension for VS Code provides a comprehensive set of tools and functionalities that enable developers to build, test, and deploy serverless applications on AWS from within the VS Code editor.

HOW TO BUILD REACTJS APPLICATION IN VS CODE

2023-04-07T19:44:00.000+05:30

BUILD REACTJS APPLICATION IN VS CODE

To run React applications, you need to install Node.js. Download and install the latest version of Node.js from the official website.
Install Visual Studio Code: If you haven't already, download and install Visual Studio Code from the official website.
Install the "Create React App" tool: Open a terminal or command prompt and run the following command to install the "Create React App" tool globally:


npm install -g create-react-app

Create a new React project: Open Visual Studio Code and create a new folder where you want to create your React project. Then, open a terminal within VS Code (Terminal > New Terminal) and navigate to the folder you just created. Run the following command to create a new React project:


npx create-react-app my-app

Replace "my-app" with the name of your application. This will create a new React project with all the necessary files and folders.

Open the project in VS Code: Open Visual Studio Code and select "File" > "Open Folder" and select the folder where you created your React project.
Run the development server: In the VS Code terminal, navigate to the project directory by running the following command:


cd my-app

Replace "my-app" with the name of your application. Then, run the following command to start the development server:


npm start

This will start the development server and open your application in your default browser.

Modify the default React component: Open the "src/App.js" file in your code editor and modify the default React component. You can add HTML, CSS, and JavaScript code to create your own user interface.
Create additional components: Create new components by creating new files in the "src" directory. Each component should be a separate file with its own HTML, CSS, and JavaScript code.
Add functionality: Use React to add functionality to your application. You can add event handlers, fetch data from APIs, and update the user interface dynamically.
Test your application: Use the development server to test your application and make sure everything is working correctly.
Build your application: When you're ready to deploy your application, run the following command to build your application for production:


npm run build

This will create a production-ready version of your application in the "build" directory.

Deploy your application: Deploy your application to a web server or hosting service of your choice. You can use services like Netlify, Heroku, or Firebase to deploy your application quickly and easily.

THALAPATHY 67 -POOJAI STILLS

2023-02-01T19:20:00.000+05:30

POOJA VIDEO

#EnNenjilKudiyirukkum

2022-12-25T10:24:00.000+05:30

EnNenjilKudiyirukkum

VarisuFirstSingle

2022-11-03T12:00:00.003+05:30

The much-awaited #VarisuFirstSingle promo is releasing

Today at 6:30 PM 💥

Stay Tuned nanba 🥁

#Thalapathy @actorvijay sir @directorvamshi @iamRashmika @MusicThaman #BhushanKumar #KrishanKumar #ShivChanana @TSeries

#Varisu #VarisuPongal

Varisu Exclusive Posters

2022-10-27T17:34:00.000+05:30

Happy Diwali nanba 🧨

Next week la irundhu summa pattasa irukum 🔥

#VarisuPongal

#Thalapathy @actorvijay sir @directorvamshi @iamRashmika @MusicThaman @KarthikPalanidp @Cinemainmygenes @scolourpencils @vaishnavi141081 #Varisu

Vikram-Aditha Karikalan

2022-09-20T08:05:00.002+05:30

See you tomorrow Trivandrum!! 💝#PonniyinSelvan

From the sets of #Varisu

2022-09-14T12:47:00.002+05:30

From the sets of #Varisu shoot!

@actorvijay @iamRashmika

PONNIYIN SELVAN AUDIO LAUNCH_CLICKS_UHD_PS-1

2022-09-08T20:53:00.000+05:30

UHD STUDIO

shots and Angles

Shot Size Explorer

Extreme Long Shot (ELS)

Camera Angle Explorer

Eye-Level

Psychological Impact Analysis

The Director's Lens

Advanced Visual Storytelling

The Dolly Zoom (Vertigo Effect)

The Long Take ("Oner")

Shallow vs. Deep Focus

Tell.Me.Lies.S01E01.720p.DSNP.WEBRip.x264-GalaxyTV

DOCKER ENGINE

Data Warehouse Architecture in detail

Data Warehouse

Characteristics of a Data Warehouse:

Architecture of Data Warehouse:

Detailed Description of data warehouse Architecture

Advantages of data warehouses:

Disadvantages of data warehouses:

Used for

Example Of Data Warehouse

Launch Your Amazon EC2 Instance labs

How to Create a Key Pair in AWS

How to Create a Key Pair in AWS

How to Create a Security Group with RDP, HTTPS, and SSH in AWS

AWS Tech Labs

AWS Tech Labs

About Admin

Dated: [12/07/2023]

What is CORBA in Distributed computing?

HOW TO HOST APPLICATION IN (EC2)BY ENABLING IIS WEB SERVER

HOW TO HOST APPLICATION IN (EC2)BY ENABLING IIS WEB SERVER

Video Tutorial

How to Launch Windows EC2 Instance in AWS

Video Tutorial

HOW TO BUILD LOGIN PAGE AND SIGN UP PAGE IN REACT JS AND AWS AMPLIFY

STEPS TO BUILD LOGIN & SIGNUP PAGEIN REACTJS,NODEJS USING AWS AMPLIFY IN VS CODE

ENABLE MULTI-FACTOR AUTHENTICATION IN LOGIN PAGE

ENABLE MULTI-FACTOR AUTHENTICATION IN LOGIN PAGE

AWS Amplify

AWS Toolkit Extension for Visual Studio Code (VS Code)

HOW TO BUILD REACTJS APPLICATION IN VS CODE

BUILD REACTJS APPLICATION IN VS CODE

THALAPATHY 67 -POOJAI STILLS

POOJA VIDEO

#EnNenjilKudiyirukkum

EnNenjilKudiyirukkum

VarisuFirstSingle

The much-awaited #VarisuFirstSingle promo is releasing

Today at 6:30 PM 💥

Stay Tuned nanba 🥁

#Thalapathy @actorvijay sir @directorvamshi @iamRashmika @MusicThaman #BhushanKumar #KrishanKumar #ShivChanana @TSeries

#Varisu #VarisuPongal

Varisu Exclusive Posters

Happy Diwali nanba 🧨

Next week la irundhu summa pattasa irukum 🔥

#VarisuPongal

#Thalapathy @actorvijay sir @directorvamshi @iamRashmika @MusicThaman @KarthikPalanidp @Cinemainmygenes @scolourpencils @vaishnavi141081 #Varisu

Vikram-Aditha Karikalan

See you tomorrow Trivandrum!! 💝#PonniyinSelvan

From the sets of #Varisu

From the sets of #Varisu shoot!

@actorvijay @iamRashmika

PONNIYIN SELVAN AUDIO LAUNCH_CLICKS_UHD_PS-1

Candids from the Grand Music & Trailer Launch Event ✨ of #PS1 🗡️

EXCLUSIVE STILLS FROM

LYCA PRODUCTIONS

TRAILERM LYCA PRODUCTIONS

STEPS TO BUILD LOGIN & SIGNUP PAGE
IN REACTJS,NODEJS USING AWS AMPLIFY IN VS CODE

TRAILER

M LYCA PRODUCTIONS