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
While pursuing an unassisted implementation, a recent custom found the key names unclear and requested clarificiation. We should consider renaming these two keys to align with the standard AWS names:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
TO DO
Determine if this change affects any logic elsewhere in the tool.
Determine if making this change to an existing implementation breaks anything (unlikely but best to confirm).
The ssm_sensitive_values_seqerakit.json contains 3 AWS entries (representing the 3 available fields for an AWS-type credential).
While pursuing an unassisted implementation, a recent custom found the key names unclear and requested clarificiation. We should consider renaming these two keys to align with the standard AWS names:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
TO DO
The text was updated successfully, but these errors were encountered: