A PROJECT REPORT

Hosting Static Website using Static Website using S3 in AWS

Project Report is submitted to Indian Cyber Security Solutions under the guidance of Stuti Mam

Submitted by Abhishek Rudra , Ayan Karfa & Soikot Dey (ICSS Students)

History

The AWS platform was launched in July 2002. [5] In its early stages, the platform consisted of only a few disparate tools and services. Then in late 2003, the AWS concept was publicly reformulated when Chris Pinkham and Benjamin Black presented a paper describing a vision for Amazon’s retail computing infrastructure that was completely standardized, completely automated, and would rely extensively on web services for services such as storage and would draw on internal work already underway.

Amazon Web Services was officially re-launched on March 14, 2006,[5] combining the three initial service offerings of Amazon S3 cloud storage, SQS, and EC2. The AWS platform finally provided an integrated suite of core online services, as Chris Pinkham and Benjamin Black had proposed back in 2003,[11] as a service offered to other developers, web sites, client-side applications, and companies.

Growth and profitability

In November 2010, it was reported that all of Amazon.com’s retail sites had migrated to AWS.[23] Prior to 2012, AWS was considered a part of Amazon.com and so its revenue was not delineated in Amazon financial statements. In that year industry watchers for the first time estimated AWS revenue to be over $1.5 billion.[24]

In April 2015, Amazon.com reported AWS was profitable, with sales of $1.57 billion in the first quarter of the year and $265 million of operating income. Founder Jeff Bezos described it as a fast-growing $5 billion business; analysts described it as “surprisingly more profitable than forecast”.

In 2016 Q1, revenue was $2.57 billion with net income of $604 million, a 64% increase over 2015 Q1 that resulted in AWS being more profitable than Amazon’s North American retail business for the first time.[28] In the first quarter of 2016, Amazon experienced a 42% rise in stock value as a result of increased earnings, of which AWS contributed 56% to corporate profits.[29][30]

AWS had $17.46 billion in annual revenue in 2017.[2]

Net sales revenue of Amazon from 2004 to 2018 (in billion U.S. dollars)

Customer base

On March 14, 2006, Amazon said in a press release:[5] “More than 150,000 developers have signed up to use Amazon Web Services since its inception.”

In November 2012, AWS hosted its first customer event in Las Vegas.[31]
On May 13, 2013, AWS was awarded an Agency Authority to Operate (ATO) from the U.S. Department of Health and Human Services under the Federal Risk and Authorization Management Program.[32]
In October 2013, it was revealed that AWS was awarded a $600M contract with the CIA.[33]
During August 2014, AWS received Department of Defense-Wide provisional authorization for all U.S. Regions.[34]
During the 2015 reinvent keynote, AWS disclosed that they have more than a million active customers every month in 190 countries, including nearly 2,000 government agencies, 5,000 education institutions and more than 17,500 nonprofits.
On April 5, 2017, AWS and DXC Technology (formed from a merger of CSC and HPE) announced an expanded alliance to increase access of AWS features for enterprise clients in existing data centers.[35]

Notable customers include NASA,[36] the Obama presidential campaign of 2012,[37] and Netflix.[38]

Working with Amazon S3 Bucket

Amazon S3 is cloud storage for the internet. To upload your data (photos, videos, documents etc.), you first create a bucket in one of the AWS Regions. You can then upload any number of objects to the bucket.

In terms of implementation, buckets and objects are resources, and Amazon S3 provides APIs for you to manage them. For example, you can create a bucket and upload objects using the Amazon S3 API. You can also use the Amazon S3 console to perform these operations. The console uses the Amazon S3 APIs to send requests to Amazon S3.

This section explains how to work with buckets. For information about working with objects, see Working with Amazon S3 Objects.

An Amazon S3 bucket name is globally unique, and the namespace is shared by all AWS accounts. This means that after a bucket is created, the name of that bucket cannot be used by another AWS account in any AWS Region until the bucket is deleted. You should not depend on specific bucket naming conventions for availability or security verification purposes. For bucket naming guidelines, see Bucket Restrictions and Limitations.

Amazon S3 creates buckets in a region you specify. To optimize latency, minimize costs, or address regulatory requirements, choose any AWS Region that is geographically close to you.