@aws-sdk/client-securitylake 3.241.0 → 3.245.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (37) hide show
  1. package/README.md +27 -11
  2. package/dist-cjs/endpoint/ruleset.js +3 -3
  3. package/dist-es/endpoint/ruleset.js +3 -3
  4. package/dist-types/SecurityLake.d.ts +138 -103
  5. package/dist-types/SecurityLakeClient.d.ts +27 -11
  6. package/dist-types/commands/CreateAwsLogSourceCommand.d.ts +12 -12
  7. package/dist-types/commands/CreateCustomLogSourceCommand.d.ts +6 -6
  8. package/dist-types/commands/CreateDatalakeAutoEnableCommand.d.ts +3 -2
  9. package/dist-types/commands/CreateDatalakeCommand.d.ts +15 -12
  10. package/dist-types/commands/CreateDatalakeDelegatedAdminCommand.d.ts +3 -3
  11. package/dist-types/commands/CreateDatalakeExceptionsSubscriptionCommand.d.ts +2 -2
  12. package/dist-types/commands/CreateSubscriberCommand.d.ts +2 -1
  13. package/dist-types/commands/CreateSubscriptionNotificationConfigurationCommand.d.ts +2 -2
  14. package/dist-types/commands/DeleteAwsLogSourceCommand.d.ts +11 -13
  15. package/dist-types/commands/DeleteCustomLogSourceCommand.d.ts +1 -1
  16. package/dist-types/commands/DeleteDatalakeAutoEnableCommand.d.ts +9 -6
  17. package/dist-types/commands/DeleteDatalakeCommand.d.ts +8 -7
  18. package/dist-types/commands/DeleteDatalakeDelegatedAdminCommand.d.ts +3 -1
  19. package/dist-types/commands/DeleteDatalakeExceptionsSubscriptionCommand.d.ts +2 -1
  20. package/dist-types/commands/DeleteSubscriberCommand.d.ts +3 -1
  21. package/dist-types/commands/DeleteSubscriptionNotificationConfigurationCommand.d.ts +2 -2
  22. package/dist-types/commands/GetDatalakeAutoEnableCommand.d.ts +3 -1
  23. package/dist-types/commands/GetDatalakeCommand.d.ts +2 -1
  24. package/dist-types/commands/GetDatalakeExceptionsExpiryCommand.d.ts +3 -2
  25. package/dist-types/commands/GetDatalakeStatusCommand.d.ts +2 -1
  26. package/dist-types/commands/GetSubscriberCommand.d.ts +2 -1
  27. package/dist-types/commands/ListDatalakeExceptionsCommand.d.ts +2 -1
  28. package/dist-types/commands/ListLogSourcesCommand.d.ts +1 -1
  29. package/dist-types/commands/ListSubscribersCommand.d.ts +2 -1
  30. package/dist-types/commands/UpdateDatalakeCommand.d.ts +2 -4
  31. package/dist-types/commands/UpdateDatalakeExceptionsExpiryCommand.d.ts +3 -4
  32. package/dist-types/commands/UpdateDatalakeExceptionsSubscriptionCommand.d.ts +2 -1
  33. package/dist-types/commands/UpdateSubscriberCommand.d.ts +2 -1
  34. package/dist-types/commands/UpdateSubscriptionNotificationConfigurationCommand.d.ts +1 -1
  35. package/dist-types/models/models_0.d.ts +201 -157
  36. package/dist-types/ts3.4/models/models_0.d.ts +1 -1
  37. package/package.json +4 -4
package/README.md CHANGED
@@ -10,18 +10,34 @@
10
10
  AWS SDK for JavaScript SecurityLake Client for Node.js, Browser and React Native.
11
11
 
12
12
  <note>
13
- <p>Amazon Security Lake is in preview release. Your use of the Amazon Security Lake
14
- preview is subject to Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service Terms</a>("Betas and Previews").</p>
13
+ <p>Amazon Security Lake is in preview release. Your use of the Security Lake preview is subject to
14
+ Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service
15
+ Terms</a>("Betas and Previews").</p>
15
16
  </note>
16
- <p>Amazon Security Lake is a fully-managed security data lake service. You can use Security Lake to automatically centralize
17
- security data from cloud, on-premises, and custom sources into a data lake that's stored in your account. Security Lake
18
- helps you analyze security data, so you can get a more complete understanding of your security posture across the entire organization and improve the protection of your workloads, applications, and data.</p>
19
- <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and
20
- you retain ownership over your data.</p>
21
- <p>Security Lake automates the collection of security-related log and event data from integrated
22
- Amazon Web Services. and third-party services and manages the lifecycle of data with customizable
23
- retention and replication settings. Security Lake also converts ingested data into Apache Parquet format and a
24
- standard open-source schema called the Open Cybersecurity Schema Framework (OCSF).</p>
17
+ <p>Amazon Security Lake is a fully managed security data lake service. You can use Security Lake to
18
+ automatically centralize security data from cloud, on-premises, and custom sources into a
19
+ data lake that's stored in your Amazon Web Servicesaccount. Amazon Web Services Organizations
20
+ is an account management service that lets you consolidate multiple Amazon Web Services
21
+ accounts into an organization that you create and centrally manage. With Organizations, you
22
+ can create member accounts and invite existing accounts to join your organization.
23
+ Security Lake helps you analyze security data for a more complete understanding of your
24
+ security posture across the entire organization. It can also help you improve the
25
+ protection of your workloads, applications, and data.</p>
26
+ <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and you
27
+ retain ownership over your data. </p>
28
+ <p>Amazon Security Lake integrates with CloudTrail, a service that provides a record of
29
+ actions taken by a user, role, or an Amazon Web Services service in Security Lake CloudTrail captures API calls for Security Lake as events. The calls captured include calls
30
+ from the Security Lake console and code calls to the Security Lake API operations. If you create a
31
+ trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Security Lake. If you don't configure a trail, you can still
32
+ view the most recent events in the CloudTrail console in Event history. Using the
33
+ information collected by CloudTrail you can determine the request that was made to
34
+ Security Lake, the IP address from which the request was made, who made the request, when it
35
+ was made, and additional details. To learn more about Security Lake information in CloudTrail, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/securitylake-cloudtrail.html">Amazon Security Lake User Guide</a>.</p>
36
+ <p>Security Lake automates the collection of security-related log and event data from
37
+ integrated Amazon Web Services and third-party services. It also helps you manage
38
+ the lifecycle of data with customizable retention and replication settings. Security Lake
39
+ converts ingested data into Apache Parquet format and a standard open-source schema called
40
+ the Open Cybersecurity Schema Framework (OCSF).</p>
25
41
  <p>Other Amazon Web Services and third-party services can subscribe to the data that's stored in Security Lake for
