UpdateSubscriberNotification
Updates an existing notification method for the subscription (SQS or HTTPs endpoint) or switches the notification subscription endpoint for a subscriber.
Request Syntax
PUT /v1/subscribers/subscriberId/notification HTTP/1.1
Content-type: application/json
{
   "configuration": { ... }
}URI Request Parameters
The request uses the following URI parameters.
- subscriberId
- 
               The subscription ID for which the subscription notification is specified. Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}Required: Yes 
Request Body
The request accepts the following data in JSON format.
- configuration
- 
               The configuration for subscriber notification. Type: NotificationConfiguration object Note: This object is a Union. Only one member of this object can be specified or returned. Required: Yes 
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
   "subscriberEndpoint": "string"
}Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- subscriberEndpoint
- 
               The subscriber endpoint to which exception messages are posted. Type: String Pattern: [\\\w\-_:/.@=+]*
Errors
For information about the errors that are common to all actions, see Common Errors.
- 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 AWS action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement. - errorCode
- 
                        A coded string to provide more information about the access denied exception. You can use the error code to check the exception type. 
 HTTP Status Code: 403 
- BadRequestException
- 
               The request is malformed or contains an error such as an invalid parameter value or a missing required parameter. HTTP Status Code: 400 
- 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. - resourceName
- 
                        The resource name. 
- resourceType
- 
                        The resource type. 
 HTTP Status Code: 409 
- InternalServerException
- 
               Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again. HTTP Status Code: 500 
- ResourceNotFoundException
- 
               The resource could not be found. - resourceName
- 
                        The name of the resource that could not be found. 
- resourceType
- 
                        The type of the resource that could not be found. 
 HTTP Status Code: 404 
- ThrottlingException
- 
               The limit on the number of requests per second was exceeded. - quotaCode
- 
                        That the rate of requests to Security Lake is exceeding the request quotas for your AWS account. 
- retryAfterSeconds
- 
                        Retry the request after the specified time. 
- serviceCode
- 
                        The code for the service in Service Quotas. 
 HTTP Status Code: 429 
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: