Book Image

Expert AWS Development

By : Atul Mistry
Book Image

Expert AWS Development

By: Atul Mistry

Overview of this book

Expert AWS Development begins with the installation of the AWS SDK and you will go on to get hands-on experience of creating an application using the AWS Management Console and the AWS Command Line Interface (CLI). Then, you will integrate applications with AWS services such as DynamoDB, Amazon Kinesis, AWS Lambda, Amazon SQS, and Amazon SWF. Following this, you will get well versed with CI/CD workflow and work with four major phases in the release process – Source, Build, Test, and Production. Then, you will learn to apply AWS Developer tools to your Continuous Integration (CI) and Continuous Deployment (CD) workflow. Later, you will learn about user authentication using Amazon Cognito, and also how you can evaluate the best architecture as per your infrastructure costs. You will learn about Amazon EC2 service and will deploy an app using it. You will also deploy a practical real-world example of a CI/CD application with the Serverless Application Framework, which is known as AWS Lambda. Finally, you will learn how to build, develop, and deploy the Application using AWS Developer tools such as AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline, as per your project requirements.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Troubleshooting instances


Following are some of the troubleshoot problems that might happen with your instance. 

Instance terminates immediately

It is always a best practice to check the status after you launch an instance; it should be in the running state after the pending state, and not in the terminated state. Here are possible reasons to terminate the instance immediately after launch:

  • Your EBS volume limit was reached. This is a soft limit and you can increase it by submitting a request to AWS Support.
  • A corrupted EBS snapshot.
  • You launch the instance from the instance store-backed AMI, and that AMI is missing a required part of the file, such as image.part.xx.

Instance termination reasons:

From the Amazon EC2 console, AWS CLI, or API, you can get the reason for instance termination.

For that, log on to the Amazon EC2 console, navigate to Instances, and select your instance. Under the Description tab, check State transition reason and State transition reason message. Or, you can execute this...