Amazon Web Services (AWS) is Amazon’s cloud web hosting platform that provides flexible, reliable, scalable, easy-to-use, and cost-effective solutions. This study notes covers different important topics illustrating how AWS works and how it is beneficial to run your website on Amazon Web Services.
This study notes is prepared for learners who want to learn how Amazon Web Services works to provide reliable, flexible, and cost-effective cloud computing services.
To benefit from this study notes, you should have the desire to understand how Amazon Web Services can assist you scale your cloud computing services.
In 2006, Amazon Web Services (AWS) started to provide IT services to the market in the form of web services, which is currently known as cloud computing. With this cloud, we need not plan for servers and other IT infrastructure which takes up much of time in advance. Instead, these services can instantly spin up hundreds or thousands of servers in minutes and deliver results faster and smoother. We pay only for what we use with no up-front expenses and no long-term commitments, which makes AWS cost efficient.
Today, AWS provides a highly reliable, scalable, low-cost infrastructure platform in the cloud that powers multitude of businesses in around 190 countries around the world.
Cloud computing is an internet-based computing service in which large groups of remote servers are networked to permit centralized data storage, and online access to computer services or resources.
Using cloud computing, organizations can use shared computing and storage resources rather than building, operating, and improving infrastructure on their own.
Cloud computing is a model that enables features as given below.
Users can provision and release resources on-demand.
Resources can be scaled up or down automatically, as per load.
Resources are accessible over a network with proper maintained security.
Cloud service providers can enable a pay-as-you-go model, where clients are charged based on the type of resources and per usage.
There are three types of clouds − Public, Private, and Hybrid cloud.
In public cloud, the third-party service providers make resources and services available to their clients via Internet. client’s data and related security is with the service providers’ owned infrastructure.
A private cloud also offers almost similar features as public cloud, but the data and services are managed by the organization or by the third party only for the client’s organization. In this type of cloud, major control is over the infrastructure so security related issues are minimized.
A hybrid cloud is the combination of both private and public cloud. The decision to run on private or public cloud usually depends on different parameters like sensitivity of data and applications, industry certifications and required standards, regulations, etc.
There are three types of service models in cloud − IaaS, PaaS, and SaaS.
IaaS stands for Infrastructure as a Service. It offers users with the capability to provision processing, storage, and network connectivity on demand. Using this service model, the clients can develop their own applications on these resources.
PaaS stands for Platform as a Service. Here, the service provider provides various services like databases, queues, workflow engines, e-mails, etc. to their clients. The client can then use these components for building their own applications. The services, availability of resources and data backup are handled by the service provider that assists the customers to focus more on their application's functionality.
SaaS stands for Software as a Service. As the name suggests, here the third-party providers provide end-user applications to their clients with some administrative capability at the application level, such as the ability to create and manage their users. Also some level of customizability is possible such as the clients can use their own corporate logos, colors, etc.
Here is a list of some of the most significant advantages that Cloud Computing has to offer −
Cost-Efficient − Building our own servers and tools is time-consuming as well as expensive as we need to order, pay for, install, and configure expensive hardware, long before we need it. However, using cloud computing, we only pay for the amount we use and when we use the computing resources. In this way, cloud computing is cost efficient.
Reliability − A cloud computing platform offers much more managed, reliable and consistent service than an in-house IT infrastructure. It guarantees 24x7 and 365 days of service. If any of the server fails, then hosted applications and services can easily be transited to any of the available servers.
Unlimited Storage − Cloud computing offers almost unlimited storage capacity, i.e., we need not worry about running out of storage space or increasing our current storage space availability. We can access as much or as little as we need.
Backup & Recovery − Storing data in the cloud, backing it up and restoring the same is relatively easier than storing it on a physical device. The cloud service providers also have enough technology to recover our data, so there is the convenience of recovering our data anytime.
Easy Access to Information − Once you register yourself in cloud, you can access your account from anywhere in the universe provided there is internet connection at that point. There are different storage and security facilities that vary with the account type chosen.
Although Cloud Computing offers a wonderful set of advantages, it has some drawbacks as well that often raise questions about its efficiency.
Security is the great issue in cloud computing. The cloud service providers implement the best security standards and industry certifications, however, storing data and significant files on external service providers always bears a risk.
AWS cloud infrastructure is designed to be the most flexible and secured cloud network. It offers scalable and highly reliable platform that enables clients to deploy applications and data quickly and securely.
As cloud service providers offer services to number of clients each day, sometimes the system can have some serious problems leading to business processes temporarily being suspended. Additionally, if the internet connection is offline then we will not be able to access any of the applications, server, or data from the cloud.
Cloud service providers promises vendors that the cloud will be flexible to use and integrate, however switching cloud services is not easy. Most organizations may find it difficult to host and integrate current cloud applications on another platform. Interoperability and support issues may arise such as applications developed on Linux platform may not work properly on Microsoft Development Framework (.Net).
This is the fundamental structure of AWS EC2, where EC2 stands for Elastic Compute Cloud. EC2 permit users to use virtual machines of various configurations as per their requirement. It permits various configuration options, mapping of individual server, various pricing options, etc. We will discuss these in detail in AWS Products chapter. Following is the diagrammatic representation of the architecture.
Note − In the above figure S3 stands for Simple Storage Service. It permits the users to store and retrieve various types of data using API calls. It doesn’t contain any computing element. We will discuss this topic in detail in AWS products chapter.
Load balancing simply means to hardware or software load over web servers, that improver's the efficiency of the server as well as the application. Following is the diagrammatic representation of AWS architecture with load balancing.
Hardware load balancer is a very common network appliance utilized in traditional web application architectures.
AWS offers the Elastic Load Balancing service, it distributes the traffic to EC2 instances across multiple available sources, and dynamic addition and removal of Amazon EC2 hosts from the load-balancing rotation.
Elastic Load Balancing can dynamically grow and shrink the load-balancing capacity to adjust to traffic demands and also support sticky sessions to address more advanced routing needs.
It is responsible for content delivery, i.e. used to deliver website. It may contain dynamic, static, and streaming content using a global network of edge locations. Requests for content at the user's end are automatically routed to the nearest edge location, which improves the performance.
Amazon Cloud-front is optimized to work with other Amazon Web Services, like Amazon S3 and Amazon EC2. It also works fine with any non-AWS origin server and stores the original files in a same way.
In Amazon Web Services, there are no contracts or monthly commitments. We pay only for as much or as little content as we deliver through the service.
It is utilized to spread the traffic to web servers, which improves performance. AWS provides the Elastic Load Balancing service, in which traffic is distributed to EC2 instances over multiple available zones, and dynamic addition and removal of Amazon EC2 hosts from the load-balancing rotation.
Elastic Load Balancing can dynamically grow and shrink the load-balancing capacity as per the traffic conditions.
Amazon’s Elastic Compute Cloud (EC2) offers a feature called security groups, which is similar to an inbound network firewall, in which we have to specify the protocols, ports, and source IP ranges that are permitted to reach your EC2 instances.
Each EC2 instance can be assigned one or more security groups, each of which routes the appropriate traffic to each instance. Security groups can be configured using specific subnets or IP addresses which limits access to EC2 instances.
Amazon Elastic Cache is a web service that manages the memory cache in the cloud. In memory management, cache has a very significant role and assists to reduce the load on the services, improves the performance and scalability on the database tier by caching frequently used information.
Amazon RDS (Relational Database Service) provides a same access as that of MySQL, Oracle, or Microsoft SQL Server database engine. The same queries, applications, and tools can be utilized with Amazon RDS.
It automatically patches the database software and manages backups as per the user’s instruction. It also supports point-in-time recovery. There are no up-front investments needed, and we pay only for the resources we use.
Amazon RDS permits users to install RDBMS (Relational Database Management System) of your choice like MySQL, Oracle, SQL Server, DB2, etc. on an EC2 instance and can manage as needed.
Amazon EC2 uses Amazon EBS (Elastic Block Storage) similar to network-attached storage. All data and logs running on EC2 instances should be placed on Amazon EBS volumes, which will be available even if the database host fails.
Amazon EBS volumes automatically offer redundancy within the availability zone, which increases the availability of simple disks. Further if the volume is not sufficient for our databases needs, volume can be added to increase the performance for our database.
Using Amazon RDS, the service provider manages the storage and we only focus on managing the data.
AWS cloud provides various options for storing, accessing, and backing up web application data and assets. The Amazon S3 (Simple Storage Service) offers a simple web-services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web.
Amazon S3 stores data as objects within resources called buckets. The user can store as many objects as per requirement within the bucket, and can read, write and delete objects from the bucket.
Amazon EBS is effective for data that needs to be accessed as block storage and requires persistence beyond the life of the running instance, such as database partitions and application logs.
Amazon EBS volumes can be maximized up to 1 TB, and these volumes can be striped for larger volumes and increased performance. Provisioned IOPS volumes are designed to meet the requirments of database workloads that are sensitive to storage performance and consistency.
Amazon EBS currently supports up to 1,000 IOPS per volume. We can stripe different volumes together to deliver thousands of IOPS per instance to an application.
The difference between AWS cloud architecture and the traditional hosting model is that AWS can dynamically scale the web application fleet on demand to handle changes in traffic.
In the traditional hosting model, traffic forecasting models are normally used to provision hosts ahead of projected traffic. In AWS, instances can be provisioned on the fly according to a set of triggers for scaling the fleet out and back in. Amazon Auto Scaling can create capacity groups of servers that can grow or shrink on demand.
Following are some of the key considerations for web hosting −
In AWS, network devices like firewalls, routers, and load-balancers for AWS applications no longer reside on physical devices and are replaced with software solutions.
Multiple options are available to ensure quality software solutions. For load balancing choose Zeus, HAProxy, Nginx, Pound, etc. For establishing a VPN connection choose OpenVPN, OpenSwan, Vyatta, etc.
AWS provides a more secured model, in which every host is locked down. In Amazon EC2, security groups are created for each type of host in the architecture, and a large variety of straight and tiered security models can be created to enable minimum access among hosts within your architecture as per requirement.
EC2 instances are easily available at most of the availability zones in AWS region and provides model for deploying your application across data centers for both high availability and reliability.
AWS Management Console is a web application for managing Amazon Web Services. AWS Management Console consists of list of different services to choose from. It also offers all information related to our account like billing.
This console offers an inbuilt user interface to perform AWS tasks like working with Amazon S3 buckets, launching and connecting to Amazon EC2 instances, setting Amazon CloudWatch alarms, etc.
Following is the screenshot of AWS management console for Amazon EC2 service.
Step 1 − Click on services. We get a list of different services.
Step 2 − Select the options from the list of categories and we get their sub-categories such as Computer and Database category is selected in the following screenshots.
Step 3 − Select the service of your option and the console of that service will open.
Click the Edit menu on the navigation bar and a list of services appears. We can create their shortcuts by simply dragging them from the menu bar to the navigation bar.
When we drag the service from the menu bar to the navigation bar, the shortcut will be created and added. We can also arrange them in any order. In the following screenshot we have created shortcut for S3, EMR and DynamoDB services.
To delete the shortcut, click the edit menu and drag the shortcut from the navigation bar to the service menu. The shortcut will be removed. In the following screenshot, we have removed the shortcut for EMR services.
Many of the services are region specific and we have to select a region so that resources can be managed. Some of the services do not require a region to be selected like AWS Identity and Access Management (IAM).
To select a region, first we have to select a service. Click the Oregon menu (on the left side of the console) and then select a region
We can change password of our AWS account. To change the password, following are the steps.
Step 1 − Click the account name on the left side of the navigation bar.
Step 2 − Choose Security Credentials and a new page will open having differnt options. Select the password option to change the password and follow the instructions.
Step 3 − After signing-in, a page opens again having certain options to change the password and follow the instructions.
When successful, we will receive a confirmation message.
Click the account name in the navigation bar and select the 'Billing & Cost Management' choice.
Now a new page will open having all the information related to money section. Using this service, we can pay AWS bills, monitor our usage and budget estimation.
The AWS Console mobile app, offered by Amazon Web Services, permits its users to see resources for select services and also supports a limited set of management functions for select resource types.
Following are the different services and supported functions that can be accessed using the mobile app.
To have access to the AWS Mobile App, we must have an existing AWS account. Simply create an identity utilizing the account credentials and select the region in the menu. This app permits us to stay signed in to multiple identities at the same time.
For security reasons, it is necessary to secure the device with a passcode and to use an IAM user's credentials to log in to the app. In case the device is lost, then the IAM user can be deactivated to prevent unauthorized access.
Root accounts cannot be deactivated via mobile console. While using AWS Multi-Factor Authentication (MFA), it is recommended to use either a hardware MFA device or a virtual MFA on a separate mobile device for account security reasons.
The latest version is 1.14. There is a feedback link in the App's menu to share our experiences and for any queries.
Following are the steps to access AWS services −
Amazon offers a fully functional free account for one year for users to use and learn the various components of AWS. You get access to AWS services like EC2, S3, DynamoDB, etc. for free. However, there are certain limitations based on the resources consumed.
Step 1 − To create an AWS account, open this link https://aws.amazon.com and sign-up for new account and enter the required details.
If we already have an account, then we can sign-in utilizing the existing AWS password.
Step 2 − After providing an email-address, fill this form. Amazon uses this information for billing, invoicing and identifying the account. After creating the account, sign-up for the services needed.
Step 3 − To sign-up for the services, enter the payment information. Amazon executes a minimal amount transaction against the card on the file to check that it is valid. This charge varies with the region.
Step 4 − Next, is the identity verification. Amazon does a call back to verify the provided contact number.
Step 5 − Choose a support plan. Subscribe to one of the plans like Basic, Developer, Business, or Enterprise. The basic plan costs nothing and has limited resources, which is good to get familiar with AWS.
Step 6 − The final step is confirmation. Click the link to login again and it redirects to AWS management console.
Now the account is created and can be utilized to avail AWS services.
AWS assigns two unique IDs to each AWS account.
It is a 12-digit number like 123456789000 and is utilized to construct Amazon Resource Names (ARN). This ID assists to distinguish our resources from resources in other AWS accounts.
To know the AWS account number, click Support on the upper right side of the navigation bar in AWS management console as given in the following screenshot.
It is a long string of alphanumeric characters like 1234abcdef1234. This ID is utilized in Amazon S3 bucket policy for cross-account access, i.e. to access resources in another AWS account.
Account alias is the URL for your sign-in page and contains the account ID by default. We can customize this URL with the company name and even overwrite the previous one.
Step 1 − Sign in to the AWS management console and open the IAM console using the following link https://console.aws.amazon.com/iam/
Step 2 − Select the customize link and create an alias of choice.
Step 3 − To delete the alias, click the customize link, then click the Yes, Delete button. This deletes the alias and it reverts to the Account ID.
Multi Factor Authentication (MFA) offers additional security by authenticating the users to enter a unique authentication code from an approved authentication device or SMS text message when they access AWS websites or services. If the MFA code is correct, then only the user can access AWS services or else not.
To use MFA services, the user has to assign a device (hardware or virtual) to IAM user or AWS root account. Each MFA device assigned to the user must be unique, i.e. the user cannot enter a code from another user's device to authenticate.
Step 1 − Open the following link, https://console.aws.amazon.com/iam/
Step 2 − On the web page, choose users from the navigation pane on the right side to view the list of user name.
Step 3 − Scroll down to security credentials and choose MFA. Click activate MFA.
Step 4 − Follow the instructions and the MFA device will get activated with the account.
There are 3 ways to enable a MFA device −
In this way, MFA requires us to configure the IAM user with the phone number of the user's SMS-compatible mobile device. When the user signs in, AWS sends a six-digit code by SMS text message to the user's mobile device. The user is required to enter the same code on a second web page during sign-in to authenticate the right user. This SMS-based MFA cannot be used with AWS root account.
In this way, MFA requires us to assign an MFA device (hardware) to the IAM user or the AWS root account. The device generates a six-digit numeric code based upon a time synchronized one-time password algorithm. The user has to enter the same code from the device on a second web page during sign-in to authenticate the right user.
In this way, MFA requires us to assign an MFA device (virtual) to the IAM user or the AWS root account. A virtual device is a software application (mobile app) running on a mobile device that emulates a physical device. The device generates a six-digit numeric code based upon a time-synchronized one-time password algorithm. The user has to enter the same code from the device on a second web page during sign-in to authenticate the right user.
IAM is a user entity which we create in AWS to represent a person that uses it with limited access to resources. Hence, we do not have to use the root account in our day-to-day activities as the root account has unrestricted access to our AWS resources.
Step 1 − Open the link https://console.aws.amazon.com/iam/ to sign-in to AWS Management console.
Step 2 − Select the Users option on the left navigation pane to open the list of all users.
Step 3 − We can also create New Users using the Create New Users option, a new window will open. Enter the user-name which we want to create. Select the create option and a new user will be created.
Step 4 − We can also see Access Key IDs and secret keys by selecting Show Users Security Credentials link. We can also save these details on the computer using the Download Credentials option.
Step 5 − We can manage the user’s own security credentials like creating password, managing MFA devices, managing security certificates, creating/deleting access keys, adding user to groups, etc.
There are many more features that are optional and are available on the web page.
Amazon EC2 (Elastic Compute Cloud) is a web service interface that gives resizable compute capacity in the AWS cloud. It is designed for developers to have complete control over web-scaling and computing resources.
EC2 instances can be resized and the number of instances scaled up or down as per our need. These instances can be launched in one or more geographical locations or regions, and Availability Zones (AZs). Each region comprises of several AZs at distinct locations, connected by low latency networks in the same region.
In AWS EC2, the users need to aware about the EC2 components, their operating systems support, security measures, pricing structures, etc.
Amazon EC2 supports multiple OS in which we have to pay additional licensing fees like: Red Hat Enterprise, SUSE Enterprise and Oracle Enterprise Linux, UNIX, Windows Server, etc. These OS needs to be implemented in conjunction with Amazon Virtual Private Cloud (VPC).
Users have finish control over the visibility of their AWS account. In AWS EC2, the security systems allow create groups and place running instances into it as per the requirement. You can specify the groups with which other groups may communicate, as well as the groups with which IP subnets on the Internet may talk.
AWS offers a variety of pricing options, depending on the type of resources, types of applications and database. It permits the users to configure their resources and compute the charges accordingly.
Amazon EC2 permits the users to access its resources to design fault-tolerant applications. EC2 also comprises geographic regions and isolated locations known as availability zones for fault tolerance and stability. It doesn’t share the exact locations of regional data centers for security reasons.
When the users launch an instance, they need to select an AMI that's in the same region where the instance will run. Instances are distributed across multiple availability zones to provide continuous services in failures, and Elastic IP (EIPs) addresses are used to quickly map failed instance addresses to concurrent running instances in other zones to avoid delay in services.
This service permits the users to move existing applications into EC2. It costs $80.00 per storage device and $2.49 per hour for data loading. This service suits those users having large amount of data to move.
Here is a list of some of the prominent features of EC2 −
Reliable − Amazon EC2 offers a highly reliable environment where replacement of instances is rapidly possible. Service Level Agreement commitment is 99.9% availability for every Amazon EC2 region.
Designed for Amazon Web Services − Amazon EC2 works fine with Amazon services like Amazon S3, Amazon RDS, Amazon DynamoDB, and Amazon SQS. It gives a complete solution for computing, query processing, and storage across a wide range of applications.
Secure − Amazon EC2 works in Amazon Virtual Private Cloud to provide a secure and robust network to resources.
Flexible Tools − Amazon EC2 provides the tools for developers and system administrators to build failure applications and isolate themselves from common failure situations.
Inexpensive − Amazon EC2 wants us to pay only for the resources that we use. It includes multiple purchase plans such as On-Demand Instances, Reserved Instances, Spot Instances, etc. which we can choose as per our need.
Step 1 − Sign-in to AWS account and open IAM console by using the following link https://console.aws.amazon.com/iam/.
Step 2 − In the navigation Panel, create/view groups and follow the instructions.
Step 3 − Create IAM user. Choose users in the navigation pane. Then create new users and add users to the groups.
Step 4 − Create a Virtual Private Cloud using the following instructions.
Open the Amazon VPC console by using the following link − https://console.aws.amazon.com/vpc/
Select VPC from the navigation panel. Then select the same region in which we have created key-pair.
Select start VPC wizard on VPC dashboard.
Select VPC configuration page and make sure that VPC with single subnet is selected. The choose Select.
VPC with a single public subnet page will open. Enter the VPC name in the name field and leave different configurations as default.
Select create VPC, then select Ok.
Step 5 − Create WebServerSG security groups and add rules using the following instructions.
On the VPC console, select security groups in the navigation panel.
Select create security group and fill the required details like group name, name tag, etc.
Select your VPC ID from the menu. Then select yes, create button.
Now a group is created. Select the edit option in the inbound rules tab to create rules.
Step 6 − Launch EC2 instance into VPC using the following instructions.
Open EC2 console by using the following link − https://console.aws.amazon.com/ec2/
Select launch instance option in the dashboard.
A new page will open. Choose Instance Type and provide the configuration. Then select Next: Configure Instance Details.
A new page will open. Select VPC from the network list. Select subnet from the subnet list and leave the other settings as default.
Click Next until the Tag Instances page appears.
Step 7 − On the Tag Instances page, give a tag with a name to the instances. Select Next: Configure Security Group.
Step 8 − On the Configure Security Group page, choose the Select an existing security group option. Select the WebServerSG group that we created previously, and then choose Review and Launch.
Step 9 − Check Instance details on Review Instance Launch page then click the Launch button.
Step 10 − A pop up dialog box will open. Select an existing key pair or create a new key pair. Then select the acknowledgement check box and click the Launch Instances button.
As the name suggests, auto scaling permits you to scale your Amazon EC2 instances up or down automatically as per the instructions set by the user. Parameters like minimum and maximum number of instances are set by the user. Using this, the number of Amazon EC2 instances you’re using increases automatically as the demand rises to maintain the performance, and decreases automatically as the demand decreases to minimize the cost.
Auto Scaling is particularly effective for those applications that fluctuate on hourly, daily, or weekly usage. Auto Scaling is enabled by Amazon CloudWatch and is available at no other cost. AWS CloudWatch can be used to measure CPU utilization, network traffic, etc.
Elastic Load Balancing (ELB) automatically distributes incoming request traffic across multiple Amazon EC2 instances and results in achieving higher fault tolerance. It detects unfit instances and automatically reroutes traffic to fit instances until the unfit instances have been restored in a round-robin manner. However, if we need more complex routing algorithms, then choose different services like Amazon Route53.
ELB consists of the following three components.
This includes monitoring and handling the requests incoming through the Internet/intranet and distributes them to EC2 instances registered with it.
This includes automatically scaling of handling capacity in response to incoming traffic by adding and removing load balancers as need. It also performs fitness check of instances.
ELB gives SSL termination that saves precious CPU cycles, encoding and decoding SSL within your EC2 instances attached to the ELB. An X.509 certificate is required to be configured within the ELB. This SSL connection in the EC2 instance is not required, we can also terminate it.
Following are the most prominent features of ELB −
ELS is designed to handle unlimited requests per second with gradually increasing load pattern.
We can configure EC2 instances and load balancers to accept traffic.
We can add/remove load balancers as per requirement without affecting the overall flow of information.
It is not designed to handle sudden increase in requests like online exams, online trading, etc.
Clients can enable Elastic Load Balancing within a single Availability Zone or across multiple zones for even more consistent application performance.
Step 1 − Go to Amazon EC2 console using this link − https://console.aws.amazon.com/ec2/.
Step 2 − Select your load balancer region from the region menu on the right side.
Step 3 − Select Load Balancers from the navigation pane and choose Create Load Balancer option. A pop-up window will open and we need to provide the required details.
Step 4 − In load Balancer name box: Enter name of your load balancer.
Step 5 − In create LB inside box: Select the same network which you have selected for instances.
Step 6 − Select Enable advanced VPC configuration, if selected default VPC.
Step 7 − Click the Add button and a new pop-up will appear to select subnets from the list of available subnets as shown in the following screenshot. Select only one subnet per availability zone. This window will not appear if we do not select Enable advanced VPC configuration.
Step 8 − Choose Next; a pop-up window will open. After selecting a VPC as your network, assign security groups to Load Balancers.
Step 9 − Follow the instructions to assign security groups to load balancers and click Next.
Step 10 − A new pop-up will open having health checkup configuration details with default values. Values can be set on our own, however these are optional. Click on Next: Add EC2 Instances.
Step 11 − A pop-up window will open having information about instances like registered instances, add instances to load balancers by selecting ADD EC2 Instance option and fill the information required. Click Add Tags.
Step 12 − Adding tags to your load balancer is not required. To add tags click the Add Tags Page and fill the details such as key, value to the tag. Then choose Create Tag option. Click Review and Create button.
A review page opens on which we can verify the setting. We can even change the settings by choosing the edit link.
Step 13 − Click Create to create your load balancer and then click the Close button.
Step 1 − Go to Amazon EC2 console using this link − https://console.aws.amazon.com/ec2/.
Step 2 − Choose Load Balancers option from the navigation pane.
Step 3 − Select Load balancer and click the Action button.
Step 4 − Click the Delete button. An alert window will appear, click the Yes, Delete button.
Amazon WorkSpaces is a fully managed desktop computing service in the cloud that permits its customers to give cloud-based desktops to their end-users. Through this the end users can access the documents, applications, and resources using devices of their choice such as laptops, iPad, Kindle Fire, or Android tablets. This service was launched to meet its clients rising demand for Cloud based 'Desktop as a Service' (DaaS).
Each WorkSpace is a persistent Windows Server 2008 R2 instance that looks like Windows 7, hosted on the AWS cloud. Desktops are streamed to users via PCoIP and the data backed up will be taken on every 12 hours by default.
An Internet connection with TCP and UDP open ports is needed at the user’s end. They have to download a free Amazon WorkSpaces client application for their device.
Step 1 − Create and configure the VPC. (This we will discuss in detail in the VPC section.)
Step 2 − Create an AD Directory using the following steps.
Use the following link to open Amazon WorkSpace Console − https://console.aws.amazon.com/workspaces/
Select Directories, then Setup Directory in the navigation panel.
A new page will open. Select Create Simple AD button, then fill the required details.
In VPC area, fill the VPC details and go to Next step.
A review page will open to review the information. Make changes if incorrect, then click the Create Simple AD button.
Step 3 − Create a WorkSpace using the following steps.
Use the following link to open Amazon WorkSpace Console − https://console.aws.amazon.com/workspaces/
Select Workspaces and then launch WorkSpaces option in the navigation panel.
Select the cloud directory. Enable/disable WorkDocs for all users in this directory, then click the Yes, Next button.
A new page will open. Fill the details for the new user and select the Create Users button. Once the user is added to the WorkSpace list, select Next.
Enter the number of bundles required in the value field of WorkSpaces Bundles page, then select Next.
A review page will open. Check the details and make changes if needed. Select Launch WorkSpaces.
There will be a message to confirm the account, after which we can use WorkSpaces.
Step 4 − Test your WorkSpaces using the following steps.
Download and install the Amazon WorkSpaces client application using the following link − https://clients.amazonworkspaces.com/.
Run the application. For the first time, we have to to enter the registration code received in email and click Register.
Connect to the WorkSpace by entering the user name and password for the user. Select Sign In.
Now WorkSpace desktop is shown. Open this link http://aws.amazon.com/workspaces/ on THE web browser. Navigate and verify that the page can be viewed.
A message saying “Congratulations! Your Amazon WorkSpaces cloud directory has been created, and your first WorkSpace is working correctly and has Internet access” will be received.
This AWS WorkSpaces feature verifies if the network and Internet connections are working, checks if WorkSpaces and their associated registration services are accessible, checks if the port 4172 is open for UDP and TCP access or not.
This AWS WorkSpaces feature permits the users to access to their WorkSpace without entering their credentials every time when they disconnect. The application installed at the client’s device saves an access token in a secure store, which is valid for 12 hours and uses to authenticate the right user. Users click on the Reconnect button on the application to get access on their WorkSpace. Users can disable this feature any time.
This AWS WorkSpaces feature allows the client to resume a session that was disconnected due to any reason in network connectivity within 20 minutes (by default and can be extended for 4 hours). Users can disable this feature any time in group policy area.
This feature permits Administrators to search for WorkSpaces by their user name, bundle type, or directory.
Easy to set up − Clients can choose AWS WorkSpaces plans of their choice and provide requirements such as CPU type, memory, storage and applications, and number of desktops.
Choice of devices and applications − Clients can install Amazon WorkSpace application on their device (Laptops, iPads, Tablets) free of cost and can choose applications from the available list.
Cost-effective − Amazon WorkSpaces require no upfront commitment and the customers pay as they customize their desktop, on a monthly basis.
AWS Lambda is a responsive cloud service that inspects actions within the application and responds by deploying the user-defined codes, called as functions. It automatically manages the compute resources across multiple availability zones and scales them when new actions are triggered.
AWS Lambda supports the code written in Java, Python and Node.js, and the service can launch processes in languages supported by Amazon Linux (includes Bash, Go & Ruby).
Following are some recommended tips while using AWS Lambda.
Write your Lambda function code in a stateless style.
Never declare any function variable outside the scope of the handler.
Make sure to have a set of +rx permissions on your files in the uploaded ZIP to ensure Lambda can execute code on your behalf.
Delete old Lambda functions when no longer needed.
Follow these steps to configure AWS Lambda for the first time.
Step 1 − Sign in to AWS account.
Step 2 − Select Lambda from AWS services section.
Step 3 − Select a Blueprint (not required) and click the Skip button.
Step 4 − Give the necessary details to create a Lambda function as shown in the following screenshot and paste the Node.js code that will be triggered automatically whenever a new item is added in DynamoDB. Select all the needed permissions.
Step 5 − Click the Next button and verify your details.
Step 6 − Click the Create Function button.
Now, when we select the Lambda service and select the Event Sources tab, there will be no records. Add at least one source to the Lambda function to work. Here, we are adding DynamoDB Table to it.
We have created a table using DynamoDB (we will discuss this in detail in DynamoDB section).
Step 7 − Select the stream tab and associate it with the Lambda function.
You will see this entry in Event Sources Tab of Lambda Service page.
Step 8 − Add some entries into the table. When the entry gets added and saved, then Lambda service should trigger the function. It can be verified using the Lambda logs.
Step 9 − To view logs, select the Lambda service and click the Monitoring tab. Then click the View Logs in CloudWatch.
Following are some of the benefits of using Lambda tasks −
Lambda tasks need not to be registered like Amazon SWF activity types.
We can use any existing Lambda functions that you’ve already defined in workflows.
Lambda functions are called directly by Amazon SWF; there is no need design a program to implement and execute them.
Lambda provides us the metrics and logs for tracking function executions.
Following are the three types of Lambda limits.
The throttle limit is 100 concurrent Lambda function executions per account and is applied to the total concurrent executions across all functions within a same region.
The formula to calculate the number of concurrent executions for a function = (average duration of the function execution) X (number of requests or events processed by AWS Lambda).
When throttle limit is reached, then it returns a throttling error having an error code 429. After 15-30 minute you can start work again. The throttle limit can be increased by contacting AWS support center.
The following table shows the list of resources limits for a Lambda function.
|Ephemeral disk capacity ("/tmp" space)||512 MB|
|Number of file descriptors||1,024|
|Number of processes and threads (combined total)||1,024|
|Maximum execution duration per request||300 seconds|
|Invoke request body payload size||6 MB|
|Invoke response body payload size||6 MB|
The following table shows the list of services limits for deploying a Lambda function.
|Lambda function deployment package size (.zip/.jar file)||50 MB|
|Size of code/dependencies that you can zip into a deployment package (uncompressed zip/jar size)||250 MB|
|Total size of all the deployment packages that can be uploaded per region||1.5 GB|
|Number of unique event sources of the Scheduled Event source type per account||50|
|Number of unique Lambda functions you can connect to each Scheduled Event||5|
For latest updated limit structure & more information, visit − https://docs.aws.amazon.com/lambda/latest/dg/limits.html/ .
Amazon Virtual Private Cloud (VPC) permits the users to use AWS resources in a virtual network. The users can customize their virtual networking environment as they like, such as selecting own IP address range, creating subnets, and configuring route tables and network gateways.
The list of AWS services that can be used with Amazon VPC are −
Following are the steps to create VPC.
Step 1 − Open the Amazon VPC console by using the following link − https://console.aws.amazon.com/vpc/
Step 2 − Select creating the VPC option on the right side of the navigation bar. Make sure that the same region is chhosen as for other services.
Step 3 − Click the start VPC wizard option, then click VPC with single public subnet option on the left side.
Step 4 − A configuration page will open. Fill in the details like VPC name, subnet name and leave the other fields as default. Click the Create VPC button.
Step 5 − A dialog box will open, showing the work in progress. When it is finished, select the OK button.
The Your VPCs page opens which shows a list of available VPCs. The setting of VPC can be changed here.
Step 1 − Open the Amazon VPC console by using the following link − https://console.aws.amazon.com/vpc/
Step 2 − Select the security groups option in the navigation bar, then choose create security group option.
Step 3 − A form will open, enter the details like group name, name tag, etc. Select ID of your VPC from VPC menu, then select the Yes, create button.
Step 4 − The list of groups opens. Select the group name from the list and set rules. Then click the Save button.
Step 1 − Open the Amazon VPC console using the following link − https://console.aws.amazon.com/vpc/
Step 2 − Select the same region as while creating VPC and security group.
Step 3 − Now select the Launch Instance option in the navigation bar.
Step 4 − A page opens. Choose the AMI which is to be used.
Step 5 − A new page opens. Choose an Instance Type and select the hardware configuration. Then select Next: Configure Instance Details.
Step 6 − Select the recently created VPC from the Network list, and the subnet from the Subnet list. Leave the other settings as default and click Next till the Tag Instance page.
Step 7 − On the Tag Instance page, tag the instance with the Name tag. This assist to identify your instance from the list of multiple instances. Click Next: Configure Security Group.
Step 8 − On the Configure Security Group page, select the recently created group from the list. Then, select Review and Launch button.
Step 9 − On the Review Instance Launch page, check your instance details, then select Launch.
Step 10 − A dialog box appears. Select the option Select an existing key pair or create a new key pair, then click the Launch Instances button.
Step 11 − The confirmation page open which shows all the details related to instances.
Step 1 − Open the Amazon VPC console using the following link − https://console.aws.amazon.com/vpc/
Step 2 − Select Elastic IP’s option in the navigation bar.
Step 3 − Select Allocate New Address. Then select Yes, Allocate button.
Step 4 − Select your Elastic IP address from the list, then select Actions, and then click the Associate Address button.
Step 5 − A dialog box will open. First select the Instance from the Associate with list. Then select your instance from the Instance list. Finally click the Yes, Associate button.
There are few steps to delete VPC without losing any resources associated with it. Following are the steps to delete a VPC.
Step 1 − Open the Amazon VPC console utilizing the following link − https://console.aws.amazon.com/vpc/
Step 2 − Select Instances option in the navigation bar.
Step 3 − Select the Instance from the list, then select the Actions → Instance State → Terminate button.
Step 4 − A new dialog box opens. Expand the Release attached Elastic IPs section, and select the checkbox next to the Elastic IP address. Click the Yes, Terminate button.
Step 5 − Again open the Amazon VPC console using the following link − https://console.aws.amazon.com/vpc/
Step 6 − Select the VPC from the navigation bar. Then select Actions & finally click the Delete VPC button.
Step 7 − A confirmation message appears. Click the Yes, Delete button.
Many connectivity options − There are different connectivity options that exist in Amazon VPC.
Connect VPC directly to the Internet via public subnets.
Connect to the Internet using Network Address Translation via private subnets.
Connect securely to your corporate datacenter via encrypted IPsec hardware VPN connection.
Connect privately to other VPCs in which we can share resources across different virtual networks through AWS account.
Connect to Amazon S3 without using an internet gateway and have good control over S3 buckets, its user requests, groups, etc.
Combine connection of VPC and datacenter is possible by configuring Amazon VPC route tables to direct all traffic to its destination.
Easy to use − Ease of creating a VPC in very straightforward steps by selecting network set-ups as per requirement. Click "Start VPC Wizard", then Subnets, IP ranges, route tables, and security groups will be automatically created.
Easy to backup data − Periodically backup data from the datacenter into Amazon EC2 instances by using Amazon EBS volumes.
Easy to extend network using Cloud − Move applications, launch additional web servers and increase storage capacity by connecting it to a VPC.
Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. It is designed for developers and corporates to route the end users to Internet applications by translating human readable names like www.domain.com, into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other.
Following are the steps to configure Route 53.
Step 1 − Open the Amazon Route 53 console using this link − https://console.aws.amazon.com/route53/.
Step 2 − Click create hosted zone option on the top left corner of the navigation bar.
Step 3 − A form page opens. Provide the required details such as domain name and comments, then click the Create button.
Step 4 − Hosted zone for the domain will be created. There will be four DNS endpoints called delegation set and these endpoints must be updated in the domain names Nameserver settings.
Step 5 − If it is godaddy.com then select domain’s control panel and update the Route 53 DNS endpoints. Delete the rest default values. It will take 2-3 minutes to update.
Step 6 − Go back to Route 53 console and select the go to record sets option. This will display you the list of record sets. By default, there are two record sets of type NS & SOA.
Step 7 − To create your record set, select the create record set option. Fill the required details such as: Name, Type, Alias, TTL seconds, Value, Routing policy, etc. Click the Save record set button.
Step 8 − Create one more record set for some other region so that there are two record sets with the same domain name pointing to various IP addresses with your selected routing policy.
Once completed, the user requests will be routed based on the network policy.
Easy to register your domain − We can buy all level of domains like .com, .net, .org, etc. directly from Route 53.
Highly reliable − Route 53 is built using AWS infrastructure. Its distributed nature towards DNS servers assist to ensure a consistent ability to route applications of end users.
Scalable − Route 53 is designed in such a way that it automatically handles large volume queries without the user’s interaction.
Can be used with other AWS Services − Route 53 also works with other AWS services. It can be used to map domain names to our Amazon EC2 instances, Amazon S3 buckets, Amazon and other AWS resources.
Easy to use − It is easy to sign-up, easy to configure DNS settings, and provides quick response to DNS queries.
Health Check: Route 53 monitors the health of the application. If an outage is detected, then it automatically redirects the users to a healthy resource.
Cost-Effective − Pay only for the domain service and the number of queries that the service answers for every domain.
Secure − By integrating Route 53 with AWS (IAM), there is complete control over every user within the AWS account, such as deciding which user can access which part of Route 53.
AWS Direct Connect allows to create a private network connection from our network to AWS location. It uses 802.1q VLANs, which can be partitioned into different virtual interfaces to access public resources using the same connection. This results in reduced network cost and increased bandwidth. Virtual interfaces can be reconfigured at any time as per the need.
Our network need to meet one of the following conditions to use AWS Direct Connect −
Our network should be in the AWS Direct Connect location. Click on this link to know about the available AWS Direct Connect locations https://aws.amazon.com/directconnect/.
We should be working with an AWS Direct Connect partner who is a member of the AWS Partner Network (APN). Click on this link to know the list of AWS Direct Connect partners − https://aws.amazon.com/directconnect/
Our service provider must be portable to connect to AWS Direct Connect.
Additionally, our network must meet the following necessary conditions −
Connections to AWS Direct Connect requires single mode fiber, 1000BASE-LX (1310nm) for 1 gigabit Ethernet, or 10GBASE-LR (1310nm) for 10 gigabit Ethernet. Auto Negotiation for the port must be disabled. Support for 802.1Q VLANs across these connections should be available.
Network must support Border Gateway Protocol (BGP) and BGP MD5 authentication. Optionally, we may configure Bidirectional Forwarding Detection (BFD).
Following are the ways to configure AWS Direct Connect −
Step 1 − Open the AWS Direct Connect console using this link − https://console.aws.amazon.com/directconnect/
step 2 − Select AWS Direct Connect region from the navigation bar.
step 3 − Welcome page of AWS Direct Connect opens. Select Get Started with Direct Connect.
step 4 − Create a Connection dialog box opens up. Fill the required details and click the Create button.
AWS will send an confirmation email within 72 hours to the authorized user.
Step 5 − Create a Virtual Interface using the following steps.
Open AWS console page again.
Select Connection in the navigation bar, then select Create Virtual Interface. Fill the required details and click the Continue button.
Select Download Router Configuration, then click the Download button.
Verify the Virtual Interface (optional). To verify the AWS Direct Connect connections use the following procedures.
To verify virtual interface connection to the AWS cloud − Run traceroute and verify that the AWS Direct Connect identifier is in the network trace.
To verify virtual interface connection to Amazon VPC − Use any pingable AMI and launch Amazon EC2 instance into the VPC that is attached to the virtual private gateway.
When an instance is running, get its private IP address and ping the IP address to get a response.
Reduces bandwidth costs − The cost gets reduced in both ways, i.e. it transfers the data to and from AWS directly. The data transferred over your dedicated connection is charged at reduced AWS Direct Connect data transfer rate rather than Internet data transfer rates.
Compatible with all AWS services − AWS Direct Connect is a network service, supports all the AWS services that are accessible over the Internet, like Amazon S3, Amazon EC2, Amazon VPC, etc.
Private connectivity to Amazon VPC − AWS Direct Connect can be utilizwd to establish a private virtual interface from our home-network to Amazon VPC directly with high bandwidth.
Elastic − AWS Direct Connect gives 1 Gbps and 10 Gbps connections, having provision to make multiple connections as per requirement.
Easy and simple − Easy to sign up on AWS Direct Connect using the AWS Management Console. Using this console, all the connections and virtual interfaces can be managed.
Amazon S3 (Simple Storage Service) is a scalable, high-speed, low-cost web-based service designed for online backup and archiving of data and application programs. It permits to upload, store, and download any type of files up to 5 TB in size. This service permits the subscribers to access the same systems that Amazon uses to run its own web sites. The subscriber has control over the accessibility of data, i.e. privately/publicly accessible.
Following are the steps to configure a S3 account.
Step 1 − Open the Amazon S3 console utilizing this link − https://console.aws.amazon.com/s3/home
Step 2 − Create a Bucket using the following steps.
A prompt window will open. Click the Create Bucket button at the bottom of the page.
Create a Bucket dialog box will open. Fill the required details and click the Create button.
The bucket is created successfully in Amazon S3. The console shows the list of buckets and its properties.
Select the Static Website Hosting option. Click the radio button Enable website hosting and fill the required details.
Step 3 − Add an Object to a bucket using the following steps.
Open the Amazon S3 console using the following link − https://console.aws.amazon.com/s3/home
Click the Upload button.
Click the Add files option. Select those files which are to be uploaded from the system and then click the Open button.
Click the start upload button. The files will get uploaded into the bucket.
To open/download an object − In the Amazon S3 console, in the Objects & Folders list, right-click on the object to be opened/downloaded. Then, select the required object.
Following are the steps to move S3 objects.
step 1 − Open Amazon S3 console.
step 2 − Select the files & folders option in the panel. Right-click on the object that is to be moved and click the Cut option.
step 3 − Open the location where we want this object. Right-click on the folder/bucket where the object is to be moved and click the Paste into option.
Step 1 − Open Amazon S3.
Step 2 − Select the files & folders option in the panel. Right-click on the object that is to be deleted. Select the delete option.
Step 3 − A pop-up window will open for confirmation. Click Ok.
Step 1 − Open Amazon S3 console.
Step 2 − Right-click on the bucket that is to be emptied and click the empty bucket option.
Step 3 − A confirmation message will appear on the pop-up window. Read it carefully and click the Empty bucket button to confirm.
Low cost and Easy to Use − Using Amazon S3, the user can store a large amount of data at very low charges.
Secure − Amazon S3 supports data transfer over SSL and the data gets encrypted automatically once it is uploaded. The user has complete control over their data by configuring bucket policies using AWS IAM.
Scalable − Using Amazon S3, there need not be any worry about storage concerns. We can store as much data as we have and access it anytime.
Higher performance − Amazon S3 is integrated with Amazon CloudFront, that distributes content to the end users with low latency and provides high data transfer speeds without any low usage commitments.
Integrated with AWS services − Amazon S3 integrated with AWS services include Amazon CloudFront, Amazon CLoudWatch, Amazon Kinesis, Amazon RDS, Amazon Route 53, Amazon VPC, AWS Lambda, Amazon EBS, Amazon Dynamo DB, etc.
Amazon Elastic Block Store (EBS) is a block storage system utilized to store persistent data. Amazon EBS is suitable for EC2 instances by providing highly available block level storage volumes. It has three types of volume, i.e. General Purpose (SSD), Provisioned IOPS (SSD), and Magnetic. These three volume types differ in performance, characteristics, and cost.
Following are the three types.
This volume type is suitable for small and medium workloads like Root disk EC2 volumes, small and medium database workloads, frequently logs accessing workloads, etc. By default, SSD supports 3 IOPS (Input Output Operations per Second)/GB means 1 GB volume will provide 3 IOPS, and 10 GB volume will provide 30 IOPS. Its storage capacity of one volume ranges from 1 GB to 1 TB. The cost of one volume is $0.10 per GB for one month.
This volume type is suitable for the most demanding I/O intensive, transactional workloads and large relational, EMR and Hadoop workloads, etc. By default, IOPS SSD supports 30 IOPS/GB means 10GB volume will provide 300 IOPS. Its storage capacity of one volume ranges from 10GB to 1TB. The cost of one volume is $0.125 per GB for one month for provisioned storage and $0.10 per provisioned IOPS for one month.
It was formerly known as standard volumes. This volume type is suitable for ideal workloads like infrequently accessing data, i.e. data backups for recovery, logs storage, etc. Its storage capacity of one volume ranges from 10GB to 1TB. The cost of one volume is $0.05 per GB for one month for provisioned storage and $0. 05 per million I/O requests.
Each account will be limited to 20 EBS volumes. For a requirement of more than 20 EBS volumes, contact Amazon’s Support team. We can attach up to 20 volumes on a single instance and each volume ranges from 1GB to 1TB in size.
In EC2 instances, we store data in local storage which is available till the instance is running. However, when we shut down the instance, the data gets lost. Thus, when we need to save anything, it is advised to save it on Amazon EBS, as we can access and read the EBS volumes anytime, once we attach the file to an EC2 instance.
Reliable and secure storage − Each of the EBS volume will automatically respond to its Availability Zone to protect from component failure.
Secure − Amazon’s flexible access control policies permits to specify who can access which EBS volumes. Access control plus encryption offers a strong defense-in-depth security strategy for data.
Higher performance − Amazon EBS uses SSD technology to deliver data results with consistent I/O performance of application.
Easy data backup − Data backup can be saved by taking point-in-time snapshots of Amazon EBS volumes.
Step 1 − Create Amazon EBS volume using the following steps.
Open the Amazon EC2 console.
Select the region in the navigation bar where the volume is to be created.
In the navigation pane, select Volumes, then select Create Volume.
Provide the required information like Volume Type list, Size, IOPS, Availability zone, etc. then click the Create button.
The volume names can be seen in the volumes list.
Step 2 − Store EBS Volume from a snapshot using the following steps.
Repeat the above 1 to 4 steps to create volume.
Type snapshot ID in the Snapshot ID field from which the volume is to be restored and select it from the list of suggested options.
If there is requirement for more storage, change the storage size in the Size field.
Select the Yes Create button.
Step 3 − Attach EBS Volume to an Instance using the following steps.
Open the Amazon EC2 console.
Select Volumes in the navigation pane. Select a volume and click the Attach Volume option.
An Attach Volume dialog box will open. Enter the name/ID of instance to attach the volume in the Instance field or select it from the list of suggestion options.
Click the Attach button.
Connect to instance and make the volume available.
Step 4 − Detach a volume from Instance.
First, use the command /dev/sdh in cmd to unmount the device.
Open the Amazon EC2 console.
In the navigation pane, select the Volumes option.
Choose a volume and click the Detach Volumes option.
A confirmation dialog box opens. Click the Yes, Detach button to confirm.
AWS Storage Gateway gives integration between the on-premises IT environment and the AWS storage infrastructure. The user can store data in the AWS cloud for scalable, data security features and cost-efficient storage.
AWS Gateway offers two types of storage, i.e. volume based and tape based.
This storage type provides cloud-backed storage volumes which can be mount as Internet Small Computer System Interface (iSCSI) devices from on-premises application servers.
AWS Storage Gateway stores all the on-premises application data in a storage volume in Amazon S3. Its storage volume ranges from 1GB to 32 TB and up to 20 volumes with a total storage of 150TB. We can attach these volumes with iSCSI devices from on-premises application servers. It is of two categories −
Every application requires storage volumes to store their data. This storage type is used to initially store data when it is to be written to the storage volumes in AWS. The data from the cache storage disk is waiting to be uploaded to Amazon S3 from the upload buffer. The cache storage disk keeps the most recently accessed data for low-latency access. When the application needs data, the cache storage disk is first checked before checking Amazon S3.
There are few guidelines to determine the amount of disk space to be allocated for cache storage. We should allocate at least 20% of the existing file store size as cache storage. It should be greater than the upload buffer.
Upload buffer disk − This type of storage disk is used to store the data before it is uploaded to Amazon S3 over SSL connection. The storage gateway uploads the data from the upload buffer over an SSL connection to AWS.
Snapshots − Sometimes we need to back up storage volumes in Amazon S3. These backups are incremental and are known as snapshots. The snapshots are stored in Amazon S3 as Amazon EBS snapshots. Incremental backup means that a new snapshot is backing up only the data that has changed since the last snapshot. We can take snapshots either at a scheduled interval or as per the need.
When the Virtual Machine (VM) is activated, gateway volumes are created and mapped to the on-premises direct-attached storage disks. Hence, when the applications write/read the data from the gateway storage volumes, it reads and writes the data from the mapped on-premises disk.
A gateway-stored volume permits to store primary data locally and provides on-premises applications with low-latency access to entire datasets. We can mount them as iSCSI devices to the on-premises application servers. It ranges from 1 GB to 16 TB in size and supports up to 12 volumes per gateway with a maximum storage of 192 TB.
This storage type gives a virtual tape infrastructure that scales seamlessly with your business needs and eliminates the operational burden of provisioning, scaling, and maintaining a physical tape infrastructure. Each gateway-VTL is preconfigured with media changer and tape drives, that are available with the existing client backup applications as iSCSI devices. Tape cartridges can be added later as needed to archive the data.
Few terms used in Architecture are explained below.
Virtual Tape − Virtual tape is similar to a physical tape cartridge. It is stored in the AWS cloud. We can create virtual tapes in two ways: by using AWS Storage Gateway console or by using AWS Storage Gateway API. The size of each virtual tape is from 100 GB to 2.5 TB. The size of one gateway is up to 150 TB and can have maximum 1500 tapes at a time.
Virtual Tape Library (VTL) − Each gateway-VTL comes with one VTL. VTL is same to a physical tape library available on-premises with tape drives. The gateway first stores data locally, then asynchronously uploads it to virtual tapes of VTL.
Tape Drive − A VTL tape drive is same to a physical tape drive that can perform I/O operations on tape. Each VTL consists of 10 tape drives that are used for backup applications as iSCSI devices.
Media Changer − A VTL media changer is same to a robot that moves tapes around in a physical tape library's storage slots and tape drives. Each VTL comes with one media changer that is used for backup applications as iSCSI device.
Virtual Tape Shelf (VTS) − A VTS is used to archive tapes from gateway VTL to VTS and vice-a-versa.
Archiving Tapes − When the backup software ejects a tape, the gateway moves the tape to the VTS for storage. It is used data archiving and backups.
Retrieving Tapes − Tapes archived to the VTS cannot be read directly so to read an archived tape, we need to retrieve the tape from gateway VTL either by using the AWS Storage Gateway console or by using the AWS Storage Gateway API.
CloudFront is a CDN (Content Delivery Network). It retrieves data from Amazon S3 bucket and distributes it to multiple datacenter locations. It delivers the data through a network of data centers called edge locations. The nearest edge location is routed when the user requests for data, resulting in lowest latency, low network traffic, fast access to data, etc.
AWS CloudFront delivers the content in the following stages.
Step 1 − The user accesses a website and requests an object to download like an image file.
Step 2 − DNS routes your request to the nearest CloudFront edge location to serve the user request.
Step 3 − At edge location, CloudFront checks its cache for the requested files. If found, then returns it to the user otherwise does the following −
First CloudFront compares the request with the specifications and forwards it to the applicable origin server for the corresponding file type.
The origin servers send the files back to the CloudFront edge location.
As soon as the first byte arrives from the origin, CloudFront begins forwarding it to the user and adds the files to the cache in the edge location for the next time when someone again requests for the same file.
Step 4 − The object is now in an edge cache for 24 hours or for the given duration in file headers. CloudFront does the following −
CloudFront forwards the next request for the object to the user’s origin to check the edge location version is updated or not.
If the edge location version is updated, then CloudFront delivers it to the user.
If the edge location version is not updated, then origin sends the latest version to CloudFront. CloudFront delivers the object to the user and stores the latest version in the cache at that edge location.
Fast − The broad network of edge locations and CloudFront caches copies of content close to the end users that yields in lowering latency, high data transfer rates and low network traffic. All these make CloudFront fast.
Simple − It is easy to use.
Can be used with other AWS Services − Amazon CloudFront is designed in such a way that it can be easily integrated with other AWS services, like Amazon S3, Amazon EC2.
Cost-effective − Using Amazon CloudFront, we pay only for the content that you deliver through the network, without any hidden charges and no up-front fees.
Elastic − Using Amazon CloudFront, we need not worry about maintenance. The service automatically responds if any action is required, in case the demand increases or decreases.
Reliable − Amazon CloudFront is built on Amazon’s highly reliable infrastructure, i.e. its edge locations will automatically re-route the end users to the next nearest location, if needed in some situations.
Global − Amazon CloudFront uses a global network of edge locations located in most of the regions.
AWS CloudFront can be set up using the following steps.
Step 1 − Sign in to AWS management console utilizing the following link − https://console.aws.amazon.com/
Step 2 − Upload Amazon S3 and choose every permission public. (How to upload content to S3 bucket is discussed in section Amazon S3)
Step 3 − Create a CloudFront Web Distribution using the following steps.
Open CloudFront console using the following link − https://console.aws.amazon.com/cloudfront/
Click the Get Started button in the web section of Select a delivery method for your content page.
Create Distribution page opens. Choose the Amazon S3 bucket created in the Origin Domain Name and leave the remaining fields as default.
Default Cache Behavior Settings page opens. Keep the values as default and move to the next page.
A Distribution settings page opens. Fill the details as per your need and click the Create Distribution button.
The Status column changes from In Progress to Deployed. Enable your distribution by selecting the Enable option. It will take around 15 minutes for the domain name to be available in the Distributions list.
After creating distribution, CloudFront knows the location of Amazon S3 server and the user knows the domain name associated with the distribution. However, we can also create a link to Amazon S3 bucket content with that domain name and have CloudFront serve it. This assists save a lot of time.
Following are the steps to link an object −
Step 1 − Copy the following HTML code to a new file and write the domain-name that CloudFront assigned to the distribution in the place of domain name. Write a file name of Amazon S3 bucket in the place of object-name.
<html> <head>CloudFront Testing link</head> <body> <p>My Cludfront.</p> <p><img src = "http://domain-name/object-name" alt = "test image"/> </body> </html>
Step 2 − Save the text in a file with .html extension.
Step 3 − Open the web page in a browser to test the links to see if they are working correctly. If not, then again check the settings.
Amazon RDS (Relational Database Service) is a fully-managed SQL database cloud service that permits to create and operate relational databases. Using RDS you can access your files and database anywhere in a cost-effective and highly scalable way.
Amazon RDS has the following features −
Scalable − Amazon RDS permits to scale the relational database by using AWS Management Console or RDS-specific API. We can increase or decrease your RDS requirements within minutes.
Host replacement − Sometimes these situations occur when the hardware of Amazon RDS fails. There is no need to worry, it will be automatically replaced by Amazon.
Inexpensive − Using Amazon RDS, we pay only for the resources we consume. There is no up-front and long-term commitment.
Secure − Amazon RDS provides complete control over the network to access their database and their associated services.
Automatic backups − Amazon RDS backs up everything in the database including transaction logs up to last five minutes and also manages automatic backup timings.
Software patching − Automatically gets all the latest patches for the database software. We can also specify when the software should be patched using DB Engine Version Management.
Step 1 − Login to AWS management console. Use the following link to open Amazon RDS console − https://console.aws.amazon.com/rds/
Step 2 − Select the region where the DB instance is to be created, at the top right corner of the Amazon RDS console.
Step 3 − Select Instances in the navigation pane, then click Launch DB Instance button.
Step 4 − The Launch DB Instance Wizard opens. Select the type of instance as required to launch and click the Select button.
Step 5 − On the Specify DB Details page, provide the mandatory details and click the Continue button.
Step 6 − On the Additional configuration page, give the additional information required to launch the MySQL DB instance and click the Continue button.
Step 7 − On Management options page, make the choices and click the Continue button.
Step 8 − On the Review page, verify the details and click the Launch DB Instance button.
Now DB instance displays in the list of DB instances.
Following are the steps to connect a database on MySQL DB instance −
Step 1 − Type the following command in the command prompt on a client computer to connect a database on MySQL DB instance (using the MySQL monitor).
Step 2 − Replace <myDBI> with DNS name of your DB instance, <myusername> with your master user-name & <mypassword> with your master password.
PROMPT> mysql -h <myDBI> -P 3306 -u <myusername> -p
After running the above command, the output looks like −
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 350 Server version: 5.2.33-log MySQL Community Server (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql>
After finishing the task, we should delete the DB instance so will not be charged for it. Follow these steps to delete a DB instance −
Step 1 − Sign in to the AWS Management Console and use the following link to open the Amazon RDS console.
Step 2 − In the DB Instances list, select the DB instances to be deleted.
Step 3 − Click the Instance Actions button and then select the Delete option from the dropdown menu.
Step 4 − Select No in the Create Final Snapshot.
Step 5 − Click the Yes, Delete to delete the DB instance.
When using Amazon RDS, pay only for only the usage without any minimum and setup charges. Billing is based on the following criteria −
Instance class − Costing is based on the class of the DB instance consumed.
Running time − Price is calculated by the instance-hour, which is same to a single instance running per hour.
Storage − Bill is calculated as per the storage capacity plan chosen in terms of per GB.
I/O requests per month − Billing structure also includes total number of storage I/O requests made in a billing cycle.
Backup storage − There is no extra charges for backup storage up to 100% of database. This service is free only for active DB instances.
For latest updated price structure and other details, visit the following link − https://aws.amazon.com/rds/pricing/
Amazon DynamoDB is a fully managed NoSQL database service that permits to create database tables that can store and retrieve any amount of data. It automatically manages the data traffic of tables over multiple servers and maintains performance. It also relieves the customers from the burden of operating and scaling a distributed database. Hence, hardware provisioning, setup, configuration, replication, software patching, cluster scaling, etc. is managed by Amazon.
Following are the stages to set up DynamoDB.
Step 1 − Following are the steps to set up DynamoDB.
Download DynamoDB (.jar file) using the below link. It supports multiple Operating Systems like Windows, Linux, Mac, etc.
.tar.gz format − http://dynamodb-local.s3-website-us-west2.amazonaws.com/dynamodb_local_latest.tar.gz
.zip format − http://dynamodb-local.s3-website-us-west2.amazonaws.com/dynamodb_local_latest.zip.
Once download is complete, unzip the contents and copy the extracted directory to a location wherever you want.
Open the command prompt and navigate to the directory where you extracted DynamoDBLocal.jar, and execute the following command −
java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
Step 2 − Create a Table using the following steps.
Open AWS Management Console and select DynamoDB.
Select the region where the table will be created and click the Create Table button.
Create Table window opens. Fill the details into their respective fields and click the Continue button.
Finally, a review page opens where we can view details. Click the Create button.
Now the Table-name is visible in the in-to the list and Dynamo Table is ready to use.
Managed service − Amazon DynamoDB is a managed service. There is no need to hire professionals to manage NoSQL installation. Developers need not worry about setting up, configuring a distributed database cluster, managing ongoing cluster operations, etc. It handles all the complexities of scaling, partitions and re-partitions data over more machine resources to meet I/O performance requirements.
Scalable − Amazon DynamoDB is designed to scale. There is no need to worry about predefined limits to the amount of data each table can store. Any amount of data can be stored and retrieved. DynamoDB will spread automatically with the amount of data stored as the table grows.
Fast − Amazon DynamoDB provides high throughput at very low latency. As datasets grow, latencies remain stable due to the distributed nature of DynamoDB's data placement and request routing algorithms.
Durable and highly available − Amazon DynamoDB replicates data over at least 3 various data centers’ results. The system operates and serves data even under different failure conditions.
Flexible: Amazon DynamoDB permits creation of dynamic tables, i.e. the table can have any number of attributes, including multi-valued attributes.
Cost-effective: Payment is for what we use without any minimum charges. Its pricing structure is simple and easy to calculate.
Amazon Redshift is a complete managed data warehouse service in the cloud. Its datasets range from 100s of gigabytes to a petabyte. The initial method to create a data warehouse is to launch a set of compute resources called nodes, which are organized into groups called cluster. After that you can process your queries.
Below are the given steps to set up Amazon Redshift.
Step 1 − Sign in and launch a Redshift Cluster utilizing the following steps.
Sign in to AWS Management console and use the following link to open Amazon Redshift console − https://console.aws.amazon.com/redshift/
Select the region where the cluster is to be created using the Region menu on the top right side corner of the screen.
Click the Launch Cluster button.
The Cluster Details page opens. Provide the required details and click the Continue button till the review page.
A confirmation page opens. Click the Close button to complete so that cluster is visible in the Clusters list.
Select the cluster in the list and review the Cluster Status information. The page will show Cluster status.
Step 2 − Configure security group to authorize client connections to the cluster. The authorizing access to Redshift depends on whether the client authorizes an EC2 instance or not.
Follow these steps to security group on EC2-VPC platform.
Open Amazon Redshift Console and click Clusters on the navigation pane.
Select the desired Cluster. Its Configuration tab opens.
Click the Security group.
Once the Security group page opens, click the Inbound tab.
Click the Edit button. Set the fields as appeared below and click the Save button.
Type − Custom TCP Rule.
Protocol − TCP.
Port Range − Type the same port number used while launching the cluster. By-default port for Amazon Redshift is 5439.
Source − Select Custom IP, then type 0.0.0.0/0.
Step 3 − Connect to Redshift Cluster.
There are two methods to connect to Redshift Cluster − Directly or via SSL.
Following are the steps to connect directly.
Connect the cluster by using a SQL client tool. It supports SQL client tools that are compatible with PostgreSQL JDBC or ODBC drivers.
Use the following links to download − JDBC https://jdbc.postgresql.org/download/postgresql-8.4-703.jdbc4.jar
ODBC https://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_08_04_0200.zip or http://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_09_00_0101x64.zip for 64 bit machines
Use the following steps to get the Connection String.
Open Amazon Redshift Console and select Cluster in the Navigation pane.
Select the cluster of choice and click the Configuration tab.
A page opens as displayed in the following screenshot with JDBC URL under Cluster Database Properties. Copy the URL.
Use the following steps to connect the Cluster with SQL Workbench/J.
Open SQL Workbench/J.
Select the File and click the Connect window.
Select Create a new connection profile and fill the required details like name, etc.
Click Manage Drivers and Manage Drivers dialog box opens.
Click the Create a new entry button and fill the required details.
Click the folder icon and navigate to the driver location. Finally, click the Open button.
Leave the Classname box and Sample URL box blank. Click OK.
Choose the Driver from the list.
In the URL field, paste the JDBC URL copied.
Enter the username and password to their respective fields.
Select the Autocommit box and click Save profile list.
Following are the features of Amazon Redshift −
Supports VPC − The users can launch Redshift within VPC and control access to the cluster through the virtual networking environment.
Encryption − Data stored in Redshift can be encrypted and configured while creating tables in Redshift.
SSL − SSL encryption is used to encrypt connections between clients and Redshift.
Scalable − With a few simple clicks, the number of nodes can be easily scaled in your Redshift data warehouse as per requirement. It also allows to scale over storage capacity without any loss in performance.
Cost-effective − Amazon Redshift is a cost-effective alternative to traditional data warehousing practices. There are no up-front costs, no long-term commitments and on-demand pricing structure.
Amazon Kinesis is a managed, scalable, cloud-based service that permits real-time processing of streaming large amount of data per second. It is designed for real-time applications and permits developers to take in any amount of data from several sources, scaling up and down that can be run on EC2 instances.
It is used to capture, store, and process data from large, distributed streams such as event logs and social media feeds. After processing the data, Kinesis distributes it to multiple consumers simultaneously.
It is used in situations where we require rapidly moving data and its continuous processing. Amazon Kinesis can be utilized in the following situations −
Data log and data feed intake − We need not wait to batch up the data, we can push data to an Amazon Kinesis stream as soon as the data is produced. It also protects data loss in case of data producer fails. For example: System and application logs can be continuously added to a stream and can be available in seconds when required.
Real-time graphs − We can extract graphs/metrics using Amazon Kinesis stream to create report results. We need not wait for data batches.
Real-time data analytics − We can run real-time streaming data analytics by using Amazon Kinesis.
Following are certain limits that should be kept in mind while using Amazon Kinesis Streams −
Records of a stream can be accessible up to 24 hours by default and can be extended up to 7 days by enabling extended data retention.
The maximum size of a data blob (the data payload before Base64-encoding) in one record is 1 megabyte (MB).
One shard supports up to 1000 PUT records per second.
For more information related to limits, click on the following link − https://docs.aws.amazon.com/kinesis/latest/dev/service-sizes-and-limits.html
Following are the steps to use Amazon Kinesis −
Step 1 − Set up Kinesis Stream using the following steps −
Sign into AWS account. Select Amazon Kinesis from Amazon Management Console.
Click the Create stream and fill the required fields such as stream name and number of shards. Click the Create button.
The Stream will now be visible in the Stream List.
Step 2 − Set up users on Kinesis stream. Create New Users & assign a policy to each user.(We have discussed the procedure above to create Users and assigning policy to them)
Step 3 − Connect your application to Amazon Kinesis; here we are connecting Zoomdata to Amazon Kinesis. Following are the stages to connect.
Log in to Zoomdata as Administrator and click Sources in menu.
Select the Kinesis icon and fill the required details. Click the Next button.
Select the desired Stream on the Stream tab.
On the Fields tab, create unique label names, as required and click the Next button.
On the Charts Tab, enable the charts for data. Customize the settings as needed and then click the Finish button to save the setting.
Real-time processing − It permits to collect and analyze information in real-time like stock trade prices otherwise we need to wait for data-out report.
Easy to use − Using Amazon Kinesis, we can create a new stream, set its requirements, and start streaming data quickly.
High throughput, elastic − It allows to collect and analyze information in real-time like stock trade prices otherwise we need to wait for data-out report.
Integrate with other Amazon services − It can be integrated with Amazon Redshift, Amazon S3 and Amazon DynamoDB.
Build kinesis applications − Amazon Kinesis gives the developers with client libraries that enable the design and operation of real-time data processing applications. Add the Amazon Kinesis Client Library to Java application and it will notify when new data is available for processing.
Cost-efficient − Amazon Kinesis is cost-efficient for workloads of any scale. Pay as we go for the resources used and pay hourly for the throughput needed.
Amazon Elastic MapReduce (EMR) is a web service that gives a managed framework to run data processing frameworks such as Apache Hadoop, Apache Spark, and Presto in an easy, cost-effective, and secure manner.
It is used for data analysis, web indexing, data warehousing, financial analysis, scientific simulation, etc.
Follow these steps to set up Amazon EMR −
Step 1 − Sign in to AWS account and select Amazon EMR on management console.
Step 2 − Create Amazon S3 bucket for cluster logs & output data. (Procedure is explained in detail in Amazon S3 section)
Step 3 − Launch Amazon EMR cluster.
Following are the stages to create cluster and launch it to EMR.
Use this link to open Amazon EMR console − https://console.aws.amazon.com/elasticmapreduce/home
Select create cluster and provide the required details on Cluster Configuration page.
Leave the Tags section options as default and proceed.
On the Software configuration section, level the options as default.
On the File System Configuration chapter, leave the options for EMRFS as set by default. EMRFS is an implementation of HDFS, it permits Amazon EMR clusters to store data on Amazon S3.
On the Hardware Configuration chapter, select m3.xlarge in EC2 instance type field and leave other settings as default. Click the Next button.
On the Security and Access chapter, for EC2 key pair, select the pair from the list in EC2 key pair field and leave the other settings as default.
On Bootstrap Actions chapter, leave the fields as set by default and click the Add button. Bootstrap actions are scripts that are executed during the setup before Hadoop starts on every cluster node.
On the Steps chapter, leave the settings as default and proceed.
Click the Create Cluster button and the Cluster Details page opens. This is where we should run the Hive script as a cluster step and use the Hue web interface to query the data.
Step 4 − Run the Hive script using the following steps.
Open the Amazon EMR console and select the desired cluster.
Move to the Steps section and expand it. Then click the Add step button.
The Add Step dialog box opens. Fill the required fields, then click the Add button.
To view the output of Hive script, use the following steps −
Open the Amazon S3 console and select S3 bucket used for the output data.
Select the output folder.
The query writes the results into a separate folder. Select os_requests.
The output is stored in a text file. This file can be downloaded.
Following are the benefits of Amazon EMR −
Easy to use − Amazon EMR is easy to use, i.e. it is easy to set up cluster, Hadoop configuration, node provisioning, etc.
Reliable − It is reliable in the sense that it retries failed tasks and automatically replaces poorly performing instances.
Elastic − Amazon EMR permits to compute large amount of instances to process data at any scale. It easily increases or decreases the number of instances.
Secure − It automatically configures Amazon EC2 firewall settings, controls network access to instances, launch clusters in an Amazon VPC, etc.
Flexible − It permits complete control over the clusters and root access to every instance. It also permits installation of additional applications and customizes your cluster as per requirement.
Cost-efficient − Its pricing is easy to estimate. It charges hourly for every instance used.
AWS Data Pipeline is a web service, designed to make it easier for users to integrate data spread across multiple AWS services and analyze it from a single location.
Using AWS Data Pipeline, data can be accessed from the source, processed, and then the results can be efficiently transferred to the respective AWS services.
Following are the steps to set up data pipeline −
Step 1 − Create the Pipeline using the following steps.
Sign-in to AWS account.
Use this link to Open AWS Data Pipeline console − https://console.aws.amazon.com/datapipeline/
Select the region in the navigation bar.
Click the Create New Pipeline button.
Fill the required details in the respective fields.
In the Source field, choose Build using a template and then select this template − Getting Started using ShellCommandActivity.
The Parameters section opens only when the template is selected. Leave the S3 input folder and Shell command to run with their default values. Click the folder icon next to S3 output folder, and select the buckets.
In Schedule, leave the values as default.
In Pipeline Configuration, leave the logging as enabled. Click the folder icon under S3 location for logs and select the buckets.
In Security/Access, leave IAM roles values as default.
Click the Activate button.
Deleting the pipeline will also delete all associated objects.
Step 1 − Select the pipeline from the pipelines list.
Step 2 − Click the Actions button and then choose Delete.
Step 3 − A confirmation prompt window opens. Click Delete.
Simple and cost-efficient − Its drag-and-drop features makes it easy to create a pipeline on console. Its visual pipeline creator provides a library of pipeline templates. These templates make it easier to create pipelines for tasks like processing log files, archiving data to Amazon S3, etc.
Reliable − Its infrastructure is designed for fault tolerant execution activities. If failures occur in the activity logic or data sources, then AWS Data Pipeline automatically retries the activity. If the failure continues, then it will send a failure notification. We can even configure these notification alerts for situations like successful runs, failure, delays in activities, etc.
Flexible − AWS Data Pipeline provides different features like scheduling, tracking, error handling, etc. It can be configured to take actions like run Amazon EMR jobs, execute SQL queries directly against databases, execute custom applications running on Amazon EC2, etc.
Amazon Machine Learning is a service that permits to develop predictive applications by using algorithms, mathematical models based on the user’s data.
Amazon Machine Learning reads data through Amazon S3, Redshift and RDS, then visualizes the data through the AWS Management Console and the Amazon Machine Learning API. This data can be imported or exported to other AWS services via S3 buckets.
It uses “industry-standard logistic regression” algorithm to generate models.
Three different types of tasks can be performed by Amazon Machine learning service −
A binary classification model can predict one of the two possible results, i.e. either yes or no.
A multi-class classification model can predict multiple conditions. For example, it can track a customer's online orders.
A regression model results in an exact value. Regression models can predict the best-selling price for a product or the number of units that will sell.
Step 1 − Sign in to AWS account and select Machine Learning. Click the Get Started button.
Step 2 − Select Standard Setup and then click Launch.
Step 3 − In the Input data section, fill the required details and select the choice for data storage, either S3 or Redshift. Click the Verify button.
Step 4 − After S3 location verification is finished, Schema section opens. Fill the fields as per requirement and proceed to the next step.
Step 5 − In Target section, reselect the variables selected in Schema section and proceed to the next step.
Step 6 − Leave the values as default in Row ID section and proceed to the Review area. Verify the details and click the Continue button.
Following are some screenshots of Machine Learning services.
Data Set Created by Machine Learning
Summary Made by Machine Learning
Exploring Performance Using Machine Learning
Easy to create machine learning models − It is easy to create ML models from data stored in Amazon S3, Amazon Redshift, Amazon RDS and query these models for predictions by using Amazon ML APIs and wizards.
High performance − Amazon ML prediction APIs can be used further to generate billions of predictions for the applications. We can use them within interactive web, mobile, or desktop applications.
Cost-efficient − Pay only for what we use without any setup charges and no upfront commitments.
The below given services fall under Application Services section −
In this section, we will discuss Amazon SWF.
Amazon Simple Workflow Service (SWF) is a task based API that makes it easy to coordinate work across distributed application components. It gives a programming model and infrastructure for coordinating distributed components and maintaining their execution state in a reliable way. Using Amazon SWF, we can focus on building the aspects of the application that differentiates it.
A workflow is a set of activities that carry out some objective, including logic that coordinates the activities to achieve the desired output.
Workflow history consists of complete and consistent record of each event that occurred since the workflow execution started. It is maintained by SWF.
Step 1 − Sign in to AWS account and select SWF on the Services dashboard.
Step 2 − Click the Launch Sample Walkthrough button.
Step 3 − Run a Sample Workflow window opens. Click the Get Started button.
Step 4 − In the Create Domain section, click the Create a new Domain radio button and then click the Continue button.
Step 5 − In Registration section, read the instructions then click the Continue button.
Step 6 − In the Deployment section, choose the desired option and click the Continue button.
Step 7 − In the Run an Execution section, choose the desired option and click the Run this Execution button.
Finally, SWF will be created and will be available in the list.
It enables applications to be stateless, because all information about a workflow execution is stored in its workflow history.
For each workflow execution, the history gives a record of which activities were scheduled, their current statuses and results. The workflow execution uses this information to determine the next steps.
The history gives steps in detail that can be used to monitor running workflow executions and verify completed workflow executions.
Amazon WorkMail was formerly known as Zocalo. It is a managed email and calendaring service that runs in Cloud. It gives security controls and is designed to work with your existing PC and Mac-based Outlook clients including the prepackaged Click-to-Run versions. It also works with mobile clients that speak the Exchange ActiveSync protocol.
Its migration tool permits to move mailboxes from on-premises email servers to the service, and works with any device that supports the Microsoft Exchange ActiveSync protocol, such as Apple’s iPad and iPhone, Google Android, and Windows Phone.
Step 1 − Sign in to AWS account and open the Amazon WorkMail console using the following link − https://console.aws.amazon.com/workmail/
Step 2 − Click the Get Started button.
Step 3 − Select the desired option and choose the Region from the top right side of the navigation bar.
Step 4 − Fill the required details and proceed to the next step to configure an account. Follow the instructions. Finally, the mailbox will look like as shown in the following screenshot.
Secure − Amazon WorkMail automatically encrypts entire data with the encryption keys using the AWS Key Management Service.
Managed − Amazon WorkMail offers full control over email and there is no need to worry about installing a software, maintaining and managing hardware. Amazon WorkMail automatically handles all these needs.
Accessibility − Amazon WorkMail supports Microsoft Outlook on both Windows and Mac OS X. Hence, users can use the existing email client without any other requirements.
Availability − Users can synchronize emails, contacts and calendars with iOS, Android, Windows Phone, etc. using the Microsoft Exchange ActiveSync protocol anywhere.
Cost-efficient − Amazon WorkMail charges 4$ per user per month up to 50GB of storage.