Amazon Elastic Compute Cloud User Guide For Linux Instances
User Manual:
Open the PDF directly: View PDF
Page Count: 836 [warning: Documents this large are best viewed by clicking the View PDF Link!]
- Amazon Elastic Compute Cloud
- Table of Contents
- What Is Amazon EC2?
- Setting Up with Amazon EC2
- Getting Started with Amazon EC2 Linux Instances
- Best Practices for Amazon EC2
- Tutorials for Amazon EC2 Instances Running Linux
- Amazon Machine Images (AMI)
- Using an AMI
- Creating Your Own AMI
- Buying, Sharing, and Selling AMIs
- Deregistering Your AMI
- Amazon Linux
- AMI Types
- Linux AMI Virtualization Types
- Finding a Linux AMI
- Shared AMIs
- Paid AMIs
- Creating an Amazon EBS-Backed Linux AMI
- Creating an Instance Store-Backed Linux AMI
- Overview of the Creation Process for Instance Store-Backed AMIs
- Prerequisites
- Setting Up the AMI Tools
- Creating an AMI from an Instance Store-Backed Instance
- Converting your Instance Store-Backed AMI to an Amazon EBS-Backed AMI
- AMIs with Encrypted Snapshots
- Copying an AMI
- Deregistering Your AMI
- Amazon Linux
- Finding the Amazon Linux AMI
- Launching and Connecting to an Amazon Linux Instance
- Identifying Amazon Linux AMI Images
- Included AWS Command Line Tools
- cloud-init
- Repository Configuration
- Adding Packages
- Accessing Source Packages for Reference
- Developing Applications
- Instance Store Access
- Product Life Cycle
- Security Updates
- Support
- User Provided Kernels
- Amazon EC2 Instances
- Instance Types
- Instance Purchasing Options
- Determining the Instance Lifecycle
- Reserved Instances
- How Reserved Instances Work
- Billing Benefits and Payment Options
- Buying Reserved Instances
- Selling in the Reserved Instance Marketplace
- Modifying Your Reserved Instances
- Troubleshooting Modification Requests
- Scheduled Reserved Instances
- Spot Instances
- Concepts
- How to Get Started
- Related Services
- Pricing
- How Spot Instances Work
- How Spot Fleet Works
- Spot Instance Pricing History
- Spot Instance Requests
- Spot Fleet Requests
- Spot Fleet Request States
- Spot Fleet Prerequisites
- Spot Fleet and IAM Users
- Planning a Spot Fleet Request
- Creating a Spot Fleet Request
- Monitoring Your Spot Fleet
- Modifying a Spot Fleet Request
- Cancelling a Spot Fleet Request
- Spot Fleet Example Configurations
- Example 1: Launch Spot Instances Using the Lowest-priced Availability Zone or Subnet in the Region
- Example 2: Launch Spot Instances Using the Lowest-priced Availability Zone or Subnet in a Specified List
- Example 3: Launch Spot Instances Using the Lowest-priced Instance Type in a Specified List
- Example 4. Override the Spot Price for the Request
- Example 5: Launch a Spot Fleet Using the Diversified Allocation Strategy
- Example 6: Launch a Spot Fleet Using Instance Weighting
- CloudWatch Metrics for Spot Fleet
- Automatic Scaling for Spot Fleet
- Spot Bid Status
- Spot Instance Interruptions
- Spot Instance Data Feed
- Spot Instance Limits
- Dedicated Hosts
- Differences between Dedicated Hosts and Dedicated Instances
- Pricing and Billing
- Dedicated Hosts Limitations and Restrictions
- Dedicated Host Configurations
- Using Dedicated Hosts
- Monitoring Dedicated Hosts
- Instance Lifecycle
- Instance Launch
- Instance Stop and Start (Amazon EBS-backed instances only)
- Instance Reboot
- Instance Retirement
- Instance Termination
- Differences Between Reboot, Stop, and Terminate
- Launch Your Instance
- Connect to Your Linux Instance
- Stop and Start Your Instance
- Reboot Your Instance
- Instance Retirement
- Terminate Your Instance
- Recover Your Instance
- Configuring Your Amazon Linux Instance
- Common Configuration Scenarios
- Managing Software on Your Linux Instance
- Managing User Accounts on Your Linux Instance
- Processor State Control for Your EC2 Instance
- Setting the Time for Your Linux Instance
- Changing the Hostname of Your Linux Instance
- Setting Up Dynamic DNS on Your Linux Instance
- Running Commands on Your Linux Instance at Launch
- Instance Metadata and User Data
- Remotely Manage Your Instances
- Amazon EC2 Run Command Components and Concepts
- Amazon EC2 Run Command Prerequisites
- Installing the SSM Agent
- Delegating Access to Amazon EC2 Run Command
- Setting Up Run Command On Managed Instances
- Executing a Command Using Amazon EC2 Run Command
- Viewing Command Output in the Amazon EC2 Console
- Creating SSM Documents
- Sharing SSM Documents
- Amazon EC2 Run Command Walkthroughs
- Cancelling a Command
- Monitoring Commands
- Troubleshooting Amazon EC2 Run Command
- Importing and Exporting Virtual Machines
- Monitoring Amazon EC2
- Automated and Manual Monitoring
- Best Practices for Monitoring
- Monitoring the Status of Your Instances
- Monitoring Your Instances Using CloudWatch
- Enable or Disable Detailed Monitoring for Your Instances
- List the Available CloudWatch Metrics for Your Instances
- Get Statistics for Metrics for Your Instances
- Graph Metrics for Your Instances
- Create a CloudWatch Alarm
- Create Alarms That Stop, Terminate, Reboot, or Recover an Instance
- Adding Stop Actions to Amazon CloudWatch Alarms
- Adding Terminate Actions to Amazon CloudWatch Alarms
- Adding Reboot Actions to Amazon CloudWatch Alarms
- Adding Recover Actions to Amazon CloudWatch Alarms
- Using the Amazon CloudWatch Console to View the History of Triggered Alarms and Actions
- Using the CLI or the API to Create an Alarm to Stop, Terminate, Reboot, or Recover an Instance
- Amazon CloudWatch Alarm Action Scenarios
- Scenario 1: Stop Idle Development and Test Instances
- Scenario 2: Stop Idle Instances
- Scenario 3: Send Email About Web Servers with Unusually High Traffic
- Scenario 4: Stop Web Servers with Unusually High Traffic
- Scenario 5: Stop an Instance Experiencing a Memory Leak
- Scenario 6: Stop an Impaired Instance
- Scenario 7: Terminate Instances When Batch Processing Jobs Are Complete
- Scenarios Using the CloudWatch Console
- Monitoring Memory and Disk Metrics for Amazon EC2 Linux Instances
- Network and Security
- Amazon EC2 Key Pairs
- Creating Your Key Pair Using Amazon EC2
- Importing Your Own Key Pair to Amazon EC2
- Retrieving the Public Key for Your Key Pair on Linux
- Retrieving the Public Key for Your Key Pair on Windows
- Verifying Your Key Pair's Fingerprint
- Deleting Your Key Pair
- Connecting to Your Linux Instance if You Lose Your Private Key
- Amazon EC2 Security Groups for Linux Instances
- Controlling Access to Amazon EC2 Resources
- Network Access to Your Instance
- Amazon EC2 Permission Attributes
- IAM and Amazon EC2
- IAM Policies for Amazon EC2
- IAM Roles for Amazon EC2
- Retrieving Security Credentials from Instance Metadata
- Granting an IAM User Permission to Launch an Instance with an IAM Role
- Creating an IAM Role Using the Console
- Launching an Instance with an IAM Role Using the Console
- Creating an IAM Role Using the AWS CLI
- Launching an Instance with an IAM Role Using the AWS CLI
- Authorizing Inbound Traffic for Your Linux Instances
- Amazon EC2 and Amazon Virtual Private Cloud
- Benefits of Using a VPC
- Differences Between EC2-Classic and EC2-VPC
- Sharing and Accessing Resources Between EC2-Classic and EC2-VPC
- Instance Types Available Only in a VPC
- Amazon VPC Documentation
- Supported Platforms
- ClassicLink
- ClassicLink Basics
- ClassicLink Limitations
- Working with ClassicLink
- Enabling a VPC for ClassicLink
- Linking an Instance to a VPC
- Creating a VPC with ClassicLink Enabled
- Linking an EC2-Classic Instance to a VPC at Launch
- Viewing Your ClassicLink-Enabled VPCs and Linked EC2-Classic Instances
- Enabling ClassicLink DNS Support
- Disabling ClassicLink DNS Support
- Unlinking a EC2-Classic Instance from a VPC
- Disabling ClassicLink for a VPC
- API and CLI Overview
- Example: ClassicLink Security Group Configuration for a Three-Tier Web Application
- Migrating from a Linux Instance in EC2-Classic to a Linux Instance in a VPC
- Full Migration to a VPC
- Incremental Migration to a VPC Using ClassicLink
- Amazon EC2 Instance IP Addressing
- Private IP Addresses and Internal DNS Hostnames
- Public IP Addresses and External DNS Hostnames
- Elastic IP Addresses
- Amazon DNS Server
- IP Address Differences Between EC2-Classic and EC2-VPC
- Determining Your Public, Private, and Elastic IP Addresses
- Assigning a Public IP Address
- Multiple Private IP Addresses
- How Multiple IP Addresses Work
- Assigning a Secondary Private IP Address
- Configuring the Operating System on Your Instance to Recognize the Secondary Private IP Address
- Associating an Elastic IP Address with the Secondary Private IP Address
- Viewing Your Secondary Private IP Addresses
- Unassigning a Secondary Private IP Address
- Elastic IP Addresses
- Elastic Network Interfaces (ENI)
- Private IP Addresses Per Network Interface Per Instance Type
- Public IP Addresses for Network Interfaces
- Creating a Management Network
- Use Network and Security Appliances in Your VPC
- Creating Dual-homed Instances with Workloads/Roles on Distinct Subnets
- Create a Low Budget High Availability Solution
- Monitoring IP Traffic on Your Network Interface
- Best Practices for Configuring Elastic Network Interfaces
- Configuring Your Network Interface Using ec2-net-utils
- Creating an Elastic Network Interface
- Deleting an Elastic Network Interface
- Viewing Details about an Elastic Network Interface
- Attaching an Elastic Network Interface When Launching an Instance
- Attaching an Elastic Network Interface to a Stopped or Running Instance
- Detaching an Elastic Network Interface from an Instance
- Changing the Security Group of an Elastic Network Interface
- Changing the Source/Destination Checking of an Elastic Network Interface
- Associating an Elastic IP Address with an Elastic Network Interface
- Disassociating an Elastic IP Address from an Elastic Network Interface
- Changing Termination Behavior for an Elastic Network Interface
- Adding or Editing a Description for an Elastic Network Interface
- Adding or Editing Tags for an Elastic Network Interface
- Placement Groups
- Network Maximum Transmission Unit (MTU) for Your EC2 Instance
- Enhanced Networking on Linux
- Enhanced Networking Types
- Enabling Enhanced Networking on Your Instance
- Enabling Enhanced Networking with the Intel 82599 VF Interface on Linux Instances in a VPC
- Testing Whether Enhanced Networking with the Intel 82599 VF Interface is Enabled
- Enabling Enhanced Networking with the Intel 82599 VF Interface on Amazon Linux
- Enabling Enhanced Networking with the Intel 82599 VF Interface on Ubuntu
- Enabling Enhanced Networking with the Intel 82599 VF Interface on Other Linux Distributions
- Troubleshooting Connectivity Issues
- Enabling Enhanced Networking with the Elastic Network Adapter (ENA) on Linux Instances in a VPC
- Troubleshoooting the Elastic Network Adapter (ENA)
- Amazon EC2 Key Pairs
- Storage
- Amazon Elastic Block Store (Amazon EBS)
- Features of Amazon EBS
- Amazon EBS Volumes
- Benefits of Using EBS Volumes
- Amazon EBS Volume Types
- Creating an Amazon EBS Volume
- Restoring an Amazon EBS Volume from a Snapshot
- Attaching an Amazon EBS Volume to an Instance
- Making an Amazon EBS Volume Available for Use
- Viewing Volume Information
- Monitoring the Status of Your Volumes
- Detaching an Amazon EBS Volume from an Instance
- Deleting an Amazon EBS Volume
- Expanding the Storage Space of an EBS Volume on Linux
- Expanding a Linux Partition
- Amazon EBS Snapshots
- Amazon EBS–Optimized Instances
- Amazon EBS Encryption
- Amazon EBS Volume Performance on Linux Instances
- Amazon EBS Performance Tips
- Use EBS-Optimized Instances
- Understand How Performance is Calculated
- Understand Your Workload
- Be Aware of the Performance Penalty When Initializing Volumes from Snapshots
- Factors That Can Degrade HDD Performance
- Increase Read-Ahead for High-Throughput, Read-Heavy Workloads on st1 and sc1
- Use a Modern Linux Kernel
- Use RAID 0 to Maximize Utilization of Instance Resources
- Track Performance with Amazon CloudWatch
- Amazon EC2 Instance Configuration
- I/O Characteristics
- Initializing Amazon EBS Volumes
- RAID Configuration on Linux
- Benchmark EBS Volumes
- Amazon EBS Performance Tips
- Amazon EC2 Instance Store
- Amazon Simple Storage Service (Amazon S3)
- Instance Volume Limits
- Device Naming on Linux Instances
- Block Device Mapping
- Using Public Data Sets
- Amazon Elastic Block Store (Amazon EBS)
- Resources and Tags
- Resource Locations
- Resource IDs
- Listing and Filtering Your Resources
- Tagging Your Amazon EC2 Resources
- Amazon EC2 Service Limits
- Amazon EC2 Usage Reports
- Troubleshooting Instances
- What To Do If An Instance Immediately Terminates
- Troubleshooting Connecting to Your Instance
- Error connecting to your instance: Connection timed out
- Error: User key not recognized by server
- Error: Host key not found, Permission denied (publickey), or Authentication failed, permission denied
- Error: Unprotected Private Key File
- Error: Server refused our key or No supported authentication methods available
- Error using MindTerm on Safari Browser
- Error Using Mac OS X RDP Client
- Cannot Ping Instance
- Troubleshooting Stopping Your Instance
- Troubleshooting Terminating (Shutting Down) Your Instance
- Troubleshooting Instance Recovery Failures
- Troubleshooting Instances with Failed Status Checks
- Initial Steps
- Retrieving System Logs
- Troubleshooting System Log Errors for Linux-Based Instances
- Out of memory: kill process
- ERROR: mmu_update failed (Memory management update failed)
- I/O error (Block device failure)
- IO ERROR: neither local nor remote disk (Broken distributed block device)
- request_module: runaway loop modprobe (Looping legacy kernel modprobe on older Linux versions)
- "FATAL: kernel too old" and "fsck: No such file or directory while trying to open /dev" (Kernel and AMI mismatch)
- "FATAL: Could not load /lib/modules" or "BusyBox" (Missing kernel modules)
- ERROR Invalid kernel (EC2 incompatible kernel)
- request_module: runaway loop modprobe (Looping legacy kernel modprobe on older Linux versions)
- fsck: No such file or directory while trying to open... (File system not found)
- General error mounting filesystems (Failed mount)
- VFS: Unable to mount root fs on unknown-block (Root filesystem mismatch)
- Error: Unable to determine major/minor number of root device... (Root file system/device mismatch)
- XENBUS: Device with no driver...
- ... days without being checked, check forced (File system check required)
- fsck died with exit status... (Missing device)
- GRUB prompt (grubdom>)
- Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring. (Hard-coded MAC address)
- Unable to load SELinux Policy. Machine is in enforcing mode. Halting now. (SELinux misconfiguration)
- XENBUS: Timeout connecting to devices (Xenbus timeout)
- Troubleshooting Instance Capacity
- Getting Console Output and Rebooting Instances
- My Instance is Booting from the Wrong Volume
- Making API Requests
- Document History
- AWS Glossary