Question : Which EC API call would you use to retrieve a list of Amazon Machine Images (AMIs)? 1. DescnbeInstances 2. DescribeAMls 3. Access Mostly Uused Products by 50000+ Subscribers 4. GetAMls 5. You cannot retrieve a list of AMIs as there are over 10,000 AMIs Ans : 3 Exp : DescribeImages
Describes one or more of the images (AMIs, AKIs, and ARIs) available to you. Images available to you include public images, private images that you own, and private images owned by other AWS accounts but for which you have explicit launch permissions.
Note Deregistered images are included in the returned results for an unspecified interval after deregistration.
We recommend that all bucket names comply with DNS naming conventions. These conventions are enforced in all regions except for the US Standard Region. DNS compliant bucket names allow customers to benefit from new features and operational improvements, as well as providing support for virtual host style access to buckets. While the US Standard Region currently allows non compliant DNS bucket naming, we are moving to the same DNS compliant bucket naming convention for the US Standard Region in the coming months. This will ensure a single, consistent naming approach for Amazon S3 buckets. The rules for DNS compliant bucket names are:
Bucket names must be at least 3 and no more than 63 characters long. Bucket names must be a series of one or more labels. Adjacent labels are separated by a single period (.). Bucket names can contain lowercase letters, numbers, and hyphens. Each label must start and end with a lowercase letter or a number. Bucket names must not be formatted as an IP address (e.g., 192.168.5.4). The following examples are valid bucket names: myawsbucket my.aws.bucket myawsbucket.1
The following examples are invalid bucket names: Invalid Bucket Name Comment .myawsbucket Bucket name cannot start with a period (.). myawsbucket. Bucket name cannot end with a period (.). my..examplebucket There can be only one period between labels. Challenges with Non DNS Compliant Bucket Names
The US Standard Region currently allows more relaxed standards to bucket naming, which can result in a bucket name that is not DNS compliant. For example, MyAWSBucket is a valid bucket name, even though it contains uppercase letters. If you try to access this bucket by using a virtual hosted style request (http://MyAWSBucket.s3.amazonaws.com/yourobject), the URL resolves to the bucket myawsbucket and not the bucket MyAWSBucket. In response, Amazon S3 will return a bucket not found error.
To avoid this problem, we recommend as a best practice that you always use DNS compliant bucket names regardless of the region in which you create the bucket. For more information about virtual hosted style access to your buckets, see Virtual Hosting of Buckets.
The rules for bucket names in the US Standard Region allow bucket names to be as long as 255 characters, and bucket names can contain any combination of uppercase letters, lowercase letters, numbers, periods (.), hyphens (-), and underscores (_).