Vets-api terminal access for Drew Fisher

[cilestin]

Your Name

Drew Fisher

Your GitHub handle (terminal access is managed through GitHub)

@cilestin

Your dsvagovcloud AWS user name (if applicable)

Drew.Fisher

Team, Role, and Company of the target individual

Engineering Crew Lead, Lighthouse Benefits & Appeals APIs @ Ad Hoc

Product Manager (PM) name and email

Janet Coutinho, janet.coutinho@va.gov

Product Owner (PO) name and email

Andrew Ramos, ramos_andrew@bah.com

COR Name (leave "None" if you listed an AWS user name above)

None

Vendor Onboarding Representative (VOR) Name (leave "None" if you listed an AWS user name above)

None

Please confirm if you are listed as a team member in Atlas or are listed in Platform Team Roster

• Team Member in Atlas
• Platform Team Roster

Please confirm E-QIP Transmittal/Adjudication. This could be a screenshot of your Transmittal/Adjudication email, a link to another request where you've submitted this proof (i.e. AWS/SOCKS), etc.

• I have attached proof that I have either transmitted my E-QIP survey or previously received a favorable decision (by including in "Additional Notes" section below)

ArgoCD terminal access requested for the following environments

• dev
• staging
• sandbox
• production (if requesting, justify prod access in 'Additional Notes' section)

Additional Notes

eQIP proof @ #104186

I will need ongoing access as I am one of the on-call production support personnel for the Lighthouse Benefits & Appeals APIs.

Additional resources for Support Engineer

• For users on a VFS team but not listed as a team member in Atlas, they must start the Platform orientation process
• Instructions for handling requests here - Support Only

[lindsay-insco]

User found in Atlas.
Transmittal notice verified here

[lindsay-insco]

@cilestin You’ve been granted access to the dev, staging, and sandbox environments. Access to prod is pending approval by OCTODE, and we'll update you as soon as it's available.

Here's some additional documentation for Vets API on EKS.