Launching AWS hosting services.

Hoisting SAAS code from AWS single cloud storage for multiple users

 

 


Steps to upload source codes to aws:

 

  1. We have to choose the required container for our application based on the use cases to upload the source codes.

  2. Then we have to make that source code public to all the other applications that are running on our AWS account within the same region.

  3. This S3 bucket can be used for more static sides of the application we are launching( images, blogs, videos) which we can be rendered fast from these buckets.

Steps to start a instance using AWS:

 

  1. Instances are nothing but virtual servers that we can use to run our application.

  2. These servers are configurable based on our needs.

  3. Scalable, Reliable and cost effective as we only have to pay as we use.

  4. We can setup the server with the required configurations for CPUs and storage needs from AWS EC2.

  5. We have to create instances in the same region as the codes are stored in a bucket.

  6. While creating an instance, we will have a key pair which contains both public and private keys, and security credentials which will be used to authenticate while accessing the EC2.

  7. While creating new instances, we have to specify the security group which will be used by AWS to provide secure connections for incoming requests and outgoing responses. We can choose one or more security groups to protect our instance. ( If the security provided by the AWS group is not enough we can maintain our own firewall in addition to security groups).

  8. Once the instance is created the public IP for the created instance is generated. We can use that to give it to clients to access our services after deployment.

 

Steps to deploy the application from github:

 

  1. We have to install code deploy agent into our created instances, to deploy our application.

  2. We can then use the github repository to link the source codes to the deployment agent.

  3. We can specify the exact commit which we want to deploy on the created EC2 instance.

  4. After deployment, we can check the status of the deployment in the status column whether it is successful or failure.

  5. If failure, we have to choose ‘view logs’ or ‘view in EC2’ to get the tips for turning failure into success.

 

Steps to deploy application from S3 bucket:

 

  1. In code deploy app, we need to choose custom deploy in that custom deployment choose the file type to be .zip file which was uploaded to S3 bucket.

  2. Then choosing deploy option will deploy the source codes into the EC2 instance that we are created.

  3. To Re-deploy the application with latest revision, we need to create new zip file in the s3 bucket then follow the steps 1 and 2 to deploy the application with the latest revision of source codes.

 

Monitoring the instances using dashboard:

  1. we can use the dashboard to monitor, audit and review the instances using Amazon cloudwatch Dashboard feature in AWS.

  2. we can use a already present dashboard or custom dashboard using line, stacked area, number, text and query result from these 5 options available.

  3. We can use the metrics available to monitor different instances like CPU usage, DB usage, Dynamo DB usage, parse logs into (latency, success and failure API calls) so then we can analyze our application more efficiently.

  4. We should write scripts to parse the logs we receive from API calls, to avoid throttling the cloudwatch as only 150 request per second is allowed to cloudwatch.

  5. Cloudwatch offers a minimum of 1 second to update the metrics, so we can choose the time frame we required to update the metrics for our analysis on dashboard.

Comments

Popular posts from this blog

Converting ids into order id in join statement.

RDBMS vs NOSQL