You are leading a software development team which uses serverless computing with AWS Lambda to build and run applications without having to set up or manage servers. You have a Lambda function that connects to a MongoDB Atlas, which is a popular Database as a Service (DBaaS) platform and also uses a third party API to fetch certain data for your application. You instructed one of your junior developers to create the environment variables for the MongoDB database hostname, username, and password as well as the API credentials that will be used by the Lambda function for DEV, SIT, UAT and PROD environments.

Considering that the Lambda function is storing sensitive database and API credentials, how can you secure these information to prevent other developers in your team, or anyone, from seeing these credentials in plain text?

You can create a new K. M. S key and use it to allow cryptographic assistants using AWS key management to store and encrypt sensitive information.

Explanation:

K. M. S is a computational model that covers more than one server on a local network, which has the power to automatically activate a set of computers that are in the same location and connected to the same network. In summary, a K. M. S key can act as a windows activation server. When a computer is activated by a K. M. S activation key, it will need to be reconnected to a K. M. S host twice a year to renew its activation. This can be very useful for the security of both files and the machine itself.

Regarding the question above, a K. M. S key is the ideal system to be used if you want to protect some information and want to prevent other developers on your team or anyone from seeing your credentials in plain text. To do this, you must create a new K. M. S key and use it to allow cryptographic assistants who use or manage AWS keys to store and encrypt as confidential information.