This article was originally written in Japanese and published on Qiita. It has been translated with the help of AI.

Original article: https://qiita.com/sassssan68/items/9f37fac0f4e2210deb0c

You switched S3 encryption from SSE-S3 to SSE-KMS, and suddenly your presigned URLs started returning errors.

Sound familiar?

It happened to me.

Presigned URLs and SSE-KMS are both common features when used on their own, but combining them comes with some tricky permission requirements.

This article covers:

• Why presigned URLs fail when you switch to SSE-KMS


• Easy-to-miss permission pitfalls (IAM policies and KMS key policies)


• Different gotchas for downloads (GET) and uploads (PUT)

Background

What Is a Presigned URL?

A presigned URL grants temporary access to an S3 object.

Even users without IAM credentials can use the URL to download or upload S3 objects.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html

Common use cases:

• Letting a user download a file temporarily


• Letting a user upload a file (e.g., form submission)
  

# Generate a download presigned URL (valid for 3600 seconds)

aws s3 presign s3://your-bucket/your-file.pdf --expires-in 3600

The important thing to keep in mind is that a presigned URL borrows the permissions of the user who generated it.

If the generator doesn't have the required permissions, the URL can still be issued, but actual access will fail.

What Is SSE-KMS?

SSE-KMS is one of S3's server-side encryption methods. It encrypts objects using a customer managed key in AWS KMS.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html

Comparing S3 encryption methods:

Why It Works with SSE-S3 but Fails with SSE-KMS

With SSE-S3, S3 manages the keys internally, so no extra permission setup is needed.

With SSE-KMS, on the other hand, separate permissions to access the KMS key are required. This is the part you need to watch out for.

Worth noting: this applies even when you use the AWS managed key (aws/s3) for SSE-KMS.

You might think, "AWS manages this key, so it should work like SSE-S3 without extra permissions, right?" But as long as it's SSE-KMS, KMS permissions are required regardless of who manages the key.

When you access an object via a presigned URL, here's what happens internally:

With SSE-S3

1. Request comes in via the presigned URL


2. S3 decrypts the data with its internal key


3. Data is returned

With SSE-KMS

1. Request comes in via the presigned URL


2. S3 asks KMS to decrypt the data key ← Without KMS key permissions, this fails
   


3. KMS decrypts and returns the data key


4. S3 decrypts the data with the data key


5. Data is returned

With SSE-KMS, you need permissions for both S3 and the KMS key.

If the user generating the presigned URL doesn't have permission to use the KMS key, the URL can still be issued, but the actual request will return an error.

Common Pitfalls

1. IAM Policies Need KMS Permissions

The IAM user or role generating the presigned URL needs to have KMS-related permissions added to its policy.

For Downloads (GET)

{

    "Version": "2012-10-17",

    "Statement": [

        {

            "Sid": "AllowS3GetObject",

            "Effect": "Allow",

            "Action": "s3:GetObject",

            "Resource": "arn:aws:s3:::my-bucket/*"

        },

        {

            "Sid": "AllowKMSDecrypt",

            "Effect": "Allow",

            "Action": "kms:Decrypt",

            "Resource": "arn:aws:kms:ap-northeast-1:123456789012:key/your-key-id"

        }

    ]

}

s3:GetObject alone isn't enough — without kms:Decrypt, you'll get an error.

For Uploads (PUT)

{

    "Version": "2012-10-17",

    "Statement": [

        {

            "Sid": "AllowS3PutObject",

            "Effect": "Allow",

            "Action": "s3:PutObject",

            "Resource": "arn:aws:s3:::my-bucket/*"

        },

        {

            "Sid": "AllowKMSForUpload",

            "Effect": "Allow",

            "Action": "kms:GenerateDataKey",

            "Resource": "arn:aws:kms:ap-northeast-1:123456789012:key/your-key-id"

        }

    ]

}

For uploads, kms:GenerateDataKey is required.

S3 needs to ask KMS to generate a data key in order to encrypt the object.

⚠️ Note

For multipart uploads, kms:Decrypt is also required.

Each part is encrypted using the same data key, which means the encrypted data key needs to be decrypted on subsequent parts.

2. Explicitly Specify Signature Version 4 in Boto3

When using SSE-KMS, Signature Version 4 (SigV4) is mandatory.

This is documented in the official AWS docs.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#aws-signature-version-4-sse-kms

Recent versions of Boto3 use SigV4 by default, but depending on your environment or configuration, it may fall back to SigV2.

In that case, you'll get an InvalidArgument error like this:

<Error>

  <Code>InvalidArgument</Code>

  <Message>

    Requests specifying Server Side Encryption with AWS KMS managed keys

    require AWS Signature Version 4.

  </Message>

  <ArgumentName>Authorization</ArgumentName>

