create_subscriber_notification `async` ¶

create_subscriber_notification(
    subscriber_id: UUID,
    configuration: NotificationConfiguration,
    *,
    config_overrides: Optional[AsyncSecurityLakeClientConfig] = None,
) -> CreateSubscriberNotificationResponse

Notifies the subscriber when new data is written to the data lake for the sources that the subscriber consumes in Security Lake. You can create only one subscriber notification per subscriber.

Parameters:

subscriber_id (UUID) –

The subscriber ID for the notification subscription.
configuration (NotificationConfiguration) –

Specify the configuration using which you want to create the subscriber notification.

Raises:

AccessDeniedException –

You do not have sufficient access to perform this action. Access denied errors appear when Amazon Security Lake explicitly or implicitly denies an authorization request. An explicit denial occurs when a policy contains a Deny statement for the specific Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
BadRequestException –

The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
ConflictException –

Occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.
InternalServerException –

Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
ResourceNotFoundException –

The resource could not be found.
ThrottlingException –

The limit on the number of requests per second was exceeded.
UnknownServiceError –

The service returned an error code this client does not model.

Source code in docs_src/capo_securitylake/_services/async_security_lake.py

async def create_subscriber_notification(
    self,
    subscriber_id: "capo_securitylake.types.uuid.UUID",
    configuration: "capo_securitylake.types.notification_configuration.NotificationConfiguration",
    *,
    config_overrides: Optional[AsyncSecurityLakeClientConfig] = None,
) -> "capo_securitylake.types.create_subscriber_notification_response.CreateSubscriberNotificationResponse":
    """<p>Notifies the subscriber when new data is written to the data lake for the sources that the subscriber consumes in Security Lake. You can create only one subscriber notification per subscriber.</p>

    Args:
        subscriber_id: <p>The subscriber ID for the notification subscription.</p>
        configuration: <p>Specify the configuration using which you want to create the subscriber notification.</p>

    Raises:
        capo_securitylake.errors.access_denied_exception.AccessDeniedException: <p>You do not have sufficient access to perform this action. Access denied errors appear when Amazon Security Lake explicitly or implicitly denies an authorization request. An explicit denial occurs when a policy contains a Deny statement for the specific Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.</p>
        capo_securitylake.errors.bad_request_exception.BadRequestException: <p>The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.</p>
        capo_securitylake.errors.conflict_exception.ConflictException: <p>Occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.</p>
        capo_securitylake.errors.internal_server_exception.InternalServerException: <p>Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.</p>
        capo_securitylake.errors.resource_not_found_exception.ResourceNotFoundException: <p>The resource could not be found.</p>
        capo_securitylake.errors.throttling_exception.ThrottlingException: <p>The limit on the number of requests per second was exceeded.</p>
        capo_securitylake.errors.UnknownServiceError: The service returned an error code this client does not model.
    """

    async def _handler(
        req: "AsyncOperationRequest[capo_securitylake.types.create_subscriber_notification_request.CreateSubscriberNotificationRequest]",
    ) -> AsyncOperationResponse[
        "capo_securitylake.types.create_subscriber_notification_response.CreateSubscriberNotificationResponse"
    ]:
        import capo_securitylake._operations.security_lake.create_subscriber_notification

        (
            output,
            http_response,
        ) = await capo_securitylake._operations.security_lake.create_subscriber_notification.async_create_subscriber_notification(
            req.options, req.input
        )
        return AsyncOperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("CreateSubscriberNotification")
    )
    input_: capo_securitylake.types.create_subscriber_notification_request.CreateSubscriberNotificationRequest = {
        "subscriber_id": subscriber_id,
        "configuration": configuration,
    }

    response = await aexecute_pipeline(
        AsyncOperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    await response.response.aclose()
    return response.output

create_subscriber_notification async ¶

create_subscriber_notification `async` ¶