SQL Server
SQL Server
S3 Put Bucket Policy
See more Amazon S3 (new) Examples
Demonstrates how to add or replace a policy on a bucket. The following information is quoted from the AWS REST API reference documentation at PUT Bucket PolicyThis implementation of the PUT operation uses the policy subresource to add to or replace a policy on a bucket. If the bucket already has a policy, the one in this request completely replaces it. To perform this operation, you must be the bucket owner. If you are not the bucket owner but have PutBucketPolicy permissions on the bucket, Amazon S3 returns a 405 Method Not Allowed. In all other cases for a PUT bucket policy request that is not from the bucket owner, Amazon S3 returns 403 Access Denied. There are restrictions about who can create bucket policies and which objects in a bucket they can apply to. For more information, go to Using Bucket Policies.
Important: This example requires Chilkat v9.5.0.66 or greater.
Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @iTmp1 int
-- Important: Do not use nvarchar(max). See the warning about using nvarchar(max).
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
-- Important: This example requires Chilkat v9.5.0.66 or greater.
DECLARE @rest int
EXEC @hr = sp_OACreate 'Chilkat.Rest', @rest OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Connect to the Amazon AWS REST server in the desired region.
DECLARE @bTls int
SELECT @bTls = 1
DECLARE @port int
SELECT @port = 443
DECLARE @bAutoReconnect int
SELECT @bAutoReconnect = 1
EXEC sp_OAMethod @rest, 'Connect', @success OUT, 's3-us-west-2.amazonaws.com', @port, @bTls, @bAutoReconnect
-- Provide AWS credentials.
DECLARE @authAws int
EXEC @hr = sp_OACreate 'Chilkat.AuthAws', @authAws OUT
EXEC sp_OASetProperty @authAws, 'AccessKey', 'AWS_ACCESS_KEY'
EXEC sp_OASetProperty @authAws, 'SecretKey', 'AWS_SECRET_KEY'
EXEC sp_OASetProperty @authAws, 'ServiceName', 's3'
-- This particular bucket is in the Oregon region, as opposed to the US Standard,
-- therefore the Region must be set appropriately.
-- Also note that we connected to "s3-us-west-2.amazonaws.com".
EXEC sp_OASetProperty @authAws, 'Region', 'us-west-2'
EXEC sp_OAMethod @rest, 'SetAuthAws', @success OUT, @authAws
-- Note: The above REST connection and setup of the AWS credentials
-- can be done once. After connecting, any number of REST calls can be made.
-- The "auto reconnect" property passed to rest.Connect indicates that if
-- the connection is lost, a REST method call will automatically reconnect
-- if needed.
-- --------------------------------------------------------------------------
-- Set the bucket name via the HOST header.
-- In this case, the bucket name is "chilkat.ocean".
-- Note that the Host header should use "bucketName.s3.amazonaws.com", not "bucketName.s3-us-west-2.amazonaws.com"
EXEC sp_OASetProperty @rest, 'Host', 'chilkat.ocean.s3.amazonaws.com'
-- Build the S3 JSON Policy to be sent in the request:
DECLARE @json int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'Version', '2012-10-17'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'Statement[0].Action[0]', 's3:GetObject'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'Statement[0].Effect', 'Allow'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'Statement[0].Resource', 'arn:aws:s3:::chilkat.ocean/'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'Statement[0].Principal', '*'
-- The JSON Policy constructed by the above lines of code is:
-- (The bucket name is "chilkat.ocean")
-- {
-- "Version": "2012-10-17",
-- "Statement": [
-- {
-- "Action": [
-- "s3:GetObject"
-- ],
-- "Effect": "Allow",
-- "Resource": "arn:aws:s3:::chilkat.ocean/",
-- "Principal": "*"
-- }
-- ]
-- }
-- Add or replace the policy on the bucket.
DECLARE @responseJsonStr nvarchar(4000)
EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
EXEC sp_OAMethod @rest, 'FullRequestString', @responseJsonStr OUT, 'PUT', '/?policy', @sTmp0
EXEC sp_OAGetProperty @rest, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @authAws
EXEC @hr = sp_OADestroy @json
RETURN
END
-- When successful, the S3 Storage service will respond with a 200 or 204 response code,
-- with an XML body.
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp1 OUT
IF (@iTmp0 <> 200) and (@iTmp1 <> 204)
BEGIN
-- Examine the request/response to see what happened.
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
PRINT 'response status code = ' + @iTmp0
EXEC sp_OAGetProperty @rest, 'ResponseStatusText', @sTmp0 OUT
PRINT 'response status text = ' + @sTmp0
EXEC sp_OAGetProperty @rest, 'ResponseHeader', @sTmp0 OUT
PRINT 'response header: ' + @sTmp0
PRINT 'response body: ' + @responseJsonStr
PRINT '---'
EXEC sp_OAGetProperty @rest, 'LastRequestStartLine', @sTmp0 OUT
PRINT 'LastRequestStartLine: ' + @sTmp0
EXEC sp_OAGetProperty @rest, 'LastRequestHeader', @sTmp0 OUT
PRINT 'LastRequestHeader: ' + @sTmp0
END
PRINT 'Success.'
-- A successful response has no response body..
-- (The Amazon documentation indicates a 204 response, but in our testing we receive a 200 response..)
-- HTTP/1.1 204 No Content
-- x-amz-id-2: Uuag1LuByR5Onimru9SAMPLEAtRPfTaOFg==
-- x-amz-request-id: 656c76696e6727732SAMPLE7374
-- Date: Tue, 04 Apr 2010 20:34:56 GMT
-- Connection: keep-alive
-- Server: AmazonS3
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @authAws
EXEC @hr = sp_OADestroy @json
END
GO