26
42
  incident response and security data analytics.</p>
27
43
 
@@ -1,7 +1,7 @@
1
1
  "use strict";
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.ruleSet = void 0;
4
- const r = "fn", s = "argv", t = "ref";
5
- const a = true, b = false, c = "String", d = "PartitionResult", e = "tree", f = "error", g = "endpoint", h = { "required": true, "default": false, "type": "Boolean" }, i = { [t]: "Endpoint" }, j = { [r]: "booleanEquals", [s]: [{ [t]: "UseFIPS" }, true] }, k = { [r]: "booleanEquals", [s]: [{ [t]: "UseDualStack" }, true] }, l = {}, m = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: d }, "supportsFIPS"] }] }, n = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: d }, "supportsDualStack"] }] }, o = [i], p = [j], q = [k];
6
- const _data = { version: "1.0", parameters: { Region: { required: a, type: c }, UseDualStack: h, UseFIPS: h, Endpoint: { required: b, type: c } }, rules: [{ conditions: [{ [r]: "aws.partition", [s]: [{ [t]: "Region" }], assign: d }], type: e, rules: [{ conditions: [{ [r]: "isSet", [s]: o }, { [r]: "parseURL", [s]: o, assign: "url" }], type: e, rules: [{ conditions: p, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: f }, { type: e, rules: [{ conditions: q, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: f }, { endpoint: { url: i, properties: l, headers: l }, type: g }] }] }, { conditions: [j, k], type: e, rules: [{ conditions: [m, n], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: f }] }, { conditions: p, type: e, rules: [{ conditions: [m], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: f }] }, { conditions: q, type: e, rules: [{ conditions: [n], type: e, rules: [{ endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: f }] }, { endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }] };
4
+ const q = "fn", r = "argv", s = "ref";
5
+ const a = true, b = false, c = "String", d = "PartitionResult", e = "tree", f = "error", g = "endpoint", h = { "required": true, "default": false, "type": "Boolean" }, i = { [s]: "Endpoint" }, j = { [q]: "booleanEquals", [r]: [{ [s]: "UseFIPS" }, true] }, k = { [q]: "booleanEquals", [r]: [{ [s]: "UseDualStack" }, true] }, l = {}, m = { [q]: "booleanEquals", [r]: [true, { [q]: "getAttr", [r]: [{ [s]: d }, "supportsFIPS"] }] }, n = { [q]: "booleanEquals", [r]: [true, { [q]: "getAttr", [r]: [{ [s]: d }, "supportsDualStack"] }] }, o = [j], p = [k];
6
+ const _data = { version: "1.0", parameters: { Region: { required: a, type: c }, UseDualStack: h, UseFIPS: h, Endpoint: { required: b, type: c } }, rules: [{ conditions: [{ [q]: "aws.partition", [r]: [{ [s]: "Region" }], assign: d }], type: e, rules: [{ conditions: [{ [q]: "isSet", [r]: [i] }], type: e, rules: [{ conditions: o, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: f }, { type: e, rules: [{ conditions: p, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: f }, { endpoint: { url: i, properties: l, headers: l }, type: g }] }] }, { conditions: [j, k], type: e, rules: [{ conditions: [m, n], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: f }] }, { conditions: o, type: e, rules: [{ conditions: [m], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: f }] }, { conditions: p, type: e, rules: [{ conditions: [n], type: e, rules: [{ endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: f }] }, { endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }] };
7
7
  exports.ruleSet = _data;
@@ -1,4 +1,4 @@
1
- const r = "fn", s = "argv", t = "ref";
2
- const a = true, b = false, c = "String", d = "PartitionResult", e = "tree", f = "error", g = "endpoint", h = { "required": true, "default": false, "type": "Boolean" }, i = { [t]: "Endpoint" }, j = { [r]: "booleanEquals", [s]: [{ [t]: "UseFIPS" }, true] }, k = { [r]: "booleanEquals", [s]: [{ [t]: "UseDualStack" }, true] }, l = {}, m = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: d }, "supportsFIPS"] }] }, n = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: d }, "supportsDualStack"] }] }, o = [i], p = [j], q = [k];
3
- const _data = { version: "1.0", parameters: { Region: { required: a, type: c }, UseDualStack: h, UseFIPS: h, Endpoint: { required: b, type: c } }, rules: [{ conditions: [{ [r]: "aws.partition", [s]: [{ [t]: "Region" }], assign: d }], type: e, rules: [{ conditions: [{ [r]: "isSet", [s]: o }, { [r]: "parseURL", [s]: o, assign: "url" }], type: e, rules: [{ conditions: p, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: f }, { type: e, rules: [{ conditions: q, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: f }, { endpoint: { url: i, properties: l, headers: l }, type: g }] }] }, { conditions: [j, k], type: e, rules: [{ conditions: [m, n], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: f }] }, { conditions: p, type: e, rules: [{ conditions: [m], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: f }] }, { conditions: q, type: e, rules: [{ conditions: [n], type: e, rules: [{ endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: f }] }, { endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }] };
1
+ const q = "fn", r = "argv", s = "ref";
2
+ const a = true, b = false, c = "String", d = "PartitionResult", e = "tree", f = "error", g = "endpoint", h = { "required": true, "default": false, "type": "Boolean" }, i = { [s]: "Endpoint" }, j = { [q]: "booleanEquals", [r]: [{ [s]: "UseFIPS" }, true] }, k = { [q]: "booleanEquals", [r]: [{ [s]: "UseDualStack" }, true] }, l = {}, m = { [q]: "booleanEquals", [r]: [true, { [q]: "getAttr", [r]: [{ [s]: d }, "supportsFIPS"] }] }, n = { [q]: "booleanEquals", [r]: [true, { [q]: "getAttr", [r]: [{ [s]: d }, "supportsDualStack"] }] }, o = [j], p = [k];
3
+ const _data = { version: "1.0", parameters: { Region: { required: a, type: c }, UseDualStack: h, UseFIPS: h, Endpoint: { required: b, type: c } }, rules: [{ conditions: [{ [q]: "aws.partition", [r]: [{ [s]: "Region" }], assign: d }], type: e, rules: [{ conditions: [{ [q]: "isSet", [r]: [i] }], type: e, rules: [{ conditions: o, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: f }, { type: e, rules: [{ conditions: p, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: f }, { endpoint: { url: i, properties: l, headers: l }, type: g }] }] }, { conditions: [j, k], type: e, rules: [{ conditions: [m, n], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: f }] }, { conditions: o, type: e, rules: [{ conditions: [m], type: e, rules: [{ endpoint: { url: "https://securitylake-fips.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: f }] }, { conditions: p, type: e, rules: [{ conditions: [n], type: e, rules: [{ endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: l, headers: l }, type: g }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: f }] }, { endpoint: { url: "https://securitylake.{Region}.{PartitionResult#dnsSuffix}", properties: l, headers: l }, type: g }] }] };
4
4
  export const ruleSet = _data;
@@ -32,121 +32,140 @@ import { UpdateSubscriptionNotificationConfigurationCommandInput, UpdateSubscrip
32
32
  import { SecurityLakeClient } from "./SecurityLakeClient";
33
33
  /**
34
34
  * <note>
35
- * <p>Amazon Security Lake is in preview release. Your use of the Amazon Security Lake
36
- * preview is subject to Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service Terms</a>("Betas and Previews").</p>
35
+ * <p>Amazon Security Lake is in preview release. Your use of the Security Lake preview is subject to
36
+ * Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service
37
+ * Terms</a>("Betas and Previews").</p>
37
38
  * </note>
38
- * <p>Amazon Security Lake is a fully-managed security data lake service. You can use Security Lake to automatically centralize
39
- * security data from cloud, on-premises, and custom sources into a data lake that's stored in your account. Security Lake
40
- * helps you analyze security data, so you can get a more complete understanding of your security posture across the entire organization and improve the protection of your workloads, applications, and data.</p>
41
- * <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and
42
- * you retain ownership over your data.</p>
43
- * <p>Security Lake automates the collection of security-related log and event data from integrated
44
- * Amazon Web Services. and third-party services and manages the lifecycle of data with customizable
45
- * retention and replication settings. Security Lake also converts ingested data into Apache Parquet format and a
46
- * standard open-source schema called the Open Cybersecurity Schema Framework (OCSF).</p>
39
+ * <p>Amazon Security Lake is a fully managed security data lake service. You can use Security Lake to
40
+ * automatically centralize security data from cloud, on-premises, and custom sources into a
41
+ * data lake that's stored in your Amazon Web Servicesaccount. Amazon Web Services Organizations
42
+ * is an account management service that lets you consolidate multiple Amazon Web Services
43
+ * accounts into an organization that you create and centrally manage. With Organizations, you
44
+ * can create member accounts and invite existing accounts to join your organization.
45
+ * Security Lake helps you analyze security data for a more complete understanding of your
46
+ * security posture across the entire organization. It can also help you improve the
47
+ * protection of your workloads, applications, and data.</p>
48
+ * <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and you
49
+ * retain ownership over your data. </p>
50
+ * <p>Amazon Security Lake integrates with CloudTrail, a service that provides a record of
51
+ * actions taken by a user, role, or an Amazon Web Services service in Security Lake CloudTrail captures API calls for Security Lake as events. The calls captured include calls
52
+ * from the Security Lake console and code calls to the Security Lake API operations. If you create a
53
+ * trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Security Lake. If you don't configure a trail, you can still
54
+ * view the most recent events in the CloudTrail console in Event history. Using the
55
+ * information collected by CloudTrail you can determine the request that was made to
56
+ * Security Lake, the IP address from which the request was made, who made the request, when it
57
+ * was made, and additional details. To learn more about Security Lake information in CloudTrail, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/securitylake-cloudtrail.html">Amazon Security Lake User Guide</a>.</p>
58
+ * <p>Security Lake automates the collection of security-related log and event data from
59
+ * integrated Amazon Web Services and third-party services. It also helps you manage
60
+ * the lifecycle of data with customizable retention and replication settings. Security Lake
61
+ * converts ingested data into Apache Parquet format and a standard open-source schema called
62
+ * the Open Cybersecurity Schema Framework (OCSF).</p>
47
63
  * <p>Other Amazon Web Services and third-party services can subscribe to the data that's stored in Security Lake for
48
64
  * incident response and security data analytics.</p>
49
65
  */
50
66
  export declare class SecurityLake extends SecurityLakeClient {
51
67
  /**
52
- * <p>Adds a natively-supported Amazon Web Services service as a Security Lake source. Enables
53
- * source types for member accounts in required Regions, based on specified parameters. You
54
- * can choose any source type in any Region for accounts that are either part of a trusted
55
- * organization or standalone accounts. At least one of the three dimensions is a mandatory
56
- * input to this API. However, any combination of the three dimensions can be supplied to this
57
- * API. </p>
58
- * <p>By default, dimension refers to the entire set. When you don't provide a dimension,
68
+ * <p>Adds a natively supported Amazon Web Service as an Amazon Security Lake source. Enables
69
+ * source types for member accounts in required Amazon Web Services Regions, based on the
70
+ * parameters you specify. You can choose any source type in any Region for either accounts
71
+ * that are part of a trusted organization or standalone accounts. At least one of the three
72
+ * dimensions is a mandatory input to this API. However, you can supply any combination of the
73
+ * three dimensions to this API. </p>
74
+ * <p>By default, a dimension refers to the entire set. When you don't provide a dimension,
59
75
  * Security Lake assumes that the missing dimension refers to the entire set. This is overridden
60
- * when you supply any one of the inputs. For instance, when members is not specified, the API
61
- * disables all Security Lake member accounts for sources. Similarly, when Regions are not
62
- * specified, Security Lake is disabled for all the Regions where Security Lake is available as a
76
+ * when you supply any one of the inputs. For instance, when you do not specify members, the
77
+ * API enables all Security Lake member accounts for all sources. Similarly, when you do not
78
+ * specify Regions, Security Lake is enabled for all the Regions where Security Lake is available as a
63
79
  * service.</p>
64
- * <p>You can use this API only to enable a natively-supported Amazon Web Services services as
65
- * a source. Use <code>CreateCustomLogSource</code> to enable data collection from a custom
80
+ * <p>You can use this API only to enable natively supported Amazon Web Services as a
81
+ * source. Use <code>CreateCustomLogSource</code> to enable data collection from a custom
66
82
  * source. </p>
67
83
  */
68
84
  createAwsLogSource(args: CreateAwsLogSourceCommandInput, options?: __HttpHandlerOptions): Promise<CreateAwsLogSourceCommandOutput>;
69
85
  createAwsLogSource(args: CreateAwsLogSourceCommandInput, cb: (err: any, data?: CreateAwsLogSourceCommandOutput) => void): void;
70
86
  createAwsLogSource(args: CreateAwsLogSourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateAwsLogSourceCommandOutput) => void): void;
71
87
  /**
72
- * <p>Adds a third-party custom source in Amazon Security Lake, from the Region where you want to
73
- * create a custom source. Security Lake can collect logs and events from third-party custom
74
- * sources. After creating the appropriate API roles, use this API to add a custom source name
75
- * in Security Lake. This operation creates a partition in the Security Lake S3 bucket as the target
76
- * location for log files from the custom source, an associated Glue table, and
77
- * an Glue crawler.</p>
88
+ * <p>Adds a third-party custom source in Amazon Security Lake, from the Amazon Web Services Region
89
+ * where you want to create a custom source. Security Lake can collect logs and events from
90
+ * third-party custom sources. After creating the appropriate IAM role to
91
+ * invoke Glue crawler, use this API to add a custom source name in Security Lake. This
92
+ * operation creates a partition in the Amazon S3 bucket for Security Lake as the target
93
+ * location for log files from the custom source in addition to an associated Glue table and an Glue crawler.</p>
78
94
  */
79
95
  createCustomLogSource(args: CreateCustomLogSourceCommandInput, options?: __HttpHandlerOptions): Promise<CreateCustomLogSourceCommandOutput>;
80
96
  createCustomLogSource(args: CreateCustomLogSourceCommandInput, cb: (err: any, data?: CreateCustomLogSourceCommandOutput) => void): void;
81
97
  createCustomLogSource(args: CreateCustomLogSourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateCustomLogSourceCommandOutput) => void): void;
82
98
  /**
83
- * <p>Initializes an Amazon Security Lake instance with the provided (or default) configuration. You can enable Security Lake in Regions with customized settings in advance before enabling log collection in Regions. You can either use the <code>enableAll</code> parameter to
84
- * specify all Regions or you can specify the Regions you want to enable Security Lake using the
85
- * <code>Regions</code> parameter and configure these Regions using the
86
- * <code>configurations</code> parameter. When the <code>CreateDataLake</code> API is called
87
- * multiple times, if that Region is already enabled, it will update the Region if
88
- * configuration for that Region is provided. If that Region is a new Region, it will be set
89
- * up with the customized configurations if it is specified. </p>
99
+ * <p>Initializes an Amazon Security Lake instance with the provided (or default) configuration. You
100
+ * can enable Security Lake in Amazon Web Services Regions with customized settings before enabling
101
+ * log collection in Regions. You can either use the <code>enableAll</code> parameter to
102
+ * specify all Regions or specify the Regions where you want to enable Security Lake. To specify
103
+ * particular Regions, use the <code>Regions</code> parameter and then configure these Regions
104
+ * using the <code>configurations</code> parameter. If you have already enabled Security Lake in a
105
+ * Region when you call this command, the command will update the Region if you provide new
106
+ * configuration parameters. If you have not already enabled Security Lake in the Region when you
107
+ * call this API, it will set up the data lake in the Region with the specified
108
+ * configurations.</p>
90
109
  * <p>When you enable Security Lake, it starts ingesting security data after the
91
- * <code>CreateAwsLogSource</code> call. This includes ingesting security
92
- * data from sources, storing data, and making data accessible to subscribers. Security Lake also
93
- * enables all the existing settings and resources that it stores or maintains for your
94
- * account in the current Region, including security log and event data. For more information,
95
- * see the Amazon Security Lake User Guide.</p>
110
+ * <code>CreateAwsLogSource</code> call. This includes ingesting security data from
111
+ * sources, storing data, and making data accessible to subscribers. Security Lake also enables
112
+ * all the existing settings and resources that it stores or maintains for your Amazon Web Services account in the current Region, including security log and event data. For
113
+ * more information, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/what-is-security-lake.html">Amazon Security Lake User
114
+ * Guide</a>.</p>
96
115
  */
97
116
  createDatalake(args: CreateDatalakeCommandInput, options?: __HttpHandlerOptions): Promise<CreateDatalakeCommandOutput>;
98
117
  createDatalake(args: CreateDatalakeCommandInput, cb: (err: any, data?: CreateDatalakeCommandOutput) => void): void;
99
118
  createDatalake(args: CreateDatalakeCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateDatalakeCommandOutput) => void): void;
100
119
  /**
101
- * <p>Automatically enable Security Lake in the specified Regions to begin ingesting security
102
- * data. When you choose to enable organization accounts automatically, then Security Lake begins to enable new accounts as member accounts as they are added to the organization. Security Lake does not enable existing organization accounts that are not yet enabled.</p>
120
+ * <p>Automatically enables Amazon Security Lake for new member accounts in your organization.
121
+ * Security Lake is not automatically enabled for any existing member accounts in your
122
+ * organization.</p>
103
123
  */
104
124
  createDatalakeAutoEnable(args: CreateDatalakeAutoEnableCommandInput, options?: __HttpHandlerOptions): Promise<CreateDatalakeAutoEnableCommandOutput>;
105
125
  createDatalakeAutoEnable(args: CreateDatalakeAutoEnableCommandInput, cb: (err: any, data?: CreateDatalakeAutoEnableCommandOutput) => void): void;
106
126
  createDatalakeAutoEnable(args: CreateDatalakeAutoEnableCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateDatalakeAutoEnableCommandOutput) => void): void;
107
127
  /**
108
- * <p>Designates the Security Lake administrator account for the organization. This API can only
109
- * be called by the organization management account. The organization management account
110
- * cannot be the delegated administrator account.</p>
128
+ * <p>Designates the Amazon Security Lake delegated administrator account for the organization. This
129
+ * API can only be called by the organization management account. The organization management
130
+ * account cannot be the delegated administrator account.</p>
111
131
  */
112
132
  createDatalakeDelegatedAdmin(args: CreateDatalakeDelegatedAdminCommandInput, options?: __HttpHandlerOptions): Promise<CreateDatalakeDelegatedAdminCommandOutput>;
113
133
  createDatalakeDelegatedAdmin(args: CreateDatalakeDelegatedAdminCommandInput, cb: (err: any, data?: CreateDatalakeDelegatedAdminCommandOutput) => void): void;
114
134
  createDatalakeDelegatedAdmin(args: CreateDatalakeDelegatedAdminCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateDatalakeDelegatedAdminCommandOutput) => void): void;
115
135
  /**
116
- * <p>Creates the specified notification subscription in Security Lake. Creates the specified
117
- * subscription notifications in the specified organization. </p>
136
+ * <p>Creates the specified notification subscription in Amazon Security Lake for the organization
137
+ * you specify.</p>
118
138
  */
119
139
  createDatalakeExceptionsSubscription(args: CreateDatalakeExceptionsSubscriptionCommandInput, options?: __HttpHandlerOptions): Promise<CreateDatalakeExceptionsSubscriptionCommandOutput>;
120
140
  createDatalakeExceptionsSubscription(args: CreateDatalakeExceptionsSubscriptionCommandInput, cb: (err: any, data?: CreateDatalakeExceptionsSubscriptionCommandOutput) => void): void;
121
141
  createDatalakeExceptionsSubscription(args: CreateDatalakeExceptionsSubscriptionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateDatalakeExceptionsSubscriptionCommandOutput) => void): void;
122
142
  /**
123
- * <p>Creates a subscription permission for accounts that are already enabled in Security Lake.</p>
143
+ * <p>Creates a subscription permission for accounts that are already enabled in
144
+ * Amazon Security Lake. You can create a subscriber with access to data in the current Amazon Web Services Region.</p>
124
145
  */
125
146
  createSubscriber(args: CreateSubscriberCommandInput, options?: __HttpHandlerOptions): Promise<CreateSubscriberCommandOutput>;
126
147
  createSubscriber(args: CreateSubscriberCommandInput, cb: (err: any, data?: CreateSubscriberCommandOutput) => void): void;
127
148
  createSubscriber(args: CreateSubscriberCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateSubscriberCommandOutput) => void): void;
128
149
  /**
129
- * <p>Creates the specified notification subscription in Security Lake. Creates the specified
130
- * subscription notifications from the specified organization. </p>
150
+ * <p>Notifies the subscriber when new data is written to the data lake for the sources that
151
+ * the subscriber consumes in Security Lake.</p>
131
152
  */
132
153
  createSubscriptionNotificationConfiguration(args: CreateSubscriptionNotificationConfigurationCommandInput, options?: __HttpHandlerOptions): Promise<CreateSubscriptionNotificationConfigurationCommandOutput>;
133
154
  createSubscriptionNotificationConfiguration(args: CreateSubscriptionNotificationConfigurationCommandInput, cb: (err: any, data?: CreateSubscriptionNotificationConfigurationCommandOutput) => void): void;
134
155
  createSubscriptionNotificationConfiguration(args: CreateSubscriptionNotificationConfigurationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateSubscriptionNotificationConfigurationCommandOutput) => void): void;
135
156
  /**
136
- * <p>Removes a natively-supported Amazon Web Services service as a Amazon Security Lake source. When you remove the
137
- * source, Security Lake stops collecting data from that source, and subscribers can no
138
- * longer consume new data from the source. Subscribers can still consume data that Amazon
157
+ * <p>Removes a natively supported Amazon Web Service as an Amazon Security Lake source. When
158
+ * you remove the source, Security Lake stops collecting data from that source, and subscribers
159
+ * can no longer consume new data from the source. Subscribers can still consume data that
139
160
  * Security Lake collected from the source before disablement.</p>
140
- * <p>You can choose any source type in any Region for accounts that are either part of a
141
- * trusted organization or standalone accounts. At least one of the three dimensions is a
142
- * mandatory input to this API. However, any combination of the three dimensions can be
143
- * supplied to this API. </p>
144
- * <p>By default, dimension refers to the entire set. This is overridden when you supply any
145
- * one of the inputs. For instance, when members is not specified, the API disables all
146
- * Security Lake member accounts for sources. Similarly, when Regions are not specified, Security Lake
147
- * is disabled for all the Regions where Security Lake is available as a service.</p>
148
- * <p>You can use this API to remove a natively-supported Amazon Web Services service as a source. Use
149
- * <code>DeregisterCustomData</code> to remove a custom source.</p>
161
+ * <p>You can choose any source type in any Amazon Web Services Region for either accounts that
162
+ * are part of a trusted organization or standalone accounts. At least one of the three
163
+ * dimensions is a mandatory input to this API. However, you can supply any combination of the
164
+ * three dimensions to this API. </p>
165
+ * <p>By default, a dimension refers to the entire set. This is overridden when you supply any
166
+ * one of the inputs. For instance, when you do not specify members, the API disables all
167
+ * Security Lake member accounts for sources. Similarly, when you do not specify Regions,
168
+ * Security Lake is disabled for all the Regions where Security Lake is available as a service.</p>
150
169
  * <p>When you don't provide a dimension, Security Lake assumes that the missing dimension refers
151
170
  * to the entire set. For example, if you don't provide specific accounts, the API applies to
152
171
  * the entire set of accounts in your organization.</p>
@@ -155,74 +174,87 @@ export declare class SecurityLake extends SecurityLakeClient {
155
174
  deleteAwsLogSource(args: DeleteAwsLogSourceCommandInput, cb: (err: any, data?: DeleteAwsLogSourceCommandOutput) => void): void;
156
175
  deleteAwsLogSource(args: DeleteAwsLogSourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteAwsLogSourceCommandOutput) => void): void;
157
176
  /**
158
- * <p>Removes a custom log source from Security Lake.</p>
177
+ * <p>Removes a custom log source from Amazon Security Lake.</p>
159
178
  */
160
179
  deleteCustomLogSource(args: DeleteCustomLogSourceCommandInput, options?: __HttpHandlerOptions): Promise<DeleteCustomLogSourceCommandOutput>;
161
180
  deleteCustomLogSource(args: DeleteCustomLogSourceCommandInput, cb: (err: any, data?: DeleteCustomLogSourceCommandOutput) => void): void;
162
181
  deleteCustomLogSource(args: DeleteCustomLogSourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteCustomLogSourceCommandOutput) => void): void;
163
182
  /**
164
- * <p>When you delete Amazon Security Lake from your account, Security Lake is disabled in all Regions.
165
- * Also, this API automatically performs the off-boarding steps to off-board the account from
166
- * Security Lake . This includes ingesting security data from sources, storing data, and making
167
- * data accessible to subscribers. Security Lake also deletes all the existing settings and
168
- * resources that it stores or maintains for your account in the current Region, including
169
- * security log and event data. <code>DeleteDatalake</code> does not delete the S3 bucket
170
- * which is owned by the Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.</p>
183
+ * <p>When you delete Amazon Security Lake from your account, Security Lake is disabled in all Amazon Web Services Regions. Also, this API automatically takes steps to remove the account from
184
+ * Security Lake . </p>
185
+ * <p>This operation disables security data collection from sources, deletes data stored, and
186
+ * stops making data accessible to subscribers. Security Lake also deletes all the existing
187
+ * settings and resources that it stores or maintains for your Amazon Web Services account in
188
+ * the current Region, including security log and event data. The <code>DeleteDatalake</code>
189
+ * operation does not delete the Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/disable-security-lake.html">Amazon Security Lake User
190
+ * Guide</a>.</p>
171
191
  */
172
192
  deleteDatalake(args: DeleteDatalakeCommandInput, options?: __HttpHandlerOptions): Promise<DeleteDatalakeCommandOutput>;
173
193
  deleteDatalake(args: DeleteDatalakeCommandInput, cb: (err: any, data?: DeleteDatalakeCommandOutput) => void): void;
174
194
  deleteDatalake(args: DeleteDatalakeCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteDatalakeCommandOutput) => void): void;
175
195
  /**
176
- * <p>Automatically delete Security Lake in the specified Regions to stop ingesting security data. When you delete Amazon Security Lake from your account, Security Lake is disabled in all Regions. Also, this API
177
- * automatically performs the off-boarding steps to off-board the account from Security Lake .
178
- * This includes ingesting security data from sources, storing data, and making data
179
- * accessible to subscribers. Security Lake also deletes all the existing settings and resources that
180
- * it stores or maintains for your account in the current Region, including security log and
181
- * event data. For more information, see the Amazon Security Lake User Guide. </p>
196
+ * <p>Automatically deletes Amazon Security Lake to stop collecting security data. When you delete
197
+ * Amazon Security Lake from your account, Security Lake is disabled in all Regions. Also, this API
198
+ * automatically takes steps to remove the account from Security Lake . </p>
199
+ * <p>This operation disables security data collection from sources, deletes data stored, and
200
+ * stops making data accessible to subscribers. Security Lake also deletes all the existing
201
+ * settings and resources that it stores or maintains for your Amazon Web Services account in
202
+ * the current Region, including security log and event data. The <code>DeleteDatalake</code>
203
+ * operation does not delete the Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/disable-security-lake.html">Amazon Security Lake User
204
+ * Guide</a>.</p>
182
205
  */
183
206
  deleteDatalakeAutoEnable(args: DeleteDatalakeAutoEnableCommandInput, options?: __HttpHandlerOptions): Promise<DeleteDatalakeAutoEnableCommandOutput>;
184
207
  deleteDatalakeAutoEnable(args: DeleteDatalakeAutoEnableCommandInput, cb: (err: any, data?: DeleteDatalakeAutoEnableCommandOutput) => void): void;
185
208
  deleteDatalakeAutoEnable(args: DeleteDatalakeAutoEnableCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteDatalakeAutoEnableCommandOutput) => void): void;
186
209
  /**
187
- * <p>Deletes the Security Lake administrator account for the organization. This API can only be called by the organization management account. The organization management account cannot be the delegated administrator account.</p>
210
+ * <p>Deletes the Amazon Security Lake delegated administrator account for the organization. This API
211
+ * can only be called by the organization management account. The organization management
212
+ * account cannot be the delegated administrator account.</p>
188
213
  */
189
214
  deleteDatalakeDelegatedAdmin(args: DeleteDatalakeDelegatedAdminCommandInput, options?: __HttpHandlerOptions): Promise<DeleteDatalakeDelegatedAdminCommandOutput>;
190
215
  deleteDatalakeDelegatedAdmin(args: DeleteDatalakeDelegatedAdminCommandInput, cb: (err: any, data?: DeleteDatalakeDelegatedAdminCommandOutput) => void): void;
191
216
  deleteDatalakeDelegatedAdmin(args: DeleteDatalakeDelegatedAdminCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteDatalakeDelegatedAdminCommandOutput) => void): void;
192
217
  /**
193
- * <p>Deletes the specified notification subscription in Security Lake. Deletes the specified subscription notifications in the specified organization.</p>
218
+ * <p>Deletes the specified notification subscription in Amazon Security Lake for the organization
219
+ * you specify.</p>
194
220
  */
195
221
  deleteDatalakeExceptionsSubscription(args: DeleteDatalakeExceptionsSubscriptionCommandInput, options?: __HttpHandlerOptions): Promise<DeleteDatalakeExceptionsSubscriptionCommandOutput>;
196
222
  deleteDatalakeExceptionsSubscription(args: DeleteDatalakeExceptionsSubscriptionCommandInput, cb: (err: any, data?: DeleteDatalakeExceptionsSubscriptionCommandOutput) => void): void;
197
223
  deleteDatalakeExceptionsSubscription(args: DeleteDatalakeExceptionsSubscriptionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteDatalakeExceptionsSubscriptionCommandOutput) => void): void;
198
224
  /**
199
- * <p>Deletes the specified subscription permissions to Security Lake. Deletes the specified subscription permissions from the specified organization. </p>
225
+ * <p>Deletes the subscription permission for accounts that are already enabled in
226
+ * Amazon Security Lake. You can delete a subscriber and remove access to data in the current Amazon Web Services
227
+ * Region.</p>
200
228
  */
201
229
  deleteSubscriber(args: DeleteSubscriberCommandInput, options?: __HttpHandlerOptions): Promise<DeleteSubscriberCommandOutput>;
202
230
  deleteSubscriber(args: DeleteSubscriberCommandInput, cb: (err: any, data?: DeleteSubscriberCommandOutput) => void): void;
203
231
  deleteSubscriber(args: DeleteSubscriberCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteSubscriberCommandOutput) => void): void;
204
232
  /**
205
- * <p>Deletes the specified notification subscription in Security Lake. Deletes the specified
206
- * subscription notifications from the specified organization. </p>
233
+ * <p>Deletes the specified notification subscription in Amazon Security Lake for the organization
234
+ * you specify.</p>
207
235
  */
208
236
  deleteSubscriptionNotificationConfiguration(args: DeleteSubscriptionNotificationConfigurationCommandInput, options?: __HttpHandlerOptions): Promise<DeleteSubscriptionNotificationConfigurationCommandOutput>;
209
237
  deleteSubscriptionNotificationConfiguration(args: DeleteSubscriptionNotificationConfigurationCommandInput, cb: (err: any, data?: DeleteSubscriptionNotificationConfigurationCommandOutput) => void): void;
210
238
  deleteSubscriptionNotificationConfiguration(args: DeleteSubscriptionNotificationConfigurationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteSubscriptionNotificationConfigurationCommandOutput) => void): void;
211
239
  /**
212
- * <p>Retrieve the Security Lake configuration object for the specified account ID. This API does not take input parameters. </p>
240
+ * <p>Retrieves the Amazon Security Lake configuration object for the specified Amazon Web Services account ID. You can use the <code>GetDatalake</code> API to know whether
241
+ * Security Lake is enabled for the current Region. This API does not take input parameters. </p>
213
242
  */
214
243
  getDatalake(args: GetDatalakeCommandInput, options?: __HttpHandlerOptions): Promise<GetDatalakeCommandOutput>;
215
244
  getDatalake(args: GetDatalakeCommandInput, cb: (err: any, data?: GetDatalakeCommandOutput) => void): void;
216
245
  getDatalake(args: GetDatalakeCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetDatalakeCommandOutput) => void): void;
217
246
  /**
218
- * <p>Retrieves the configuration that will be automatically set up for accounts added to the organization after the organization has on boarded to Amazon Security Lake. This API does not take input parameters.</p>
247
+ * <p>Retrieves the configuration that will be automatically set up for accounts added to the
248
+ * organization after the organization has onboarded to Amazon Security Lake. This API does not take
249
+ * input parameters.</p>
219
250
  */
220
251
  getDatalakeAutoEnable(args: GetDatalakeAutoEnableCommandInput, options?: __HttpHandlerOptions): Promise<GetDatalakeAutoEnableCommandOutput>;
221
252
  getDatalakeAutoEnable(args: GetDatalakeAutoEnableCommandInput, cb: (err: any, data?: GetDatalakeAutoEnableCommandOutput) => void): void;
222
253
  getDatalakeAutoEnable(args: GetDatalakeAutoEnableCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetDatalakeAutoEnableCommandOutput) => void): void;
223
254
  /**
224
- * <p>Retrieves the expiration period and time-to-live (TTL) for which the exception message will remain. Exceptions are stored by default, for a 2 week period of time from when a record was
225
- * created in Security Lake. This API does not take input parameters. This API does not take input parameters.</p>
255
+ * <p>Retrieves the expiration period and time-to-live (TTL) for which the exception message
256
+ * will remain. Exceptions are stored by default, for 2 weeks from when a record was created
257
+ * in Amazon Security Lake. This API does not take input parameters.</p>
226
258
  */
