create_subscriber
¶
create_subscriber(
subscriber_identity: AwsIdentity,
subscriber_name: str,
sources: LogSourceResourceList,
*,
config_overrides: Optional[SecurityLakeClientConfig] = None,
subscriber_description: Optional[DescriptionString] = None,
access_types: Optional[AccessTypeList] = None,
tags: Optional[TagList] = None,
) -> CreateSubscriberResponse
Creates a subscriber 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.
Parameters:
-
subscriber_identity(AwsIdentity) –The Amazon Web Services identity used to access your data.
-
subscriber_name(str) –The name of your Security Lake subscriber account.
-
subscriber_description(Optional[DescriptionString], default:None) –The description for your subscriber account in Security Lake.
-
sources(LogSourceResourceList) –The supported Amazon Web Services services from which logs and events are collected. Security Lake supports log and event collection for natively supported Amazon Web Services services.
-
access_types(Optional[AccessTypeList], default:None) –The Amazon S3 or Lake Formation access type.
-
tags(Optional[TagList], default:None) –An array of objects, one for each tag to associate with the subscriber. For each tag, you must specify both a tag key and a tag value. A tag value cannot be null, but it can be an empty string.
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/security_lake.py
1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 | |