id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
819155de5278-1 | + [Amazon Machine Images (AMI)](AMIs.md)
+ [AMI types](ComponentsAMIs.md)
+ [Linux AMI virtualization types](virtualization_types.md)
+ [Finding a Linux AMI](finding-an-ami.md)
+ [Shared AMIs](sharing-amis.md)
+ [Finding shared AMIs](usingsharedamis-finding.md)
+ [Making an AMI public](sharingamis-intro.md)
+ [Sharing an AMI with specific AWS accounts](sharingamis-explicit.md)
+ [Using bookmarks](using-bookmarks.md)
+ [Guidelines for shared Linux AMIs](building-shared-amis.md)
+ [Paid AMIs](paid-amis.md)
+ [Creating an Amazon EBS-backed Linux AMI](creating-an-ami-ebs.md)
+ [Creating an instance store-backed Linux AMI](creating-an-ami-instance-store.md)
+ [Setting up the AMI tools](set-up-ami-tools.md)
+ [Creating an AMI from an instance store-backed instance](create-instance-store-ami.md)
+ [Converting your instance store-backed AMI to an Amazon EBS-backed AMI](Using_ConvertingS3toEBS.md)
+ [AMI tools reference](ami-tools-commands.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-2 | + [AMI tools reference](ami-tools-commands.md)
+ [Using encryption with EBS-backed AMIs](AMIEncryption.md)
+ [Copying an AMI](CopyingAMIs.md)
+ [Obtaining billing information](ami-billing-info.md)
+ [Deregistering your Linux AMI](deregister-ami.md)
+ [Amazon Linux](amazon-linux-ami-basics.md)
+ [Running Amazon Linux 2 as a virtual machine on premises](amazon-linux-2-virtual-machine.md)
+ [Kernel Live Patching on Amazon Linux 2](al2-live-patching.md)
+ [User provided kernels](UserProvidedKernels.md)
+ [Using the MATE desktop environment provided with Amazon Linux 2](amazon-linux-ami-mate.md)
+ [Amazon EC2 instances](Instances.md)
+ [Instance types](instance-types.md)
+ [General purpose instances](general-purpose-instances.md)
+ [Burstable performance instances](burstable-performance-instances.md)
+ [CPU credits and baseline utilization for burstable performance instances](burstable-credits-baseline-concepts.md)
+ [Unlimited mode for burstable performance instances](burstable-performance-instances-unlimited-mode.md)
+ [Unlimited mode concepts](burstable-performance-instances-unlimited-mode-concepts.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-3 | + [Unlimited mode concepts](burstable-performance-instances-unlimited-mode-concepts.md)
+ [Unlimited mode examples](unlimited-mode-examples.md)
+ [Standard mode for burstable performance instances](burstable-performance-instances-standard-mode.md)
+ [Standard mode concepts](burstable-performance-instances-standard-mode-concepts.md)
+ [Standard mode examples](standard-mode-examples.md)
+ [Working with burstable performance instances](burstable-performance-instances-how-to.md)
+ [Monitoring your CPU credits](burstable-performance-instances-monitoring-cpu-credits.md)
+ [Compute optimized instances](compute-optimized-instances.md)
+ [Memory optimized instances](memory-optimized-instances.md)
+ [Storage optimized instances](storage-optimized-instances.md)
+ [Linux accelerated computing instances](accelerated-computing-instances.md)
+ [Installing NVIDIA drivers on Linux instances](install-nvidia-driver.md)
+ [Activate NVIDIA GRID Virtual Applications](activate_grid.md)
+ [Optimizing GPU settings](optimize_gpu.md)
+ [FPGA development](fpga-getting-started.md)
+ [Getting started with AWS Inferentia development](inf-getting-started.md)
+ [Finding an Amazon EC2 instance type](instance-discovery.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-4 | + [Finding an Amazon EC2 instance type](instance-discovery.md)
+ [Changing the instance type](ec2-instance-resize.md)
+ [Getting recommendations for an instance type](ec2-instance-recommendations.md)
+ [Instance purchasing options](instance-purchasing-options.md)
+ [On-Demand Instances](ec2-on-demand-instances.md)
+ [Reserved Instances](ec2-reserved-instances.md)
+ [Regional and zonal Reserved Instances (scope)](reserved-instances-scope.md)
+ [Types of Reserved Instances (offering classes)](reserved-instances-types.md)
+ [How Reserved Instances are applied](apply_ri.md)
+ [How you are billed](concepts-reserved-instances-application.md)
+ [Buying Reserved Instances](ri-market-concepts-buying.md)
+ [Reserved Instance Marketplace](ri-market-general.md)
+ [Modifying Reserved Instances](ri-modifying.md)
+ [Exchanging Convertible Reserved Instances](ri-convertible-exchange.md)
+ [Scheduled Reserved Instances](ec2-scheduled-instances.md)
+ [Spot Instances](using-spot-instances.md)
+ [Best practices for EC2 Spot](spot-best-practices.md)
+ [How Spot Instances work](how-spot-instances-work.md)
+ [How Spot Fleet works](spot-fleet.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-5 | + [How Spot Instances work](how-spot-instances-work.md)
+ [How Spot Fleet works](spot-fleet.md)
+ [Spot Instance pricing history](using-spot-instances-history.md)
+ [Savings from purchasing Spot Instances](spot-savings.md)
+ [Spot Instance requests](spot-requests.md)
+ [Spot Instance request example launch specifications](spot-request-examples.md)
+ [Spot Fleet requests](spot-fleet-requests.md)
+ [Spot Fleet example configurations](spot-fleet-examples.md)
+ [CloudWatch metrics for Spot Fleet](spot-fleet-cloudwatch-metrics.md)
+ [Automatic scaling for Spot Fleet](spot-fleet-automatic-scaling.md)
+ [Scale Spot Fleet using a target tracking policy](spot-fleet-target-tracking.md)
+ [Scale Spot Fleet using step scaling policies](spot-fleet-step-scaling.md)
+ [Scale Spot Fleet using scheduled scaling](spot-fleet-scheduled-scaling.md)
+ [Spot request status](spot-request-status.md)
+ [Spot Instance interruptions](spot-interruptions.md)
+ [Spot Instance data feed](spot-data-feeds.md)
+ [Spot Instance considerations](using-spot-limits.md)
+ [Dedicated Hosts](dedicated-hosts-overview.md)
+ [Working with Dedicated Hosts](how-dedicated-hosts-work.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-6 | + [Dedicated Hosts](dedicated-hosts-overview.md)
+ [Working with Dedicated Hosts](how-dedicated-hosts-work.md)
+ [Working with shared Dedicated Hosts](dh-sharing.md)
+ [Host recovery](dedicated-hosts-recovery.md)
+ [Tracking configuration changes](dedicated-hosts-aws-config.md)
+ [Dedicated Instances](dedicated-instance.md)
+ [On-Demand Capacity Reservations](ec2-capacity-reservations.md)
+ [Capacity Reservation pricing and billing](capacity-reservations-pricing-billing.md)
+ [Working with Capacity Reservations](capacity-reservations-using.md)
+ [Working with shared Capacity Reservations](capacity-reservation-sharing.md)
+ [CloudWatch metrics for On-Demand Capacity Reservations](capacity-reservation-cw-metrics.md)
+ [Instance lifecycle](ec2-instance-lifecycle.md)
+ [Launch your instance](LaunchingAndUsingInstances.md)
+ [Launching an instance using the Launch Instance Wizard](launching-instance.md)
+ [Launching an instance from a launch template](ec2-launch-templates.md)
+ [Launching an instance using parameters from an existing instance](launch-more-like-this.md)
+ [Launching an AWS Marketplace instance](launch-marketplace-console.md)
+ [Launching instances using an EC2 Fleet](ec2-fleet.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-7 | + [Launching instances using an EC2 Fleet](ec2-fleet.md)
+ [EC2 Fleet configuration strategies](ec2-fleet-configuration-strategies.md)
+ [Managing an EC2 Fleet](manage-ec2-fleet.md)
+ [EC2 Fleet example configurations](ec2-fleet-examples.md)
+ [Connect to your Linux instance](AccessingInstances.md)
+ [General prerequisites for connecting to your instance](connection-prereqs.md)
+ [Connecting to your Linux instance using SSH](AccessingInstancesLinux.md)
+ [Connecting to your Linux instance using EC2 Instance Connect](Connect-using-EC2-Instance-Connect.md)
+ [Set up EC2 Instance Connect](ec2-instance-connect-set-up.md)
+ [Connect using EC2 Instance Connect](ec2-instance-connect-methods.md)
+ [Uninstall EC2 Instance Connect](ec2-instance-connect-uninstall.md)
+ [Connecting to your Linux instance from Windows using PuTTY](putty.md)
+ [Connecting to your Linux instance from Windows using Windows Subsystem for Linux](WSL.md)
+ [Connecting to your Linux instance using Session Manager](session-manager.md)
+ [Stop and start your instance](Stop_Start.md)
+ [Hibernate your Linux instance](Hibernate.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-8 | + [Stop and start your instance](Stop_Start.md)
+ [Hibernate your Linux instance](Hibernate.md)
+ [Reboot your instance](ec2-instance-reboot.md)
+ [Instance retirement](instance-retirement.md)
+ [Terminate your instance](terminating-instances.md)
+ [Recover your instance](ec2-instance-recover.md)
+ [Configuring your Amazon Linux instance](Configure_Instance.md)
+ [Managing software on your Amazon Linux instance](managing-software.md)
+ [Updating instance software on your Amazon Linux instance](install-updates.md)
+ [Adding repositories on an Amazon Linux instance](add-repositories.md)
+ [Finding software packages on an Amazon Linux instance](find-software.md)
+ [Installing software packages on an Amazon Linux instance](install-software.md)
+ [Preparing to compile software on an Amazon Linux instance](compile-software.md)
+ [Managing user accounts on your Amazon Linux instance](managing-users.md)
+ [Processor state control for your EC2 instance](processor_state_control.md)
+ [Setting the time for your Linux instance](set-time.md)
+ [Optimizing CPU options](instance-optimize-cpu.md)
+ [Changing the hostname of your Amazon Linux instance](set-hostname.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-9 | + [Changing the hostname of your Amazon Linux instance](set-hostname.md)
+ [Setting up dynamic DNS on Your Amazon Linux instance](dynamic-dns.md)
+ [Running commands on your Linux instance at launch](user-data.md)
+ [Instance metadata and user data](ec2-instance-metadata.md)
+ [Configuring the instance metadata service](configuring-instance-metadata-service.md)
+ [Retrieving instance metadata](instancedata-data-retrieval.md)
+ [Working with instance user data](instancedata-add-user-data.md)
+ [Retrieving dynamic data](instancedata-dynamic-data-retrieval.md)
+ [Example: AMI launch index value](AMI-launch-index-examples.md)
+ [Instance metadata categories](instancedata-data-categories.md)
+ [Instance identity documents](instance-identity-documents.md)
+ [Using the PKCS7 signature to verify the instance identity document](verify-pkcs7.md)
+ [Using the base64-encoded signature to verify the instance identity document](verify-signature.md)
+ [Using the RSA-2048 signature to verify the instance identity document](verify-rsa2048.md)
+ [Amazon Elastic Inference](elastic-inference.md)
+ [Identify EC2 Linux instances](identify_ec2_instances.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-10 | + [Amazon Elastic Inference](elastic-inference.md)
+ [Identify EC2 Linux instances](identify_ec2_instances.md)
+ [Monitoring Amazon EC2](monitoring_ec2.md)
+ [Automated and manual monitoring](monitoring_automated_manual.md)
+ [Best practices for monitoring](monitoring_best_practices.md)
+ [Monitoring the status of your instances](monitoring-instances-status-check.md)
+ [Status checks for your instances](monitoring-system-instance-status-check.md)
+ [Scheduled events for your instances](monitoring-instances-status-check_sched.md)
+ [Monitoring your instances using CloudWatch](using-cloudwatch.md)
+ [Enable or disable detailed monitoring for your instances](using-cloudwatch-new.md)
+ [List the available CloudWatch metrics for your instances](viewing_metrics_with_cloudwatch.md)
+ [Get statistics for metrics for your instances](monitoring_get_statistics.md)
+ [Get statistics for a specific instance](US_SingleMetricPerInstance.md)
+ [Aggregate statistics across instances](GetSingleMetricAllDimensions.md)
+ [Aggregate statistics by Auto Scaling group](GetMetricAutoScalingGroup.md)
+ [Aggregate statistics by AMI](US_SingleMetricPerAMI.md)
+ [Graph metrics for your instances](graphs-in-the-aws-management-console.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-11 | + [Graph metrics for your instances](graphs-in-the-aws-management-console.md)
+ [Create a CloudWatch alarm for an instance](using-cloudwatch-createalarm.md)
+ [Create alarms that stop, terminate, reboot, or recover an instance](UsingAlarmActions.md)
+ [Automating Amazon EC2 with CloudWatch Events](automating_with_cloudwatch_events.md)
+ [Monitoring memory and disk metrics for Amazon EC2 Linux instances](mon-scripts.md)
+ [Logging Amazon EC2 and Amazon EBS API calls with AWS CloudTrail](monitor-with-cloudtrail.md)
+ [Networking in Amazon EC2](ec2-networking.md)
+ [Amazon EC2 instance IP addressing](using-instance-addressing.md)
+ [Multiple IP addresses](MultipleIP.md)
+ [Bring your own IP addresses (BYOIP) in Amazon EC2](ec2-byoip.md)
+ [Elastic IP addresses](elastic-ip-addresses-eip.md)
+ [Elastic network interfaces](using-eni.md)
+ [Requester-managed network interfaces](requester-managed-eni.md)
+ [Enhanced networking on Linux](enhanced-networking.md)
+ [Enabling enhanced networking with the Elastic Network Adapter (ENA) on Linux instances](enhanced-networking-ena.md)
+ [Operating system optimizations](enhanced-networking-os.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-12 | + [Operating system optimizations](enhanced-networking-os.md)
+ [Enabling enhanced networking with the Intel 82599 VF interface on Linux instances](sriov-networking.md)
+ [Troubleshooting the Elastic Network Adapter (ENA)](troubleshooting-ena.md)
+ [Elastic Fabric Adapter](efa.md)
+ [Getting started with EFA and MPI](efa-start.md)
+ [Getting started with EFA and NCCL](efa-start-nccl.md)
+ [Using a base AMI](efa-start-nccl-base.md)
+ [Using an AWS Deep Learning AMI](efa-start-nccl-dlami.md)
+ [Working with EFA](efa-working-with.md)
+ [Monitoring an EFA](efa-working-monitor.md)
+ [Verifying the EFA installer using a checksum](efa-verify.md)
+ [Placement groups](placement-groups.md)
+ [Network maximum transmission unit (MTU) for your EC2 instance](network_mtu.md)
+ [Virtual private clouds](using-vpc.md)
+ [EC2-Classic](ec2-classic-platform.md)
+ [ClassicLink](vpc-classiclink.md)
+ [Migrating from EC2-Classic to a VPC](vpc-migrate.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-13 | + [Migrating from EC2-Classic to a VPC](vpc-migrate.md)
+ [Security in Amazon EC2](ec2-security.md)
+ [Infrastructure security in Amazon EC2](infrastructure-security.md)
+ [Amazon EC2 and interface VPC endpoints](interface-vpc-endpoints.md)
+ [Resilience in Amazon EC2](disaster-recovery-resiliency.md)
+ [Data protection in Amazon EC2](data-protection.md)
+ [Identity and access management for Amazon EC2](security-iam.md)
+ [IAM policies for Amazon EC2](iam-policies-for-amazon-ec2.md)
+ [Policy structure](iam-policy-structure.md)
+ [Granting permission to tag resources during creation](supported-iam-actions-tagging.md)
+ [Controlling access to EC2 resources using resource tags](control-access-with-tags.md)
+ [Example policies for working with the AWS CLI or an AWS SDK](ExamplePolicies_EC2.md)
+ [Example policies for working in the Amazon EC2 console](iam-policies-ec2-console.md)
+ [IAM roles for Amazon EC2](iam-roles-for-amazon-ec2.md)
+ [Authorizing inbound traffic for your Linux instances](authorizing-access-to-an-instance.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-14 | + [Authorizing inbound traffic for your Linux instances](authorizing-access-to-an-instance.md)
+ [Amazon EC2 key pairs and Linux instances](ec2-key-pairs.md)
+ [Connecting to your Linux instance if you lose your private key](replacing-lost-key-pair.md)
+ [Amazon EC2 security groups for Linux instances](ec2-security-groups.md)
+ [Working with security groups](working-with-security-groups.md)
+ [Security group rules reference](security-group-rules-reference.md)
+ [Update management in Amazon EC2](update-management.md)
+ [Compliance validation for Amazon EC2](compliance-validation.md)
+ [Storage](Storage.md)
+ [Amazon Elastic Block Store (Amazon EBS)](AmazonEBS.md)
+ [Amazon EBS volumes](ebs-volumes.md)
+ [Amazon EBS volume types](ebs-volume-types.md)
+ [Constraints on the size and configuration of an EBS volume](volume_constraints.md)
+ [Creating an Amazon EBS volume](ebs-creating-volume.md)
+ [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)
+ [Attaching a volume to multiple instances with Amazon EBS Multi-Attach](ebs-volumes-multi.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-15 | + [Attaching a volume to multiple instances with Amazon EBS Multi-Attach](ebs-volumes-multi.md)
+ [Making an Amazon EBS volume available for use on Linux](ebs-using-volumes.md)
+ [Viewing information about an Amazon EBS volume](ebs-describing-volumes.md)
+ [Replacing an Amazon EBS volume using a previous snapshot](ebs-restoring-volume.md)
+ [Monitoring the status of your volumes](monitoring-volume-status.md)
+ [Detaching an Amazon EBS volume from a Linux instance](ebs-detaching-volume.md)
+ [Deleting an Amazon EBS volume](ebs-deleting-volume.md)
+ [Amazon EBS snapshots](EBSSnapshots.md)
+ [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)
+ [Deleting an Amazon EBS snapshot](ebs-deleting-snapshot.md)
+ [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)
+ [Viewing Amazon EBS snapshot information](ebs-describing-snapshots.md)
+ [Sharing an Amazon EBS snapshot](ebs-modifying-snapshot-permissions.md)
+ [Accessing the contents of an EBS snapshot](ebs-accessing-snapshot.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-16 | + [Accessing the contents of an EBS snapshot](ebs-accessing-snapshot.md)
+ [Logging API Calls for the EBS direct APIs with AWS CloudTrail](logging-ebs-apis-using-cloudtrail.md)
+ [Idempotency for StartSnapshot API](ebs-direct-api-idempotency.md)
+ [Automating the Amazon EBS snapshot lifecycle](snapshot-lifecycle.md)
+ [Amazon EBS data services](ebs-data-services.md)
+ [Amazon EBS Elastic Volumes](ebs-modify-volume.md)
+ [Requirements when modifying volumes](modify-volume-requirements.md)
+ [Requesting modifications to your EBS Volumes](requesting-ebs-volume-modifications.md)
+ [Monitoring the progress of volume modifications](monitoring-volume-modifications.md)
+ [Extending a Linux file system after resizing a volume](recognize-expanded-volume-linux.md)
+ [Amazon EBS encryption](EBSEncryption.md)
+ [Amazon EBS fast snapshot restore](ebs-fast-snapshot-restore.md)
+ [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md)
+ [Amazon EBS–optimized instances](ebs-optimized.md)
+ [Amazon EBS volume performance on Linux instances](EBSPerformance.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-17 | + [Amazon EBS volume performance on Linux instances](EBSPerformance.md)
+ [I/O characteristics and monitoring](ebs-io-characteristics.md)
+ [Initializing Amazon EBS volumes](ebs-initialize.md)
+ [RAID Configuration on Linux](raid-config.md)
+ [Benchmark EBS volumes](benchmark_procedures.md)
+ [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)
+ [Amazon CloudWatch Events for Amazon EBS](ebs-cloud-watch-events.md)
+ [Amazon EC2 instance store](InstanceStorage.md)
+ [Add instance store volumes to your EC2 instance](add-instance-store-volumes.md)
+ [SSD instance store volumes](ssd-instance-store.md)
+ [Instance store swap volumes](instance-store-swap-volumes.md)
+ [Optimizing disk performance for instance store volumes](disk-performance.md)
+ [File storage](file-storage.md)
+ [Using Amazon S3 with Amazon EC2](AmazonS3.md)
+ [Using Amazon EFS with Amazon EC2](AmazonEFS.md)
+ [Instance volume limits](volume_limits.md)
+ [Device naming on Linux instances](device_naming.md)
+ [Block device mapping](block-device-mapping-concepts.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-18 | + [Device naming on Linux instances](device_naming.md)
+ [Block device mapping](block-device-mapping-concepts.md)
+ [Resources and tags](EC2_Resources.md)
+ [Resource locations](resources.md)
+ [Resource IDs](resource-ids.md)
+ [Listing and filtering your resources](Using_Filtering.md)
+ [Tagging your Amazon EC2 resources](Using_Tags.md)
+ [Amazon EC2 service quotas](ec2-resource-limits.md)
+ [Amazon EC2 usage reports](usage-reports.md)
+ [Troubleshooting EC2 instances](ec2-instance-troubleshoot.md)
+ [Troubleshooting instance launch issues](troubleshooting-launch.md)
+ [Troubleshooting connecting to your instance](TroubleshootingInstancesConnecting.md)
+ [Troubleshooting stopping your instance](TroubleshootingInstancesStopping.md)
+ [Troubleshooting terminating (shutting down) your instance](TroubleshootingInstancesShuttingDown.md)
+ [Troubleshooting instances with failed status checks](TroubleshootingInstances.md)
+ [Troubleshooting an unreachable instance](instance-console.md)
+ [Booting from the wrong volume](instance-booting-from-wrong-volume.md)
+ [Using EC2Rescue for Linux](Linux-Server-EC2Rescue.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-19 | + [Using EC2Rescue for Linux](Linux-Server-EC2Rescue.md)
+ [Installing EC2Rescue for Linux](ec2rl_install.md)
+ [(Optional) Verify the signature of EC2Rescue for Linux](ec2rl_verify.md)
+ [Working with EC2Rescue for Linux](ec2rl_working.md)
+ [Developing EC2Rescue modules](ec2rl_moduledev.md)
+ [Sending a diagnostic interrupt (for advanced users)](diagnostic-interrupt.md)
+ [Document history](DocumentHistory.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
ed63f9701353-0 | You can create a security group and add rules that reflect the role of the instance that's associated with the security group\. For example, an instance that's configured as a web server needs security group rules that allow inbound HTTP and HTTPS access\. Likewise, a database instance needs rules that allow access for the type of database, such as access over port 3306 for MySQL\.
The following are examples of the kinds of rules that you can add to security groups for specific kinds of access\.
**Topics**
+ [Web server rules](#sg-rules-web-server)
+ [Database server rules](#sg-rules-db-server)
+ [Rules to connect to instances from your computer](#sg-rules-local-access)
+ [Rules to connect to instances from an instance with the same security group](#sg-rules-other-instances)
+ [Rules for ping/ICMP](#sg-rules-ping)
+ [DNS server rules](#sg-rules-dns)
+ [Amazon EFS rules](#sg-rules-efs)
+ [Elastic Load Balancing rules](#sg-rules-elb)
+ [VPC peering rules](#peer-vpc-rules) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
8b28d060194f-0 | The following inbound rules allow HTTP and HTTPS access from any IP address\. If your VPC is enabled for IPv6, you can add rules to control inbound HTTP and HTTPS traffic from IPv6 addresses\.
| Protocol type | Protocol number | Port | Source IP | Notes |
| --- | --- | --- | --- | --- |
| TCP | 6 | 80 \(HTTP\) | 0\.0\.0\.0/0 | Allows inbound HTTP access from any IPv4 address |
| TCP | 6 | 443 \(HTTPS\) | 0\.0\.0\.0/0 | Allows inbound HTTPS access from any IPv4 address |
| TCP | 6 | 80 \(HTTP\) | ::/0 | Allows inbound HTTP access from any IPv6 address |
| TCP | 6 | 443 \(HTTPS\) | ::/0 | Allows inbound HTTPS access from any IPv6 address | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
c2f9781f48f3-0 | The following inbound rules are examples of rules you might add for database access, depending on what type of database you're running on your instance\. For more information about Amazon RDS instances, see the [Amazon RDS User Guide](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/)\.
For the source IP, specify one of the following:
+ A specific IP address or range of IP addresses \(in CIDR block notation\) in your local network
+ A security group ID for a group of instances that access the database
| Protocol type | Protocol number | Port | Notes |
| --- | --- | --- | --- |
| TCP | 6 | 1433 \(MS SQL\) | The default port to access a Microsoft SQL Server database, for example, on an Amazon RDS instance |
| TCP | 6 | 3306 \(MYSQL/Aurora\) | The default port to access a MySQL or Aurora database, for example, on an Amazon RDS instance |
| TCP | 6 | 5439 \(Redshift\) | The default port to access an Amazon Redshift cluster database\. |
| TCP | 6 | 5432 \(PostgreSQL\) | The default port to access a PostgreSQL database, for example, on an Amazon RDS instance |
| TCP | 6 | 1521 \(Oracle\) | The default port to access an Oracle database, for example, on an Amazon RDS instance | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
c2f9781f48f3-1 | | TCP | 6 | 1521 \(Oracle\) | The default port to access an Oracle database, for example, on an Amazon RDS instance |
You can optionally restrict outbound traffic from your database servers\. For example, you might want to allow access to the internet for software updates, but restrict all other kinds of traffic\. You must first remove the default outbound rule that allows all outbound traffic\.
| Protocol type | Protocol number | Port | Destination IP | Notes |
| --- | --- | --- | --- | --- |
| TCP | 6 | 80 \(HTTP\) | 0\.0\.0\.0/0 | Allows outbound HTTP access to any IPv4 address |
| TCP | 6 | 443 \(HTTPS\) | 0\.0\.0\.0/0 | Allows outbound HTTPS access to any IPv4 address |
| TCP | 6 | 80 \(HTTP\) | ::/0 | \(IPv6\-enabled VPC only\) Allows outbound HTTP access to any IPv6 address |
| TCP | 6 | 443 \(HTTPS\) | ::/0 | \(IPv6\-enabled VPC only\) Allows outbound HTTPS access to any IPv6 address | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
7b047fe50da6-0 | To connect to your instance, your security group must have inbound rules that allow SSH access \(for Linux instances\) or RDP access \(for Windows instances\)\.
| Protocol type | Protocol number | Port | Source IP |
| --- | --- | --- | --- |
| TCP | 6 | 22 \(SSH\) | The public IPv4 address of your computer, or a range of IP addresses \(in CIDR block notation\) in your local network\. If your VPC is enabled for IPv6 and your instance has an IPv6 address, you can enter an IPv6 address or range\. |
| TCP | 6 | 3389 \(RDP\) | The public IPv4 address of your computer, or a range of IP addresses \(in CIDR block notation\) in your local network\. If your VPC is enabled for IPv6 and your instance has an IPv6 address, you can enter an IPv6 address or range\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
a4a2483af752-0 | To allow instances that are associated with the same security group to communicate with each other, you must explicitly add rules for this\.
The following table describes the inbound rule for a security group that enables associated instances to communicate with each other\. The rule allows all types of traffic\.
| Protocol type | Protocol number | Ports | Source IP |
| --- | --- | --- | --- |
| \-1 \(All\) | \-1 \(All\) | \-1 \(All\) | The ID of the security group | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
26b521c27d6e-0 | The `ping` command is a type of ICMP traffic\. To ping your instance, you must add the following inbound ICMP rule\.
| Protocol type | Protocol number | ICMP type | ICMP code | Source IP |
| --- | --- | --- | --- | --- |
| ICMP | 1 | 8 \(Echo\) | N/A | The public IPv4 address of your computer, or a range of IPv4 addresses \(in CIDR block notation\) in your local network |
To use the `ping6` command to ping the IPv6 address for your instance, you must add the following inbound ICMPv6 rule\.
| Protocol type | Protocol number | ICMP type | ICMP code | Source IP |
| --- | --- | --- | --- | --- |
| ICMPv6 | 58 | 128 \(Echo\) | 0 | The IPv6 address of your computer, or a range of IPv6 addresses \(in CIDR block notation\) in your local network | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
52b17730c099-0 | If you've set up your EC2 instance as a DNS server, you must ensure that TCP and UDP traffic can reach your DNS server over port 53\.
For the source IP, specify one of the following:
+ An IP address or range of IP addresses \(in CIDR block notation\) in a network
+ The ID of a security group for the set of instances in your network that require access to the DNS server
| Protocol type | Protocol number | Port |
| --- | --- | --- |
| TCP | 6 | 53 |
| UDP | 17 | 53 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
43c740290fca-0 | If you're using an Amazon EFS file system with your Amazon EC2 instances, the security group that you associate with your Amazon EFS mount targets must allow traffic over the NFS protocol\.
| Protocol type | Protocol number | Ports | Source IP | Notes |
| --- | --- | --- | --- | --- |
| TCP | 6 | 2049 \(NFS\) | The ID of the security group\. | Allows inbound NFS access from resources \(including the mount target\) associated with this security group\. |
To mount an Amazon EFS file system on your Amazon EC2 instance, you must connect to your instance\. Therefore, the security group associated with your instance must have rules that allow inbound SSH from your local computer or local network\.
| Protocol type | Protocol number | Ports | Source IP | Notes |
| --- | --- | --- | --- | --- |
| TCP | 6 | 22 \(SSH\) | The IP address range of your local computer, or the range of IP addresses \(in CIDR block notation\) for your network\. | Allows inbound SSH access from your local computer\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
8a69c5845c67-0 | If you're using a load balancer, the security group associated with your load balancer must have rules that allow communication with your instances or targets\.
|
|
| **Inbound** |
| --- |
| Protocol type | Protocol number | Port | Source IP | Notes |
| TCP | 6 | The listener port | For an Internet\-facing load\-balancer: 0\.0\.0\.0/0 \(all IPv4 addresses\) For an internal load\-balancer: the IPv4 CIDR block of the VPC | Allow inbound traffic on the load balancer listener port\. |
| **Outbound** |
| --- |
| Protocol type | Protocol number | Port | Destination IP | Notes |
| TCP | 6 | The instance listener port | The ID of the instance security group | Allow outbound traffic to instances on the instance listener port\. |
| TCP | 6 | The health check port | The ID of the instance security group | Allow outbound traffic to instances on the health check port\. |
The security group rules for your instances must allow the load balancer to communicate with your instances on both the listener port and the health check port\.
|
|
| **Inbound** |
| --- |
| Protocol type | Protocol number | Port | Source IP | Notes | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
8a69c5845c67-1 | | **Inbound** |
| --- |
| Protocol type | Protocol number | Port | Source IP | Notes |
| TCP | 6 | The instance listener port | The ID of the load balancer security group | Allow traffic from the load balancer on the instance listener port\. |
| TCP | 6 | The health check port | The ID of the load balancer security group | Allow traffic from the load balancer on the health check port\. |
For more information, see [Configure security groups for your Classic Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-groups.html) in the *User Guide for Classic Load Balancers*, and [Security groups for your Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-update-security-groups.html) in the *User Guide for Application Load Balancers*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
41264617fbe3-0 | You can update the inbound or outbound rules for your VPC security groups to reference security groups in the peered VPC\. Doing so allows traffic to flow to and from instances that are associated with the referenced security group in the peered VPC\. For more information about how to configure security groups for VPC peering, see [Updating your security groups to reference peer VPC groups](https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-security-groups.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/security-group-rules-reference.md |
a897d1c4aace-0 | You can copy an Amazon Machine Image \(AMI\) within or across AWS Regions using the AWS Management Console, the AWS Command Line Interface or SDKs, or the Amazon EC2 API, all of which support the `CopyImage` action\. You can copy both Amazon EBS\-backed AMIs and instance\-store\-backed AMIs\. You can copy AMIs with encrypted snapshots and also change encryption status during the copy process\.
Copying a source AMI results in an identical but distinct target AMI with its own unique identifier\. In the case of an Amazon EBS\-backed AMI, each of its backing snapshots is, by default, copied to an identical but distinct target snapshot\. \(The sole exceptions are when you choose to encrypt or re\-encrypt the snapshot\.\) You can change or deregister the source AMI with no effect on the target AMI\. The reverse is also true\.
There are no charges for copying an AMI\. However, standard storage and data transfer rates apply\. If you copy an EBS\-backed AMI, you will incur charges for the storage of any additional EBS snapshots\.
AWS does not copy launch permissions, user\-defined tags, or Amazon S3 bucket permissions from the source AMI to the new AMI\. After the copy operation is complete, you can apply launch permissions, user\-defined tags, and Amazon S3 bucket permissions to the new AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
a897d1c4aace-1 | You can't copy an AMI that was obtained from the AWS Marketplace, regardless of whether you obtained it directly or it was shared with you\. Instead, launch an EC2 instance using the AWS Marketplace AMI and then create an AMI from the instance\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0ece83c812f2-0 | If you use an IAM user to copy an instance store\-backed AMI, the user must have the following Amazon S3 permissions: `s3:CreateBucket`, `s3:GetBucketAcl`, `s3:ListAllMyBuckets`, `s3:GetObject`, `s3:PutObject`, and `s3:PutObjectAcl`\.
The following example policy allows the user to copy the AMI source in the specified bucket to the specified Region\.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": [
"arn:aws:s3:::*"
]
},
{
"Effect": "Allow",
"Action": "s3:GetObject",
"Resource": [
"arn:aws:s3:::ami-source-bucket/*"
]
},
{
"Effect": "Allow",
"Action": [
"s3:CreateBucket",
"s3:GetBucketAcl",
"s3:PutObjectAcl",
"s3:PutObject"
], | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0ece83c812f2-1 | "s3:PutObjectAcl",
"s3:PutObject"
],
"Resource": [
"arn:aws:s3:::amis-for-123456789012-in-us-east-1*"
]
}
]
}
```
To find the Amazon Resource Name \(ARN\) of the AMI source bucket, open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/), in the navigation pane choose **AMIs**, and locate the bucket name in the **Source** column\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
a7765cf51285-0 | Copying an AMI across geographically diverse Regions provides the following benefits:
+ Consistent global deployment: Copying an AMI from one Region to another enables you to launch consistent instances in different Regions based on the same AMI\.
+ Scalability: You can more easily design and build global applications that meet the needs of your users, regardless of their location\.
+ Performance: You can increase performance by distributing your application, as well as locating critical components of your application in closer proximity to your users\. You can also take advantage of Region\-specific features, such as instance types or other AWS services\.
+ High availability: You can design and deploy applications across AWS regions, to increase availability\.
The following diagram shows the relations among a source AMI and two copied AMIs in different Regions, as well as the EC2 instances launched from each\. When you launch an instance from an AMI, it resides in the same Region where the AMI resides\. If you make changes to the source AMI and want those changes to be reflected in the AMIs in the target Regions, you must recopy the source AMI to the target Regions\.
![\[AMIs copied in different Regions\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami_copy.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
a7765cf51285-1 | When you first copy an instance store\-backed AMI to a Region, we create an Amazon S3 bucket for the AMIs copied to that Region\. All instance store\-backed AMIs that you copy to that Region are stored in this bucket\. The bucket names have the following format: amis\-for\-*account*\-in\-*region*\-*hash*\. For example: `amis-for-123456789012-in-us-east-2-yhjmxvp6`\.
**Prerequisite**
Prior to copying an AMI, you must ensure that the contents of the source AMI are updated to support running in a different Region\. For example, you should update any database connection strings or similar application configuration data to point to the appropriate resources\. Otherwise, instances launched from the new AMI in the destination Region may still use the resources from the source Region, which can impact performance and cost\.
**Limits**
+ Destination Regions are limited to 50 concurrent AMI copies\.
+ You cannot copy a paravirtual \(PV\) AMI to a Region that does not support PV AMIs\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
a1c51cedcd68-0 | You can share an AMI with another AWS account\. Sharing an AMI does not affect the ownership of the AMI\. The owning account is charged for the storage in the Region\. For more information, see [Sharing an AMI with specific AWS accounts](sharingamis-explicit.md)\.
If you copy an AMI that has been shared with your account, you are the owner of the target AMI in your account\. The owner of the source AMI is charged standard Amazon EBS or Amazon S3 transfer fees, and you are charged for the storage of the target AMI in the destination Region\.
**Resource Permissions**
To copy an AMI that was shared with you from another account, the owner of the source AMI must grant you read permissions for the storage that backs the AMI, either the associated EBS snapshot \(for an Amazon EBS\-backed AMI\) or an associated S3 bucket \(for an instance store\-backed AMI\)\. If the shared AMI has encrypted snapshots, the owner must share the key or keys with you as well\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
7310aed2f85f-0 | The following table shows encryption support for various AMI\-copying scenarios\. While it is possible to copy an unencrypted snapshot to yield an encrypted snapshot, you cannot copy an encrypted snapshot to yield an unencrypted one\.
| Scenario | Description | Supported |
| --- | --- | --- |
| 1 | Unencrypted\-to\-unencrypted | Yes |
| 2 | Encrypted\-to\-encrypted | Yes |
| 3 | Unencrypted\-to\-encrypted | Yes |
| 4 | Encrypted\-to\-unencrypted | No |
**Note**
Encrypting during the `CopyImage` action applies only to Amazon EBS\-backed AMIs\. Because an instance store\-backed AMI does not rely on snapshots, you cannot use copying to change its encryption status\.
By default \(i\.e\., without specifying encryption parameters\), the backing snapshot of an AMI is copied with its original encryption status\. Copying an AMI backed by an unencrypted snapshot results in an identical target snapshot that is also unencrypted\. If the source AMI is backed by an encrypted snapshot, copying it results in an identical target snapshot that is encrypted by the same customer master key \(CMK\)\. Copying an AMI backed by multiple snapshots preserves, by default, the source encryption status in each target snapshot\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
7310aed2f85f-1 | If you specify encryption parameters while copying an AMI, you can encrypt or re\-encrypt its backing snapshots\. The following example shows a non\-default case that supplies encryption parameters to the `CopyImage` action in order to change the target AMI's encryption state\.
**Copy an unencrypted source AMI to an encrypted target AMI**
In this scenario, an AMI backed by an unencrypted root snapshot is copied to an AMI with an encrypted root snapshot\. The `CopyImage` action is invoked with two encryption parameters, including a CMK\. As a result, the encryption status of the root snapshot changes, so that the target AMI is backed by a root snapshot containing the same data as the source snapshot, but encrypted using the specified key\. You incur storage costs for the snapshots in both AMIs, as well as charges for any instances you launch from either AMI\.
**Note**
Enabling [encryption by default](EBSEncryption.md#encryption-by-default) has the same effect as setting the `Encrypted` parameter to `true` for all snapshots in the AMI\.
![\[Copy AMI and encrypt snapshot on the fly\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami-to-ami-convert.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
7310aed2f85f-2 | Setting the `Encrypted` parameter encrypts the single snapshot for this instance\. If you do not specify the `KmsKeyId` parameter, the default CMK is used to encrypt the snapshot copy\.
For more information about copying AMIs with encrypted snapshots, see [Using encryption with EBS\-backed AMIs](AMIEncryption.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0c65dc042fcf-0 | You can copy an AMI as follows\.
**Prerequisite**
Create or obtain an AMI backed by an Amazon EBS snapshot\. Note that you can use the Amazon EC2 console to search a wide variety of AMIs provided by AWS\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md) and [Finding a Linux AMI](finding-an-ami.md)\.
**To copy an AMI using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the console navigation bar, select the Region that contains the AMI\. In the navigation pane, choose **Images**, **AMIs** to display the list of AMIs available to you in the Region\.
1. Select the AMI to copy and choose **Actions**, **Copy AMI**\.
1. In the **Copy AMI** dialog box, specify the following information and then choose **Copy AMI**:
+ **Destination region**: The Region in which to copy the AMI\.
+ **Name**: A name for the new AMI\. You can include operating system information in the name, as we do not provide this information when displaying details about the AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0c65dc042fcf-1 | + **Description**: By default, the description includes information about the source AMI so that you can distinguish a copy from its original\. You can change this description as needed\.
+ **Encryption**: Select this field to encrypt the target snapshots, or to re\-encrypt them using a different key\. If you have enabled [encryption by default](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/encryption-by-default.html), the **Encryption** option is set and cannot be unset from the AMI console\.
+ **Master Key**: The KMS key to used to encrypt the target snapshots\.
1. We display a confirmation page to let you know that the copy operation has been initiated and to provide you with the ID of the new AMI\.
To check on the progress of the copy operation immediately, follow the provided link\. To check on the progress later, choose **Done**, and then when you are ready, use the navigation bar to switch to the target region \(if applicable\) and locate your AMI in the list of AMIs\.
The initial status of the target AMI is `pending` and the operation is complete when the status is `available`\.
**To copy an AMI using the AWS CLI** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0c65dc042fcf-2 | **To copy an AMI using the AWS CLI**
You can copy an AMI using the [copy\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/copy-image.html) command\. You must specify both the source and destination Regions\. You specify the source Region using the `--source-region` parameter\. You can specify the destination Region using either the `--region` parameter or an environment variable\. For more information, see [Configuring the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html)\.
When you encrypt a target snapshot during copying, you must specify these additional parameters: `--encrypted` and `--kms-key-id`\.
**To copy an AMI using the Tools for Windows PowerShell**
You can copy an AMI using the [Copy\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Copy-EC2Image.html) command\. You must specify both the source and destination Regions\. You specify the source Region using the `-SourceRegion` parameter\. You can specify the destination Region using either the `-Region` parameter or the `Set-AWSDefaultRegion` command\. For more information, see [Specifying AWS Regions](https://docs.aws.amazon.com/powershell/latest/userguide/pstools-installing-specifying-region.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
0c65dc042fcf-3 | When you encrypt a target snapshot during copying, you must specify these additional parameters: `-Encrypted` and `-KmsKeyId`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
48fb1f752893-0 | You can stop a pending AMI copy as follows\.
**To stop an AMI copy operation using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the navigation bar, select the destination Region from the Region selector\.
1. In the navigation pane, choose **AMIs**\.
1. Select the AMI to stop copying and choose **Actions**, **Deregister**\.
1. When asked for confirmation, choose **Continue**\.
**To stop an AMI copy operation using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [deregister\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/deregister-image.html) \(AWS CLI\)
+ [Unregister\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2Image.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/CopyingAMIs.md |
b41aec00f631-0 | Amazon Linux is provided by Amazon Web Services \(AWS\)\. It is designed to provide a stable, secure, and high\-performance execution environment for applications running on Amazon EC2\. It also includes packages that enable easy integration with AWS, including launch configuration tools and many popular AWS libraries and tools\. AWS provides ongoing security and maintenance updates for all instances running Amazon Linux\. Many applications developed on CentOS \(and similar distributions\) run on Amazon Linux\.
**Topics**
+ [Amazon Linux availability](#amazon-linux-availability)
+ [Connecting to an Amazon Linux instance](#connect-to-amazon-linux-limits)
+ [Identifying Amazon Linux images](#amazon-linux-image-id)
+ [AWS command line tools](#amazon-linux-aws-command-line-tools)
+ [Package repository](#package-repository)
+ [Extras library \(Amazon Linux 2\)](#extras-library)
+ [Accessing source packages for reference](#amazon-linux-source-packages)
+ [cloud\-init](#amazon-linux-cloud-init)
+ [Subscribing to Amazon Linux notifications](#linux-ami-notifications)
+ [Running Amazon Linux 2 as a virtual machine on premises](amazon-linux-2-virtual-machine.md)
+ [Kernel Live Patching on Amazon Linux 2](al2-live-patching.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
709a9fb9c6cb-0 | AWS provides Amazon Linux 2 and the Amazon Linux AMI\. If you are migrating from another Linux distribution to Amazon Linux, we recommend that you migrate to Amazon Linux 2\.
The last version of the Amazon Linux AMI, 2018\.03, reaches the end of standard support on December 31, 2020\. For more information, see the following blog post: [Amazon Linux AMI end of life](http://aws.amazon.com/blogs/aws/update-on-amazon-linux-ami-end-of-life/)\. If you are currently using the Amazon Linux AMI, we recommend that you migrate to Amazon Linux 2\. To migrate to Amazon Linux 2, launch an instance or create a virtual machine using the current Amazon Linux 2 image\. Install your applications, plus any required packages\. Test your application, and make any changes required for it to run on Amazon Linux 2\.
For more information, see [Amazon Linux 2](https://aws.amazon.com/amazon-linux-2/) and [Amazon Linux AMI](https://aws.amazon.com/amazon-linux-ami/)\. For Amazon Linux Docker container images, see [amazonlinux](https://hub.docker.com/_/amazonlinux/) on Docker Hub\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
2a943de476e3-0 | Amazon Linux does not allow remote root SSH by default\. Also, password authentication is disabled to prevent brute\-force password attacks\. To enable SSH logins to an Amazon Linux instance, you must provide your key pair to the instance at launch\. You must also set the security group used to launch your instance to allow SSH access\. By default, the only account that can log in remotely using SSH is ec2\-user; this account also has sudo | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
2a943de476e3-1 | is ec2\-user; this account also has sudo privileges\. If you enable remote root login, be aware that it is less secure than relying on key pairs and a secondary user\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
bb62086f3f26-0 | Each image contains a unique `/etc/image-id` file that identifies it\. This file contains the following information about the image:
+ `image_name`, `image_version`, `image_arch` — Values from the build recipe that Amazon used to construct the image\.
+ `image_stamp` — A unique, random hex value generated during image creation\.
+ `image_date` — The UTC time of image creation, in *YYYYMMDDhhmmss* format
+ `recipe_name`, `recipe_id` — The name and ID of the build recipe Amazon used to construct the image\.
Amazon Linux contains an `/etc/system-release` file that specifies the current release that is installed\. This file is updated using yum and is part of the `system-release` RPM\.
Amazon Linux also contains a machine\-readable version of `/etc/system-release` that follows the CPE specification; see `/etc/system-release-cpe`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
b4ae0b7d7d5d-0 | The following is an example of `/etc/image-id` for the current version of Amazon Linux 2:
```
[ec2-user ~]$ cat /etc/image-id
image_name="amzn2-ami-hvm"
image_version="2"
image_arch="x86_64"
image_file="amzn2-ami-hvm-2.0.20180810-x86_64.xfs.gpt"
image_stamp="8008-2abd"
image_date="20180811020321"
recipe_name="amzn2 ami"
recipe_id="c652686a-2415-9819-65fb-4dee-9792-289d-1e2846bd"
```
The following is an example of `/etc/system-release` for the current version of Amazon Linux 2:
```
[ec2-user ~]$ cat /etc/system-release
Amazon Linux 2
```
The following is an example of `/etc/os-release` for Amazon Linux 2:
```
[ec2-user ~]$ cat /etc/os-release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
b4ae0b7d7d5d-1 | VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
5e90501992b8-0 | The following is an example of `/etc/image-id` for the current Amazon Linux AMI:
```
[ec2-user ~]$ cat /etc/image-id
image_name="amzn-ami-hvm"
image_version="2018.03"
image_arch="x86_64"
image_file="amzn-ami-hvm-2018.03.0.20180811-x86_64.ext4.gpt"
image_stamp="cc81-f2f3"
image_date="20180811012746"
recipe_name="amzn ami"
recipe_id="5b283820-dc60-a7ea-d436-39fa-439f-02ea-5c802dbd"
```
The following is an example of `/etc/system-release` for the current Amazon Linux AMI:
```
[ec2-user ~]$ cat /etc/system-release
Amazon Linux AMI release 2018.03
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
fba4cd8e972a-0 | The following command line tools for AWS integration and usage are included in the Amazon Linux AMI, or in the default repositories for Amazon Linux 2\. For the complete list of packages in the Amazon Linux AMI, see [Amazon Linux AMI 2017\.09 Packages](https://aws.amazon.com/amazon-linux-ami/2017.09-packages/)\.
+ aws\-amitools\-ec2
+ aws\-apitools\-as
+ aws\-apitools\-cfn
+ aws\-apitools\-elb
+ aws\-apitools\-mon
+ aws\-cfn\-bootstrap
+ aws\-cli
Amazon Linux 2 and the minimal versions of Amazon Linux \(`amzn-ami-minimal-*` and `amzn2-ami-minimal-*`\) do not always contain all of these packages; however, you can install them from the default repositories using the following command:
```
[ec2-user ~]$ sudo yum install -y package_name
```
For instances launched using IAM roles, a simple script has been included to prepare `AWS_CREDENTIAL_FILE`, `JAVA_HOME`, `AWS_PATH`, `PATH`, and product\-specific environment variables after a credential file has been installed to simplify the configuration of these tools\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
fba4cd8e972a-1 | Also, to allow the installation of multiple versions of the API and AMI tools, we have placed symbolic links to the desired versions of these tools in `/opt/aws`, as described here:
`/opt/aws/bin`
Symbolic links to `/bin` directories in each of the installed tools directories\.
`/opt/aws/{apitools|amitools}`
Products are installed in directories of the form *name*\-*version* and a symbolic link *name* that is attached to the most recently installed version\.
`/opt/aws/{apitools|amitools}/name/environment.sh`
Used by `/etc/profile.d/aws-apitools-common.sh` to set product\-specific environment variables, such as `EC2_HOME`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
60fb18134977-0 | Amazon Linux 2 and the Amazon Linux AMI are designed to be used with online package repositories hosted in each Amazon EC2 AWS Region\. These repositories provide ongoing updates to packages in Amazon Linux 2 and the Amazon Linux AMI, as well as access to hundreds of additional common open\-source server applications\. The repositories are available in all Regions and are accessed using yum update tools\. Hosting repositories in each Region enables us to deploy updates quickly and without any data transfer charges\.
Amazon Linux 2 and the Amazon Linux AMI are updated regularly with security and feature enhancements\. If you do not need to preserve data or customizations for your instances, you can simply launch new instances using the current AMI\. If you need to preserve data or customizations for your instances, you can maintain those instances through the Amazon Linux package repositories\. These repositories contain all the updated packages\. You can choose to apply these updates to your running instances\. Older versions of the AMI and update packages continue to be available for use, even as new versions are released\.
**Important**
Your instance must have access to the internet in order to access the repository\.
To install packages, use the following command:
```
[ec2-user ~]$ sudo yum install package
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
60fb18134977-1 | ```
[ec2-user ~]$ sudo yum install package
```
For the Amazon Linux AMI, access to the Extra Packages for Enterprise Linux \(EPEL\) repository is configured, but it is not enabled by default\. Amazon Linux 2 is not configured to use the EPEL repository\. EPEL provides third\-party packages in addition to those that are in the repositories\. The third\-party packages are not supported by AWS\. You can enable the EPEL repository with the following commands:
+ For Amazon Linux 2:
```
[ec2-user ~]$ sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
```
+ For the Amazon Linux AMI:
```
[ec2-user ~]$ sudo yum-config-manager --enable epel
```
If you find that Amazon Linux does not contain an application you need, you can simply install the application directly on your Amazon Linux instance\. Amazon Linux uses RPMs and yum for package management, and that is likely the simplest way to install new applications\. You should always check to see if an application is available in our central Amazon Linux repository first, because many applications are available there\. These applications can easily be added to your Amazon Linux instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
60fb18134977-2 | To upload your applications onto a running Amazon Linux instance, use scp or sftp and then configure the application by logging on to your instance\. Your applications can also be uploaded during the instance launch by using the PACKAGE\_SETUP action from the built\-in cloud\-init package\. For more information, see [cloud\-init](#amazon-linux-cloud-init)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
b3407fcd116f-0 | Security updates are provided using the package repositories as well as updated AMI security alerts are published in the [Amazon Linux Security Center](https://alas.aws.amazon.com)\. For more information about AWS security policies or to report a security problem, go to the [AWS Security Center](https://aws.amazon.com/security/)\.
Amazon Linux is configured to download and install critical or important security updates at launch time\. We recommend that you make the necessary updates for your use case after launch\. For example, you may want to apply all updates \(not just security updates\) at launch, or evaluate each update and apply only the ones applicable to your system\. This is controlled using the following cloud\-init setting: `repo_upgrade`\. The following snippet of cloud\-init configuration shows how you can change the settings in the user data text you pass to your instance initialization:
```
#cloud-config
repo_upgrade: security
```
The possible values for `repo_upgrade` are as follows:
`critical`
Apply outstanding critical security updates\.
`important`
Apply outstanding critical and important security updates\.
`medium`
Apply outstanding critical, important, and medium security updates\.
`low`
Apply all outstanding security updates, including low\-severity security updates\.
`security`
Apply outstanding critical or important updates that Amazon marks as security updates\.
`bugfix` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
b3407fcd116f-1 | `security`
Apply outstanding critical or important updates that Amazon marks as security updates\.
`bugfix`
Apply updates that Amazon marks as bug fixes\. Bug fixes are a larger set of updates, which include security updates and fixes for various other minor bugs\.
`all`
Apply all applicable available updates, regardless of their classification\.
`none`
Do not apply any updates to the instance on startup\.
The default setting for `repo_upgrade` is security\. That is, if you don't specify a different value in your user data, by default, Amazon Linux performs the security upgrades at launch for any packages installed at that time\. Amazon Linux also notifies you of any updates to the installed packages by listing the number of available updates upon login using the `/etc/motd` file\. To install these updates, you need to run sudo yum upgrade on the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
5c0c30ab37dc-0 | With Amazon Linux, AMIs are treated as snapshots in time, with a repository and update structure that always gives you the latest packages when you run yum update \-y\.
The repository structure is configured to deliver a continuous flow of updates that enable you to roll from one version of Amazon Linux to the next\. For example, if you launch an instance from an older version of the Amazon Linux AMI \(such as 2017\.09 or earlier\) and run yum update \-y, you end up with the latest packages\.
You can disable rolling updates by enabling the *lock\-on\-launch* feature\. The lock\-on\-launch feature locks your instance to receive updates only from the specified release of the AMI\. For example, you can launch a 2017\.09 AMI and have it receive only the updates that were released prior to the 2018\.03 AMI, until you are ready to migrate to the 2018\.03 AMI\.
**Important**
If you lock to a version of the repositories that is not the latest, you do not receive further updates\. To receive a continuous flow of updates, you must use the latest AMI, or consistently update your AMI with the repositories pointed to latest\.
To enable lock\-on\-launch in new instances, launch it with the following user data passed to cloud\-init:
```
#cloud-config
repo_releasever: 2017.09
```
**To lock existing instances to their current AMI version**
1. Edit `/etc/yum.conf`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
5c0c30ab37dc-1 | **To lock existing instances to their current AMI version**
1. Edit `/etc/yum.conf`\.
1. Comment out `releasever=latest`\.
1. To clear the cache, run yum clean all\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
6ac4e20b9682-0 | With Amazon Linux 2, you can use the Extras Library to install application and software updates on your instances\. These software updates are known as *topics*\. You can install a specific version of a topic or omit the version information to use the most recent version\.
To list the available topics, use the following command:
```
[ec2-user ~]$ amazon-linux-extras list
```
To enable a topic and install the latest version of its package to ensure freshness, use the following command:
```
[ec2-user ~]$ sudo amazon-linux-extras install topic
```
To enable topics and install specific versions of their packages to ensure stability, use the following command:
```
[ec2-user ~]$ sudo amazon-linux-extras install topic=version topic=version
```
To remove a package installed from a topic, use the following command:
```
[ec2-user ~]$ sudo yum remove $(yum list installed | grep amzn2extra-topic | awk '{ print $1 }')
```
**Note**
This command does not remove packages that were installed as dependencies of the extra\.
To disable a topic and make the packages inaccessible to the yum package manager, use the following command:
```
[ec2-user ~]$ sudo amazon-linux-extras disable topic
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
6ac4e20b9682-1 | ```
[ec2-user ~]$ sudo amazon-linux-extras disable topic
```
**Important**
This command is intended for advanced users\. Improper usage of this command could cause package compatibility conflicts\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
6b7fc214cd35-0 | You can view the source of packages you have installed on your instance for reference purposes by using tools provided in Amazon Linux\. Source packages are available for all of the packages included in Amazon Linux and the online package repository\. Simply determine the package name for the source package you want to install and use the yumdownloader \-\-source command to view source within your running instance\. For example:
```
[ec2-user ~]$ yumdownloader --source bash
```
The source RPM can be unpacked, and, for reference, you can view the source tree using standard RPM tools\. After you finish debugging, the package is available for use\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
3b7a88869c58-0 | The cloud\-init package is an open\-source application built by Canonical that is used to bootstrap Linux images in a cloud computing environment, such as Amazon EC2\. Amazon Linux contains a customized version of cloud\-init\. It enables you to specify actions that should happen to your instance at boot time\. You can pass desired actions to cloud\-init through the user data fields when launching an instance\. This means you can use common AMIs for many use cases and configure them dynamically at startup\. Amazon Linux also uses cloud\-init to perform initial configuration of the ec2\-user account\.
For more information, see the [cloud\-init documentation](http://cloudinit.readthedocs.org/en/latest/)\.
Amazon Linux uses the cloud\-init actions found in `/etc/cloud/cloud.cfg.d` and `/etc/cloud/cloud.cfg`\. You can create your own cloud\-init action files in `/etc/cloud/cloud.cfg.d`\. All files in this directory are read by cloud\-init\. They are read in lexical order, and later files overwrite values in earlier files\.
The cloud\-init package performs these \(and other\) common configuration tasks for instances at boot:
+ Set the default locale\.
+ Set the hostname\.
+ Parse and handle user data\.
+ Generate host private SSH keys\.
+ Add a user's public SSH keys to `.ssh/authorized_keys` for easy login and administration\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
3b7a88869c58-1 | + Add a user's public SSH keys to `.ssh/authorized_keys` for easy login and administration\.
+ Prepare the repositories for package management\.
+ Handle package actions defined in user data\.
+ Execute user scripts found in user data\.
+ Mount instance store volumes, if applicable\.
+ By default, the `ephemeral0` instance store volume is mounted at `/media/ephemeral0` if it is present and contains a valid file system; otherwise, it is not mounted\.
+ By default, any swap volumes associated with the instance are mounted \(only for `m1.small` and `c1.medium` instance types\)\.
+ You can override the default instance store volume mount with the following cloud\-init directive:
```
#cloud-config
mounts:
- [ ephemeral0 ]
```
For more control over mounts, see [Mounts](http://cloudinit.readthedocs.io/en/latest/topics/modules.html#mounts) in the cloud\-init documentation\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
3b7a88869c58-2 | + Instance store volumes that support TRIM are not formatted when an instance launches, so you must partition and format them before you can mount them\. For more information, see [Instance store volume TRIM support](ssd-instance-store.md#InstanceStoreTrimSupport)\. You can use the `disk_setup` module to partition and format your instance store volumes at boot\. For more information, see [Disk Setup](http://cloudinit.readthedocs.io/en/latest/topics/modules.html#disk-setup) in the cloud\-init documentation\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
9ad5fa4fb5aa-0 | The cloud\-init package supports user\-data handling of a variety of formats:
+ Gzip
+ If user\-data is gzip compressed, cloud\-init decompresses the data and handles it appropriately\.
+ MIME multipart
+ Using a MIME multipart file, you can specify more than one type of data\. For example, you could specify both a user\-data script and a cloud\-config type\. Each part of the multipart file can be handled by cloud\-init if it is one of the supported formats\.
+ Base64 decoding
+ If user\-data is base64\-encoded, cloud\-init determines if it can understand the decoded data as one of the supported types\. If it understands the decoded data, it decodes the data and handles it appropriately\. If not, it returns the base64 data intact\.
+ User\-Data script
+ Begins with `#!` or `Content-Type: text/x-shellscript`\.
+ The script is executed by `/etc/init.d/cloud-init-user-scripts` during the first boot cycle\. This occurs late in the boot process \(after the initial configuration actions are performed\)\.
+ Include file
+ Begins with `#include` or `Content-Type: text/x-include-url`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
9ad5fa4fb5aa-1 | + Include file
+ Begins with `#include` or `Content-Type: text/x-include-url`\.
+ This content is an include file\. The file contains a list of URLs, one per line\. Each of the URLs is read, and their content passed through this same set of rules\. The content read from the URL can be gzipped, MIME\-multi\-part, or plaintext\.
+ Cloud Config Data
+ Begins with `#cloud-config` or `Content-Type: text/cloud-config`\.
+ This content is cloud\-config data\. For a commented example of supported configuration formats, see the examples\.
+ Upstart job
+ Begins with `#upstart-job` or `Content-Type: text/upstart-job`\.
+ This content is stored in a file in `/etc/init`, and upstart consumes the content as per other upstart jobs\.
+ Cloud Boothook
+ Begins with `#cloud-boothook` or `Content-Type: text/cloud-boothook`\.
+ This content is boothook data\. It is stored in a file under `/var/lib/cloud` and then executed immediately\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
9ad5fa4fb5aa-2 | + This content is boothook data\. It is stored in a file under `/var/lib/cloud` and then executed immediately\.
+ This is the earliest "hook" available\. There is no mechanism provided for running it only one time\. The boothook must take care of this itself\. It is provided with the instance ID in the environment variable `INSTANCE_ID`\. Use this variable to provide a once\-per\-instance set of boothook data\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
d8842a729836-0 | To be notified when new AMIs are released, you can subscribe using Amazon SNS\.
**To subscribe to Amazon Linux notifications**
1. Open the Amazon SNS console at [https://console\.aws\.amazon\.com/sns/v3/home](https://console.aws.amazon.com/sns/v3/home)\.
1. In the navigation bar, change the Region to **US East \(N\. Virginia\)**, if necessary\. You must select the Region in which the SNS notification that you are subscribing to was created\.
1. In the navigation pane, choose **Subscriptions**, **Create subscription**\.
1. For the **Create subscription** dialog box, do the following:
1. \[Amazon Linux 2\] For **Topic ARN**, copy and paste the following Amazon Resource Name \(ARN\): **arn:aws:sns:us\-east\-1:137112412989:amazon\-linux\-2\-ami\-updates**\.
1. \[Amazon Linux\] For **Topic ARN**, copy and paste the following Amazon Resource Name \(ARN\): **arn:aws:sns:us\-east\-1:137112412989:amazon\-linux\-ami\-updates**\.
1. For **Protocol**, choose **Email**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
d8842a729836-1 | 1. For **Protocol**, choose **Email**\.
1. For **Endpoint**, enter an email address that you can use to receive the notifications\.
1. Choose **Create subscription**\.
1. You receive a confirmation email with the subject line "AWS Notification \- Subscription Confirmation"\. Open the email and choose **Confirm subscription** to complete your subscription\.
Whenever AMIs are released, we send notifications to the subscribers of the corresponding topic\. To stop receiving these notifications, use the following procedure to unsubscribe\.
**To unsubscribe from Amazon Linux notifications**
1. Open the Amazon SNS console at [https://console\.aws\.amazon\.com/sns/v3/home](https://console.aws.amazon.com/sns/v3/home)\.
1. In the navigation bar, change the Region to **US East \(N\. Virginia\)**, if necessary\. You must use the Region in which the SNS notification was created\.
1. In the navigation pane, choose **Subscriptions**, select the subscription, and choose **Actions**, **Delete subscriptions**\.
1. When prompted for confirmation, choose **Delete**\.
**Amazon Linux AMI SNS message format**
The schema for the SNS message is as follows\.
```
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
d8842a729836-2 | The schema for the SNS message is as follows\.
```
{
"description": "Validates output from AMI Release SNS message",
"type": "object",
"properties": {
"v1": {
"type": "object",
"properties": {
"ReleaseVersion": {
"description": "Major release (ex. 2018.03)",
"type": "string"
},
"ImageVersion": {
"description": "Full release (ex. 2018.03.0.20180412)",
"type": "string"
},
"ReleaseNotes": {
"description": "Human-readable string with extra information",
"type": "string"
},
"Regions": {
"type": "object",
"description": "Each key will be a region name (ex. us-east-1)",
"additionalProperties": {
"type": "array",
"items": {
"type": "object",
"properties": {
"Name": { | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
d8842a729836-3 | "items": {
"type": "object",
"properties": {
"Name": {
"description": "AMI Name (ex. amzn-ami-hvm-2018.03.0.20180412-x86_64-gp2)",
"type": "string"
},
"ImageId": {
"description": "AMI Name (ex.ami-467ca739)",
"type": "string"
}
},
"required": [
"Name",
"ImageId"
]
}
}
}
},
"required": [
"ReleaseVersion",
"ImageVersion",
"ReleaseNotes",
"Regions"
]
}
},
"required": [
"v1"
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-basics.md |
d4405fedf369-0 | You can get statistics for the CloudWatch metrics for your instances\.
**Topics**
+ [Statistics overview](#overview-statistics)
+ [Get statistics for a specific instance](US_SingleMetricPerInstance.md)
+ [Aggregate statistics across instances](GetSingleMetricAllDimensions.md)
+ [Aggregate statistics by Auto Scaling group](GetMetricAutoScalingGroup.md)
+ [Aggregate statistics by AMI](US_SingleMetricPerAMI.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_get_statistics.md |
929b2c02b138-0 | *Statistics* are metric data aggregations over specified periods of time\. CloudWatch provides statistics based on the metric data points provided by your custom data or provided by other services in AWS to CloudWatch\. Aggregations are made using the namespace, metric name, dimensions, and the data point unit of measure, within the time period you specify\. The following table describes the available statistics\.
| Statistic | Description |
| --- | --- |
| Minimum | The lowest value observed during the specified period\. You can use this value to determine low volumes of activity for your application\. |
| Maximum | The highest value observed during the specified period\. You can use this value to determine high volumes of activity for your application\. |
| Sum | All values submitted for the matching metric added together\. This statistic can be useful for determining the total volume of a metric\. |
| Average | The value of `Sum` / `SampleCount` during the specified period\. By comparing this statistic with the `Minimum` and `Maximum`, you can determine the full scope of a metric and how close the average use is to the `Minimum` and `Maximum`\. This comparison helps you to know when to increase or decrease your resources as needed\. |
| SampleCount | The count \(number\) of data points used for the statistical calculation\. |
| pNN\.NN | The value of the specified percentile\. You can specify any percentile, using up to two decimal places \(for example, p95\.45\)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_get_statistics.md |
17173a28a7ac-0 | If you have a need for a custom kernel on your Amazon EC2 instances, you can start with an AMI that is close to what you want, compile the custom kernel on your instance, and modify the `menu.lst` file to point to the new kernel\. This process varies depending on the virtualization type that your AMI uses\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\.
**Topics**
+ [HVM AMIs \(GRUB\)](#HVM_instances)
+ [Paravirtual AMIs \(PV\-GRUB\)](#Paravirtual_instances) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
15b8774206b6-0 | HVM instance volumes are treated like actual physical disks\. The boot process is similar to that of a bare metal operating system with a partitioned disk and bootloader, which allows it to work with all currently supported Linux distributions\. The most common bootloader is GRUB, and the following section describes configuring GRUB to use a custom kernel\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
46093339a1dd-0 | The following is an example of a `menu.lst` configuration file for an HVM AMI\. In this example, there are two kernel entries to choose from: Amazon Linux 2018\.03 \(the original kernel for this AMI\) and Vanilla Linux 4\.16\.4 \(a newer version of the Vanilla Linux kernel from [https://www\.kernel\.org/](https://www.kernel.org/)\)\. The Vanilla entry was copied from the original entry for this AMI, and the `kernel` and `initrd` paths were updated to the new locations\. The `default 0` parameter points the bootloader to the first entry that it sees \(in this case, the Vanilla entry\), and the `fallback 1` parameter points the bootloader to the next entry if there is a problem booting the first\.
By default, GRUB does not send its output to the instance console because it creates an extra boot delay\. For more information, see [Instance console output](instance-console.md#instance-console-console-output)\. If you are installing a custom kernel, you should consider enabling GRUB output by deleting the `hiddenmenu` line and adding `serial` and `terminal` lines to `/boot/grub/menu.lst` as shown in the example below\.
**Important**
Avoid printing large amounts of debug information during the boot process; the serial console does not support high rate data transfer\.
```
default=0
fallback=1
timeout=5
serial --unit=0 --speed=9600 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
46093339a1dd-1 | default=0
fallback=1
timeout=5
serial --unit=0 --speed=9600
terminal --dumb --timeout=5 serial console
title Vanilla Linux 4.16.4
root (hd0)
kernel /boot/vmlinuz-4.16.4 root=LABEL=/ console=tty1 console=ttyS0
initrd /boot/initrd.img-4.16.4
title Amazon Linux 2018.03 (4.14.26-46.32.amzn1.x86_64)
root (hd0,0)
kernel /boot/vmlinuz-4.14.26-46.32.amzn1.x86_64 root=LABEL=/ console=tty1 console=ttyS0
initrd /boot/initramfs-4.14.26-46.32.amzn1.x86_64.img
```
You don't need to specify a fallback kernel in your `menu.lst` file, but we recommend that you have a fallback when you test a new kernel\. GRUB can fall back to another kernel in the event that the new kernel fails\. Having a fallback kernel allows the instance to boot even if the new kernel isn't found\.
If your new Vanilla Linux kernel fails, the output will be similar to the example below\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
46093339a1dd-2 | If your new Vanilla Linux kernel fails, the output will be similar to the example below\.
```
^M Entry 0 will be booted automatically in 3 seconds. ^M Entry 0 will be booted automatically in 2 seconds. ^M Entry 0 will be booted automatically in 1 seconds.
Error 13: Invalid or unsupported executable format
[ 0.000000] Initializing cgroup subsys cpuset
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
f6f3c5be4e34-0 | Amazon Machine Images that use paravirtual \(PV\) virtualization use a system called *PV\-GRUB* during the boot process\. PV\-GRUB is a paravirtual bootloader that runs a patched version of GNU GRUB 0\.97\. When you start an instance, PV\-GRUB starts the boot process and then chain loads the kernel specified by your image's `menu.lst` file\.
PV\-GRUB understands standard `grub.conf` or `menu.lst` commands, which allows it to work with all currently supported Linux distributions\. Older distributions such as Ubuntu 10\.04 LTS, Oracle Enterprise Linux or CentOS 5\.x require a special "ec2" or "xen" kernel package, while newer distributions include the required drivers in the default kernel package\.
Most modern paravirtual AMIs use a PV\-GRUB AKI by default \(including all of the paravirtual Linux AMIs available in the Amazon EC2 Launch Wizard Quick Start menu\), so there are no additional steps that you need to take to use a different kernel on your instance, provided that the kernel you want to use is compatible with your distribution\. The best way to run a custom kernel on your instance is to start with an AMI that is close to what you want and then to compile the custom kernel on your instance and modify the `menu.lst` file as shown in [Configuring GRUB for paravirtual AMIs](#configuringGRUB) to boot with that kernel\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
f6f3c5be4e34-1 | You can verify that the kernel image for an AMI is a PV\-GRUB AKI by executing the following [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) command with the Amazon EC2 command line tools \(substituting the kernel image ID you want to check:
```
aws ec2 describe-images --filters Name=image-id,Values=aki-880531cd
```
Check whether the `Name` field starts with `pv-grub`\.
**Topics**
+ [Limitations of PV\-GRUB](#pv-grub-limitations)
+ [Configuring GRUB](#configuringGRUB)
+ [Amazon PV\-GRUB Kernel Image IDs](#AmazonKernelImageIDs)
+ [Updating PV\-GRUB](#UpdatingPV-GRUB) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
727c460302d0-0 | PV\-GRUB has the following limitations:
+ You can't use the 64\-bit version of PV\-GRUB to start a 32\-bit kernel or vice versa\.
+ You can't specify an Amazon ramdisk image \(ARI\) when using a PV\-GRUB AKI\.
+ AWS has tested and verified that PV\-GRUB works with these file system formats: EXT2, EXT3, EXT4, JFS, XFS, and ReiserFS\. Other file system formats might not work\.
+ PV\-GRUB can boot kernels compressed using the gzip, bzip2, lzo, and xz compression formats\.
+ Cluster AMIs don't support or need PV\-GRUB, because they use full hardware virtualization \(HVM\)\. While paravirtual instances use PV\-GRUB to boot, HVM instance volumes are treated like actual disks, and the boot process is similar to the boot process of a bare metal operating system with a partitioned disk and bootloader\.
+ PV\-GRUB versions 1\.03 and earlier don't support GPT partitioning; they support MBR partitioning only\.
+ If you plan to use a logical volume manager \(LVM\) with Amazon EBS volumes, you need a separate boot partition outside of the LVM\. Then you can create logical volumes with the LVM\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
b08254d5ab73-0 | To boot PV\-GRUB, a GRUB `menu.lst` file must exist in the image; the most common location for this file is `/boot/grub/menu.lst`\.
The following is an example of a `menu.lst` configuration file for booting an AMI with a PV\-GRUB AKI\. In this example, there are two kernel entries to choose from: Amazon Linux 2018\.03 \(the original kernel for this AMI\), and Vanilla Linux 4\.16\.4 \(a newer version of the Vanilla Linux kernel from [https://www\.kernel\.org/](https://www.kernel.org/)\)\. The Vanilla entry was copied from the original entry for this AMI, and the `kernel` and `initrd` paths were updated to the new locations\. The `default 0` parameter points the bootloader to the first entry it sees \(in this case, the Vanilla entry\), and the `fallback 1` parameter points the bootloader to the next entry if there is a problem booting the first\.
```
default 0
fallback 1
timeout 0
hiddenmenu
title Vanilla Linux 4.16.4
root (hd0)
kernel /boot/vmlinuz-4.16.4 root=LABEL=/ console=hvc0
initrd /boot/initrd.img-4.16.4
title Amazon Linux 2018.03 (4.14.26-46.32.amzn1.x86_64)
root (hd0) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
b08254d5ab73-1 | title Amazon Linux 2018.03 (4.14.26-46.32.amzn1.x86_64)
root (hd0)
kernel /boot/vmlinuz-4.14.26-46.32.amzn1.x86_64 root=LABEL=/ console=hvc0
initrd /boot/initramfs-4.14.26-46.32.amzn1.x86_64.img
```
You don't need to specify a fallback kernel in your `menu.lst` file, but we recommend that you have a fallback when you test a new kernel\. PV\-GRUB can fall back to another kernel in the event that the new kernel fails\. Having a fallback kernel allows the instance to boot even if the new kernel isn't found\.
PV\-GRUB checks the following locations for `menu.lst`, using the first one it finds:
+ `(hd0)/boot/grub`
+ `(hd0,0)/boot/grub`
+ `(hd0,0)/grub`
+ `(hd0,1)/boot/grub`
+ `(hd0,1)/grub`
+ `(hd0,2)/boot/grub`
+ `(hd0,2)/grub`
+ `(hd0,3)/boot/grub`
+ `(hd0,3)/grub` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
b08254d5ab73-2 | + `(hd0,3)/boot/grub`
+ `(hd0,3)/grub`
Note that PV\-GRUB 1\.03 and earlier only check one of the first two locations in this list\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
bd138e0f1e29-0 | PV\-GRUB AKIs are available in all Amazon EC2 regions\. There are AKIs for both 32\-bit and 64\-bit architecture types\. Most modern AMIs use a PV\-GRUB AKI by default\.
We recommend that you always use the latest version of the PV\-GRUB AKI, as not all versions of the PV\-GRUB AKI are compatible with all instance types\. Use the following [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) command to get a list of the PV\-GRUB AKIs for the current region:
```
aws ec2 describe-images --owners amazon --filters Name=name,Values=pv-grub-*.gz
```
Note that PV\-GRUB is the only AKI available in the `ap-southeast-2` Region\. You should verify that any AMI you want to copy to this Region is using a version of PV\-GRUB that is available in this Region\.
The following are the current AKI IDs for each Region\. Register new AMIs using an hd0 AKI\.
**Note**
We continue to provide hd00 AKIs for backward compatibility in regions where they were previously available\.
**ap\-northeast\-1, Asia Pacific \(Tokyo\)**
| Image ID | Image Name |
| --- | --- | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
bd138e0f1e29-1 | | Image ID | Image Name |
| --- | --- |
| aki\-f975a998 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-7077ab11 | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**ap\-southeast\-1, Asia Pacific \(Singapore\) Region**
| Image ID | Image Name |
| --- | --- |
| aki\-17a40074 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-73a50110 | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**ap\-southeast\-2, Asia Pacific \(Sydney\)**
| Image ID | Image Name |
| --- | --- |
| aki\-ba5665d9 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-66506305 | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**eu\-central\-1, Europe \(Frankfurt\)**
| Image ID | Image Name | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
bd138e0f1e29-2 | **eu\-central\-1, Europe \(Frankfurt\)**
| Image ID | Image Name |
| --- | --- |
| aki\-1419e57b | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-931fe3fc | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**eu\-west\-1, Europe \(Ireland\)**
| Image ID | Image Name |
| --- | --- |
| aki\-1c9fd86f | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-dc9ed9af | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**sa\-east\-1, South America \(São Paulo\)**
| Image ID | Image Name |
| --- | --- |
| aki\-7cd34110 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-912fbcfd | pv\-grub\-hd0\_1\.05\-x86\_64\.gz | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
bd138e0f1e29-3 | **us\-east\-1, US East \(N\. Virginia\)**
| Image ID | Image Name |
| --- | --- |
| aki\-04206613 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-5c21674b | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**us\-gov\-west\-1, AWS GovCloud \(US\-West\)**
| Image ID | Image Name |
| --- | --- |
| aki\-5ee9573f | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-9ee55bff | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**us\-west\-1, US West \(N\. California\)**
| Image ID | Image Name |
| --- | --- |
| aki\-43cf8123 | pv\-grub\-hd0\_1\.05\-i386\.gz | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
bd138e0f1e29-4 | | aki\-43cf8123 | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-59cc8239 | pv\-grub\-hd0\_1\.05\-x86\_64\.gz |
**us\-west\-2, US West \(Oregon\)**
| Image ID | Image Name |
| --- | --- |
| aki\-7a69931a | pv\-grub\-hd0\_1\.05\-i386\.gz |
| aki\-70cb0e10 | pv\-grub\-hd0\_1\.05\-x86\_64\.gz | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
d8c4cbb39201-0 | We recommend that you always use the latest version of the PV\-GRUB AKI, as not all versions of the PV\-GRUB AKI are compatible with all instance types\. Also, older versions of PV\-GRUB are not available in all regions, so if you copy an AMI that uses an older version to a Region that does not support that version, you will be unable to boot instances launched from that AMI until you update the kernel image\. Use the following procedures to check your instance's version of PV\-GRUB and update it if necessary\.
**To check your PV\-GRUB version**
1. Find the kernel ID for your instance\.
```
aws ec2 describe-instance-attribute --instance-id instance_id --attribute kernel --region region
{
"InstanceId": "instance_id",
"KernelId": "aki-70cb0e10"
}
```
The kernel ID for this instance is `aki-70cb0e10`\.
1. View the version information of that kernel ID\.
```
aws ec2 describe-images --image-ids aki-70cb0e10 --region region
{
"Images": [
{
"VirtualizationType": "paravirtual",
"Name": "pv-grub-hd0_1.05-x86_64.gz",
... | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
d8c4cbb39201-1 | "Name": "pv-grub-hd0_1.05-x86_64.gz",
...
"Description": "PV-GRUB release 1.05, 64-bit"
}
]
}
```
This kernel image is PV\-GRUB 1\.05\. If your PV\-GRUB version is not the newest version \(as shown in [Amazon PV\-GRUB Kernel Image IDs](#AmazonKernelImageIDs)\), you should update it using the following procedure\.
**To update your PV\-GRUB version**
If your instance is using an older version of PV\-GRUB, you should update it to the latest version\.
1. Identify the latest PV\-GRUB AKI for your Region and processor architecture from [Amazon PV\-GRUB Kernel Image IDs](#AmazonKernelImageIDs)\.
1. Stop your instance\. Your instance must be stopped to modify the kernel image used\.
```
aws ec2 stop-instances --instance-ids instance_id --region region
```
1. Modify the kernel image used for your instance\.
```
aws ec2 modify-instance-attribute --instance-id instance_id --kernel kernel_id --region region
```
1. Restart your instance\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
d8c4cbb39201-2 | ```
1. Restart your instance\.
```
aws ec2 start-instances --instance-ids instance_id --region region
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/UserProvidedKernels.md |
85f1c46719fe-0 | You can create a point\-in\-time snapshot of an EBS volume and use it as a baseline for new volumes or for data backup\. If you make periodic snapshots of a volume, the snapshots are incremental—the new snapshot saves only the blocks that have changed since your last snapshot\.
Snapshots occur asynchronously; the point\-in\-time snapshot is created immediately, but the status of the snapshot is `pending` until the snapshot is complete \(when all of the modified blocks have been transferred to Amazon S3\), which can take several hours for large initial snapshots or subsequent snapshots where many blocks have changed\. While it is completing, an in\-progress snapshot is not affected by ongoing reads and writes to the volume\.
You can take a snapshot of an attached volume that is in use\. However, snapshots only capture data that has been written to your Amazon EBS volume at the time the snapshot command is issued\. This might exclude any data that has been cached by any applications or the operating system\. If you can pause any file writes to the volume long enough to take a snapshot, your snapshot should be complete\. However, if you can't pause all file writes to the volume, you should unmount the volume from within the instance, issue the snapshot command, and then remount the volume to ensure a consistent and complete snapshot\. You can remount and use your volume while the snapshot status is `pending`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-snapshot.md |
85f1c46719fe-1 | To make snapshot management easier, you can tag your snapshots during creation or add tags afterward\. For example, you can apply tags describing the original volume from which the snapshot was created, or the device name that was used to attach the original volume to an instance\. For more information, see [Tagging your Amazon EC2 resources](Using_Tags.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-snapshot.md |
8cd74e0cd5fb-0 | Snapshots that are taken from encrypted volumes are automatically encrypted\. Volumes that are created from encrypted snapshots are also automatically encrypted\. The data in your encrypted volumes and any associated snapshots is protected both at rest and in motion\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\.
By default, only you can create volumes from snapshots that you own\. However, you can share your unencrypted snapshots with specific AWS accounts, or you can share them with the entire AWS community by making them public\. For more information, see [Sharing an Amazon EBS snapshot](ebs-modifying-snapshot-permissions.md)\.
You can share an encrypted snapshot only with specific AWS accounts\. For others to use your shared, encrypted snapshot, you must also share the CMK key that was used to encrypt it\. Users with access to your encrypted snapshot must create their own personal copy of it and then use that copy\. Your copy of a shared, encrypted snapshot can also be re\-encrypted using a different key\. For more information, see [Sharing an Amazon EBS snapshot](ebs-modifying-snapshot-permissions.md)\.
**Note**
If you copy a snapshot and encrypt it to a new CMK, a complete \(non\-incremental\) copy is always created, resulting in additional delay and storage costs\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-snapshot.md |
Subsets and Splits