227
259
  getDatalakeExceptionsExpiry(args: GetDatalakeExceptionsExpiryCommandInput, options?: __HttpHandlerOptions): Promise<GetDatalakeExceptionsExpiryCommandOutput>;
228
260
  getDatalakeExceptionsExpiry(args: GetDatalakeExceptionsExpiryCommandInput, cb: (err: any, data?: GetDatalakeExceptionsExpiryCommandOutput) => void): void;
@@ -234,67 +266,70 @@ export declare class SecurityLake extends SecurityLakeClient {
234
266
  getDatalakeExceptionsSubscription(args: GetDatalakeExceptionsSubscriptionCommandInput, cb: (err: any, data?: GetDatalakeExceptionsSubscriptionCommandOutput) => void): void;
235
267
  getDatalakeExceptionsSubscription(args: GetDatalakeExceptionsSubscriptionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetDatalakeExceptionsSubscriptionCommandOutput) => void): void;
236
268
  /**
237
- * <p>Retrieve the Security Lake configuration object for the specified account ID. This API does not take input parameters. </p>
269
+ * <p>Retrieves a snapshot of the current Region, including whether Amazon Security Lake is enabled
270
+ * for those accounts and which sources Security Lake is collecting data from. </p>
238
271
  */
239
272
  getDatalakeStatus(args: GetDatalakeStatusCommandInput, options?: __HttpHandlerOptions): Promise<GetDatalakeStatusCommandOutput>;
