AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Deletes the resource-based policy attached to the resource, which can be a table or stream.
DeleteResourcePolicy is an idempotent operation; running it multiple times
on the same resource doesn't result in an error response, unless you specify
an ExpectedRevisionId, which will then return a PolicyNotFoundException.
To make sure that you don't inadvertently lock yourself out of your own resources,
the root principal in your Amazon Web Services account can perform DeleteResourcePolicy
requests, even if your resource-based policy explicitly denies the root principal's
access.
DeleteResourcePolicy is an asynchronous operation. If you issue a GetResourcePolicy
request immediately after running the DeleteResourcePolicy request, DynamoDB
might still return the deleted policy. This is because the policy for your resource
might not have been deleted yet. Wait for a few seconds, and then try the GetResourcePolicy
request again.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginDeleteResourcePolicy and EndDeleteResourcePolicy.
Namespace: Amazon.DynamoDBv2
Assembly: AWSSDK.DynamoDBv2.dll
Version: 3.x.y.z
public abstract Task<DeleteResourcePolicyResponse> DeleteResourcePolicyAsync( DeleteResourcePolicyRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the DeleteResourcePolicy service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
| Exception | Condition |
|---|---|
| InternalServerErrorException | An error occurred on the server side. |
| LimitExceededException | There is no limit to the number of daily on-demand backups that can be taken. For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive, RestoreTableFromBackup, and RestoreTableToPointInTime. When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations. When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account. There is a soft account quota of 2,500 tables. GetRecords was called with a value of more than 1000 for the limit request parameter. More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling. |
| PolicyNotFoundException | The operation tried to access a nonexistent resource-based policy. If you specified an ExpectedRevisionId, it's possible that a policy is present for the resource but its revision ID didn't match the expected value. |
| ResourceInUseException | The operation conflicts with the resource's availability. For example: You attempted to recreate an existing table. You tried to delete a table currently in the CREATING state. You tried to update a resource that was already being updated. When appropriate, wait for the ongoing update to complete and attempt the request again. |
| ResourceNotFoundException | The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE. |
.NET:
Supported in: 8.0 and newer, Core 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5 and newer