You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,22 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
## 1.1.0 - 2024-10-25
6
+
### Added features
7
+
- Added the ability to define an optional KMS Key for the target buckets in the configuration files. This allows you to set up a default encryption with KMS on the target buckets.
8
+
- Added KMS Encryption for the reporting bucket with a new dedicated key.
9
+
- Added the ability to define Permission Boundaries for all the created roles.
10
+
11
+
### Changed
12
+
- Modified `transfer_sync_service_stack` and how the lambda layer is created for boto3.
13
+
- Centralized all the solution parameters in `configuration/solution_parameters/parameters.json`.
14
+
- Updated CLI to support the new KMS Configuration.
15
+
16
+
### Dependencies
17
+
- Bump lambda-powertools from 2.40.1 to 3.2.0.
18
+
- Bump boto3 from 1.34.134 to 1.35.47 for lambda layers and environment.
19
+
- Bump cdk-monitoring-constructs from 8.1.0 to 8.3.2.
Copy file name to clipboardExpand all lines: README.md
+23-2Lines changed: 23 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ A combination of Lambda, Step Functions and Transfer Family features facilitates
45
45
- The connector uses the configured security policy, trusted public keys and secrets stored in AWS Secrets Manager to ensure secure communication with the remote server.
46
46
47
47
4.**S3 Buckets**
48
-
- Only one bucket is created by this solution to store the results generated by the Transfer Family SFTP Connector when Listing the remote SFTP directories.
48
+
- Only one bucket is created by this solution to store the results generated by the Transfer Family SFTP Connector when Listing the remote SFTP directories. This bucket is encrypted using a KMS Customer managed keys created by the solution.
49
49
- The solution can use as many S3 Buckets as needed for a target for the Transfer Family SFTP Connector Sync process, when the files are copied from the remote SFTP to local the local S3 Bucket. These S3 Buckets are defined in the Configuration Files.
50
50
51
51
5.**AWS Secrets Manager**
@@ -81,7 +81,8 @@ The configuration file structure and content needs the following data:
81
81
{
82
82
"LocalRepository": {
83
83
"BucketName": <Local Bucket Name>,
84
-
"Prefix": <Local Prefix>
84
+
"Prefix": <Local Prefix>,
85
+
(OPTIONAL) "KmsKeyArn": <KMS Key ARN used for the Bucket default encryption configuration>
85
86
},
86
87
"RemoteFolders": {
87
88
"Folder": <Remote Folder to Sync>,
@@ -118,6 +119,13 @@ For the Cron expression, you can use any of the pre-defined TAGs for simplicity
118
119
|@saturday| 0 0 ? * 7 * |
119
120
|@every10min| 0/10 * * * ? * |
120
121
122
+
### Target Bucket KMS Encryption
123
+
124
+
The solution supports target S3 Buckets that use [server-side encryption with AWS KMS (SSE-KMS)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/specifying-kms-encryption.html).
125
+
If your target S3 Bucket is encrypted using KMS, you must specify the ARN of the KMS Key used for encryption in your configuration file under: `SyncSettings > LocalRepository > KmsKeyArn`
126
+
127
+
**Note:** The `KmsKeyArn` parameter is optional. **Only include it if your target bucket uses KMS encryption.**
128
+
121
129
### Replaceable Tags in Remote Folder Paths
122
130
123
131
The solution supports the use of replaceable tags in the remote folder paths. This feature allows for dynamic folder selection based on the current date (in UTC). The following tags are available:
@@ -184,6 +192,19 @@ This project is built using Python3 and CDK, before you start, make sure to have
184
192
* Python venv
185
193
186
194
## Deployment
195
+
196
+
### Permission Boundaries
197
+
If you are enforcing the usage of IAM Permission Boundaries for IAM Roles created in the account, you can update the [solution parameters file](configuration/solution_parameters/parameters.json) and add the managed policy ARN you are using to the `permission_boundary_policy_arn` parameter.
198
+
199
+
**Note:**
200
+
- This step is optional. Only add this parameter if you're enforcing IAM Permission Boundaries in your account.
201
+
- Ensure you have the correct ARN for your permission boundary policy.
202
+
- If you're not using permission boundaries, you can omit this parameter or leave it as an empty string.
203
+
204
+
By setting this parameter, all IAM roles created by this solution will adhere to the specified permission boundary, enhancing your security posture and compliance with organizational policies.
0 commit comments