240
273
  getDatalakeStatus(args: GetDatalakeStatusCommandInput, cb: (err: any, data?: GetDatalakeStatusCommandOutput) => void): void;
241
274
  getDatalakeStatus(args: GetDatalakeStatusCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetDatalakeStatusCommandOutput) => void): void;
242
275
  /**
243
- * <p>Retrieves subscription information for the specified subscription ID.</p>
276
+ * <p>Retrieves the subscription information for the specified subscription ID. You can get
277
+ * information about a specific subscriber.</p>
244
278
  */
245
279
  getSubscriber(args: GetSubscriberCommandInput, options?: __HttpHandlerOptions): Promise<GetSubscriberCommandOutput>;
246
280
  getSubscriber(args: GetSubscriberCommandInput, cb: (err: any, data?: GetSubscriberCommandOutput) => void): void;
247
281
  getSubscriber(args: GetSubscriberCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetSubscriberCommandOutput) => void): void;
248
282
  /**
249
- * <p>List the Amazon Security Lake exceptions that you can use to find the source of problems and fix them.</p>
283
+ * <p>Lists the Amazon Security Lake exceptions that you can use to find the source of problems and
284
+ * fix them.</p>
250
285
  */
251
286
  listDatalakeExceptions(args: ListDatalakeExceptionsCommandInput, options?: __HttpHandlerOptions): Promise<ListDatalakeExceptionsCommandOutput>;
