kevinslin / cdk-constants

Useful constants for aws-cdk

I'm Kevin. I'm a software engineer that's been obsessed with PKM for the last decade - mostly for personal reasons as I needed a tool that could help me make use of my own corpus of +30K notes.

After a decade of experimenting, I found that existing workflows and tools (sometimes) made it easy to create notes but past the 1K note threshold, made it impossible to find again.

This led me to create my own workflow - A Hierarchy First Approach to Note Taking. This workflow, combined with custom tooling I created to facilitate it, completely solved information overload for myself, allowing me to easily create, organize and reference my own knowledge.

In 2019, I left my job at Amazon to focus on distilling everything I had learned about PKM to build Dendron - a tool for thought that helps humans manage knowledge at scale.

cdk-constants's Issues

Add releases section for easier tracking

I'd like to request adding request section to this repository. Would be much easier to track releases ;-)

Version 3.0.3 incompatible with CDK 1.26.0

Hi,

cdk-constants version 3.0.3 depends on jsii (>=0.21.1,<0.22.0), which is not compatible with CDK 1.26.0 (it requires jsii (>=0.22.0,<0.23.0)).

Can you please release a new version with updated/relaxed jsii dependency?

Here's a complete output of poetry update in my Python project where I tried upgrading CDK core to 1.26.0:

[SolverProblemError]
Because no versions of cdk-constants match >3.0.3,<4.0.0
 and cdk-constants (3.0.3) depends on jsii (>=0.21.1,<0.22.0), cdk-constants (>=3.0.3,<4.0.0) requires jsii (>=0.21.1,<0.22.0).
And because aws-cdk.core (1.26.0) depends on jsii (>=0.22.0,<0.23.0)
 and no versions of aws-cdk.core match >1.26.0,<2.0.0, cdk-constants (>=3.0.3,<4.0.0) is incompatible with aws-cdk.core (>=1.26.0,<2.0.0).
So, because bp-tornado-online depends on both aws-cdk.core (^1.26.0) and cdk-constants (^3.0.3), version solving failed.

Thank you :)

Error trying to install

Hi! I love the idea of this library, thank you for making it.

I ran into an error trying to install:

> npm i [email protected]                                   
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.

npm ERR! path /Users/emurphy/kindlyops/kindlyops/cdk/node_modules/cdk-constants/lib/bin/cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/emurphy/kindlyops/kindlyops/cdk/node_modules/cdk-constants/lib/bin/cli.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

Is there any extra info I can provide to help figure out why this isn't installing?

Add `cloudwatch.amazonaws.com` to `ServicePrincipals`

Source: https://aws.amazon.com/premiumsupport/knowledge-center/cloudwatch-receive-sns-for-alarm-trigger/

Add `scheduler.amazonaws.com` to `ServicePrincipals`

Mentioned in https://docs.aws.amazon.com/scheduler/latest/UserGuide/security_iam_id-based-policy-examples.html

Add `pipes.amazonaws.com` to `ServicePrincipals`

Used by EventBridge Pipes.

Add `delivery.logs.amazonaws.com` to `ServicePrincipals`

Example of the policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AWSLogDeliveryWrite",
      "Effect": "Allow",
      "Principal": {
        "Service": "delivery.logs.amazonaws.com"
      },
      "Action": [
        "logs:CreateLogStream",
        "logs:PutLogEvents"
      ],
      "Resource": [
        "arn:aws:logs:x:x:log-group:/aws/vendedlogs/*"
      ]
    }
  ]
}

Support PrivateLink service name

Hi,

I use it very conveniently.
I would like to manage the ServiceName for PrivateLink with this library as well, do you plan to support it?
ref. https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html

If you don't have a support schedule at this time and I'm willing to add it, I'd like to send you a pull request. In that case, I'd appreciate any advice on the appropriate namespace.

Requesting an updated version release

Good afternoon, Kevin!

We're currently using this library to great effect, but we just encountered an issue where we we're standing up a new EventBridge scheduler, and noticed that the ServicePrincipals list does not include the SCHEDULER role. I see that there was a PR that added this merged back in May, is there any chance we could get a release cut to use the new principal?

Thanks!

Add `iotwireless.amazonaws.com` to `ServicePrincipals`

Used for LPWAN devices