After the secure hash is generated, it’s returned to Amazon Redshift and combined in an Amazon Redshift view. This key is generated and stored by Secrets Manager and should be accessible only to allowed applications. To further secure the hash, keyed hashing is used, which is a faster and simpler alternative to hash-based message authentication code (HMAC). The hashing mechanism used here is the popular BLAKE2 function (available in the Python library hashlib). To generate a hash, Amazon Redshift invokes a scalar Lambda UDF. The first step in the solution is to generate a hash or a message digest of the set of attributes in Amazon Redshift by invoking a Lambda function. The following figure shows the workflow to perform write-backs from QuickSight.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |