AWS access for Casey Williams

[caseywilliams]

COR Name

Courtney Bethea

Vendor Onboarding Representative Name

Liberty IT - Michael G. Lovejoy

Your Name

Casey Williams

Your Email

casey.williams@adhocteam.us

Team, Role, and Company of the target individual

Backend engineer on Lighthouse Appeals APIs team (Banana Peels), Ad Hoc LLC

Product Manager (PM) name and email

Michael Hobson (michael.hobson@adhocteam.us)

Product Owner (PO) name and email

Janet Coutinho (janet.coutinho@va.gov)

Desired AWS Access

I need access to the rails console for vets-api in all environments so that I can help with questions from support. Currently, I seem to have access to the lower environments, but not production. For reference, my teammates are Kristin Brown, Michel McDonald, and Matt Kelly (although I am not sure that Matt has prod access himself).

Access Expiration

ongoing

E-QIP Transmittal Confirmation

Additional Notes

I need access to the rails console for development work on the Decision Reviews, Appeals Status, Benefits Intake, and Forms APIs on Lighthouse. My team is expected to provide production support for these APIs - I was recently unable to help with a production issue because my access had expired or been removed.

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

• [x] Search for user on the VFS Team Roster
• [ ] Or search for user on the Platform Team Roster
• [ ] If user is on a VFS team but not in the VFS Team Roster, 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.
• [x] Comment in this issue saying which roster the user is listed in.

[patrick-black-oddball]

Found of VFS team roster

[JonathanKamensDVA]

Approved.

[patrick-black-oddball]

Access provided

[lindsay-insco]

User @caseywilliams initially intended to request for VetsAPI Prod access as evidenced in #74016