Best practice to store single value in AWS Lambda : <p>I have a Lambda that is generating and returning a value. This value can expire. Therefore I need to check the values validity before returning.
As generating is quite expensive (taken from another service) I'd like to store the value somehow.</p>

<p>What is the best practice for storing those 2 values (timestamp and a corresponding value)?</p>

<ul>
<li>DynamoDB, but using a database service for 2 values seems to be a lot of overhead. There will never be more items; The same entry will only get updated.</li>
<li>I thought about S3, but this would also imply creating a S3-Bucket and storing one object containing the information, only for this 2 values (but probably the most "lean" way?)</li>
<li>Would love to update Lambdas configuration in order to update the environment variables (but even if this is possible, its probably no best practice?! Also not sure about inconsistencies with Lambda runtimes...)</li>
</ul>

<p>Whats best practice here? Whats the way to go in terms of performance?</p>
