aws-s3 | Amazon S3 volume type for Craft CMS | Plugin library

In the AWS S3 service in a single PUT operation, you can upload a single object up to 5 GB in size.

To upload > 5GB files to S3 you need to use the multipart upload S3 API, and also the AwsS3Multipart Uppy API.

Check your upload code to understand if you are using AWSS3Multipart correctly, setting the limit properly for example, in this case a limit between 5 and 15 is recommended.

Your syntax creates list of maps, not maps. The correct way to create the maps is:

Main problem is the tymon/jwt-auth removing this package and clean install fixed the problem.

The Bitbucket Pipelines yml file is just running Bash/shell commands on a Linux Docker machine. So you can use the normal Bash commands, like sed and perl, to do a "find and replace" inside a JSON text file.

We need to write an expression that will search the text in a file for "version": "dd.dd.dd" and replace it with "version": "dd.dd.ddb123" , where "d" is a digit from 0-9.

Use https://regex101.com to write and test a regex that does this. Here's a working expression and demo and an explanation: https://regex101.com/r/sRviUF/2

• Regular Expression: ("version".*:.*"\d.*(?="))
• Substitution: ${1}b123

Explanation:

• ( and ) = Capture the found text as group 1, to use it as a substitution/replacement later
• "version".*:.*" = Look for the string "version":" with 0 or more spaces allowed before and after the colon :
• \d.*(?=") = Look for a single digit 0-9, then any characters. Then use a Positive Lookahead (?=") to stop the capture before the next speech mark character "
• ${1}b123 = Replace with the captured group 1, then add a "b" then add the numbers 123.

Test and practice on a Linux or MacOS Terminal, or use the Linux Bash Shell on Windows 10, or use an online Linux Terminal.

You will discover that the sed command cannot handle regexes with positive lookahead or negative lookahead, so we have to use perl instead. We also need to simulate the BITBUCKET_BUILD_NUMBER environment variable that is available on the Docker machine when the Pipeline is running.

So I found a solution. Maybe not the solution. Indeed, this seems quite convoluted ... and I am sure there is a better way.

So the solution lies in the fact that the ShellStep in the CodePipeline construct attaches the output of additionalInputs (so the result of the previous CodeBuildStep i.e. lambdaBuildStep) in a specific directory which is dynamically generated but stored in an environment variable called CODEBUILD_SRC_DIR_BuildLambda_lambda_repo so you can see it's a combination of the name of the CodeBuildStep and the repo (with the dash changed to underscores).

So my solution was to use this environment variables as my Lambda code asset.

You cannot depend on CDK pipeline to fix itself if the synth stage is failing, since the Pipeline CloudFormation Stack is changed in the SelfMutate stage which uses the output of the synth stage. You will need to do one of the following options to fix your pipeline:

1. Run cdk synth and cdk deploy PipelineStack locally (or anywhere outside the pipeline, where you have the required AWS IAM permissions). Edit: You will need to temporarily set selfMutatation to false for this to work (Reference)

2. Temporarily remove route53.HostedZone.fromLookup and route53.CnameRecord from your MainStack while still keeping the rolePolicyStatements change. Commit and push your code, let CodePipeline run once, making sure that the Pipeline self mutates and the IAM role has the required additional permissions. Add back the route53 constructs, commit, push again and check whether your code works with the new changes.

1. If you're returning of(result) inside a switchMap(), then use map() instead. You can simply return the result without wrapping it in of().
2. Your switch block handles two cases, but what if both cases fail? That is when you are not returning anything. Try adding a default case at the end to return something if both cases fail.

I got my problem solved. At first i tried to apply solutions at this post but it didn't solve my problem.

The only thing that solved my problem was by upgrading my composer version.

So i upgraded my composer from 1.8.0 to 2.1.3 by:

Well, at this point I was really sure it's a bug and reported it at Strapi Github issues. But according to this answer I received some more configuration had to be done in middlewares.js file: