Download Full Version ebook - Visit ebookmeta.

com

Spring Boot with React and AWS: Learn to Deploy a

Full Stack Spring Boot React Application to AWS
1st Edition Ravi Kant Soni

https://ebookmeta.com/product/spring-boot-with-react-and-
aws-learn-to-deploy-a-full-stack-spring-boot-react-
application-to-aws-1st-edition-ravi-kant-soni/

OR CLICK HERE

DOWLOAD NOW

Discover More Ebook - Explore Now at ebookmeta.com

 Instant digital products (PDF, ePub, MOBI) ready for you
Download now and discover formats that fit your needs...

Start reading on any device today!

Learn Microservices with Spring Boot 3 Moises Macero

Garcia

https://ebookmeta.com/product/learn-microservices-with-spring-
boot-3-moises-macero-garcia/

ebookmeta.com

Spring Boot Persistence Best Practices: Optimize Java

Persistence Performance in Spring Boot Applications 1st
Edition Anghel Leonard
https://ebookmeta.com/product/spring-boot-persistence-best-practices-
optimize-java-persistence-performance-in-spring-boot-applications-1st-
edition-anghel-leonard/
ebookmeta.com

Spring Boot in Practice (Final Release) 1st Edition

Somnath Musib

https://ebookmeta.com/product/spring-boot-in-practice-final-
release-1st-edition-somnath-musib/

ebookmeta.com

Dawson (Alpha Company Renegades Book 4) 1st Edition Kali

