Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
22
contributors
Commits on Dec 10, 2021
-
fix(glue): remove
batchDeletePartitionfromgrantRead()permissio……ns (#17941) It is convention in the CDK to expose the underlying `grant()` API to make it simple for users to grant custom permissions to their resource. In addition, this PR removes 'glue:BatchDeletePartition' from `readPermissions`, which was previously erroneously added. closes #17935 and #15116. BREAKING CHANGE: the grantRead API previously included 'glue:BatchDeletePartition', and now it does not. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(logs): log retention fails with OperationAbortedException (#17688)
Fixes: #17546 This adds to the fix in #16083 that was addressing the issue where the LogRetention Lambda can be executed concurrently and create a race condition where multiple invocations are trying to create or modify the same log group. The previous fix addressed the issue if it occurred during log group creation, in the `createLogGroupSafe` method, but did not account for the same problem happening when modifying a log group's retention period in the `setRetentionPolicy` method. This fix applies the same logic from the last fix to the other method. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
chore: update contract for registerContextProvider (#17954)
We're trialling open context providers internally. Not ready yet to call this a public API but we will maintain firmer guarantees on this function going forward. Issues already uncovered by doing this that the more general open framework will have to deal with: * `SdkProvider` would need to be open and stable * What if the provider doesn't need account/region? * Schema validation in query and response * Side channel instructions to the context framework * (not to mention: how will the code get on the user's machine?) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(aws-applicationautoscaling): enabling autoscaling for ElastiCach…
…e Redis cluster (#17919) Following the recently released support for autoscaling in ElastiCache Redis cluster, I'd like to use CDK in order to manage the infrastructure. The only required change is to introduce a new enum value for 'elasticache' key ([cloudformation doc](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-applicationautoscaling-scalabletarget.html#cfn-applicationautoscaling-scalabletarget-servicenamespace)), however to improve dev experience I've introduced three new `PredefinedMetricType` following [cloudformation docs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-predefinedmetricspecification.html#cfn-applicationautoscaling-scalingpolicy-predefinedmetricspecification-predefinedmetrictype) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
-
feat(cli): Hotswapping Support for S3 Bucket Deployments (#17638)
This PR adds hotswap support for S3 Bucket Deployments. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(cli): hotswapping StateMachines with a name fails (#17892)
Before, when the `stateMachineName` property was used, the value of `stateMachineName` was passed directly to the SDK where an ARN was required. Now, when the `stateMachineName` property is used, we construct the ARN from its value, and pass that ARN to the SDK. Closes #17716 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Commits on Dec 11, 2021
-
feat(iotevents): add IoT Events input L2 Construct (#17847)
This is proposed by #17711. This PR was created for implemeting `Input` L2 Construct. Implementing it is needed before `DetectorModel`. The reason is described in here: #17711 (comment) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(aws-autoscaling): notificationTargetArn should be optional in Lif…
…ecycleHook (#16187) This makes the notificationTargetArn optional in LifecycleHook. CloudFormation docs specify it as optional [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-as-lifecyclehook.html). Closes #14641. To achieve this, the `role` parameter was made optional. To avoid breaking users, a role is provided if users specify a `notificationTarget` (which they currently all do, as it is a required property) and is not provided otherwise. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Commits on Dec 13, 2021
-
feat(aws-ecs): expose environment from containerDefinition (#17889)
Closes #17867 * Assigned props.environment to a public readonly member * Added integration test that confirms the environment can be appended after the task is instantiated Made 2 cosmetic, but no obvious changes. Environment values are specified: name: value name2: value But in the test and the README.md files the sample values were: name: something value: something else This is using the string 'value" as a key - which, as someone reading the code for the first time, was confusing. So I changed the sample values to more clearly display what's a key and what's a value. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(lambda): add cloudwatch lambda insights arm support (#17665)
Adding builtin support for the new ARM64 CloudWatch insights Lambda layers which were [announced](https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-cloudwatch-lambda-insights-functions-graviton2/) yesterday. also fixes #17133 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(aws-s3): add support for BucketOwnerEnforced to S3 ObjectOwnersh…
-
feat(cfnspec): cloudformation spec v51.0.0 (#17955)
Closes #17943. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(ec2): add high memory instances u-6tb1, u-9tb1, u-12tb1, u-18tb1…
…, and u-24tb1 (#17964) `u-6tb1`,`u-9tb1`, `u-12tb1` blog post: https://aws.amazon.com/blogs/aws/now-available-amazon-ec2-high-memory-instances-with-6-9-and-12-tb-of-memory-perfect-for-sap-hana/ `u-18tb1` `u-24tb1` blog post: https://aws.amazon.com/blogs/aws/ec2-high-memory-update-new-18-tb-and-24-tb-instances/ ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(custom-resources): assumedRole from AwsCustomResource invocation …
…leaked to next execution (#15776) Fixes #15425 Credit to @nicolai-shape for proposing the fix itself. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(ec2): add d3 and d3en instances (#17782)
`d3` and `d3en` storage optimized instances: https://aws.amazon.com/blogs/aws/ec2-update-d3-d3en-dense-storage-instances/   CFN docs have already been updated: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-instancetype ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(ec2): add im4gn and is4gen instances (#17780)
Newly announced `im4gn` and `is4gen` storage optimized instances: https://aws.amazon.com/blogs/aws/new-storage-optimized-amazon-ec2-instances-im4gn-and-is4gen-powered-by-aws-graviton2-processors/   CFN docs have already been updated: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-instancetype ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
chore(rds): add MariaDB 10.5.13, 10.4.22, 10.3.32, 10.2.41 and Aurora…
… MySQL 3.01.0 (#17959) Add new RDS versions: **MariaDbEngineVersion 10.5.13, 10.4.22, 10.3.32 and 10.2.41** [Announcement](https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-rds-mariadb-supports-new-minor-versions/) **AuroraMysqlEngineVersion 3.01.0** [Announcement](https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-aurora-mysql-8-0/) Version informations retrieved from CLI command: `aws rds describe-db-engine-versions --region us-east-1 --engine aurora-mysql --engine-version 8.0` Deployment tested successfully: ```ts new rds.DatabaseCluster(this, 'DatabaseCluster', { engine: rds.DatabaseClusterEngine.auroraMysql({ version: rds.AuroraMysqlEngineVersion.VER_3_01_0 }), instanceProps: { instanceType: ec2.InstanceType.of(ec2.InstanceClass.R5, ec2.InstanceSize.XLARGE), vpc, }, removalPolicy: RemovalPolicy.DESTROY, }); ``` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(apigateway): add option to set the base path when adding a domai…
…n name to a Rest API (#17915) If a domain name has an empty base path mapping, API Gateway does not allow the creation of additional base path mappings. The problem is that `addDomainName` always creates an empty base path mapping, preventing users to add their own afterwards. Add a property to define a base path mapping at the same time as adding the domain name. Fixes #9581. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Commits on Dec 14, 2021
-
feat(aws-applicationautoscaling): Allow autoscaling with "M out of N"…
… datapoints (#17441) This PR closes #17433. It adds a `datapointsToAlarm` property to the `StepScalingPolicy` construct which allows auto-scaling activities to trigger when only a portion of the data points in the evaluation periods are breaching. Motivation: Some metrics may have a certain amount of noise/randomness and in these cases it may make more sense to not require that all data points must be breaching for auto-scaling activity to trigger. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(appmesh): adding support with gateway route priority (#17694)
Adding the Gateway Route `Priority` support. This is not a new feature but it was missed from the implementation. The implementation method is mimicking how Route's `Priority` is implemented: - [route-spec.ts](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-appmesh/lib/route-spec.ts) - [route.ts](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-appmesh/lib/route.ts) Fixes #16821 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
chore(appsync): fixed indentation of the query template (#17975)
---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(cli): asset publishing broken cross account (#18007)
In #17668, cross-account S3 asset publishing was broken. The reason is that the `account()` function was always broken, using the default account instead of the target account. However, previously this function was only called in an irrecoverable situation anyway, and its failure would be rare. The recent change also calls this function for logging purposes in a happy-case scenario, but then triggers an error during the logging. Fix the invocation to use the right account. Fixes #17988. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(aws-lambda-nodejs): use closest lockfile when autodetecting (#16629)
fixes #15847 A bug in the automatic lockfile finding logic causes lockfiles higher in the directory tree to be used over lower/closer ones. This is because the code traverses the tree once per lockfile type in series, stopping when it finds one: https://github.com/aws/aws-cdk/blob/58fda9104ad884026d578dc0602f7d64dd533f6d/packages/%40aws-cdk/aws-lambda-nodejs/lib/function.ts#L137-L139 This updates the code to traverse the tree once looking for all the lockfile types at the same time and stop when one or more is found. If multiple are found at the same level, an error is thrown (per #15847 (comment)). ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
chore(ubergen): tell users about experimental package (#18012)
When ubergen generate a barebones README for an experimental package's stable variant, add in a paragraph that directs users to the experimental library so they have an easier time finding it. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(amplify): Add Amplify asset deployment resource (#16922)
This change adds a custom resource that allows users to publish S3 assets to AWS Amplify. fixes #16208 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(apigatewayv2): Lambda authorizer for WebSocket API (#16886)
closes #13869 By this PR, you will be able to enable WebSocket authorizer as the below code: ```ts const integration = new LambdaWebSocketIntegration({ handler, }); const authorizer = new WebSocketLambdaAuthorizer('Authorizer', authHandler); new WebSocketApi(stack, 'WebSocketApi', { connectRouteOptions: { integration, authorizer, }, }); ``` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
fix(appsync):
ttlproperty ofCachingConfigis not required (#17981)According to the current CloudFormaton spec for [AWS::AppSync::Resolver CachingConfig][1], the `Ttl` property is not required. But if it's not provided, the deploy will fail with the message: > TTL value cannot be smaller than 1 second and larger than 3600 seconds. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException The AppSync team has confirmed that the property is indeed required and they will push a change to the spec. This change is proactively making the property required on the CDK. Fixes #17925. BREAKING CHANGE: The `CachingConfig#ttl` property is now required. [1]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-appsync-resolver-cachingconfig.html#cfn-appsync-resolver-cachingconfig-ttl ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
-
feat(codecommit): allow initializing a Repository with contents (#17968)
This repo introduces new properties to the constructor signature of the codecommit L2 Repository. It allows users to upload code when creating a codecommit repository by leveraging the aws-s3-assets lib. The user is able to upload whole directories at the moment. The behaviour has a unit tests, and an integration test, which is passing (verified manually as well). Closes #17967, provides a possible fix to #16958 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Commits on Dec 15, 2021
-
fix(rds): unable to use tokens as port in
DatabaseInstance(#17995)In `DatabaseInstance` the port number can be specified using data type number. If a token value (e.g. CloudFormation Parameter) was used here, the token was not resolved correctly. The conversion of property `port` has been corrected by using method `Tokenization.stringifyNumber()`. Fixes #17948. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
There are no files selected for viewing