Question : Describe the process of registering a Android mobile device with SNS push notification service using GCM.
1. Submit GCM notification credentials to Amazon SNS; Receive Registration ID for each mobile device; Pass device token to SNS; SNS then creates a mobile subscription endpoint for each device and communicates with the GCM service on your behalf
2. Pass device token to SNS to create mobile subscription endpoint for each mobile device; Request device token from each mobile device; SNS then communicates on your behalf to the GCM service 3. Access Mostly Uused Products by 50000+ Subscribers Amazon SNS; pass GCM token credentials to Amazon SNS
Explanation: Google Cloud Messaging for Android (GCM) is a service that enables you to send push notification messages to an Android app. This section describes how to obtain the GCM prerequisites and send a push notification message to a mobile endpoint.
To send push notification messages to an Android app, you need the following:
Android app registered with GCM
Registration ID
Server API key (sender auth token) Step 1: Create a Google API Project and Enable the GCM Service
To send an push notification message to an Android app, you must have a Google API project and enable the GCM service.
To create a Google API project and enable the GCM service
If you do not already have a Google API project, then see the Creating a Google API project in the Android developer documentation.
Step 2: Obtain the Server API Key
To communicate with GCM on your behalf, Amazon SNS uses your server API key. This key will be used in a later step to send a push notification to a mobile endpoint. Step 3: Obtain a Registration ID from GCM
When you register your app with GCM to receive push notification messages, a registration ID is generated. Amazon SNS uses this value to determine which app and associated device to send mobile push notifications to.
Step 4: Send a Push Notification Message to a Mobile Endpoint using GCM
This section describes how to send a push notification message to your mobile endpoint. You add the gathered prerequisite information to the AWS sample file SNSMobilePush.java, which is included in the snsmobilepush.zip file.
Question : Which of the following is a correct command to make AMI private (Using the AWS CLI)
Explanation: Use the modify-image-attribute command as follows to add the all group to the launchPermission list for the specified AMI. aws ec2 modify-image-attribute --image-id ami-2bb65342 --launch-permission "{\"Add\":[{\"Group\":\"all\"}]}"
To verify the launch permissions of the AMI, use the following describe-image-attribute command. aws ec2 describe-image-attribute --image-id ami-2bb65342 --attribute launchPermission
(Optional) To make the AMI private again, remove the all group from its launch permissions. Note that the owner of the AMI always has launch permissions and is therefore unaffected by this command. aws ec2 modify-image-attribute --image-id ami-2bb65342 "{\"Remove\":[{\"Group\":\"all\"}]}"
Question : Which features can be used to restrict access to data in S? Choose answers A. Use S3 Virtual Hosting B. Set an S3 Bucket policy. C. Enable IAM Identity Federation. D. Set an S3 ACL on the bucket or the object. E. Create a CloudFront distribution for the bucket 1. A,B 2. B,C 3. Access Mostly Uused Products by 50000+ Subscribers 4. B,D 5. A,E
Explanation: Amazon S3 is secure by default. Only the bucket and object owners originally have access to Amazon S3 resources they create. Amazon S3 supports user authentication to control access to data. You can use access control mechanisms such as bucket policies and Access Control Lists (ACLs) to selectively grant permissions to users and groups of users. You can securely upload/download your data to Amazon S3 via SSL endpoints using the HTTPS protocol. If you need extra security you can use the Server Side Encryption (SSE) option or the Server Side Encryption with Customer-Provide Keys (SSE-C) option to encrypt data stored-at-rest. Amazon S3 provides the encryption technology for both SSE and SSE-C. Alternatively you can use your own encryption libraries to encrypt data before storing it in Amazon S3.
1. You can only associate two IAM role with an EC2 instance at this time, so applying these two roles are fine 2. All the HR and Finance application which were part of HRFinance will be denied access immediately 3. Access Mostly Uused Products by 50000+ Subscribers 4. 1 and 2 5. 2 and 3
1. IAM roles for EC2 instances also work in Virtual Private Cloud, with spot insnaces only 2. IAM roles for EC2 instances also work in Virtual Private Cloud, with with reserved instances only 3. Access Mostly Uused Products by 50000+ Subscribers 4. The AWS temporary security credentials associated with an IAM role are automatically rotated multiple times a day on the EC2 instance 5. 3 and 4