Using steps in https://github.com/aws-samples/aws-codepipeline-bitbucket-integration am trying to integrate CodePipeline with on prem Bitbucket Server
when I pushing the code to repo am getting following error. am not sure what am missing still
/* `File downloaded successfully: <ref *2> IncomingMessage {
_events:
close: [Function: onclose],
error: [Function: onerror],
data: undefined,
end: [ [Function: responseOnEnd], [Function: onend] ],
readable: undefined,
finish: [Function: onfinish]
WARN Are you using a Stream of unknown length as the Body of a PutObject request? Consider using Upload instead from @aws-sdk/lib-storage.
WARN An error was encountered in a non-retryable streaming request.
INFO Exiting with error NotImplemented: A header you provided implies functionality that is not implemented
at throwDefaultError (/var/runtime/node_modules/@aws-sdk/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)
at /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5
at de_CommandError (/var/runtime/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4756:14)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at async /var/runtime/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:225:18
at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
at async /var/runtime/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:173:18
at async /var/runtime/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:97:20
at async /var/runtime/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:120:14 {
‘$fault’: ‘client’,
‘$metadata’:
httpStatusCode: 501,
requestId: ‘G64RMGHEPWVDE’,
extendedRequestId: ‘FTZNy/uEqwgkrWH3XP/QIIiCIZAc5f+ZxCG3tFJp7QhFrCopRunG5ScmqfMxbpWus3o6cuXoC1M=’,
cfId: undefined
Code: ‘NotImplemented’,
Header: ‘Transfer-Encoding’,
RequestId: ‘G64RMGHYPWVDE’,
HostId: ‘FTZNy/uEqwgkrWH3XP/QIIiCIZAc5f3tFJp7QhFrCopRunG5ScmqfMxbpWus3o6cuXoC1M=’
I have updated bucket policies and IAM role
Bucket Policy
{ "Version": "2008-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::xxxxxxxxx:role/lambda-executionrole" }, "Action": [ "s3:Get*", "s3:List*", "s3:Put*", "s3:Delete*" ], "Resource": [ "arn:aws:s3:::bucketname", "arn:aws:s3:::bucketname/*" ] } ] }
Lambda IAM have S3 full access and AWSLambdaVPCAccessExecutionRole managed policies attached to it and custom policy have below premission
{ "Version": "2012-10-17", "Statement": [ { "Action": [ "s3:GetBucket*", "s3:ListBucket*" ], "Resource": [ "arn:aws:s3:::bucketname" ], "Effect": "Allow", "Sid": "S3BucketPolicy" }, { "Action": [ "s3:AbortMultipartUpload", "s3:GetObject*", "s3:PutObject*", "s3:DeleteObject*", "s3:RestoreObject", "s3:ListMultipartUploadParts" ], "Resource": [ "arn:aws:s3:::bucketname/*" ], "Effect": "Allow" }, { "Action": [ "kms:decrypt" ], "Resource": [ "arn:aws:kms:us-east-1:xxxxxxxxx:key/xxxxxxxxxxxxx9" ], "Effect": "Allow" } ] }