Question : A user has launched an EBS backed EC instance in the US-East-a region. The user stopped the instance and started it back after days. AWS throws up an `InsufficientInstanceCapacity' error. What can be the possible reason for this?
1. AWS does not have sufficient capacity in that availability zone 2. AWS zone mapping is changed for that user account 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user account has reached the maximum EC2 instance limit
When the user gets an `InsufficientInstanceCapacity' error while launching or starting an EC2 instance, it means that AWS does not currently have enough available capacity to service the user request. If the user is requesting a large number of instances, there might not be enough server capacity to host them. The user can either try again later, by specifying a smaller number of instances or changing the availability zone if launching a fresh instance.
Question : An organization has created IAM users. The organization wants each of the IAM users to have access to a separate DyanmoDB table. All the users are added to the same group and the organization wants to setup a group level policy for this. How can the organization achieve this?
1. Define the group policy and add a condition which allows the access based on the IAM name 2. Create a DynamoDB table with the same name as the IAM user name and define the policy rule which grants access based on the DynamoDB ARN using a variable 3. Access Mostly Uused Products by 50000+ Subscribers 4. It is not possible to have a group level policy which allows different IAM users to different DynamoDB Tables
Explanation:AWS Identity and Access Management is a web service which allows organizations to manage users and user permissions for various AWS services. AWS DynamoDB has only tables and the organization cannot makeseparate databases. The organization should create a table with the same name as the IAM user name and use the ARN of DynamoDB as part of the group policy. The sample policy is shown below: { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": ["dynamodb:*"], "Resource": "arn:aws:dynamodb:region:account-number-without-hyphens:table/${aws:username}" } ] }
Question : QuickTechie.com is currently runs several FTP servers that their customers use to upload and download large video files. They wish to move this system to AWS to make it more scalable, but they wish to maintain customer privacy and Keep costs to a minimum. What AWS architecture would you recommend? 1. Ask their customers to use an S3 client instead of an FTP client. Create a single S3 bucket. Create an IAM user for each customer. Put the IAM Users in a Group that has an IAM policy that permits access to sub-directories within the bucket via use of the 'username' Policy variable. 2. Create a single S3 bucket with Reduced Redundancy Storage turned on and ask their customers to use an S3 client instead of an FTP client. Create a bucket for each customer with a Bucket Policy that permits access only to that one customer. 3. Access Mostly Uused Products by 50000+ Subscribers threshold. Load a central list of ftp users from S3 as part of the user Data startup script on each Instance. 4. Create a single S3 bucket with Requester Pays turned on and ask their customers to use an S3 client instead of an FTP client. Create a bucket for each customer with a Bucket Policy that permits access only to that one customer.
Answer: 1 Explanation: Best solution to store static graphic file is S3. So we can use S3 client to access s3 files. Now next part is permission in the bucket object for 250 customers. We can create 250 IAM users as well. And each customer can access their private content. There is no limit to the amount of objects you can store in a bucket, so generally you would have a single bucket per application, or even across multiple applications. Bucket names have to be globally unique across S3 so it would certainly be impossible to manage a bucket per object. A bucket per user would also be difficult if you had more than a handful of users. (Hence avoid option 2,4)
We should not have any FTP servers (As priority is reduced cost), so avoid option 3 as well. Remaining option is 1. Read this article : http://docs.aws.amazon.com/IAM/latest/UserGuide/PolicyVariables.html