Amazon Web Services SCS-C02 Exam With Confidence Using Practice Dumps

Enabling AWS CloudTrail with a trail applied to all regions and specifying a single S3 bucket for storage is the simplest method to record and retain API call activity for security analysis. This configuration ensures comprehensive coverage across all current and future AWS regions, centralizing log collection and simplification of log management.

AWS Organizations and SCPs:

SCPs allow centralized control over permissions across all accounts in an AWS Organization.

Use SCPs to prevent specific actions, such as S3 bucket deletion, across all accounts.

Create an SCP for S3 Bucket Deletion:

Define an SCP that explicitly denies thes3:DeleteBucketaction.

Example SCP:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Deny",

"Action": "s3:DeleteBucket",

"Resource": "*"

}

]

}

Attach SCP to the Root or Specific OUs:

Attach the SCP to the root of the organization or specific organizational units (OUs) as needed.

Advantages:

Scalability: Applies to all accounts in the organization without the need for individual configuration.

Compliance: Ensures sensitive S3 buckets are protected from accidental or malicious deletion.

AWS Organizations SCP Documentation

Restricting S3 Actions with SCPs

because these are the steps that can ensure that the service-linked role can launch instances with encrypted volumes. A service-linked role is a type of IAM role that is linked to an AWS service and allows the service to perform actions on your behalf. A KMS grant is a mechanism that allows you to delegate permissions to use a customer master key (CMK) to a principal such as a service-linked role.A KMS grant specifies the actions that the principal can perform, such as encrypting and decrypting data. By creating a KMS grant for the service-linked role with the specified actions, you can allow the service-linked role to use the CMK in Account-2 to launch instances with encrypted volumes. By attaching an IAM policy to the role attached to the EC2 instances with KMS actions and then allowing Account-1 in the KMS key policy, you can also enable cross-account access to the CMK and allow the EC2 instances to use the encrypted volumes. The other options are either incorrect or unnecessary for meeting the requirement.