252
287
  listDatalakeExceptions(args: ListDatalakeExceptionsCommandInput, cb: (err: any, data?: ListDatalakeExceptionsCommandOutput) => void): void;
253
288
  listDatalakeExceptions(args: ListDatalakeExceptionsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListDatalakeExceptionsCommandOutput) => void): void;
254
289
  /**
255
- * <p>Lists the log sources in the current region.</p>
290
+ * <p>Retrieves the log sources in the current Amazon Web Services Region. </p>
256
291
  */
257
292
  listLogSources(args: ListLogSourcesCommandInput, options?: __HttpHandlerOptions): Promise<ListLogSourcesCommandOutput>;
258
293
  listLogSources(args: ListLogSourcesCommandInput, cb: (err: any, data?: ListLogSourcesCommandOutput) => void): void;
259
294
  listLogSources(args: ListLogSourcesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListLogSourcesCommandOutput) => void): void;
260
295
  /**
261
- * <p>List all subscribers for the specific Security Lake account ID.</p>
296
+ * <p>List all subscribers for the specific Amazon Security Lake account ID. You can retrieve a list
297
+ * of subscriptions associated with a specific organization or Amazon Web Services account.</p>
262
298
  */
263
299
  listSubscribers(args: ListSubscribersCommandInput, options?: __HttpHandlerOptions): Promise<ListSubscribersCommandOutput>;
