Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SCS-C01 Topic 2 Question 57 Discussion

Actual exam question for Amazon's SCS-C01 exam
Question #: 57
Topic #: 2
[All SCS-C01 Questions]

A security team is developing an application on an Amazon EC2 instance to get objects from an Amazon S3 bucket. All objects in the S3 bucket are encrypted with an AWS Key Management Service (AWS KMS) customer managed key. All network traffic for requests that are made within the VPC is restricted to the AWS infrastructure. This traffic does not traverse the public internet.

The security team is unable to get objects from the S3 bucket

Which factors could cause this issue? (Select THREE.)

Show Suggested Answer Hide Answer
Suggested Answer: A, D, E

https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html

To get objects from an S3 bucket that are encrypted with a KMS customer managed key, the security team needs to have the following factors in place:

The IAM instance profile that is attached to the EC2 instance must allow the s3:GetObject action to the S3 bucket or object in the AWS account. This permission is required to read the object from S3. Option A is incorrect because it specifies the s3:ListBucket action, which is only required to list the objects in the bucket, not to get them.

The KMS key policy that encrypts the object in the S3 bucket must allow the kms:Decrypt action to the EC2 instance profile ARN. This permission is required to decrypt the object using the KMS key. Option D is correct.

The security group that is attached to the EC2 instance must have an outbound rule to the S3 managed prefix list over port 443. This rule is required to allow HTTPS traffic from the EC2 instance to S3 within the AWS infrastructure. Option E is correct. Option B is incorrect because it specifies the s3:ListParts action, which is only required for multipart uploads, not for getting objects. Option C is incorrect because it specifies the kms:ListKeys action, which is not required for getting objects. Option F is incorrect because it specifies an inbound rule from the S3 managed prefix list, which is not required for getting objects. Verified Reference:

https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html

https://docs.aws.amazon.com/kms/latest/developerguide/control-access.html

https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints-s3.html


Contribute your Thoughts:

Leigha
6 months ago
Actually, I believe options C and D are also important to consider. The KMS key policy could be preventing access.
upvoted 0 times
...
Bok
6 months ago
I agree with Josue. The IAM instance profile and security group rules seem like common causes of such issues.
upvoted 0 times
...
Josue
7 months ago
I think options A, E, and F could be causing the issue.
upvoted 0 times
...
Brigette
7 months ago
I also think the missing outbound rule in the security group could be causing the issue.
upvoted 0 times
...
Heike
7 months ago
Yeah, I agree. That could definitely be one of the factors causing the problem.
upvoted 0 times
...
Audra
7 months ago
I think the issue could be because the IAM instance profile does not allow the s3 ListBucket action.
upvoted 0 times
...
Aileen
8 months ago
Haha, I bet the security team is pulling their hair out trying to figure this one out. I'm guessing they've already checked the obvious stuff, like the security group and IAM permissions.
upvoted 0 times
Yvonne
6 months ago
Maybe they missed setting up the outbound rule in the security group?
upvoted 0 times
...
Yvonne
7 months ago
I agree, they should also review the KMS key policy to see if there are any restrictions.
upvoted 0 times
...
Yvonne
7 months ago
Yep, they probably need to double-check the IAM instance profile permissions.
upvoted 0 times
...
...
Valda
8 months ago
Yeah, we need to make sure the instance profile has the necessary permissions to interact with the S3 bucket and the KMS key.
upvoted 0 times
Jaleesa
8 months ago
E) The security group that is attached to the EC2 instance is missing an outbound rule to the S3 managed prefix list over port 443.
upvoted 0 times
...
Josue
8 months ago
C) The KMS key policy that encrypts the object in the S3 bucket does not allow the kms ListKeys action to the EC2 instance profile ARN.
upvoted 0 times
...
Lou
8 months ago
A) The IAM instance profile that is attached to the EC2 instance does not allow the s3 ListBucket action to the S3 bucket in the AWS accounts.
upvoted 0 times
...
...
Jaime
8 months ago
Hmm, yeah, the KMS key policy is a good point. And don't forget about the security group - it might be missing the right rules to allow the traffic to and from S3.
upvoted 0 times
...
Alesia
8 months ago
Ah, I see. The IAM instance profile and the KMS key policy are likely the culprits here.
upvoted 0 times
...
Daniel
8 months ago
You're probably right, they've likely gone through the basics. But you know what they say, 'the devil is in the details' when it comes to AWS security.
upvoted 0 times
...
Maile
8 months ago
That's a good point. We need to focus on the permissions and configurations within the AWS environment.
upvoted 0 times
...
Basilia
8 months ago
Wow, this is a tricky one. Let's see, we need to select three factors that could be causing the issue. I'm guessing the IAM instance profile permissions might be the culprit, since the team is unable to get objects from the S3 bucket.
upvoted 0 times
...
Taryn
8 months ago
The key thing here is that the traffic is restricted to the AWS infrastructure, so the public internet is not an issue.
upvoted 0 times
...
Ligia
8 months ago
Hmm, let's think this through step-by-step. I'm confident we can figure this out.
upvoted 0 times
...
Vanda
8 months ago
Oh, this question seems tricky. I'm not sure if I would be able to get the right answer on the first try.
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