AWS

Articles

AWS Status
AWS Support
AWS Developer Forum
AWS Security Center

Articles
Main Getting Started Guide
Management Console
Miscellaneous
Developer Tools, SDKs, and sample code

Lambda - Serverless
EC2: Provides the basic computing need. It provide the machine.
RDS: (Relational Database Service) Makes it easy to set up, operate, and scale a relational database in the cloud.
SES: (Simple Email Service) Highly scalable and cost-effective bulk and transactional email-sending service for the cloud.
S3: Simple Storage Service
Auto Scaling: Allows you to automatically scale your Amazon EC2 capacity up or down according to conditions you define.
Elastic Load Balancing: Fill the role of the traditional load balancer.
CloudFront: Content Delivery Network. Distribute content with low latency via a global network of edge locations.
IAM (Identity and Access Management)
CloudWatch: Provides monitoring for AWS resources.
Beanstalk: Automated Deployment.
AWS-CLI
Sample scripts
Other services

https://youtu.be/atXNUnttjh0 - AWS June 2016 Webinar Series - Amazon Redshift or Big Data Analytics
https://youtu.be/wfUTdeH7-Ko - AWS June 2016 Webinar Series - Amazon Aurora Deep Dive - Optimizing Database Performance
https://d0.awsstatic.com/product-marketing/Aurora/RDS_Aurora_Performance_Assessment_Benchmarking_v1-2.pdf
https://d0.awsstatic.com/whitepapers/RDS/Migrating%20your%20databases%20to%20Amazon%20Aurora.pdf

CloudFormation: Provides developers and businesses an easy way to create a collection of related AWS resources and provision them in an orderly and predictable fashion.

How can we log into AWS Management console?

  1. Go to http://console.aws.amazon.com/ and login with your regular Amazon account

How can we launch an EC2 instance?

  1. Log into the main AWS Management console
  2. Click on EC2
  3. Click on the "Launch Instance" button
  4. Select appropriate AMI and follow on-screen instruction

How can we get back to the main management console from inside a service-specific management console?

  1. Click on the AWS orange icon in the top left corner

How can we navigate between different management console?

  1. Click on the Services drop-down arrow in the top navigation bar

How can we get various information of an EC2 instance?

  1. Log into the main management console
  2. Click on EC2
  3. Click on Running Instances
  4. Click on the appropriate instance
  5. Look at the bottom frame

You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or ec2-describe-instances (Amazon EC2 CLI) command.

How can we enable inbound SSH traffic from your IP address to your instance?

Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address.

How can we verify the RSA key fingerprint of an instance?

You can verify the RSA key fingerprint on your running instance by using one of the following commands on your local system (not on the instance). This is useful if you've launched your instance from a public AMI from a third party. Locate the SSH HOST KEY FINGERPRINTS section, and note the RSA fingerprint (for example, 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f) and compare it to the fingerprint of the instance.

aws ec2 get-console-output --instance-id instance_id
ec2-get-console-output instance_id

Ensure that the instance is in the running state, not the pending state. The SSH HOST KEY FINGERPRINTS section is only available after the first boot of the instance.

How can we connect to an instance via SSH?

  1. Open a command line shell.
  2. Change directories to the location of the private key file that you created when you launched the instance.
  3. Use the chmod command to make sure your private key file isn't publicly viewable. For example, if the name of your private key file is my-key-pair.pem, use the following command: chmod 400 /path/my-key-pair.pem
  4. Use the ssh command to connect to the instance. You'll specify the private key (.pem) file and user_name@public_dns_name. For Amazon Linux, the user name is ec2-user. For RHEL5, the user name is either root or ec2-user. For Ubuntu, the user name is ubuntu. For Fedora, the user name is either fedora or ec2-user. For SUSE Linux, the user name is either root or ec2-user. Otherwise, if ec2-user and root don't work, check with your AMI provider.
ssh -i /path/my-key-pair.pem ec2-user@ec2-198-51-100-1.compute-1.amazonaws.com
ssh -i /Users/khaidoan/.ssh/KhaiPersonalKeyPair.pem ec2-user@52.88.189.101

You'll see a response like the following.

The authenticity of host 'ec2-198-51-100-1.compute-1.amazonaws.com (10.254.142.33)'
can't be established.  RSA key fingerprint is 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f.
Are you sure you want to continue connecting (yes/no)?

(Optional) Verify that the fingerprint in the security alert matches the fingerprint that you obtained in step 1. If these fingerprints don't match, someone might be attempting a "man-in-the-middle" attack. If they match, continue to the next step.

scp -i /path/my-key-pair.pem SampleFile.txt ec2-user@ec2-198-51-100-1.compute-1.amazonaws.com:~

Where should we keep the key pair file?

Windows users: We recommend saving your key pair in your user directory in a sub-directory called .ssh (ex. C:\user\{yourusername}\.ssh\MyFirstKey.pem).

Mac/Linux users: We recommend saving your key pair in the .ssh sub-directory from your home directory (ex. ~/.ssh/MyFirstKey.pem).

What is the definition of Availability Zones and Regions?

Availability Zones are distinct locations that are engineered to be insulated from failures in other Availability Zones and provide inexpensive, low latency network connectivity to other Availability Zones in the same Region. Regions consist of one or more Availability Zones, are geographically dispersed, and will be in separate geographic areas or countries.

How can we protect our application from failure that occur in a geographical area?

By launching instances in separate Availability Zones, you can protect your applications from failure of a single location.

What is Enhanced Networking?

Enhanced Networking enables you to get significantly higher packet per second (PPS) performance, lower network jitter and lower latencies. This feature uses a new network virtualization stack that provides higher I/O performance and lower CPU utilization compared to traditional implementations. In order to take advantage of Enhanced Networking, you should launch an HVM AMI in VPC, and install the appropriate driver. Enhanced Networking is currently supported in C3 instances. For instructions on how to enable Enhanced Networking on EC2 instances, see the Enhanced Networking on Linux and Enhanced Networking on Windows tutorials. To learn more about this feature, check out the Enhanced Networking FAQ section.

What can we do when you exceed your limit?

If you wish to run more than 20 On-Demand or Reserved Instances or 100 Spot Instances, create more than 5,000 EBS volumes, need more than 5 Elastic IP addresses or 5 Elastic Load Balancers, or need to send large quantities of email from your EC2 account, please complete the Amazon EC2 instance request form, Amazon EBS volume request form, Elastic IP request form, Elastic Load Balancers, or the Email request form respectively and your request will be considered.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License