264
300
  listSubscribers(args: ListSubscribersCommandInput, cb: (err: any, data?: ListSubscribersCommandOutput) => void): void;
265
301
  listSubscribers(args: ListSubscribersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListSubscribersCommandOutput) => void): void;
266
302
  /**
267
- * <p>Amazon Security Lake allows you to specify where to store your security data and for how long.
268
- * You can specify a rollup Region to consolidate data from multiple regions. </p>
269
- * <p>You can update the properties of a Region or source. Input can either be directly
270
- * specified to the API. </p>
303
+ * <p>Specifies where to store your security data and for how long. You can add a rollup
304
+ * Region to consolidate data from multiple Amazon Web Services Regions. </p>
271
305
  */
272
306
  updateDatalake(args: UpdateDatalakeCommandInput, options?: __HttpHandlerOptions): Promise<UpdateDatalakeCommandOutput>;
273
307
  updateDatalake(args: UpdateDatalakeCommandInput, cb: (err: any, data?: UpdateDatalakeCommandOutput) => void): void;
274
308
  updateDatalake(args: UpdateDatalakeCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateDatalakeCommandOutput) => void): void;
275
309
  /**
276
- * <p>Update the expiration period for the exception message to your preferred time, and control
277
- * the time-to-live (TTL) for the exception message to remain.
278
- * Exceptions are stored by default, for a 2 week period of time from when a record was
279
- * created in Security Lake. </p>
310
+ * <p>Update the expiration period for the exception message to your preferred time, and
311
+ * control the time-to-live (TTL) for the exception message to remain. Exceptions are stored
312
+ * by default for 2 weeks from when a record was created in Amazon Security Lake. </p>
280
313
  */