</Error>

To make sure it works reliably, explicitly specify SigV4 when creating the client.

from botocore.config import Config



s3_client = boto3.client("s3", config=Config(signature_version="s3v4"))

I actually got tripped up by this myself.

Everything worked fine with SSE-S3, but the moment I switched to SSE-KMS, presigned URLs stopped working — and the cause was that I forgot to explicitly specify SigV4.

⚠️ Note

SigV4 may not be the default in environments like:

• Older versions of Boto3 / Botocore


• When signature_version is explicitly set in ~/.aws/config
  


• Legacy region settings

When using SSE-KMS, always specify Config(signature_version="s3v4") to be safe.

3. KMS Key Policy Permissions

If you created the KMS key with default settings, the root delegation policy means IAM policies alone are sufficient.

If you've modified the key policy, however, the KMS key policy must also grant permission, or you'll get an error.

KMS keys have a key policy that controls "who can use this key."

Permission must be granted in both the IAM policy and the key policy.

Example Key Policy

{

    "Sid": "AllowPresignedUrlRole",

    "Effect": "Allow",

    "Principal": {

        "AWS": "arn:aws:iam::123456789012:role/PresignedUrlGeneratorRole"

    },

    "Action": [

        "kms:Decrypt",

        "kms:GenerateDataKey"

    ],

    "Resource": "*"

}

Note

Using * for Resource in a KMS key policy is fine.

Since the key policy is attached to the key itself, * refers to that very key.

KMS keys created with default settings include a policy with root as the Principal.

Specifying root delegates the decision to the account's IAM policies, which means IAM policy alone is enough to use the KMS key.

However, if you've removed or modified this statement for security reasons, you'll need to explicitly grant the presigned URL generator's principal in the key policy.

4. PUT Presigned URLs Need SSE Parameters in the Signature

This applies when you don't use bucket default encryption and instead specify the KMS key explicitly in the request.

If the bucket's default encryption is set to SSE-KMS, S3 handles encryption automatically server-side, so this step isn't needed.

When generating a presigned URL for upload, you need to include the SSE-KMS parameters in the signature.

With AWS CLI

The AWS CLI's presign command is designed for GET (download) use cases.

For PUT use cases that need SSE-KMS parameters, it's more reliable to use an SDK.

With AWS SDK (Python / Boto3)

import boto3

from botocore.config import Config



s3_client = boto3.client("s3", config=Config(signature_version="s3v4"))



# For downloads (GET)

download_url = s3_client.generate_presigned_url(

    "get_object",

    Params={

        "Bucket": "my-bucket",

        "Key": "my-file.pdf",

    },

    ExpiresIn=3600,

)



# For uploads (PUT)

upload_url = s3_client.generate_presigned_url(

    "put_object",

    Params={

        "Bucket": "my-bucket",

        "Key": "upload/new-file.pdf",

        "ServerSideEncryption": "aws:kms",

        "SSEKMSKeyId": "arn:aws:kms:ap-northeast-1:123456789012:key/your-key-id",

    },

    ExpiresIn=3600,

)

For PUT presigned URLs, include ServerSideEncryption and SSEKMSKeyId in Params.

⚠️ Note

The headers in the PUT request must match the parameters included in the signature.

When making the request from the client side (curl, fetch, etc.), include the following headers:

curl -X PUT \

  -H "x-amz-server-side-encryption: aws:kms" \

  -H "x-amz-server-side-encryption-aws-kms-key-id: arn:aws:kms:ap-northeast-1:123456789012:key/your-key-id" \

  --upload-file ./new-file.pdf \

  "<presigned-url>"

Missing headers will result in a SignatureDoesNotMatch error.

Note

For multipart uploads (upload_part), SSE parameters are specified at the create_multipart_upload step.

The presigned URLs for individual parts don't need ServerSideEncryption or SSEKMSKeyId.

Troubleshooting Checklist

Here's a checklist for when you hit errors with presigned URLs and SSE-KMS:

Summary

The biggest reason presigned URLs and SSE-KMS trip people up is that switching to SSE-KMS introduces a separate requirement: permissions on the KMS key itself.

On top of that, you also need to be careful about SigV4 and how SSE parameters are handled.

Key takeaways:

1. 
   When you switch to SSE-KMS, add KMS permissions — kms:Decrypt, plus kms:GenerateDataKey for PUT


2. 
   In Boto3, explicitly set Config(signature_version="s3v4") — without SigV4, you'll get InvalidArgument
   


3. 
   Check the KMS key policy too — IAM policies alone may not be enough


4. 
   Include SSE parameters in PUT presigned URLs — header mismatches lead to SignatureDoesNotMatch
   

You're most likely to hit these errors when migrating from SSE-S3 to SSE-KMS, so use this checklist when you do!