@alliander-opensource/aws-jwt-sts 0.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE.txt ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [2023] [Alliander NV]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,130 @@
1
+ # Use IAM roles to authenticate principals in workloads outside of AWS using JWT
2
+ There is an inherent risk in maintaining and storing permanent credentials. In their lifetime, they are bound to be shared, compromised, and lost. When shared, it is often among a broader audience than initially intended. They can also be lost and found, sometimes by the wrong person. And when any of this occurs, it can put your systems, data or even organization at risk.
3
+
4
+ Workloads running on AWS can communicate with each other or with AWS services without the need of storing permanent credentials by assuming roles or instance profiles. However, if one of the workloads lives outside of AWS, AWS principals can no longer be used for authentication.
5
+
6
+ An alternative to authenticating with external workloads is to use short-lived credentials issued by a trusted party, the issuer, that the target system can accept. JWTs (JSON Web Tokens), as used by the OIDC (OpenID Connect) standard, are an example of such credentials. JWTs are short-lived credentials that can be signed and verified using a public key in what is known as public-key cryptography.
7
+
8
+ ## Secure Token Service (STS)
9
+ Exchanging credentials from on form to the other is done with a Secure Token Service (STS) function. AWS also provides STS functions not the one we need. Only the other way around: to exchange a JWT to IAM Session which is called [AssumeRoleWithWebIdentity](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html).
10
+ This repo contains a CDK Construct which will deploy a new function which adds the function to exchange an AWS IAM (Session) credential with a signed JWT.
11
+
12
+ ## Solution overview
13
+
14
+ The solution provides 2 endpoints; an OIDC discovery endpoint and a token endpoint. The OIDC discovery endpoint can be used to establish a trust between te STS function and a resource. The token endpoint can be used by client in AWS to exchange their IAM credentials to a JWT.
15
+
16
+ When a client wants to retrieve a JWT key, it will invoke the token API via the API GW. The backing lambda creates a JWT based on the invoking IAM identity and invokes KMS to sign the token.
17
+
18
+ On time based events, EventBridge will trigger a Step function rotation flow. This flow triggers a lambda which in subsequent steps will create a new KMS signing key. Based on that signing key a JWKS is generated and stored in S3 together with discovery files.
19
+
20
+ ![Solution architecture](/doc/sts-jwt-function.drawio.png "Solution architecture")
21
+
22
+ ## Using the construct
23
+
24
+ 1. Init a new typescript CDK project
25
+ `cdk init app --language typescript`
26
+ 2. Config npm to retrieve packages from github package repository
27
+ `echo @alliander-opensource:registry=https://npm.pkg.github.com > .npmrc`
28
+ 3. Install the aws-jwt-sts construct
29
+ `npm install @alliander-opensource/aws-jwt-sts`
30
+ 4. Edit lib/my-sts-stack.ts to add the construct to the stack
31
+ See the comments in the code for possible options
32
+
33
+ ```ts
34
+ import * as cdk from 'aws-cdk-lib';
35
+ import { Construct } from 'constructs';
36
+ import { AwsJwtSts, wafUsage } from '@alliander-opensource/aws-jwt-sts'
37
+
38
+ export class MyStsStack extends cdk.Stack {
39
+ constructor(scope: Construct, id: string, props?: cdk.StackProps) {
40
+ super(scope, id, props);
41
+
42
+ new AwsJwtSts(this, 'sts', {
43
+ /*
44
+ * Mandatory:
45
+ *
46
+ * Set the default aud claim in the jwt, when not specified in the GET param
47
+ */
48
+ defaultAudience: 'api://resourceAudience',
49
+
50
+ /*
51
+ * Optional: when using a custom domain
52
+ *
53
+ * The construct can run on a custom domain, for this the following properties need to be added
54
+ * Ensure a hosted zone is present in the account where the sts function will be deployed
55
+ * Both needed to be set to use the custom domain
56
+ */
57
+ hostedZoneName: 'test.example.com', // domain name of the zone
58
+ hostedZoneId: 'ZXXXXXXXXXXXXXXXXXXXX', // zoneId of the zone
59
+
60
+ /*
61
+ * Optional; when using a custom domain the subdomains of the endpoints can optionally be set
62
+ */
63
+ oidcSubdomain: 'oidc', // default 'oidc' for the discovery endpoint (cloudfront)
64
+ tokenSubdomain: 'token', // default 'token' for the the token api gw endpoint
65
+
66
+ /*
67
+ * Optional:
68
+ *
69
+ * AWS WAF can be applied to the API GW
70
+ * apiGwWaf acceptes the folling values:
71
+ * wafUsage.ConstructProvided to use the WAF defined by the contruct
72
+ * wafUsage.ProvideWebAclArn in combination with the apiGwWafWebAclArn param to specify an already deployed webAcl
73
+ *
74
+ * By not setting apiGwWaf, no WAF will be deployed
75
+ */
76
+ apiGwWaf: wafUsage.ProvideWebAclArn,
77
+
78
+ /*
79
+ * Optional; only applicable if apiGwWaf is set to: wafUsage.ProvideWebAclArn
80
+ *
81
+ * Specify the WebAcl to use for the API GW
82
+ */
83
+ apiGwWafWebAclArn: 'arn:aws:wafv2:{REGION}:{ACCOUNTID}:regional/webacl/{WebAclName}/{WebAclId}',
84
+
85
+ /*
86
+ * Optional:
87
+ *
88
+ * When used in a multi account structure with AWS Organizations specify the organization ID.
89
+ * This sets a resource policy on the API GW Stage so that the whole org may access it
90
+ * When not specified no policy is places on the API GW Stage and it will only allow access from within that account
91
+ */
92
+ orgId: 'o-xxxxxxxxxx'
93
+
94
+ })
95
+ }
96
+ }
97
+ ```
98
+
99
+ 5. Deploy the stack
100
+ `cdk deploy`
101
+
102
+ The stack outputs the urls of the endpoints. So if no custom domain is provided observe the CDK Stack output.
103
+
104
+ ## Using the STS function
105
+ A token from the STS function can be obained by invoking the token endpoint.
106
+ `GET https://$host/token`
107
+ optionally an audience can be provided if this needs to be different than the installed default
108
+ `GET https://$host/token?aud=api://myAudience`
109
+
110
+ > Note: The IAM Role / User invoking the endpoint must have *execute-api:Invoke* permissions
111
+
112
+ In CDK these permission is added as followed:
113
+ ```ts
114
+ role.addToPolicy(new iam.PolicyStatement({
115
+ actions: ['execute-api:Invoke'],
116
+ resources: ['*']
117
+ }))
118
+ ```
119
+
120
+ > Note: keep in mind that *resource '\*'* should only be used if no other API GW's with IAM auth are used in that account.
121
+
122
+ ### Test obtaining a JWT
123
+ 1. Ensure the AWS IAM Role / User invoking the token endpoint has execute-api permissions. If you are using administrator access then that is more than sufficient.
124
+ 2. Use a shell with AWS cli logged in, you can use your cli with which you deployed the stack or use cloudshell for this.
125
+ 3. Install awscurl for authentication
126
+ `pip3 install awscurl`
127
+ 4. Install jwt-cli for jwt formatting
128
+ `npm install -g jwt-cli`
129
+ 5. Invoke the api: `awscurl {your token endpoint}/token --service execute-api --region {your_region} | jq -r .token | jwt decode – `
130
+ 6. Observe the JWT
@@ -0,0 +1,78 @@
1
+ import * as lambda from 'aws-cdk-lib/aws-lambda';
2
+ import * as sns from 'aws-cdk-lib/aws-sns';
3
+ import { Construct } from 'constructs';
4
+ export declare enum wafUsage {
5
+ ConstructProvided = 0,
6
+ ProvideWebAclArn = 1
7
+ }
8
+ export interface AwsJwtStsProps {
9
+ /**
10
+ * defaultAudience which is used in de JWT's
11
+ */
12
+ readonly defaultAudience: string;
13
+ /**
14
+ * HostedZoneId of the domain used for hosting the sts function
15
+ */
16
+ readonly hostedZoneId?: string;
17
+ /**
18
+ * Name of the hostedZone.
19
+ */
20
+ readonly hostedZoneName?: string;
21
+ /**
22
+ * Optional subdomain name of oidc discovery, default: oidc.
23
+ */
24
+ readonly oidcSubdomain?: string;
25
+ /**
26
+ * Optional subdomain name of the token api (on api gw), default: token.
27
+ */
28
+ readonly tokenSubdomain?: string;
29
+ /**
30
+ * If waf needs to be added to the API GW
31
+ *
32
+ * None: no waf is used
33
+ * ConstructProvided: the construct will deploy a wafAcl with opinionated rules
34
+ * ProvideWebAclArn: provide your own arn
35
+ */
36
+ readonly apiGwWaf?: wafUsage;
37
+ /**
38
+ * Arn of the waf webAcl rule to be associated with the API GW
39
+ *
40
+ */
41
+ readonly apiGwWafWebAclArn?: string;
42
+ /**
43
+ * The ID of the AWS Organization 0-xxxx
44
+ *
45
+ */
46
+ readonly orgId?: string;
47
+ /**
48
+ * CPU Architecture
49
+ */
50
+ readonly architecture?: lambda.Architecture;
51
+ /**
52
+ * Optional boolean to specify if key rotation should be triggered on creation of the stack, default: false
53
+ */
54
+ readonly disableKeyRotateOnCreate?: boolean;
55
+ /**
56
+ * Optional custom name for the CloudWatch Alarm monitoring Step Function failures, default: sts-key_rotate_sfn-alarm
57
+ */
58
+ readonly alarmNameKeyRotationStepFunctionFailed?: string;
59
+ /**
60
+ * Optional custom name for the CloudWatch Alarm monitoring 5xx errors on the API Gateway, default: sts-5xx_api_gw-alarm
61
+ */
62
+ readonly alarmNameApiGateway5xx?: string;
63
+ /**
64
+ * Optional custom name for the CloudWatch Alarm monitoring Sign Lambda failures, default: sts-sign_errors_lambda-alarm
65
+ */
66
+ readonly alarmNameSignLambdaFailed?: string;
67
+ /**
68
+ * Optional custom name for the CloudWatch Alarm monitoring Key Rotation Lambda failures, default: sts-key_rotate_errors_lambda-alarm
69
+ */
70
+ readonly alarmNameKeyRotationLambdaFailed?: string;
71
+ }
72
+ export declare class AwsJwtSts extends Construct {
73
+ /**
74
+ * SNS topic used to publish errors from the Step Function rotation flow
75
+ */
76
+ readonly failedRotationTopic: sns.Topic;
77
+ constructor(app: Construct, id: string, props: AwsJwtStsProps);
78
+ }