281
314
  updateDatalakeExceptionsExpiry(args: UpdateDatalakeExceptionsExpiryCommandInput, options?: __HttpHandlerOptions): Promise<UpdateDatalakeExceptionsExpiryCommandOutput>;
282
315
  updateDatalakeExceptionsExpiry(args: UpdateDatalakeExceptionsExpiryCommandInput, cb: (err: any, data?: UpdateDatalakeExceptionsExpiryCommandOutput) => void): void;
283
316
  updateDatalakeExceptionsExpiry(args: UpdateDatalakeExceptionsExpiryCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateDatalakeExceptionsExpiryCommandOutput) => void): void;
284
317
  /**
285
- * <p>Update the subscription notification for exception notification.</p>
318
+ * <p>Updates the specified notification subscription in Amazon Security Lake for the organization
319
+ * you specify.</p>
286
320
  */
287
321
  updateDatalakeExceptionsSubscription(args: UpdateDatalakeExceptionsSubscriptionCommandInput, options?: __HttpHandlerOptions): Promise<UpdateDatalakeExceptionsSubscriptionCommandOutput>;
288
322
  updateDatalakeExceptionsSubscription(args: UpdateDatalakeExceptionsSubscriptionCommandInput, cb: (err: any, data?: UpdateDatalakeExceptionsSubscriptionCommandOutput) => void): void;
289
323
  updateDatalakeExceptionsSubscription(args: UpdateDatalakeExceptionsSubscriptionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateDatalakeExceptionsSubscriptionCommandOutput) => void): void;
290
324
  /**
291
- * <p>Update the subscription permission for the given Security Lake account ID.</p>
325
+ * <p>Updates an existing subscription for the given Amazon Security Lake account ID. You can update
326
+ * a subscriber by changing the sources that the subscriber consumes data from. </p>
292
327
  */
293
328
  updateSubscriber(args: UpdateSubscriberCommandInput, options?: __HttpHandlerOptions): Promise<UpdateSubscriberCommandOutput>;
294
329
  updateSubscriber(args: UpdateSubscriberCommandInput, cb: (err: any, data?: UpdateSubscriberCommandOutput) => void): void;
295
330
  updateSubscriber(args: UpdateSubscriberCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateSubscriberCommandOutput) => void): void;
296
331
  /**
297
- * <p>Create a new subscription notification or add the existing subscription notification
332
+ * <p>Creates a new subscription notification or adds the existing subscription notification
298
333
  * setting for the specified subscription ID.</p>
299
334
  */
300
335
  updateSubscriptionNotificationConfiguration(args: UpdateSubscriptionNotificationConfigurationCommandInput, options?: __HttpHandlerOptions): Promise<UpdateSubscriptionNotificationConfigurationCommandOutput>;
@@ -154,18 +154,34 @@ export interface SecurityLakeClientResolvedConfig extends SecurityLakeClientReso
154
154
  }
155
155
  /**
156
156
  * <note>
157
- * <p>Amazon Security Lake is in preview release. Your use of the Amazon Security Lake
158
- * preview is subject to Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service Terms</a>("Betas and Previews").</p>
157
+ * <p>Amazon Security Lake is in preview release. Your use of the Security Lake preview is subject to
158
+ * Section 2 of the <a href="http://aws.amazon.com/service-terms/">Amazon Web Services Service
159
+ * Terms</a>("Betas and Previews").</p>
159
160
  * </note>
160
- * <p>Amazon Security Lake is a fully-managed security data lake service. You can use Security Lake to automatically centralize
161
- * security data from cloud, on-premises, and custom sources into a data lake that's stored in your account. Security Lake
162
- * helps you analyze security data, so you can get a more complete understanding of your security posture across the entire organization and improve the protection of your workloads, applications, and data.</p>
163
- * <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and
164
- * you retain ownership over your data.</p>
165
- * <p>Security Lake automates the collection of security-related log and event data from integrated
166
- * Amazon Web Services. and third-party services and manages the lifecycle of data with customizable
167
- * retention and replication settings. Security Lake also converts ingested data into Apache Parquet format and a
168
- * standard open-source schema called the Open Cybersecurity Schema Framework (OCSF).</p>
161
+ * <p>Amazon Security Lake is a fully managed security data lake service. You can use Security Lake to
162
+ * automatically centralize security data from cloud, on-premises, and custom sources into a
163
+ * data lake that's stored in your Amazon Web Servicesaccount. Amazon Web Services Organizations
164
+ * is an account management service that lets you consolidate multiple Amazon Web Services
165
+ * accounts into an organization that you create and centrally manage. With Organizations, you
166
+ * can create member accounts and invite existing accounts to join your organization.
167
+ * Security Lake helps you analyze security data for a more complete understanding of your
168
+ * security posture across the entire organization. It can also help you improve the
169
+ * protection of your workloads, applications, and data.</p>
170
+ * <p>The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and you
171
+ * retain ownership over your data. </p>
172
+ * <p>Amazon Security Lake integrates with CloudTrail, a service that provides a record of
173
+ * actions taken by a user, role, or an Amazon Web Services service in Security Lake CloudTrail captures API calls for Security Lake as events. The calls captured include calls
174
+ * from the Security Lake console and code calls to the Security Lake API operations. If you create a
175
+ * trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Security Lake. If you don't configure a trail, you can still
176
+ * view the most recent events in the CloudTrail console in Event history. Using the
177
+ * information collected by CloudTrail you can determine the request that was made to
178
+ * Security Lake, the IP address from which the request was made, who made the request, when it
179
+ * was made, and additional details. To learn more about Security Lake information in CloudTrail, see the <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/securitylake-cloudtrail.html">Amazon Security Lake User Guide</a>.</p>
180
+ * <p>Security Lake automates the collection of security-related log and event data from
181
+ * integrated Amazon Web Services and third-party services. It also helps you manage
182
+ * the lifecycle of data with customizable retention and replication settings. Security Lake
183
+ * converts ingested data into Apache Parquet format and a standard open-source schema called
184
+ * the Open Cybersecurity Schema Framework (OCSF).</p>
169
185
  * <p>Other Amazon Web Services and third-party services can subscribe to the data that's stored in Security Lake for
170
186
  * incident response and security data analytics.</p>
171
187
  */