AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre:Post

Lambda: save to S3 successful but no files created

0

I'm running a Python Lambda function which when ran locally, successfully saves a file to an S3 bucket. However, when ran in Lambda, there is no error output but no file is created in the target bucket.

Below is the output log:

I'm running a Lambda function which when ran locally, successfully saves a file to an S3 bucket. However, when ran in Lambda, there is no error output but no file is created in the target bucket.

Has anyone experienced this before?

Below is the output log:

2024-04-14 21:32:57 [botocore.httpsession] DEBUG: Certificate path: /var/lang/lib/python3.11/site-packages/certifi/cacert.pem
2024-04-14 21:32:57 [urllib3.connectionpool] DEBUG: Starting new HTTPS connection (1): my-lake.s3.eu-west-2.amazonaws.com:443
2024-04-14 21:32:57 [s3transfer.futures] DEBUG: Submitting task UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 1, 'extra_args': {}}) to executor <s3transfer.futures.BoundedExecutor object at 0x7f4bac3f40d0> for transfer request: 0.
2024-04-14 21:32:57 [s3transfer.utils] DEBUG: Acquiring 0
2024-04-14 21:32:57 [s3transfer.futures] DEBUG: Submitting task UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/latest/my_json_file.json', 'part_number': 1, 'extra_args': {}}) to executor <s3transfer.futures.BoundedExecutor object at 0x7f4bac1e6ad0> for transfer request: 0.
2024-04-14 21:32:57 [s3transfer.utils] DEBUG: Acquiring 0
2024-04-14 21:32:57 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 1, 'extra_args': {}}) about to wait for the following futures [<s3transfer.futures.ExecutorFuture object at 0x7f4bac1ca090>]
2024-04-14 21:32:57 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 1, 'extra_args': {}}) about to wait for <s3transfer.futures.ExecutorFuture object at 0x7f4bac1ca090>
2024-04-14 21:32:57 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/latest/my_json_file.json', 'part_number': 1, 'extra_args': {}}) about to wait for the following futures [<s3transfer.futures.ExecutorFuture object at 0x7f4bac1c87d0>]
2024-04-14 21:32:57 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/latest/my_json_file.json', 'part_number': 1, 'extra_args': {}}) about to wait for <s3transfer.futures.ExecutorFuture object at 0x7f4bac1c87d0>
2024-04-14 21:32:58 [s3transfer.futures] DEBUG: Submitting task UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 2, 'extra_args': {}}) to executor <s3transfer.futures.BoundedExecutor object at 0x7f4bac3f40d0> for transfer request: 0.
2024-04-14 21:32:58 [s3transfer.utils] DEBUG: Acquiring 0
2024-04-14 21:32:58 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 2, 'extra_args': {}}) about to wait for the following futures [<s3transfer.futures.ExecutorFuture object at 0x7f4bac1ca090>]
2024-04-14 21:32:58 [s3transfer.tasks] DEBUG: UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 2, 'extra_args': {}}) about to wait for <s3transfer.futures.ExecutorFuture object at 0x7f4bac1ca090>
2024-04-14 21:32:58 [s3transfer.futures] DEBUG: Submitting task UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/latest/my_json_file.json', 'part_number': 2, 'extra_args': {}}) to executor <s3transfer.futures.BoundedExecutor object at 0x7f4bac1e6ad0> for transfer request: 0.
2024-04-14 21:32:58 [s3transfer.utils] DEBUG: Acquiring 0
2024-04-14 21:32:59 [s3transfer.futures] DEBUG: Submitting task UploadPartTask(transfer_id=0, {'bucket': 'my-lake', 'key': 'my_bucket/my_json_file', 'part_number': 3, 'extra_args': {}}) to executor <s3transfer.futures.BoundedExecutor object at 0x7f4bac3f40d0> for transfer request: 0.
END RequestId: 0330e488-5847-43fa-b604-9a0634e7deca
REPORT RequestId: 0330e488-5847-43fa-b604-9a0634e7deca	Duration: 485178.65 ms	Billed Duration: 485298 ms	Memory Size: 128 MB	Max Memory Used: 129 MB	Init Duration: 118.59 ms
  • ben-from-aws 전문가
    5달 전

    Hi Horus, to assist you better, it would be helpful to understand the permissions attached to the function as well as the code that you use to upload to S3

주제
스토리지서버리스컴퓨팅
태그
아마존 심플 스토리지 서비스AWS Lambda스토리지
언어
English
Horus
질문됨 5달 전364회 조회
1개 답변
0

There are a few reasons why your Python Lambda function might be saving a file to S3 successfully locally but not when deployed:

  1. IAM Permissions: Lambda functions run in a specific IAM role. This role needs to have appropriate permissions to access and write objects to the S3 bucket. Ensure your Lambda function's IAM role has the following permissions: s3:PutObject on the specific object key within the target bucket.

Optionally, you might also need s3:GetObject permission if your code reads the file before uploading.

  1. Environment Variables: If your code uses environment variables to store S3 bucket details (e.g., bucket name), make sure these environment variables are set correctly in your Lambda function configuration when deployed. Locally, you might have them set differently.

  2. AWS Credentials: Locally, you might have AWS credentials configured (e.g., through ~/.aws/credentials file). Lambda functions don't use these by default. They rely on IAM roles for authorization. Double-check you're not accidentally relying on local credentials in your code.

profile pictureAWS
cloudyy
답변함 5달 전
profile picture
전문가
Giovanni Lauria
검토됨 5달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