Versions Compared

Old Version 13

changes.mady.by.user Aaron Gabriel

Saved on

compared with

New Version 14

changes.mady.by.user Aaron Gabriel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor


Anchor
Pre-deployment considerations
Pre-deployment considerations
Pre-Deployment Considerations

...


Update Your AWS Permissions

...

Note

According to AWS, "An IAM user is a resource in IAM that has associated credentials and permissions. An IAM user can represent a person or an application that uses its credentials to make AWS requests. This is typically referred to as aservice account."


Option 1: For existing AWS service accounts

...

  1. In the AWS console, in Amazon S3 URL, verify that the displayed link is: https://s3-us-west-2.amazonaws.com/logs.armor.com/guard-duty-forwarding/setup-guard-duty-forwarding.yml
  2. Click Next.
  3. (Optional) In StackSet name, enter a descriptive name for the StackSet.
    • This name must begin with a letter, and can only contain letters, numbers, and hyphens.
  4. (Optional) In Log Retention In Days, specify the number of days to maintain logs.
    • By default, Armor has configured 3 days.
  5. Click Next.
  6. In Deploy stacks in accounts, enter the AWS account number for the AWS service account.
    • This is the same AWS service account number that you previously entered in AMP.
    • You must remove any dashes or hyphens ( - ).
  7. Under Specify regions, under Available regions, click Add all.
  8. Click Next.
  9. Click Next.
  10. At the bottom of the screen, mark the box to accept the terms, and then click Create.
  11. Skip Step 5, and proceed to Step 6.

...

Expand

AWS is in the process of updating the screens in their AWS console. As a result, there are two versions of the AWS CloudFormation screen.

Review the following table to understand your particular view, and then review the appropriate option.

ViewSample Image
Old View

New View


Option 1: Old View

  1. In the AWS console, in the top menu, on the right side, select the desired region.


  2. In Specify an Amazon S3 template URL, verify that the displayed link is: https://s3-us-west-2.amazonaws.com/logs.armor.com/guard-duty-forwarding/setup-guard-duty-forwarding.yml


  3. Click Next.
  4. (Optional) In Stack name, enter a descriptive name for the stack.
    • This name must begin with a letter, and can only contain letters, numbers, and hyphens.
  5. (Optional) In Log Retention In Days, specify the number of days to maintain logs.
  6. Click Next.
  7. (Optional) If required by your organization, under Tags, add your organization's tags to the CloudFormation deployment.
  8. (Optional) If required by your organization, under Permissions, in the drop-down menu, select IAM role ARN, and then in the corresponding field, enter AWSCloudFormationStackSetExecutionRole.


  9. Click Next.
  10. At the bottom of the screen, mark the box to accept the terms, and then click Create.


Option 2: New View

  1. In the AWS console, in the top menu, on the right side, select the desired region for log collection.


  2. In Amazon S3 URL, verify that the displayed link is: https://s3-us-west-2.amazonaws.com/logs.armor.com/guard-duty-forwarding/setup-guard-duty-forwarding.yml


  3. Click Next.
  4. (Optional) In Stack name, enter a descriptive name.
    • This name must begin with a letter, and can only contain letters, numbers, and hyphens.
  5. (Optional) In Number of days AWS GuardDuty Findings will be retained inside of AWS Log Group, specify the number of days to maintain logs.
    • By default, Armor has configured 3 days.
  6. Click Next.
  7. Click Next.
  8. At the bottom of the screen, mark the box to accept the terms, and then click Create stack.

...