GuardDuty legacy actions and parameters - Amazon GuardDuty

GuardDuty legacy actions and parameters

Amazon GuardDuty has deprecated the some of the API actions and parameters but still supports them. The best practice is to use the new API actions and parameters that replace the legacy options. The following table compares the legacy and new actions and parameters.

Legacy actions/parameters

New actions/parameters

Comparison

DisassociateFromMasterAccount

DisassociateFromAdministratorAccount

With the same implementation in both the actions, GuardDuty uses the term Administrator in DisassociateFromAdministratorAccount.

autoEnable parameter in DescribeOrganizationConfiguration and UpdateOrganizationConfiguration

autoEnableOrganizationMembers

With autoEnableOrganizationMembers, the GuardDuty administrator account can audit and enforce GuardDuty for all member accounts to either of the values. Using the APIs, it may take up to 24 hours to update the configuration for all the member accounts. For more information about the possible values of the autoEnableOrganizationMembers field, see autoEnableOrganizationMembers

dataSources parameter in the APIs listed in GuardDuty API changes in March 2023.

features

Starting March 2023, you can configure GuardDuty Malware Protection for EC2 and the new GuardDuty protection plans using features. The protection plans launched prior to March 2023, including Malware Protection for EC2 still support configuration using dataSources. If you use APIs to configure a protection plan, each API request can either include dataSources or features, not both.