Hart [Hart

https://ebookmeta.com/product/dawson-alpha-company-renegades-
book-4-1st-edition-kali-hart-hart/

ebookmeta.com
Cambridge Little Steps Level 3 Student s Book Zapiain

https://ebookmeta.com/product/cambridge-little-steps-level-3-student-
s-book-zapiain/

ebookmeta.com

Circuits Packets and Protocols Entrepreneurs and Computer

Communications 1968 1988 1st Edition James L. Pelkey

https://ebookmeta.com/product/circuits-packets-and-protocols-
entrepreneurs-and-computer-communications-1968-1988-1st-edition-james-
l-pelkey/
ebookmeta.com

Studies in Ancient Greek Philosophy In Honor of Professor

Anthony Preus 1st Edition D. M. Spitzer

https://ebookmeta.com/product/studies-in-ancient-greek-philosophy-in-
honor-of-professor-anthony-preus-1st-edition-d-m-spitzer/

ebookmeta.com

Intoxication An Ethnography of Effervescent Revelry 1st

Edition Sébastien Tutenges

https://ebookmeta.com/product/intoxication-an-ethnography-of-
effervescent-revelry-1st-edition-sebastien-tutenges/

ebookmeta.com

Alamosa Arena 1st Edition Aaron Crash Crash Aaron

https://ebookmeta.com/product/alamosa-arena-1st-edition-aaron-crash-
crash-aaron/

ebookmeta.com
Data Modeling for the Sciences: Applications, Basics,
Computations 1st Edition Steve Pressé

https://ebookmeta.com/product/data-modeling-for-the-sciences-
applications-basics-computations-1st-edition-steve-presse/

ebookmeta.com
Spring Boot with
React and AWS
Learn to Deploy a Full Stack Spring
Boot React Application to AWS
—
Ravi Kant Soni
Namrata Soni
 Spring Boot with
React and AWS
Learn to Deploy a
Full Stack Spring Boot React
Application to AWS

Ravi Kant Soni

Namrata Soni
Spring Boot with React and AWS: Learn to Deploy a Full Stack Spring Boot
React Application to AWS
Ravi Kant Soni Namrata Soni
s/o – Late. Ras Bihari Prasad, Sri Niwash, d/o – Late. Ras Bihari Prasad, Sri Niwash,
Lashkariganj, Sasaram, Bihar, India Lashkariganj, Sasaram, Bihar, India

ISBN-13 (pbk): 978-1-4842-7391-3 ISBN-13 (electronic): 978-1-4842-7392-0

https://doi.org/10.1007/978-1-4842-7392-0

Copyright © 2021 by Ravi Kant Soni and Namrata Soni

This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or
part of the material is concerned, specifically the rights of translation, reprinting, reuse of
illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way,
and transmission or information storage and retrieval, electronic adaptation, computer software,
or by similar or dissimilar methodology now known or hereafter developed.
Trademarked names, logos, and images may appear in this book. Rather than use a trademark
symbol with every occurrence of a trademarked name, logo, or image we use the names, logos,
and images only in an editorial fashion and to the benefit of the trademark owner, with no
intention of infringement of the trademark.
The use in this publication of trade names, trademarks, service marks, and similar terms, even if
they are not identified as such, is not to be taken as an expression of opinion as to whether or not
they are subject to proprietary rights.
While the advice and information in this book are believed to be true and accurate at the date of
publication, neither the authors nor the editors nor the publisher can accept any legal
responsibility for any errors or omissions that may be made. The publisher makes no warranty,
express or implied, with respect to the material contained herein.
Managing Director, Apress Media LLC: Welmoed Spahr
Acquisitions Editor: Spandana Chatterjee
Development Editor: James Markham
Coordinating Editor: Divya Modi
Cover designed by eStudioCalamar
Cover image designed by Pixabay
Distributed to the book trade worldwide by Springer Science+Business Media New York, 1
New York Plaza, Suite 4600, New York, NY 10004-1562, USA. Phone 1-800-SPRINGER, fax (201)
348-4505, e-mail [email protected], or visit www.springeronline.com. Apress Media,
LLC is a California LLC and the sole member (owner) is Springer Science + Business Media
Finance Inc (SSBM Finance Inc). SSBM Finance Inc is a Delaware corporation.
For information on translations, please e-mail [email protected]; for reprint,
paperback, or audio rights, please e-mail [email protected].
Apress titles may be purchased in bulk for academic, corporate, or promotional use. eBook
versions and licenses are also available for most titles. For more information, reference our Print
and eBook Bulk Sales web page at http://www.apress.com/bulk-sales.
Any source code or other supplementary material referenced by the author in this book is
available to readers on GitHub via the book’s product page, located at www.apress.com/
9781484273913. For more detailed information, please visit http://www.apress.com/source-­code.
Printed on acid-free paper
 To my beloved father,
the late Ras Bihari Prasad
We miss you and love you, Papa. A strong and gentle
soul who taught us to trust God and to believe in ourselves
and our dreams.

To my beloved mother,
Smt. Manorma Devi
We love you, Maa. We could never have completed this
book without your true love, warmest support, and
constant encouragement.
Table of Contents
About the Authors��������������������������������������������������������������������������������ix

About the Technical Reviewer�������������������������������������������������������������xi

Acknowledgments�����������������������������������������������������������������������������xiii

Chapter 1: An Introduction to Amazon Web Services (AWS)����������������1

Introduction to Amazon Web Services������������������������������������������������������������������2
AWS Key Services�������������������������������������������������������������������������������������������������4
Elastic Cloud Compute (EC2)���������������������������������������������������������������������������5
Elastic Beanstalk���������������������������������������������������������������������������������������������7
Relational Database Service (RDS)������������������������������������������������������������������8
Route 53����������������������������������������������������������������������������������������������������������8
Use Case: AWS Application Architecture���������������������������������������������������������������9
Create a Free AWS Account for Developer������������������������������������������������������������9
Explore and Create an AWS Elastic Beanstalk Server�����������������������������������������19
Create a HelloWorld JSP Application, Build WAR with Maven,
and Upload WAR to Elastic Beanstalk�����������������������������������������������������������������26
Create a HelloWorld JSP Application�������������������������������������������������������������26
Package a WAR File Using Maven�����������������������������������������������������������������32
Upload WAR to Elastic Beanstalk�������������������������������������������������������������������34
Summary������������������������������������������������������������������������������������������������������������40

v
Table of Contents

Chapter 2: Deploy a Spring Boot Application as a

REST API in AWS���������������������������������������������������������������������������������41
Build a Spring Boot Application as a REST API����������������������������������������������������42
Introduction to REST��������������������������������������������������������������������������������������42
System Requirements�����������������������������������������������������������������������������������44
Create Spring Boot Application Using Spring Tool Suite��������������������������������45
A Walk-Through���������������������������������������������������������������������������������������������48
Run a Spring Boot Application in STS������������������������������������������������������������53
Add Swagger UI to a Spring Boot Application�����������������������������������������������������56
Introduction to Swagger 2�����������������������������������������������������������������������������56
Add Dependency in a Maven POM�����������������������������������������������������������������57
Configure Swagger 2 into a Project���������������������������������������������������������������57
Configuration Verification������������������������������������������������������������������������������59
Swagger UI����������������������������������������������������������������������������������������������������60
Configure the Server Port for a Spring Boot Project�������������������������������������������61
Build a JAR for a Spring Boot Application�����������������������������������������������������������63
Deploy a Spring Boot Application in AWS Elastic Beanstalk�������������������������������67
Test a Spring Boot Application as a REST API in the Cloud���������������������������������73
Explore Logs from Elastic Beanstalk�������������������������������������������������������������������74
Summary������������������������������������������������������������������������������������������������������������75

Chapter 3: Deploy MySQL as a Database in AWS with RDS����������������77

Introduction to Amazon RDS (Amazon Relational Database Service)�����������������78
Create an Instance of the RDS Database in AWS������������������������������������������������78
Configure Amazon RDS���������������������������������������������������������������������������������������86
Step 1. Configure Security for Inbound Connection Rules�����������������������������88
Step 2. Test an Amazon RDS Database Instance Connection with
MySQL Workbench����������������������������������������������������������������������������������������91

vi
 Table of Contents

Create a Table Inside an RDS Database Instance������������������������������������������������96

Summary����������������������������������������������������������������������������������������������������������102

Chapter 4: Deploy a Spring Boot Application Talking to

MySQL in AWS����������������������������������������������������������������������������������103
Create Spring Boot UserRegistrationApp Talking to MySQL Database��������������103
Maven Dependency in pom.xml������������������������������������������������������������������105
Project Lombok�������������������������������������������������������������������������������������������108
Application Properties���������������������������������������������������������������������������������111
Domain Implementation: UserDTO Entity Class�������������������������������������������112
Repository Implementation: UserJpaRepository�����������������������������������������114
Service Implementation: UserService���������������������������������������������������������116
REST Controller Implementation: UserRegistrationController����������������������117
Run and Test UserRegistrationApp Locally��������������������������������������������������������121
Retrieve All Users: /api/users����������������������������������������������������������������������122
Retrieve an Individual User: /api/user/id/{id}�����������������������������������������������123
Create a New User: /api/user/save��������������������������������������������������������������124
Delete an Existing User: /api/user/delete/id/{id}������������������������������������������126
Swagger UI: API Documentation������������������������������������������������������������������126
Build a JAR for a Spring Boot Application���������������������������������������������������������128
Deploy the UserRegistrationApp Spring Boot Application in
AWS Elastic Beanstalk��������������������������������������������������������������������������������������129
Test Deployed REST API in AWS Using Swagger UI�������������������������������������������135
List All Users: /api/users������������������������������������������������������������������������������137
Create New Users: /api/users����������������������������������������������������������������������139
Summary����������������������������������������������������������������������������������������������������������141

vii
Table of Contents

Chapter 5: Deploy a Full Stack Spring Boot React Application

in AWS and S3����������������������������������������������������������������������������������143
Develop and Run React as a Front-End Application������������������������������������������145
Introducing React as a Front-end Framework���������������������������������������������145
Set up a Development Environment������������������������������������������������������������149
Cross-Origin Resource Sharing (CORS) Error����������������������������������������������150
Developing React Front-End Application with create-react-app�����������������151
Build React Code as a Front-end Application for AWS��������������������������������������180
Verify the AWS Elastic Beanstalk Environment Is Up�����������������������������������180
Update BaseURL in a React App with an AWS Elastic Beanstalk
Environment URL�����������������������������������������������������������������������������������������181
Build React Code for AWS Deployment��������������������������������������������������������183
Deploy a React Front-End to AWS S3: Hosting a Static Website�����������������������185
Introduction to S3: Simple Storage Service in AWS�������������������������������������185
Create a Bucket�������������������������������������������������������������������������������������������188
Verify the Successful Deployment of a React Front-end Application:
Resolve a 404 Error�������������������������������������������������������������������������������������198
Summary����������������������������������������������������������������������������������������������������������200

Appendix A: Install MySQL Workbench on Windows 10�������������������201

Step 1. Download Workbench���������������������������������������������������������������������������201
Step 2. Install Workbench���������������������������������������������������������������������������������204

Appendix B: AWS Command-Line Interface (CLI)������������������������������213

Step 1. Download and Install the AWS CLI on a Windows Operating System���214
Step 2. Create an Access Key���������������������������������������������������������������������������214
Configure AWS CLI��������������������������������������������������������������������������������������������217
Example Commands That Work with S3�����������������������������������������������������������217

Index�������������������������������������������������������������������������������������������������219

viii
About the Authors
Ravi Kant Soni is a principal full stack
engineer with more than 11 years of IT
experience. He is also an AWS Certified
Solutions Architect. Ravi has experience
in software development, software
design, systems architecture, application
programming, and automation testing. He has
a bachelor’s degree in Information Science and
Engineering from Reva University, Bangalore;
and schooling from Bal Vikash Vidyalaya, Sasaram, and Bihar (India).
He is the author of Build Microservices with Spring Cloud and Spring
Boot (codered eccouncil, 2021), Full Stack AngularJS for Java Developers
(Apress, 2018), Spring: Developing Java Applications for the Enterprise
(Packt, 2017), and Learning Spring Application Development (Packt,
2015). He is also an esteemed member of the Board of Studies at the REVA
University School of Computing and Information Technology in Bangalore.
Contact Ravi at ­www.linkedin.com/in/november03ravikantsoni/.

ix
About the Authors

Namrata Soni is a self-taught web application

developer with a passion for beautiful and
interactive UIs. She has a degree in computer
science from Sagar Institute of Science &
Technology, Bhopal; and schooling from Bal
Vikash Vidyalaya, Sasaram, and Bihar (India).
She loves clean and well-tested code, is a
big fan of open source, and enjoys learning
something new. Currently, she is working
with React and Node.js to craft modern JavaScript applications. Contact
Namrata at ­www.linkedin.com/in/september-­6-­namrata-­soni/.

x
About the Technical Reviewer
Karunesh Chandra Tiwari is an IT professional
with ten years of experience and has worked
across distinct technologies and domains. He is
a technologist and speaker and loves to provide
his views on articles and blogs.
Karunesh is a BTech IT graduate from
Anna University. He worked as a full stack
developer for the first half of his career and
currently works with BPM and CRM tools
and cloud-related technologies, including
developing and working with applications for
some of the world’s leading banks. He is a very focused and determined
person and loves to learn, work in new technologies. He loves to mentor
people both from a professional and a personal perspective.
Karunesh enjoys working with new technologies and loves to
mentor people. Check out his LinkedIn profile at www.linkedin.com/in/
karunesh-­chandra-­tiwari-­20b9a82a/.

xi
Acknowledgments
Writing a technical book involves fathomless research, review, and
support. I wrote this book, but it wouldn’t have been possible without the
love and support of many people. I truly want to thank everyone listed
here, from the deep bottom of my heart!
First and foremost, I need to express gratitude toward Michael Gorriz,
Group Chief Information Officer, Standard Chartered Bank, for inspiring
me and giving me the confidence to write this book when I anticipated my
career break. All I can offer in return is a heartfelt thank you!
I want to thank my colleagues at Standard Chartered Bank. I learn
something new every day and enjoy a camaraderie I've never felt in any
company before. I am fortunate enough to work with such an experienced
team that helped me enhance my skills. My gratitude goes to Anshu
Sharma Raja, CIO, Consumer Private Business Banking at Standard
Chartered Bank, and Dr. Ashish Chandra, Location Head- aXess Labs
(Banking Innovation) at Standard Chartered Bank; for their guidance and
strong support.
I want to thank the Apress publishing team for the utmost
professionalism. The one individual who has been the roof of this shelter
is Divya Modi, coordinating editor, for supporting me in the writing of this
book. Also, I would like to express my special gratitude to James Markham,
development editor, whose vision, commitment, and persistent efforts
made publishing this book efficient.
My heartfelt thanks go to the technical reviewer, Karunesh Chandra
Tiwari, for his valuable input.

xiii
Acknowledgments

My deepest gratitude and appreciation go to my dear friend Awanish

Kumar, IAS – Deputy Commissioner, Delhi; for the intellectual stimulus
from time to time, which helped me approach the book from a unique
perspective.
Thanks to my dearest friend, Dr. Meena Soni (Incharge Medical
Officer, Surajpur - Basdei, and Chhattisgarh), for invariably motivating,
encouraging, and giving me positive thoughts that worked as fuel to carry on.
Without my families’ love, support, and understanding, this book
would have remained a virtual commodity. My profound thanks to my
beloved mother, Smt. Manorma Devi, for her love and support, which
encourages my knowledge to come out on paper to ignite the imagination
of others.
My special thanks go to a man who has been a rock of stability
throughout my life and whose loving spirit sustains me still—my uncle
Shri. Arun Kumar Soni for the great inspiration he has given me to achieve
all success in life. Thanks also to my brothers, Shashi Kant and Shree Kant,
and all my family members who have loved me.
My special thanks to my co-author and sister, Namrata Soni, for
agreeing to co-author this book and helping me write Chapter 5, which
discusses React and AWS S3. I’m still amazed that she agreed to get
involved with this book, considering how enormously busy she is.
Namrata, thank you!
I want to thank the goddess Maa Tara Chandi, Sasaram, Bihar, India;
for giving me to such an extent.
Finally, this book is based on the innovative work of many people in
our industry who have become my idols. I am thankful to everyone who
supported me in one way or another in writing this book.
Welcome to Spring Boot with React and AWS.

—Ravi Kant Soni

xiv
CHAPTER 1

An Introduction
to Amazon Web
Services (AWS)
When you hear the word amazon, you likely first think of Amazon.com,
which is one of the biggest and most successful online stores. While
Amazon built its brand on developing online retail services, it has also
branched out into alternative industries, among them the web services
industry, where they have the eponymous Amazon Web Service (AWS),
a form of cloud-computing that assists users develop software, database,
and other programs that need heavy-duty computing resources.
This chapter overviews Amazon Web Services (AWS), including several
AWS key services, such as Amazon Elastic Compute Cloud (Amazon EC2),
AWS Elastic Beanstalk, Amazon Relational Database Service (Amazon
RDS), and Amazon Route 53. It covers creating a free AWS account for
developers, creating an Elastic Beanstalk server, creating a HelloWorld JSP
application, building a WAR file with Maven, and uploading it to Elastic
Beanstalk.

© Ravi Kant Soni and Namrata Soni 2021 1

R. K. Soni and N. Soni, Spring Boot with React and AWS,
https://doi.org/10.1007/978-1-4842-7392-0_1
Chapter 1 An Introduction to Amazon Web Services (AWS)

Introduction to Amazon Web Services

What precisely is Amazon Web Services (AWS)? At a really high level,
AWS is a web-hosting service offered by Amazon, where you can deploy
your web applications and conjointly deploy your databases. Once it’s
deployed, your apps are out there online. Anyone can simply enter your
URL (Universal Resource Locator) in their web browser to access your
application. The web connects everybody. You can deploy your application
online within the cloud, so that anyone can access it. It’s not only running
locally; it’s now running online.
AWS is a full-service cloud platform. It is more than just an application
hosting platform. There are plenty of belongings you do with AWS.

• On-demand delivery of IT resources via the web

• You can spin up servers on-demand, and you can

choose your operating system.

• You can even deploy databases within the cloud,

and you get more options for the database as you
wish.

• Pay-as-you-go pricing model

• This book uses free developer accounts. You can get

a free developer account for 12 months.

And, the nice thing about using the Amazon Web Services cloud is that
you can be global within minutes because Amazon has worldwide data
centers, as shown in Figure 1-1.

2
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-1. Amazon data center

You’ll be able to deploy your application to a single data center;

otherwise, you’ll deploy it to multiple data centers. Also, there are no
restrictions on which data center you’ll be able to deploy to.
If you’re based mostly within the United States, however, you can
deploy applications to the data center in South America, China, or the Asia
Pacific. It’s completely up to you. The user can select the regions based on
the application usage so that latency is low. There’s no restriction as such
on it.
Once you’re logged in to the Amazon console, then essentially, you
choose the services that you simply wish to use. You need to only deploy
your applications to have a pleasant web admin console where you only
configure your environment, configure your servers, then reasonably
push-button deploy. Figure 1-2 shows the AWS services on AWS
Management Console.

3
Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-2. AWS

This was all about an introduction to Amazon Web Services. Let’s dig
into some of the AWS key Services.

AWS Key Services

AWS offers a wide range of services underneath different categories. This
section explores several AWS key services (see Figure 1-3). First, let’s look
at Amazon Elastic Compute Cloud (Amazon EC2), which may include
remote VMs (virtual machines). Next, you briefly look at AWS Elastic

4
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Beanstalk, which allows developers to deploy web applications. Then, you

move on to the Amazon Relational Database Service (Amazon RDS), which
is a database within the cloud. Finally, you look at Amazon Route 53, which
routes custom domain names to your application.

Figure 1-3. AWS key services

Elastic Cloud Compute (EC2)

Elastic Cloud Compute (EC2) is one of the first web service interfaces when
AWS was released, allowing users to create and configure compute machines
within the cloud. EC2 allows users to create VM (virtual machine) on the
Amazon cloud for running applications that can be accessed via the Internet.
The software can be configured on cloud servers based on your
specifications. You select the operating system (i.e., Microsoft Windows or
Linux) best suited to your requirements or applications, and you get the
operating system pre-installed. EC2 provides the actual host server and
operating system. Figure 1-4 shows how it is set up.

5
Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-4. How EC2 is set up

If you want any additional software, you must manually install it on

top of the OS as a developer. So, if you want JDK (Java Development Kit),
you can install Java. You can also install Tomcat, a database, and so on. It’s
almost like getting a brand-new laptop that only has the operating system,
and you need to install your tools on top of it.

6
 Chapter 1 An Introduction to Amazon Web Services (AWS)

E lastic Beanstalk
Elastic Beanstalk is a pre-packaged platform, allowing you to quickly
deploy and handle your web applications without worrying about the
infrastructure. You select a pre-configured virtual machine for your
given web stack, like Java and Tomcat. And, there is no need to install
any additional software’s on the virtual machine. You simply upload the
application’s deployable file, and then you are out there and ready to go.
Elastic Beanstalk automatically provides the application server, language
runtime, operating server, and the host server, as shown in Figure 1-5.

Figure 1-5. Elastic Beanstalk

7
Chapter 1 An Introduction to Amazon Web Services (AWS)

It also has support for .NET, Node.js, PHP, Docker, and so on. You can
choose the web stack that gives you all the software’s pre-installed, pre-­
configured, and you simply deploy your code.
It’s great for deployment on a web stack, you simply select the services
that you need, and it is set up for you. This is known as platform as a
service, or PaaS. All you have to do is deploy your code.
Now, when you develop Java applications on AWS, you can use your
regular Java EE APIs. You can also use third-party frameworks like Spring
Boot, Hibernate, and anything in standard Java. Whatever you can run
on Tomcat locally, you can run that same code on Amazon. So, there are
no code changes you need to make and no special Amazon JAR files or
anything.

Relational Database Service (RDS)

AWS Relational Database Service (RDS) is your relational database in the
cloud. This allows you to quickly deploy a relational database in the cloud.
It has support for a wide range of databases to choose from, including
MySQL, Oracle, Microsoft SQL Server, and so on.
You can manage these tools using your normal admin tools. If you are
using MySQL, you can use MySQL Workbench. If you are using the Oracle
Database, you can use Oracle SQL Developer, and the list goes on.
AWS also has support for NoSQL databases such as MongoDB. So,
all major database feature’s that you need can be found in AWS with the
support of the relational Database Service.

Route 53
Amazon Route 53 is a Domain Name System (DNS), which allows you to
route your custom domain names to your actual application on AWS. So,
you configure Route 53 to send requests from the browser to your AWS
application. The AWS DNS sets up your custom domain name.

8
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Use Case: AWS Application Architecture

For your apps, start with AWS Elastic Beanstalk because you can quickly
get started with deploying your application by leveraging those pre-­
configured web stacks out of the box.
Use EC2 if you need some low-level control. For example, you may
want to use a version of Java that Elastic Beanstalk does not support, or you
may want to use a Java application server like WebLogic or make another
OS-specific customization.
Figure 1-6 shows that the architecture uses Elastic Beanstalk to deploy
the web application. The Java application runs on Tomcat. RDS is the
database in the cloud using MySQL. Route 53 routes your custom domain
name to your application hosted on AWS.

Figure 1-6. AWS application architecture

Create a Free AWS Account for Developer

To access Amazon Web Services, you need to create an AWS account. First,
let’s talk about the AWS free tier, where developers get a free 12 months trial
period and enough resources to deploy your application and database for
free. There is also a smaller version of AWS servers that you can use for free.

9
Chapter 1 An Introduction to Amazon Web Services (AWS)

If you need to have some more advanced features, then you must
pay and get access. This book uses the free tier. If you would like more
information on the free tier, go to https://aws.amazon.com/free/.
In your web browser, go to https://aws.amazon.com to open the
Amazon Web Services home page (see Figure 1-7; this screenshot may be
different on your screen due to any updates by Amazon).

Figure 1-7. AWS main page

To create an AWS account, you need to provide your contact

information, including your address, and a valid debit or credit card. Even
though you are using a free account, Amazon needs your credit or debit
card information. So, have it handy when creating your AWS account.
On the top right of the main page, click the Create an AWS Account
button. You are redirected to the sign up for the AWS page, as shown in
Figure 1-8.

10
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-8. Sign up for AWS

Enter your email address, password (choose a strong password to

prevent getting hacked), and the AWS account name that you want for
this account. You must be sure that the account information you enter
is correct, especially your email address. If you enter an incorrect email
address, you can’t access your account.
Click the Continue button to enter your contact information, as shown
in Figure 1-9.

11
Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-9. Contact information

First, select the Personal account type. (A business account is

associated with an organization, and a personal account is associated with
an individual.) Enter your full name, phone number, country, address, city,
state, and postal code.

12
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Finally, select the little check box at the bottom to show that you have
read and agree to the terms of the AWS Customer Agreement, and then
click the Continue button.
You receive an email from AWS to confirm that your AWS account has
been created. You can sign in to your new account using the email address
and password you registered with. However, you can’t use AWS services
until you finish your account activation.
Billing information is where you must enter your credit or debit card
number and so forth, as shown in Figure 1-10. It is used for verification
purposes.

13
Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-10. Billing information

Amazon does not charge your card unless your usage exceeds AWS
Free Tier limits. In this book, everything that we show you is within the
Free Tier limits.
AWS requires phone number verification, as shown in Figure 1-11.
Choose your country or region code from the list, enter a phone number
where you can be immediately reached, and enter the characters displayed
in Security Check.

14
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-11. Phone number verification

Once you type the security check characters, click the Call Me Now
button. A verification code is displayed on the screen, and at the same
time, you get a call from Amazon to verify your registered phone number.
You must enter the PIN you received and choose to continue. Once your
identity has been successfully verified, you can see on the window that
your phone is verified, and you are redirected to the next screen to choose
your support plan, as shown in Figure 1-12.

15
Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-12. Support plan

Choose the support plan that meets your needs. Select the Basic Plan
for free support. Click the Free button, and you are redirected to the AWS
Registration Confirmation page.
Now you can sign in to the AWS Management Console. Go to https://
console.aws.amazon.com to start using AWS.
Select Root user, enter your AWS account email address, and click the
Next button, as shown in Figure 1-13.

16
 Chapter 1 An Introduction to Amazon Web Services (AWS)

Figure 1-13. Sign in to the console

Next, enter your AWS account password, and click Sign in, as shown in
Figure 1-14.

17
Discovering Diverse Content Through
Random Scribd Documents
The Project Gutenberg eBook of The Death of
Captain Wells
This ebook is for the use of anyone anywhere in the United States
and most other parts of the world at no cost and with almost no
restrictions whatsoever. You may copy it, give it away or re-use it
under the terms of the Project Gutenberg License included with this
ebook or online at www.gutenberg.org. If you are not located in the
United States, you will have to check the laws of the country where
you are located before using this eBook.

Title: The Death of Captain Wells

Author: Allan H. Dougall

Creator: Public Library of Fort Wayne and Allen County

Release date: July 21, 2021 [eBook #65890]

Language: English

Credits: Stephen Hutcheson and the Online Distributed Proofreading

Team at https://www.pgdp.net

*** START OF THE PROJECT GUTENBERG EBOOK THE DEATH OF

CAPTAIN WELLS ***
 Captain William Wells

THE DEATH OF CAPTAIN WELLS

Prepared by the Staff of the

Public Library of Fort Wayne and Allen County
1954

i
One of a historical series, this pamphlet is published under the direction of
the governing Boards of the Public Library of Fort Wayne and Allen County.

BOARD OF TRUSTEES OF THE SCHOOL CITY OF FORT WAYNE

B.F. Geyer, President
Joseph E. Kramer, Secretary
W. Page Yarnelle, Treasurer
Mrs. Sadie Fulk Roehrs
Willard Shambaugh

PUBLIC LIBRARY BOARD FOR ALLEN COUNTY

The members of this Board include the members of the Board of Trustees of
the School City of Fort Wayne (with the same officers) together with the
following citizens chosen from Allen County outside the corporate City of Fort
Wayne.

James E. Graham
Arthur Niemeier
Mrs. Glenn Henderson
Mrs. Charles Reynolds

1
 FOREWORD
The character of William Wells remains an enigma, for his life has
long been obscured by conflicting accounts of his role in Indian
affairs. At one time, William Henry Harrison, governor of the Indiana
Territory, thought him untrustworthy and believed that he should be
removed from his position as Indian agent. Wells often appeared to
his contemporaries as a turncoat and a traitor to his own people
because of his sympathy with the red men. Other accounts, chiefly
by his military associates, are earnest tributes to his strength and
valor. Captain Allan H. Dougall, author of the following article,
considered Wells only a “celebrated Indian fighter.”

Captain Dougall relates the death of Wells at the Massacre of Fort

Dearborn, on the site of the present city of Chicago. His account first
appeared in the FORT WAYNE DAILY GAZETTE, December 18, 1887.
The Boards and the Staff of the Public Library of Fort Wayne and
Allen County reprint the item in the hope that it will interest and
inform local readers. Grammar, spelling, and punctuation have been
changed to conform to current usage.

3
In July, 1812, Captain Nathan Heald, then in command of Fort
Dearborn, notified General William Hull that he was being
surrounded by a furious band of Indians who were in communication
with Tecumseh; Heald desired aid immediately. General Hull sent an
express to Fort Wayne to speed the immediate relief of Captain
Heald and his command. Hearing of the proposed expedition,
Captain William Wells volunteered to go to the relief of Captain
Heald and to act as escort for the soldiers. His offer was accepted;
on August 3, 1812, he set out with thirty hand-picked Miami
warriors, who were friendly, fully equipped, and full of hope and
courage.

Wells had been stolen by the Miami when he was a boy of twelve;
soon afterward he was adopted by Little Turtle, their great chief. He
served with the Indians at the outbreak of hostilities in 1790 and
was present at the defeat of St. Clair near Fort Recovery, Ohio. It is
said, however, that he then began to realize that he was fighting
against his own kindred, and he soon resolved to leave the Indians.
Therefore, he asked Little Turtle to accompany him east of Fort
Wayne to a point on the Maumee known as the “Big Elm.” When the
two had reached this spot, Wells said: “Father, we have long been
friends; I now leave you to go to my own people. We will be friends
until the sun reaches the midday height. From that time we will be
enemies. If you want to kill me then, you may. If I want to kill you, I
may.” He then crossed the Maumee River and set out for General
Wayne’s army. Sometime after reaching Wayne, he was made
captain of a company of scouts. Later he settled north of the St.
Mary’s River on a farm which is still known as Wells Reserve. At this
time he served as Indian agent and as justice of the peace. Wells
also rendered valuable services to General Harrison, governor of the
territory.

4
 “...we have long been friends...”

Nothing unusual occurred on the journey of Captain Wells to 5

Fort Dearborn with his Miami warriors. He arrived safely on the
evening of August 12, but he was too late to have any influence on
the question of the evacuation of the fort. Captain Heald had already
determined to follow out General Hull’s instructions by agreeing to
deliver the fort and its contents to the Indians. The supplies of
muskets, ammunition, and whisky were very large; and it appears
that Captain Heald had thought of leaving them as they were. On
learning this, Captain Wells told him that it was madness to hand
over these supplies, which would only serve to excite the already
infuriated Indians. In this opinion, Captain Wells was ably supported
by John Kinzie and some of the junior officers, who prevailed on
Captain Heald to destroy the supplies. Accordingly, on the night of
the thirteenth, he caused all surplus ammunition and arms to be
destroyed and all the whisky to be thrown into Lake Michigan. In the
afternoon of the fourteenth, a council was held between the whites
and the Indians, at which the Potawatomi professed to be highly
indignant at the destruction of the whisky and ammunition; they
made numerous threats which plainly showed their murderous
intentions.

Black Partridge, who was one of the most influential of the

Potawatomi chiefs, had been friendly to the whites since the Treaty
of Greenville in 1795, when he had received a medal from General
Wayne. In the evening Black Partridge came to the fort and entered
Captain Heald’s headquarters. “Father,” he said, “I come to deliver
up to you the medal I wear. It was given me by the Americans, and I
have long worn it as a token of mutual friendship. But now our
young men are resolved to imbrue their hands with the blood of the
whites, and I cannot restrain them. I will not wear a token of peace
when I am compelled to act as an enemy.”
As the number of Indians about the fort was constantly increasing,
Captain Heald at last decided to evacuate the fort, which he should
have done before. On the morning of August 15, 1812, the troops
commenced to move out of the fort; by some strange and weird
choice of the drum major, a dead march was played as they
marched.

6
 to deliver up to you the medal

They advanced along the lake shore, keeping near the water 7
east of the sand hills and banks; these elevations partially
screened them from view. The group had not proceeded far, when to
their surprise the five hundred Potawatomi who had volunteered as
an escort suddenly filed to the right and rapidly disappeared among
the sand hills. As soon as the Indians were out of sight on the west
side of the hills, they crouched down to hide their movements and
ran ahead some distance to form an ambuscade. Then they awaited
the coming of the troops. Riding ahead, Captain Wells had observed
their movements; with his experience he knew immediately that the
party would be attacked. He returned to the troops, dismounted,
assembled the soldiers, and marched them forward. When the little
band had reached a point about one and a half miles from the fort,
the Indians opened fire on them. The company of soldiers charged
up the bank and over the sand hills, firing as they advanced, while
the Indians returned the fire with deadly effect from their sheltered
position. As soon as the fighting commenced, the friendly Miami who
had come from Fort Wayne and had stood by their adopted brother,
Captain Wells, and their white allies, deserted them and took no part
in the fight. Captains Wells and Heald and their small body of troops,
fighting against fearful odds, succeeded in dislodging the enemy
from their sheltered position; but the Indians were so numerous that
part of them were able to outflank the soldiers and to take
possession of their horses and baggage.

During the fight a young Indian crept up to the baggage wagon,

which contained twelve children, and tomahawked and scalped all of
its occupants. Captain Wells, after fighting desperately, was
surrounded and stabbed in the back. His body was horribly mangled;
his head was cut off, and his heart was cut out and eaten by the
savages. They thought that some of the brave captain’s courage and
skill would thus be imparted to them. He was indeed a fearless
officer and a celebrated Indian fighter, but the odds against him had
been too great. Fifty-two whites were killed, including twenty-six
soldiers, twelve militiamen, two women, and twelve children.

Captain Heald ordered a retreat and withdrew the small remnant of

his command. A parley ensued, and Heald surrendered on the
condition that lives be spared. The soldiers then marched back to
the fort, which was immediately plundered and burned by the
Indians.

It is sentimental nonsense to attribute the massacre to the 8

failure of Captain Heald to act promptly at the time of the
evacuation. The experiences and records of those who lived with
and had dealings with Indians show beyond all doubt that as a race
they are treacherous by nature. The more the government and
individuals do for them, the more treacherous and unreliable they
become.

CAPTAIN ALLAN H. DOUGALL

FORT WAYNE DAILY GAZETTE, December 18, 1887

 Transcriber’s Notes
Silently corrected a few typos.
Retained publication information from the printed edition: this
eBook is public-domain in the country of publication.
In the text versions only, text in italics is delimited by
_underscores_.
 *** END OF THE PROJECT GUTENBERG EBOOK THE DEATH OF
CAPTAIN WELLS ***

Updated editions will replace the previous one—the old editions will
be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying
copyright royalties. Special rules, set forth in the General Terms of
Use part of this license, apply to copying and distributing Project
Gutenberg™ electronic works to protect the PROJECT GUTENBERG™
concept and trademark. Project Gutenberg is a registered trademark,
and may not be used if you charge for an eBook, except by following
the terms of the trademark license, including paying royalties for use
of the Project Gutenberg trademark. If you do not charge anything
for copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the free

distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund
from the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only be

used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law
in the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name associated
with the work. You can easily comply with the terms of this
agreement by keeping this work in the same format with its attached
full Project Gutenberg™ License when you share it without charge
with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the
terms of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.

1.E. Unless you have removed all references to Project Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears,
or with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:
 This eBook is for the use of anyone anywhere in the United States
and most other parts of the world at no cost and with almost no
restrictions whatsoever. You may copy it, give it away or re-use it
under the terms of the Project Gutenberg License included with
this eBook or online at www.gutenberg.org. If you are not located
in the United States, you will have to check the laws of the
country where you are located before using this eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is derived

from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is posted

with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning
of this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute this

electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the Project
Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or
expense to the user, provide a copy, a means of exporting a copy, or
a means of obtaining a copy upon request, of the work in its original
“Plain Vanilla ASCII” or other form. Any alternate format must
include the full Project Gutenberg™ License as specified in
paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or providing

access to or distributing Project Gutenberg™ electronic works
provided that:

• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
 about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who

notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of

any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™

electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend

considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or
damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for

the “Right of Replacement or Refund” described in paragraph 1.F.3,
the Project Gutenberg Literary Archive Foundation, the owner of the
Project Gutenberg™ trademark, and any other party distributing a
Project Gutenberg™ electronic work under this agreement, disclaim
all liability to you for damages, costs and expenses, including legal
fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR
NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR
BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK
OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL
NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF
YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you

discover a defect in this electronic work within 90 days of receiving
it, you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or
entity that provided you with the defective work may elect to provide
a replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.

1.F.4. Except for the limited right of replacement or refund set forth
in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied

warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.

1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation,

the trademark owner, any agent or employee of the Foundation,
anyone providing copies of Project Gutenberg™ electronic works in
accordance with this agreement, and any volunteers associated with
the production, promotion and distribution of Project Gutenberg™
electronic works, harmless from all liability, costs and expenses,
including legal fees, that arise directly or indirectly from any of the
following which you do or cause to occur: (a) distribution of this or
any Project Gutenberg™ work, (b) alteration, modification, or
additions or deletions to any Project Gutenberg™ work, and (c) any
Defect you cause.

Section 2. Information about the Mission

of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the

assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will
remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.

Section 3. Information about the Project

Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.

The Foundation’s business office is located at 809 North 1500 West,

Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact

Section 4. Information about Donations to

the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many
small donations ($1 to $5,000) are particularly important to
maintaining tax exempt status with the IRS.

The Foundation is committed to complying with the laws regulating

charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states where

we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot make

any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.

Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.

Section 5. General Information About

Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.
Project Gutenberg™ eBooks are often created from several printed
editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.