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

IAM best practices


The security of your AWS resources can be maintained by following these best practices:

  • Never share credentials (that is, the password or access key and secret key). Specifically, sharing root user credentials can pose a very serious security threat as they carry the highest level of access in the relevant AWS account.
  • Never use the root account for day-to-day tasks. Create individual IAM users for designated roles and responsibilities.
  • Until and unless it is essential, do not create an access key and a secret key. Also, keep rotating the password and keys periodically.
  • It is not best practice to hardcode the access key and secret key in any program or application.
  • Keep your access key and secret key secured so that they do not fall into the hands of any unauthorized person. A secret key is only generated once paired with a relevant access key. If a secret key is lost, then there is no mechanism in AWS to retrieve it. You need to discard the existing key and regenerate it....