AWS key-value store configuration

[itowlson]

• @ogghead (can't add you as a reviewer but would appreciate any comments you have - thanks!)

Content must go through a pre-merge checklist.

Pre-Merge Content Checklist

This documentation has been checked to ensure that:

• The title, template, and date are all set
• Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
• File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep $'\r' | wc -l and expect 0 as a result)
• Has passed bart check
• Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
• Headings are using Title Case
• Code blocks have the programming language set to properly highlight syntax and the proper copy directive
• Have tested with npm run test and resolved all errors
• Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

[ogghead]

Just one tiny change for clarity, thank you for creating this!

[ogghead]

lgtm! Thank you for adding this!

[ogghead]

Does this PR need any additional work @itowlson? Seems like it failed build due to unrelated changes

[itowlson]

@ogghead Yeah those links are fixed on main and I will force bypass them when the time comes. I don't believe any more work is needed; it remains open because we hold off merging feature content until the feature is in a release (because merging auto publishes), and I believe AWS KV didn't quite make it into 3.0.

[ogghead]

it remains open because we hold off merging feature content until the feature is in a release (because merging auto publishes), and I believe AWS KV didn't quite make it into 3.0.

That makes sense, thank you for the context!