Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam Amazon-DEA-C01 Topic 1 Question 13 Discussion

Actual exam question for Amazon's Amazon-DEA-C01 exam
Question #: 13
Topic #: 1
[All Amazon-DEA-C01 Questions]

A company uses Amazon S3 to store data and Amazon QuickSight to create visualizations.

The company has an S3 bucket in an AWS account named Hub-Account. The S3 bucket is encrypted by an AWS Key Management Service (AWS KMS) key. The company's QuickSight instance is in a separate account named BI-Account

The company updates the S3 bucket policy to grant access to the QuickSight service role. The company wants to enable cross-account access to allow QuickSight to interact with the S3 bucket.

Which combination of steps will meet this requirement? (Select TWO.)

Show Suggested Answer Hide Answer
Suggested Answer: D, E

Problem Analysis:

The company needs cross-account access to allow QuickSight in BI-Account to interact with an S3 bucket in Hub-Account.

The bucket is encrypted with an AWS KMS key.

Appropriate permissions must be set for both S3 access and KMS decryption.

Key Considerations:

QuickSight requires IAM permissions to access S3 data and decrypt files using the KMS key.

Both S3 and KMS permissions need to be properly configured across accounts.

Solution Analysis:

Option A: Use Existing KMS Key for Encryption

While the existing KMS key is used for encryption, it must also grant decryption permissions to QuickSight.

Option B: Add S3 Bucket to QuickSight Role

Granting S3 bucket access to the QuickSight service role is necessary for cross-account access.

Option C: AWS RAM for Bucket Sharing

AWS RAM is not required; bucket policies and IAM roles suffice for granting cross-account access.

Option D: IAM Policy for KMS Access

QuickSight's service role in BI-Account needs explicit permissions to use the KMS key for decryption.

Option E: Add KMS Key as Resource for Role

The KMS key must explicitly list the QuickSight role as an entity that can access it.

Implementation Steps:

S3 Bucket Policy in Hub-Account: Add a policy to the S3 bucket granting the QuickSight service role access:

json

{

'Version': '2012-10-17',

'Statement': [

{

'Effect': 'Allow',

'Principal': { 'AWS': 'arn:aws:iam::<BI-Account-ID>:role/service-role/QuickSightRole' },

'Action': 's3:GetObject',

'Resource': 'arn:aws:s3:::<Bucket-Name>/*'

}

]

}

KMS Key Policy in Hub-Account: Add permissions for the QuickSight role:

{

'Version': '2012-10-17',

'Statement': [

{

'Effect': 'Allow',

'Principal': { 'AWS': 'arn:aws:iam::<BI-Account-ID>:role/service-role/QuickSightRole' },

'Action': [

'kms:Decrypt',

'kms:DescribeKey'

],

'Resource': '*'

}

]

}

IAM Policy for QuickSight Role in BI-Account: Attach the following policy to the QuickSight service role:

{

'Version': '2012-10-17',

'Statement': [

{

'Effect': 'Allow',

'Action': [

's3:GetObject',

'kms:Decrypt'

],

'Resource': [

'arn:aws:s3:::<Bucket-Name>/*',

'arn:aws:kms:<region>:<Hub-Account-ID>:key/<KMS-Key-ID>'

]

}

]

}


Setting Up Cross-Account S3 Access

AWS KMS Key Policy Examples

Amazon QuickSight Cross-Account Access

Contribute your Thoughts:

Lauran
14 days ago
Yes, and we should also add an IAM policy to the QuickSight service role to give QuickSight access to the KMS key that encrypts the S3 bucket.
upvoted 0 times
...
Dell
17 days ago
I believe we should add the KMS key as a resource that the QuickSight service role can access as well.
upvoted 0 times
...
Jaclyn
18 days ago
I agree with that. We also need to add the S3 bucket as a resource that the QuickSight service role can access.
upvoted 0 times
...
Fidelia
20 days ago
Hah, I can just imagine the conversation in the office. 'Wait, you mean we have to use AWS RAM for this? I thought we were just going to add another IAM policy!'
upvoted 0 times
...
Lauran
26 days ago
I think we should use the existing AWS KMS key to encrypt connections from QuickSight to the S3 bucket.
upvoted 0 times
...
Ma
1 months ago
C is definitely the way to do it. Sharing the S3 bucket through RAM is the simplest and most secure option.
upvoted 0 times
...
Bong
1 months ago
I agree with Mable. B and C are the way to do it. Although D sounds like it could work, it's not the most efficient approach.
upvoted 0 times
Tarra
13 days ago
Yeah, D might work but it seems like B and C are more efficient.
upvoted 0 times
...
Aja
16 days ago
I agree, those seem like the best choices.
upvoted 0 times
...
Sharen
22 days ago
I think we should go with options B and C.
upvoted 0 times
...
...
Mable
1 months ago
B and C are the correct options. Sharing the S3 bucket through AWS RAM is the way to go for cross-account access.
upvoted 0 times
Mi
18 days ago
That makes sense. Sharing through AWS RAM is the best option for cross-account access.
upvoted 0 times
...
Jina
19 days ago
C) Use AWS Resource Access Manager (AWS RAM) to share the S3 bucket with the BI-Account account.
upvoted 0 times
...
Catarina
22 days ago
B) Add the S3 bucket as a resource that the QuickSight service role can access.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77