Skip to main content

Amazon Web Services (AWS) Introduction

In This article, you are going to learn about AWS means Amazon Web Services. AWS is the current global leader in Cloud Computing. Getting Started with Amazon Web Service (AWS) is nothing but creating computers in the Cloud. There could be hundreds of virtual machines on one hardware computer running on independently on one another. Amazon Web Services (AWS) calls each of the virtual computers (VM) an instance.


AWS is capable of doing massive things on Cloud. We can create and run one instance or, multiple instances, either independently or together across the world. We can scale these instances up and down in computer power, memory, storage, creating a cache, Creating Databases and the balance loads the across the multiple instances over the availability zones.
To manage all the above services on cloud AWS is providing dashboard called Amazon Management Console, this is where we can control all the services what you want on AWS. Now check the below description for what is AWS and how it’s going to work in the cloud.

What is Amazon Web Services (AWS)

Amazon Web Services (AWS) are a collection of remote services (Also called as web service) offered by the amazon.com over the internet build and run an application. Amazon Web Services (AWS) – robust, scalable and affordable infrastructure for cloud computing.
Amazon Web Service is a cloud computing platform that enables a user to access the on-demand computing services like EC2 virtual Cloud instance(VM), database, storage, virtual Network, etc.
AWS provides the compute, storage and database service quickly provisioning to the IT needs with massive Availability, scalability, Flexibility, Elasticity. AWS is a set of cloud computing services which will available fully on demand.


Benefits of using Amazon Web Services (AWS)

  • Pay-per-use model
You are only charged for disk space, CPU, Memory. That means what type of instance you’re choosing for your use,Time and bandwidth that you use.
  • Instant scalability
Your Service automatically Scales on AWS stack.
  • Reliable/Redundant
Infrequent outages (so far).
Data is redundant in the cloud.
All services have built-in high availability mode.
  • Security
AWS delivers a scalable cloud-computing and All services have built-in Security
A platform that provides customers with end-to-end security and end-to-end privacy.
  • Most services accessed via simple
REST/SOAP API
Libraries are available in all major languages.
Minimal learning curve.
Service Level Agreement (SLA)
SLA between 99.99 and 100% availability, Amazon S3 maintains a durability of 99.99999%
  • Support
AWS provides 24/7 support in the real-time
Operational status of all services around the globe
  • Availability
Availability Zones exist on isolated fault Lines, flood plains, and electrical grids to substantially reduce the chance of Simultaneous failure
Below image will give you good understand about Amazon Web Services (AWS) various types of components.

For getting start with AWS, we have one more good service called AWS free Tier to use most of Amazon Web Services for 12 months of period. The Free Tier service will give you hands-on experience to explore AWS Cloud Services. It is available for every account, and creating a Free Tier account it needs credit card details and also Telephone verification to activate the AWS Free Tier Account.
Conclusion:  I hope this article will help you to understand, What is AWS and how to get start with Amazone Web Service (AWS). Follow the next article for how to create an AWS Free Tier account step by step. If you already have an account with AWS, the next step is to play with Most used service is EC2.

Comments

Post a Comment

Popular posts from this blog

Tomcat - Basic Clustering

Tomcat - Basic Clustering Till now we have 1 tomcat instance running and now we'll learn how to loadbalance multiple tomcat instances. For this let us have another tomcat instance configured first. Go to the  /opt  directory and copy  tomcat8  to  tomcat8-n2 # cp -prv tomcat8 tomcat8-n2 Now we know that we are using some ports for tomcat say 8080, 8005, 8009 For our additional tomcat instance we need to change the ports. If we don't then we might need to experience port conflict I am going to edit  server.xml  config file in the new node and increment the port numbers by 1 # cd /opt/tomcat8-n2/conf/ # vi server.xml 8005 -> 8006 8080 -> 8081 8443 -> 8444 8009 -> 8010 Now you need to add your new Catalina home, base and temp directories First you need to change the  catalina.sh  script and redirect the above 3 variables to the new variables Edit the  catalina.sh  script and add the following lines # vi...

CI-CD_004 - Git with Jenkins

Integrating Git with Jenkins If we are dealing with some specific code based builds where the code doesn't need any modification can be directly used for a build. But in some cases the code need to be changed several times depending on the need. In such case the periodic builds need to have those modifications. We use SCM (Source Code Management) to overcome this situation. And instead of manually copying the code to the build we can integrate the repositories from the SCM tools with our Jenkins builds. Configuration Global Settings In the Configure System page, the Git Plugin provides the following options: Global Config user.name Value: if provided git config user.name is called before builds. This can be overridden by individual projects. Global Config user.email Value: if provided git config user.email is called before builds. This can be overridden by individual projects. Create new accounts base on author/committer's email: if checked, upon parsing of git c...

Troubleshooting Tomcat using Catalina log

Troubleshooting Tomcat using Catalina log We can get the  catalina  logs in  $CATALINA_HOME/logs Here we'll have a  catalina.out We can see some huge info in that log file. If we want to what exactly happens since the start of tomcat then we need to log that into a new file. By default we have log rotation enabled on this logs. For now let us stop tomcat and nullify the catalina.out file and then start tomcat to have some new info in the catalina.out # service tomcat stop # cd $CATALINA_HOME/logs # :> catalina.out (or) cat /dev/null > catalina.out # ll catalina.out -rw-r----- 1 root root 0 Feb 18 16:19 catalina.out # service tomcat start # ll catalina.out -rw-r----- 1 root root 17341 Feb 18 16:21 catalina.out We can see the log being written after the start of tomcat. Now we can notice the instance giving some information about the starting of tomcat, about the configuration for the startup, path of the servlet instance for which the log is re...