AWS CLOUD

AWS Import/Export:

1. AWS Import/Export accelerates transferring data between the AWS cloud and portable storage devices that you mail to us. AWS Import/Export is a good choice if you have 16 terabytes (TB) or less of data to import into (TB) or Amazon Simple Storage Service or Amazon Elastic Block Store (Amazon EBS) You can also export data from Amazon 53 with AWS Import/Export.
2. AWS Import/Export doesn’t support export jobs from Amazon Elastic Block Store (EBS).
3. An Amazon $3 export transfers individual objects from Amazon S3 buckets to your device, creating one tile for each object. You can export from more than one bucket and you can specify which files to export using manifest file options.
4. You cannot export Amazon 53 objects that have been transitioned to Amazon Glacier Storage Class using Amazon 53-Object Lifecycle Management.
5. Network Load Balancer provides TCP (Layer 4) load balancing. It is architected to handle millions of requests/sec, sudden volatile traffic patterns and provides extremely low latencies. In addition Network Load Balancer also preserves the source IP of the clients, provides stable IP support and Zonal isolation. It also supports long-running connections that are very useful for Web Socket type applications.
6. . Network Load Balancer preserves the source IP of the client which in the Classic Load Balancer is not preserved. Customers can use proxy protocol with Classic Load Balancer to get the source IP. Network Load Balancer automatically provides a static IP per Availability Zone to the load balancer and also enables assigning an Elastic IP to the load balancer per Availability Zone. This is not supported with Classic Load Balancer.
7. . Application Load Balancer supports load balancing of applications using HTTP and HTTPS (Secure HTTP) protocols.
8. An Auto Scaling group contains a collection of EC2 instances that share similar characteristics and are treated as a logical grouping for the purposes of instance scaling and management.
9. A launch configuration is a template that an Auto Scaling group uses to launch EC2 instances. When you create a launch configuration, you specify information for the instances such as the ID of the Amazon Machine image (AMI), the instance type. Key Pair, Security Groups and Block Storage devices are optional.
10. An auto scaling policy is a policy used by Auto Scaling that uses CloudWatch alarms to determine when your Auto Scaling group should scale out or scale in. Each CloudWatch alarm watches a single metric and messages to Auto scalling when the metric breaches a threshold thar you specify in the policy.
11. The instance that you want to attach must meet the following criteria:

The instance is in the running state.

The AMI used to launch the instance must still exist.

The instance is not a member of another Auto Scaling group.

The instance is in the same Availability Zone as the Auto Scaling group.

If the Auto Scaling group has an attached load balancer, the instance and the load balancer must both be in EC2-Classic or the same VPC. If the Auto Scaling group has an attached target group, the instance and the load balancer must both be in the same VPC.

12. Elastic Load Balancing provides access logs that capture deaded information about requests sent to your load balancer. Each log contains information such as the time the request was received, the client’s IP address, latencies, request paths, and server responses.
13. . Access logging is an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logging for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify as compressed files. You can disable access logging at any time.
14. There is no additional charge for access logs. You are charged storage costs for Amazon S3, but not charged for the bandwidth used by Elastic Load Balancing to send log files to Amazon S3.