Which two requirements must be met to register an AWS account with Falcon Cloud Security using a CloudFormation stack? (Choose two)

Question

Options

• AA valid S3 bucket name
• BAn IAM role that grants required integration permissions
• CA CrowdStrike API token
• DA linked cloud account in the Falcon console

• A
  4% (1)
• B
  85% (23)
• C
  11% (3)

Explanation

Registering an AWS account with CrowdStrike Falcon Cloud Security via CloudFormation requires an IAM role (B) because the stack needs programmatic permission to read cloud resources and send findings to Falcon - without it, the integration has no access. A linked cloud account in the Falcon console (D) must exist first because the CloudFormation stack ties the AWS account to a pre-configured Falcon cloud account record; the stack deployment completes that linkage, not creates it from scratch.

Why the distractors are wrong:

• (A) S3 bucket - CloudFormation stacks for Falcon don't require a dedicated S3 bucket as a registration prerequisite; that's not part of the integration handshake.
• (C) CrowdStrike API token - Falcon Cloud Security uses IAM-based trust (cross-account roles), not a standalone API token, for the AWS integration flow.

Memory tip: Think "IAM + Console first." The IAM role is the technical key (permissions), and the linked cloud account is the logical key (the slot in Falcon to plug into). Both keys must exist before the CloudFormation stack can complete registration.

No community discussion yet for this question.