Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

SecurityLake

import { SecurityLake } from "https://aws-api.deno.dev/v0.4/services/securitylake.ts?docs=full";
class SecurityLake {
constructor(apiFactory: client.ApiFactory);
async createAwsLogSource(params: CreateAwsLogSourceRequest, opts?: client.RequestOptions): Promise<CreateAwsLogSourceResponse>;
async createCustomLogSource(params: CreateCustomLogSourceRequest, opts?: client.RequestOptions): Promise<CreateCustomLogSourceResponse>;
async createDatalake(params?: CreateDatalakeRequest, opts?: client.RequestOptions): Promise<void>;
async createDatalakeAutoEnable(params: CreateDatalakeAutoEnableRequest, opts?: client.RequestOptions): Promise<void>;
async createDatalakeDelegatedAdmin(params: CreateDatalakeDelegatedAdminRequest, opts?: client.RequestOptions): Promise<void>;
async createDatalakeExceptionsSubscription(params: CreateDatalakeExceptionsSubscriptionRequest, opts?: client.RequestOptions): Promise<void>;
async createSubscriber(params: CreateSubscriberRequest, opts?: client.RequestOptions): Promise<CreateSubscriberResponse>;
async deleteAwsLogSource(params: DeleteAwsLogSourceRequest, opts?: client.RequestOptions): Promise<DeleteAwsLogSourceResponse>;
async deleteCustomLogSource(params: DeleteCustomLogSourceRequest, opts?: client.RequestOptions): Promise<DeleteCustomLogSourceResponse>;
async deleteDatalake(opts?: client.RequestOptions): Promise<void>;
async deleteDatalakeAutoEnable(params: DeleteDatalakeAutoEnableRequest, opts?: client.RequestOptions): Promise<void>;
async deleteDatalakeDelegatedAdmin(params: DeleteDatalakeDelegatedAdminRequest, opts?: client.RequestOptions): Promise<void>;
async deleteDatalakeExceptionsSubscription(opts?: client.RequestOptions): Promise<DeleteDatalakeExceptionsSubscriptionResponse>;
async deleteSubscriber(params: DeleteSubscriberRequest, opts?: client.RequestOptions): Promise<void>;
async deleteSubscriptionNotificationConfiguration(params: DeleteSubscriptionNotificationConfigurationRequest, opts?: client.RequestOptions): Promise<void>;
async getDatalake(opts?: client.RequestOptions): Promise<GetDatalakeResponse>;
async getDatalakeAutoEnable(opts?: client.RequestOptions): Promise<GetDatalakeAutoEnableResponse>;
async getDatalakeExceptionsExpiry(opts?: client.RequestOptions): Promise<GetDatalakeExceptionsExpiryResponse>;
async getDatalakeExceptionsSubscription(opts?: client.RequestOptions): Promise<GetDatalakeExceptionsSubscriptionResponse>;
async getDatalakeStatus(params?: GetDatalakeStatusRequest, opts?: client.RequestOptions): Promise<GetDatalakeStatusResponse>;
async getSubscriber(params: GetSubscriberRequest, opts?: client.RequestOptions): Promise<GetSubscriberResponse>;
async listDatalakeExceptions(params?: ListDatalakeExceptionsRequest, opts?: client.RequestOptions): Promise<ListDatalakeExceptionsResponse>;
async listLogSources(params?: ListLogSourcesRequest, opts?: client.RequestOptions): Promise<ListLogSourcesResponse>;
async listSubscribers(params?: ListSubscribersRequest, opts?: client.RequestOptions): Promise<ListSubscribersResponse>;
async updateDatalake(params: UpdateDatalakeRequest, opts?: client.RequestOptions): Promise<void>;
async updateDatalakeExceptionsExpiry(params: UpdateDatalakeExceptionsExpiryRequest, opts?: client.RequestOptions): Promise<void>;
async updateDatalakeExceptionsSubscription(params: UpdateDatalakeExceptionsSubscriptionRequest, opts?: client.RequestOptions): Promise<void>;
async updateSubscriber(params: UpdateSubscriberRequest, opts?: client.RequestOptions): Promise<UpdateSubscriberResponse>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new SecurityLake(apiFactory: client.ApiFactory)
[src]

§Methods

§

Adds a natively supported Amazon Web Service as an Amazon Security Lake source. Enables source types for member accounts in required Amazon Web Services Regions, based on the parameters you specify. You can choose any source type in any Region for either accounts that are part of a trusted organization or standalone accounts. At least one of the three dimensions is a mandatory input to this API. However, you can supply any combination of the three dimensions to this API.

By default, a dimension refers to the entire set. When you don't provide a dimension, Security Lake assumes that the missing dimension refers to the entire set. This is overridden when you supply any one of the inputs. For instance, when you do not specify members, the API enables all Security Lake member accounts for all sources. Similarly, when you do not specify Regions, Security Lake is enabled for all the Regions where Security Lake is available as a service.

You can use this API only to enable natively supported Amazon Web Services as a source. Use CreateCustomLogSource to enable data collection from a custom source.

§

Adds a third-party custom source in Amazon Security Lake, from the Amazon Web Services Region where you want to create a custom source. Security Lake can collect logs and events from third-party custom sources. After creating the appropriate IAM role to invoke Glue crawler, use this API to add a custom source name in Security Lake. This operation creates a partition in the Amazon S3 bucket for Security Lake as the target location for log files from the custom source in addition to an associated Glue table and an Glue crawler.

§
createDatalake(params?: CreateDatalakeRequest, opts?: client.RequestOptions): Promise<void>
[src]

Initializes an Amazon Security Lake instance with the provided (or default) configuration. You can enable Security Lake in Amazon Web Services Regions with customized settings before enabling log collection in Regions. You can either use the enableAll parameter to specify all Regions or specify the Regions where you want to enable Security Lake. To specify particular Regions, use the Regions parameter and then configure these Regions using the configurations parameter. If you have already enabled Security Lake in a Region when you call this command, the command will update the Region if you provide new configuration parameters. If you have not already enabled Security Lake in the Region when you call this API, it will set up the data lake in the Region with the specified configurations.

When you enable Security Lake, it starts ingesting security data after the CreateAwsLogSource call. This includes ingesting security data from sources, storing data, and making data accessible to subscribers. Security Lake also enables 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 more information, see the Amazon Security Lake User Guide.

§
createDatalakeAutoEnable(params: CreateDatalakeAutoEnableRequest, opts?: client.RequestOptions): Promise<void>
[src]

Automatically enables Amazon Security Lake for new member accounts in your organization. Security Lake is not automatically enabled for any existing member accounts in your organization.

§
createDatalakeDelegatedAdmin(params: CreateDatalakeDelegatedAdminRequest, opts?: client.RequestOptions): Promise<void>
[src]

Designates the Amazon Security Lake delegated 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.

§
createDatalakeExceptionsSubscription(params: CreateDatalakeExceptionsSubscriptionRequest, opts?: client.RequestOptions): Promise<void>
[src]

Creates the specified notification subscription in Amazon Security Lake for the organization you specify.

§

Creates a subscription permission for accounts that are already enabled in Amazon Security Lake. You can create a subscriber with access to data in the current Amazon Web Services Region.

§

Notifies the subscriber when new data is written to the data lake for the sources that the subscriber consumes in Security Lake.

§

Removes a natively supported Amazon Web Service as an Amazon Security Lake source. When you remove the source, Security Lake stops collecting data from that source, and subscribers can no longer consume new data from the source. Subscribers can still consume data that Security Lake collected from the source before disablement.

You can choose any source type in any Amazon Web Services Region for either accounts that are part of a trusted organization or standalone accounts. At least one of the three dimensions is a mandatory input to this API. However, you can supply any combination of the three dimensions to this API.

By default, a dimension refers to the entire set. This is overridden when you supply any one of the inputs. For instance, when you do not specify members, the API disables all Security Lake member accounts for sources. Similarly, when you do not specify Regions, Security Lake is disabled for all the Regions where Security Lake is available as a service.

When you don't provide a dimension, Security Lake assumes that the missing dimension refers to the entire set. For example, if you don't provide specific accounts, the API applies to the entire set of accounts in your organization.

§

Removes a custom log source from Amazon Security Lake.

§
deleteDatalake(opts?: client.RequestOptions): Promise<void>
[src]

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 Security Lake .

This operation disables security data collection from sources, deletes data stored, and stops making data accessible to subscribers. Security Lake also deletes 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. The DeleteDatalake operation does not delete the Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.

§
deleteDatalakeAutoEnable(params: DeleteDatalakeAutoEnableRequest, opts?: client.RequestOptions): Promise<void>
[src]

Automatically deletes Amazon Security Lake to stop collecting security data. When you delete Amazon Security Lake from your account, Security Lake is disabled in all Regions. Also, this API automatically takes steps to remove the account from Security Lake .

This operation disables security data collection from sources, deletes data stored, and stops making data accessible to subscribers. Security Lake also deletes 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. The DeleteDatalake operation does not delete the Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.

§
deleteDatalakeDelegatedAdmin(params: DeleteDatalakeDelegatedAdminRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes the Amazon Security Lake delegated 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.

§
deleteDatalakeExceptionsSubscription(opts?: client.RequestOptions): Promise<DeleteDatalakeExceptionsSubscriptionResponse>
[src]

Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.

§
deleteSubscriber(params: DeleteSubscriberRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes the subscription permission for accounts that are already enabled in Amazon Security Lake. You can delete a subscriber and remove access to data in the current Amazon Web Services Region.

§
deleteSubscriptionNotificationConfiguration(params: DeleteSubscriptionNotificationConfigurationRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.

§
getDatalake(opts?: client.RequestOptions): Promise<GetDatalakeResponse>
[src]

Retrieves the Amazon Security Lake configuration object for the specified Amazon Web Services account ID. You can use the GetDatalake API to know whether Security Lake is enabled for the current Region. This API does not take input parameters.

§
getDatalakeAutoEnable(opts?: client.RequestOptions): Promise<GetDatalakeAutoEnableResponse>
[src]

Retrieves the configuration that will be automatically set up for accounts added to the organization after the organization has onboarded to Amazon Security Lake. This API does not take input parameters.

§
getDatalakeExceptionsExpiry(opts?: client.RequestOptions): Promise<GetDatalakeExceptionsExpiryResponse>
[src]

Retrieves the expiration period and time-to-live (TTL) for which the exception message will remain. Exceptions are stored by default, for 2 weeks from when a record was created in Amazon Security Lake. This API does not take input parameters.

§
getDatalakeExceptionsSubscription(opts?: client.RequestOptions): Promise<GetDatalakeExceptionsSubscriptionResponse>
[src]

Retrieves the details of exception notifications for the account in Amazon Security Lake.

§

Retrieves a snapshot of the current Region, including whether Amazon Security Lake is enabled for those accounts and which sources Security Lake is collecting data from.

§

Retrieves the subscription information for the specified subscription ID. You can get information about a specific subscriber.

§

Lists the Amazon Security Lake exceptions that you can use to find the source of problems and fix them.

§

Retrieves the log sources in the current Amazon Web Services Region.

§

List all subscribers for the specific Amazon Security Lake account ID. You can retrieve a list of subscriptions associated with a specific organization or Amazon Web Services account.

§
updateDatalake(params: UpdateDatalakeRequest, opts?: client.RequestOptions): Promise<void>
[src]

Specifies where to store your security data and for how long. You can add a rollup Region to consolidate data from multiple Amazon Web Services Regions.

§
updateDatalakeExceptionsExpiry(params: UpdateDatalakeExceptionsExpiryRequest, opts?: client.RequestOptions): Promise<void>
[src]

Update the expiration period for the exception message to your preferred time, and control the time-to-live (TTL) for the exception message to remain. Exceptions are stored by default for 2 weeks from when a record was created in Amazon Security Lake.

§
updateDatalakeExceptionsSubscription(params: UpdateDatalakeExceptionsSubscriptionRequest, opts?: client.RequestOptions): Promise<void>
[src]

Updates the specified notification subscription in Amazon Security Lake for the organization you specify.

§

Updates an existing subscription for the given Amazon Security Lake account ID. You can update a subscriber by changing the sources that the subscriber consumes data from.

§

Creates a new subscription notification or adds the existing subscription notification setting for the specified subscription ID.

§Static Properties