PowerShell

Configure AWS Signature Authentication for REST

Demonstrates Rest.SetAuthAws, which associates an AuthAws provider so Chilkat signs each request using AWS Signature Version 4. The provider supplies the access key, secret key, region, and service name.

Background. AWS requires each request to be signed with a signature derived from the secret key, region, service, and request contents. Configuring the provider lets Chilkat compute and attach the signature automatically.

Chilkat PowerShell Downloads

Download Chilkat for PowerShell

PowerShell

Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"

$success = $false

$rest = New-Object Chilkat.Rest
$bTls = $true
$bAutoReconnect = $true
$success = $rest.Connect("example.com",443,$bTls,$bAutoReconnect)
if ($success -eq $false) {
    $($rest.LastErrorText)
    exit
}

#  Configure AWS Signature Version 4 request signing.  Provide the access key, secret key, region,
#  and service name.
$authAws = New-Object Chilkat.AuthAws
#  Normally you would not hard-code secrets in source.  You should instead obtain them from an
#  interactive prompt, environment variable, or a secrets vault.
$authAws.AccessKey = "AWS_ACCESS_KEY"
$authAws.SecretKey = "AWS_SECRET_KEY"
$authAws.Region = "us-east-1"
$authAws.ServiceName = "s3"

#  Associate the provider so Chilkat signs each request according to AWS requirements.
$success = $rest.SetAuthAws($authAws)
if ($success -eq $false) {
    $($rest.LastErrorText)
    exit
}

$responseText = $rest.FullRequestNoBody("GET","/")
if ($rest.LastMethodSuccess -eq $false) {
    $($rest.LastErrorText)
    exit
}

$($responseText)