cdk | : fire : SDK for developing with Mixer Interactive

Most probably an issue with SSL. For me it was the pass phrase in the SSL key.

As I researched a lot and did not find a solution to this issue as it's occurring only on the newer version of the animation package.

I tried the below versions:

• 13.2.4 (Latest one) throwing same es error

• 13.2.3 throwing same es error

• 13.2.2 throwing same es error

• 13.2.1 throwing same es error

• 13.2.0 working without error.

So I think for a temporary fix you should update your package.json by pointing to a specific version of this npm like below.

Yes and yes. Earlier CDK versions did not even permit passing text values to the Secret constructor. We only recently got the secretStringBeta1: string prop along with a stern warning:

It is highly encouraged to leave this field undefined and allow SecretsManager to create the secret value. The secret string -- if provided -- will be included in the output of the cdk as part of synthesis, and will appear in the CloudFormation template in the console. This can be secure(-ish) if that value is merely reference to another resource (or one of its attributes), but if the value is a plaintext string, it will be visible to anyone with access to the CloudFormation template (via the AWS Console, SDKs, or CLI).

Our CDK code and generated templates are meant to be deterministic and version-controlled, further heightening the risk of leakage if plaintext secrets are used.

Edit: Per @gshpychka's comment, a safe alternative to importing with Secret.fromSecretArn is to construct a new Secret without a secret value. This creates a secret with a random password, which you change post-deploy in the Console. This approach helpfully ties the secret's lifecycle to the Stack and lets you set its properties in the context of the Stack.

It turns out it was a missing/misconfigured policy. I was able to get it working within CodeBuild by adding a role with the AmazonEC2ContainerRegistryPowerUser managed policy:

From migrating to AWS CDK V2:

Experimental constructs are provided in separate, independently-versioned packages with names that end in alpha and an alpha version number that corresponds to the first release of aws-cdk-lib with which they are compatible.

Since the HttpApi construct is considered experimental, it has been moved to a separate package:

Link to construct page

Link to overview of new experimental package labelled alpha

CfnHttpApi documentation (Not experimental)

CfnApi documentation (Not experimental)

HttpApi documentation (Experimental)

CfnHttpApi and CfnApi are L1 constructs, which means they directly convert to a single CloudFormation resource block. HttpApi is a L2 construct, which are usually more complex and can convert to one or more CloudFormation resource blocks. This CDK Developer guide page on Constructs provides more details on how L1 and L2 constructs work.

CfnHttpApi and CfnApi are both CloudFormation resource types which create HTTP APIs, but CfnHttpApi is the AWS SAM version of CfnApi. Quoting this page, AWS SAM templates are an extension of AWS CloudFormation templates, with some additional components that make them easier to work with.

From the restrictions page of Lambda@Edge

The Lambda function must be in the US East (N. Virginia) Region.

Your code will be still executed in the closest in the closest Edge location to the user, but the function itself must be located in us-east-1.

Based on your usecase (which seems to be a simple url redirect) you might want to consider using the newer CloudFront Functions feature, which is faster and more lightweight. This documentation page has a good comparison table.

Edit:

I haven't used CloudFront functions before, but looking at the CDK documentation and your link, I can suggest a few changes.

From v13 angular doesn't use tslint anymore due to deprecation.

Run ng add @angular-eslint/schematics to add eslint to your application.

It will use tslint-to-eslint-config to migrate you to eslint automatically.

It will generate a .eslintrc.json file and migrate tslint.json to it.

Nothing else is needed to be done.

These limits can be accessed programmatically via the Action.actionProperties.artifactBounds property.

The limits are described here, and CodeBuild actions do have a limit of 5 input artifacts. To work around this, You can have intermediate CodeBuild actions that merge input artifacts into one. You could use two of them, feed each one a subset of the artifacts, and feed the resulting two to the build action. Or you can just get away with one merging action, and pass the rest of the artifacts directly. I would look into merging some repos, though.

Solved! After 2 hours, we finally found the culprit: a Hubspot (CRM) script imported in index.html ... (apparently it broke the HTML structure)

We removed the