update_subscriber
async
¶
update_subscriber(
subscriber_id: UUID,
*,
config_overrides: Optional[AsyncSecurityLakeClientConfig] = None,
subscriber_identity: Optional[AwsIdentity] = None,
subscriber_name: Optional[SafeString] = None,
subscriber_description: Optional[DescriptionString] = None,
sources: Optional[LogSourceResourceList] = None,
) -> UpdateSubscriberResponse
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.
Parameters:
-
subscriber_id(UUID) –A value created by Security Lake that uniquely identifies your subscription.
-
subscriber_identity(Optional[AwsIdentity], default:None) –The Amazon Web Services identity used to access your data.
-
subscriber_name(Optional[SafeString], default:None) –The name of the Security Lake account subscriber.
-
subscriber_description(Optional[DescriptionString], default:None) –The description of the Security Lake account subscriber.
-
sources(Optional[LogSourceResourceList], default:None) –The supported Amazon Web Services services from which logs and events are collected. For the list of supported Amazon Web Services services, see the Amazon Security Lake User Guide.
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
1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 | |