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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1160,7 +1160,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1160
1160
1161
1161
-[ ] Amazon SNS with fanout to an SQS queue for each application.
1162
1162
-[ ] Amazon SNS with fanout to an SQS FIFO (first-in, first-out) queue for each application.
1163
-
-[ ] Amazon Kinesis Firehouse.
1163
+
-[ ] Amazon Kinesis Firehose.
1164
1164
-[x] Amazon Kinesis Streams.
1165
1165
1166
1166
**[⬆ Back to Top](#table-of-contents)**
@@ -1249,7 +1249,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1249
1249
1250
1250
### An organization must store thousands of sensitive audio and video files in an Amazon S3 bucket. Organizational security policies require that all data written to this bucket be encrypted. How can compliance with this policy be ensured?
1251
1251
1252
-
-[ ] Use AWS Lambda to send notifications to the security team if unencrypted objects are pun in the bucket.
1252
+
-[ ] Use AWS Lambda to send notifications to the security team if unencrypted objects are put in the bucket.
1253
1253
-[x] Configure an Amazon S3 bucket policy to prevent the upload of objects that do not contain the x-amz-server-side-encryption header.
1254
1254
-[ ] Create an Amazon CloudWatch event rule to verify that all objects stored in the Amazon S3 bucket are encrypted.
1255
1255
-[ ] Configure an Amazon S3 bucket policy to prevent the upload of objects that contain the x-amz-serverside-encryption header.
@@ -3609,7 +3609,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
3609
3609
3610
3610
-[ ] Use Amazon Glue to perform frequent ETL updates from the Accounts database to the Payments database.
3611
3611
-[ ] Use Amazon ElastiCache in Payments, with the cache updated by triggers in the Accounts database.
3612
-
-[ ] Use Amazon Kinesis Data Firehouse to deliver all changes from the Accounts database to the Payments database.
3612
+
-[ ] Use Amazon Kinesis Data Firehose to deliver all changes from the Accounts database to the Payments database.
3613
3613
-[x] Use Amazon DynamoDB Streams to deliver all changes from the Accounts database to the Payments database.
0 commit comments