boa VS cloudformation-guard

boa

Yeah, pretty much. I'm not sure if we're gonna need to implement Static Shapes first but at least we need to make it possible to separate codeblocks from contexts for this to be feasible.

Hi, I'm looking for full time work and I'm interested in roles related to compilers, developer tools and systems. I'm a college senior(graduating on May, 2023) and have been working as an [IOS Developer](https://www.cyengagement.org/) for the past two years. At University, I took a compilers class where I learnt to use LLVM and MLIR to compile programs to various architectures. In Oct. 2022, I was selected to attend the [Programming Language Implementation Summer School](https://pliss.org/2022/) where I got to learn about compiler implementation and language tools from leading researchers around the world. Recently, I have been contributing to [Boa](https://github.com/boa-dev/boa), an embeddable Javascript engine written in Rust, by fixing issues and implementing features to improve conformance with ECMAScript specification. Aside from working on compilers, I have volunteered at conferences like ICFP'21 and PLDI'22 to familiarize myself with latest research in the field of compilers. You can find more information about me and my work in my [blog](https://veera.app) and Github [profile](https://github.com/veera-sivarajan). Thank you for your time and consideration.

I have great news

I already use it in my project to run some parts of the youtube js player. I must say it was broken on one version of the player because of a generated regex inside (more on the issue), but definitely recommending.

I would be curious how much effort it would be to swap boa for V8 to have an all Rust runtime :) If it's not meant to be a production-ready project anyways.

We'd love to see these benchmarks too! We have an open issue to set-up these benchmarks: https://github.com/boa-dev/boa/issues/1924

Although you probably could use it for something else, Boa[1] is a good demonstration of this (it uses the GC crate, but the same principle probably applies).

[1]: https://github.com/boa-dev/boa

If you now use these services to fix the infrastructure findings, a drift occurs that is not always easy to fix. It is better to check for possible problems before the actual deployment. This approach is called “Shift-Left”. This can be done with the package cdk-validator-cfnguard. It's based on the CloudFormation Guard package.

AWS Config rules allow you to determine if a resource is compliant or not. Previously when you wanted to do custom checks you needed to write AWS Lambda functions to validate the configuration of a resource. Since Aug 2, 2022 you have the ability to use cfn-guard rules to achieve the same.

In my previous blog, How do you prove that your infrastructure is compliant. I explained how you can prove your infrastructure is compliant using CloudFormation Guard. But, how do you write those rules? And even more important, how do you test your rules? If you look at the repository CloudFormation Guard. You will notice that the project itself offers a testing framework. Alright! Let’s build a ruleset and write some tests for it!

When you use CloudFormation Guard in combination with CodeBuild Reports it makes it easier to see what rules have failed and keeps a history. When you have a solid set of compliance rules. It gives you a report that you can use to prove that the build of the infrastructure was compliant. You are also able to prevent non-compliant code rollout in production.

cloudformation-guard.

AWS CloudFormation: can help with deploying compliant stacks. You can make sure that a stack is compliant by using AWS CloudFormation guard.

See https://github.com/aws-cloudformation/cloudformation-guard

Currently, we're also exploring the brand new AWS Config rules backed by guard. Now you can write rules using guard which is a policy-as-code language. Here is some example of a Guard Rule which we are testing.

https://github.com/aws-cloudformation/cloudformation-guard is also very useful, but more so when you want to keep your templates consistent to standards.