AWS access for Stacy Wise

[dysbo]

COR Name

Laurene "Reney" Cook

Vendor Onboarding Representative Name

Coforma - Jeff Langworthy

Your Name

Stacy Wise

Your Email

[email protected]

Team, Role, and Company of the target individual

Benefits Management Team II, Tech Lead, Coforma

Product Manager (PM) name and email

Saliha Ghaffar [email protected]

Product Owner (PO) name and email

Amy Lai [email protected]

Desired AWS Access

I am not 100% sure on this as I am pretty new to the org and not super well versed with AWS and its lingo - I need to be able to set up a client ID and an RSA key for use with the benefits-claims Lighthouse API that will be used with the review instances deployed as part of the PR process for vets-api and vets-website.

A lot of the other parameters I'm seeing in the settings file point to /dsva-vagov/vets-api/staging for their values so that may be what I am looking for.

Access Expiration

1/1/2025

E-QIP Transmittal Confirmation

Additional Notes

No response

User must exist in a roster before AWS access can be granted. See AWS access documentation for the steps involved.

• Search for VFS team member in Atlas
• Or search for user on the Platform Team Roster
• If user is on a VFS team but not a team member in Atlas, add the 'NOT YET' label and instruct them to start the Platform orientation process
• If a user is on a Platform team but not on the Platform Team Roster in Confluence, add the 'NOT YET' label and instruct them to reach out to their Product Manager to be added.
• Comment in this issue saying which roster the user is listed in.
• ⚠️ Is production access being requested or extended? Be sure to communicate to the Tier 1 Team that they need to set a reminder for the access expiration ⚠️