Book Image

AWS Certified Developer - Associate Guide

By : Vipul Tankariya, Bhavin Parmar
Book Image

AWS Certified Developer - Associate Guide

By: Vipul Tankariya, Bhavin Parmar

Overview of this book

AWS Certified Developer - Associate Guide starts with a quick introduction to AWS and the prerequisites to get you started. Then, this book gives you a fair understanding of core AWS services and basic architecture. Next, this book will describe about getting familiar with Identity and Access Management (IAM) along with Virtual private cloud (VPC). Moving ahead you will learn about Elastic Compute cloud (EC2) and handling application traffic with Elastic Load Balancing (ELB). Going ahead you we will talk about Monitoring with CloudWatch, Simple storage service (S3) and Glacier and CloudFront along with other AWS storage options. Next we will take you through AWS DynamoDB – A NoSQL Database Service, Amazon Simple Queue Service (SQS) and CloudFormation Overview. Finally, this book covers understanding Elastic Beanstalk and overview of AWS lambda. At the end of this book, we will cover enough topics, tips and tricks along with mock tests for you to be able to pass the AWS Certified Developer - Associate exam and develop as well as manage your applications on the AWS platform.
Table of Contents (29 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
Index

Understanding the AWS root user


Creating an AWS account also creates a root user. The email and password supplied at the time of creating the AWS account becomes the username and password for the root user. This combination of an email address and password is called the root account credentials.

The root account, that is, the root user, has complete, unrestricted access to all resources, including billing information on the account. This is a supreme user and its permission cannot be altered by any other user on the account.

Since the root account has unrestricted access to all the resources on the account, it is highly recommended that you avoid using the root account for day-to-day activities. On a newly created AWS account, it is recommended that you create individual IAM users based on the organizational need and assign them the required permissions. These non-root-user accounts should be used for day-to-day activities.

Note

It is best practice not to share individual credentials with other...