Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Commit bf8e80f

Browse files
davemooreuwsraksiv
authored andcommitted
Apply suggestions from code review
1 parent 8665f76 commit bf8e80f

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

docs/guides/terraform/checkov.mdx

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Checkov can be used with any Nitric project that you intend to deploy with Terra
2828

2929
Let's start by creating a new project from a Nitric template, this will provide a base to start building the API.
3030

31-
```typescript
31+
```bash
3232
nitric new my-profile-api ts-starter
3333
```
3434

@@ -48,7 +48,7 @@ nitric start
4848

4949
## Deploying to AWS with a Terraform provider
5050

51-
To deploy your application with Terraform you'll need to use Nitric's Terraform providers. You can learn more about using Nitric with Terraform here.
51+
To deploy your application with Terraform you'll need to use Nitric's Terraform providers. You can learn more about using Nitric with Terraform [here](/providers/terraform).
5252

5353
```bash
5454
nitric stack new dev aws-tf
@@ -97,10 +97,6 @@ checkov -f tfplan.json
9797

9898
Checkov comes with some great default checks, however, they do need to be aligned with the requirements of your application.
9999

100-
Here is an example:
101-
102-
The Checkov policy ‘CKV_AWS_136‘ checks specifically for SSE-KMS using a customer-managed KMS key (or at least AWS-managed KMS key). Thus, Checkov will fail if it doesn’t see a KMS key reference, even though your ECR repository is still encrypted by SSE-S3 automatically.
103-
104-
This finding might not always be relevant because, by default, Amazon ECR encrypts container images at rest using Amazon S3 server-side encryption (SSE-S3). That means your images are always encrypted, even if you don’t explicitly configure a KMS key.
100+
For example the Checkov policy ‘CKV_AWS_136‘ checks specifically for SSE-KMS using a customer-managed KMS key (or at least AWS-managed KMS key). This finding might not always be relevant because, by default, Amazon ECR encrypts container images at rest using Amazon S3 server-side encryption (SSE-S3). That means your images are always encrypted, even if you don’t explicitly configure a KMS key.
105101

106-
If you have any concerns, please don't hesitate to [reach out](https://discord.com/invite/Webemece5C).
102+
If you have any concerns, please don't hesitate to [reach out](https://nitric.io/chat).

0 commit comments

Comments
 (0)