blocks|key|2020034|text|是的，我让它正常工作，基本上在生成签名URL之后，我需要发送所有元数据和内容-在标题中的分解以及签名的URL。对于示例:我的元数据字典是{'test':'test'}，那么我需要将这个元数据发送到报头，即x-amz-meta-test以及它的值和content-dispostion|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2020035|entityMap^0|2U|F|3F|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Yes I got it working,
Basically after the signed URL is generated I need to send all the metadata and Content-Dispostion in header along with the signed URL.
For eg: My metadata dictionary is {'test':'test'} then I need to send this metadata in header i.e. x-amz-meta-test along with its value and content-dispostion to AWS

blocks|key|2013348|text|我使用的是createPresignedPost，对我来说，通过将我想要的元数据添加到Fields参数中，我可以这样做:-|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2013349|const+params+=+{
++++Expires:+60,
++++Bucket:+process.env.fileStorageName,
++++Conditions:+[['content-length-range',+1,+1000000000]],+//+1GB
++++Fields:+{
++++++++'Content-Type':+'application/pdf',
++++++++key:+strippedName,
++++++++'x-amz-meta-pdf-type':+pdfType,
++++++++'x-amz-meta-pdf-id':+pdfId,
++++},
};|code-block|syntax|javascript|2013350|只要您将所需的数据(在文件的元数据中)传递给用于创建preSignedPost响应的lambda，上面的内容就会有效。希望能帮助别人..。|2013351|entityMap^0|5|J|17|6|0|0|Q|D|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

I was using <code>createPresignedPost</code> and for me I got this working by adding the metadata I wanted to the <code>Fields</code> param like so :-
<pre><code>const params = {
 Expires: 60,
 Bucket: process.env.fileStorageName,
 Conditions: [['content-length-range', 1, 1000000000]], // 1GB
 Fields: {
 'Content-Type': 'application/pdf',
 key: strippedName,
 'x-amz-meta-pdf-type': pdfType,
 'x-amz-meta-pdf-id': pdfId,
 },
};
</code></pre>
As long as you pass the data you want, in the file's metadata, to the lambda that you're using to create the <code>preSignedPost</code> response then the above will work. Hopefully will help someone else...

blocks|key|2467140|text|我发现元数据对象需要是键/值对，值作为字符串(示例是Nodejs+)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2467141|const+AWS+=+require('aws-sdk');
const+s3+=+new+AWS.S3();

exports.handler+=+async+(event)+=>+{
++++const+{+key,+type,+metadata+}+=+JSON.parse(event.body);

++++//+example
++++/*metadata:+{
++++++foo:+'bar',
++++++x:+'123',
++++++y:+'22.4213213'
++++}*/

++++return+await+s3.getSignedUrlPromise('putObject',+{
++++++++Bucket:+'the-product-uploads',
++++++++Key:+key,
++++++++Expires:+300,
++++++++ContentType:+type,
++++++++Metadata:+metadata
++++});
};|code-block|syntax|javascript|2467142|然后，在请求头中，需要显式地添加每个k/v：|2467143|await+fetch(signedUrl,+{
++++++method:+"PUT",
++++++headers:+{
++++++++"Content-Type":+fileData.type,
++++++++"x-amz-meta-foo":+"bar",
++++++++"x-amz-meta-x":+x.toString(),
++++++++"x-amz-meta-y":+y.toString()
++++++},
++++++body:+fileBuffer
++++});|2467144|entityMap^0|J|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

I found the metadata object needs to be key/value pairs, with the value as a string (example is Nodejs lambda):
<pre><code>const AWS = require('aws-sdk');
const s3 = new AWS.S3();

exports.handler = async (event) =&gt; {
 const { key, type, metadata } = JSON.parse(event.body);

 // example
 /*metadata: {
 foo: 'bar',
 x: '123',
 y: '22.4213213'
 }*/

 return await s3.getSignedUrlPromise('putObject', {
 Bucket: 'the-product-uploads',
 Key: key,
 Expires: 300,
 ContentType: type,
 Metadata: metadata
 });
};
</code></pre>
Then in your request headers you need to add each k/v explicitly:
<pre><code>await fetch(signedUrl, {
 method: &quot;PUT&quot;,
 headers: {
 &quot;Content-Type&quot;: fileData.type,
 &quot;x-amz-meta-foo&quot;: &quot;bar&quot;,
 &quot;x-amz-meta-x&quot;: x.toString(),
 &quot;x-amz-meta-y&quot;: y.toString()
 },
 body: fileBuffer
 });
</code></pre>

blocks|key|245263|text|在boto中，您应该提供Metadata参数，以传递您的键的dict值元数据。您不需要将密钥命名为x-amz-meta，因为显然boto正在为您做这件事。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|245264|另外，在上传到预先签名的URL时，我不必再传递元数据：|245265|params+=+{'Bucket':+bucket_name,+
++++++++++'Key':+object_key,+
++++++++++'Metadata':+{'test-key':+value}
+++++++++}

response+=+s3_client.generate_presigned_url('put_object',
+++++++++++++++++++++++++++++++++++++++++++++Params=params,
+++++++++++++++++++++++++++++++++++++++++++++ExpiresIn=3600)|code-block|syntax|javascript|245266|我在API后面的lambda函数中使用了类似的代码|245267|entityMap^0|C|8|1D|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

In boto, you should provide the <code>Metadata</code> parameter passing the dict of your key, value metadata. You don't need to name the key as <code>x-amz-meta</code> as apparently boto is doing it for you now.
Also, I didn't have to pass the metadata again when uploading to the pre-signed URL:
<pre><code>params = {'Bucket': bucket_name, 
 'Key': object_key, 
 'Metadata': {'test-key': value}
 }

response = s3_client.generate_presigned_url('put_object',
 Params=params,
 ExpiresIn=3600)
</code></pre>
I'm using a similar code in a lambda function behind an API

I am trying to create presigned-url using boto3 below

<pre><code>s3 = boto3.client(
 's3', 
 aws_access_key_id=settings.AWS_ACCESS_KEY, 
 aws_secret_access_key=settings.AWS_ACCESS_SECRET, 
 region_name=settings.AWS_SES_REGION_NAME,
 config=Config(signature_version='s3v4')
)
metadata = {
 'test':'testing'
}
presigned_url = s3.generate_presigned_url(
ClientMethod='put_object', 
Params={
 'Bucket': settings.AWS_S3_BUCKET_NAME,
 'Key': str(new_file.uuid),
 'ContentDisposition': 'inline',
 'Metadata': metadata
})
</code></pre>

So, after the URL is generated and I try to upload it to S3 using Ajax it gives 403 forbidden. If I remove Metadata and ContentDisposition while creating URL it gets uploaded successfully.

Boto3 version: 1.9.33

Below is the doc that I referring to:
<a href="https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Client.generate_presigned_url" rel="noreferrer">https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Client.generate_presigned_url</a>

AWS S3 presigned URL with metadata

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在尝试使用下面的boto3创建预签名-url。s3 = boto3.client(    's3',     aws_access_key_id=settings.AWS_ACCESS_KEY,     aws_secret_access_key=settings.AWS_ACCESS_SECRET,     re...

问带有元数据的AWS S3预签名URL
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带有元数据的AWS S3预签名URLEN