s3-deploy | NodeJS bash utility for deploying files to Amazon S3 | Cloud Storage library

React runs in the user's web browser and therefore does not have access to environment variables running on the server. They are different environments.

You can embed environment variables in your app at build time:

Note: You must create custom environment variables beginning with REACT_APP_. Any other variables except NODE_ENV will be ignored to avoid accidentally exposing a private key on the machine that could have the same name. Changing any environment variables will require you to restart the development server if it is running.

The "at build time" part of this is important. To include and use your REACT_APP_BASE_URL variable in your app, make sure to define it in a way your "Build and Test" step can see.

Assuming you have defined that variable for the Production deployment environment, make sure to use that environment for the build step:

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.

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.

Your website doesn't feel like 100% (client side) static website. By that I mean every HTML page is pre-generated and everything is static on client side. If that's the case then /work/1 should not load any html page as it's not a html resource. For it to be HTML resource it should be like /work/1.html

With that being said, it looks like you're using React or some other technology which translates the routing when previous page is known. / -> /work/1

As you have CloudFront already in your stack. Just set the error pages to redirect back to home page and then it should work fine. Attaching the solution for my react app hosted on S3+CloudFront.

If the problem has to do with JSON, you could try the aws sync --metadata Shorthand Syntax:

To simplify your scripts, you can use GM_addStyle - a Tampermonkey's native method - to apply your CSS. However, if your scripts are just going to include a call to GM_addStyle, then you should probably use an extension like Stylus.

1. For your first script, you can use pure CSS instead of attempting to get the element, fetch its class name, then apply some styles to that class.

   Here's what I came up with:

Finally we are able to solve this issue. This was due to multiple modules with same java package structure names. This created a conflict in loading and finding the module when running from java.

After changing the package structure, it started working fine.

We have multiple modules like cloudwatch and nodejs-canary inside a main project.

Before

package.json for cloudwatch

"jsii": { "outdir": "dist", "targets": { "java": { "package": "com.company.common.aws.cdk", "maven": { "groupId": "com.company.common.aws.cdk", "artifactId": "cloudwatch" } } } }

package.json for nodejs-canary

"jsii": { "outdir": "dist", "targets": { "java": { "package": "com.company.common.aws.cdk", "maven": { "groupId": "com.company.common.aws.cdk", "artifactId": "nodejs-canary" } } } }

After

"jsii": { "outdir": "dist", "targets": { "java": { "package": "com.company.common.aws.cdk.cloudwatch", "maven": { "groupId": "com.company.common.aws.cdk", "artifactId": "cloudwatch" } } } }

package.json

"jsii": { "outdir": "dist", "targets": { "java": { "package": "com.company.common.aws.cdk.nodejs_canary", "maven": { "groupId": "com.company.common.aws.cdk", "artifactId": "nodejs-canary" } } } }

Just to add little more, initially when we ran with one module it worked fine. Later after adding additional modules while using in Java we got Module not found error.

based on https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-aws-with-s3/

You have to install the missing package for aws-cdk before calling cdk synth myStack.

run this command under pipeline task: