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.
Creates a new origin access identity. If you're using Amazon S3 for your origin, you can use an origin access identity to require users to access your content using a CloudFront URL instead of the Amazon S3 URL. For more information about how to use origin access identities, see Serving Private Content through CloudFront in the Amazon CloudFront Developer Guide.
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 BeginCreateCloudFrontOriginAccessIdentity and EndCreateCloudFrontOriginAccessIdentity.
Namespace: Amazon.CloudFront
Assembly: AWSSDK.CloudFront.dll
Version: 3.x.y.z
public abstract Task<CreateCloudFrontOriginAccessIdentityResponse> CreateCloudFrontOriginAccessIdentityAsync( CreateCloudFrontOriginAccessIdentityRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the CreateCloudFrontOriginAccessIdentity service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
| Exception | Condition |
|---|---|
| CloudFrontOriginAccessIdentityAlreadyExistsException | If the CallerReference is a value you already sent in a previous request to create an identity but the content of the CloudFrontOriginAccessIdentityConfig is different from the original request, CloudFront returns a CloudFrontOriginAccessIdentityAlreadyExists error. |
| InconsistentQuantitiesException | The value of Quantity and the size of Items don't match. |
| InvalidArgumentException | An argument is invalid. |
| MissingBodyException | This operation requires a body. Ensure that the body is present and the Content-Type header is set. |
| TooManyCloudFrontOriginAccessIdentitiesException | Processing your request would cause you to exceed the maximum number of origin access identities allowed. |
.NET Core App:
Supported in: 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5