Adding Support for EncryptionConfiguration

[VaidSaraswat]

Reason for this change

• Step Functions now supports customer managed KMS key encryption. You can provide a customer managed KMS key to your state machine or activity to encrypt execution data using your own key.
• The CFN schema for AWS::StepFunctions::StateMachine and AWS::StepFunctions::Activity now have a new (optional) field called EncryptionConfiguration

Description of changes

• This change updates the L2 construct for both Activity and StateMachine so that customers can easily create StateMachines/Activities with encryption
• This change is assuming the CFN schema PR will be merged and included in the next release the CDK which will update the L1 constructs for Activity and StateMachine

Description of how you validated changes

• Created unit tests
• Ran the CDK locally and verified CFN templates generated were valid and deployed successfully

Notes:

• I will be removing the schema files attached with this PR after the initial round of feedback is complete (since the new schema has already been publicly released).
• I will be adding integration tests after the initial round of feedback is complete. - I needed to wait for the SDK changes to be released in order to write the assertions.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

[aws-cdk-automation]

Your pull request must be based off of a branch in a personal account (not an organization owned account, and not the main branch). You must also have the setting enabled that allows the CDK team to push changes to your branch (this setting is enabled by default for personal accounts, and cannot be enabled for organization owned accounts). The reason for this is that our automation needs to synchronize your branch with our main after it has been approved, and we cannot do that if we cannot push to your branch.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ The title of this pull request does not follow the Conventional Commits format, see https://www.conventionalcommits.org/.
❌ Pull requests from `main` branch of a fork cannot be accepted. Please reopen this contribution from another branch on your fork. For more information, see https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md#step-4-pull-request.

PRs must pass status checks before we can provide a meaningful review.

If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing Exemption Request and/or Clarification Request.

[aws-cdk-automation]

Your pull request must be based off of a branch in a personal account (not an organization owned account, and not the main branch). You must also have the setting enabled that allows the CDK team to push changes to your branch (this setting is enabled by default for personal accounts, and cannot be enabled for organization owned accounts). The reason for this is that our automation needs to synchronize your branch with our main after it has been approved, and we cannot do that if we cannot push to your branch.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: f9b5d7a
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository