AWS Access For Chelsey Randolph
Introduction
As a Java API Developer on the Lighthouse Team Quokka at Technatomy, Chelsey Randolph requires AWS Console access to develop and maintain the Lighthouse dev portal. This access is essential for her to perform her job duties efficiently. In this article, we will outline the necessary steps to grant Chelsey Randolph AWS access, ensuring compliance with the required documentation and procedures.
COR and Vendor Information
COR Name
- Other - please specify in 'Additional Notes'
- Keith Riley - Keith.Riley@va.gov
Vendor Onboarding Representative Name
- Other - please specify in 'Additional Notes'
- Gary Trio - gary.trio@va.gov
Your Name
- Chelsey Randolph
Your Email
Your Slack Member ID
- U08MBCQ0BN0
Team, Role, and Company of the target individual
- Lighthouse Team Quokka, Java API Developer, Technatomy
Product Manager (PM) name and email
- Nathan Peterson - nathan.peterson2@va.gov
Product Owner (PO) name and email
- Peter Tebbenhoff - peter.tebbenhoff@va.gov
Desired AWS Access
Chelsey Randolph requires AWS Console access for developing and maintaining the Lighthouse dev portal. The desired access level is the same as Krutarth Joshi (Engineering Team Lead - Quokka).
Access Expiration
The access expiration date is set to 12/2028.
E-QIP Transmittal Confirmation
Chelsey Randolph has completed her E-QIP at a previous employer and it was accepted for the VA onboarding. She was told that her PIV could be used in place of it.
Additional Notes
- COR - Keith Riley Keith.Riley@va.gov
- Vendor: Technatomy : Gary Trio gary.trio@va.gov
User Roster Verification
Before granting AWS access, the user must exist in a roster. To verify this, follow the steps outlined in the AWS access documentation.
Search for VFS team member in Atlas
- Search for VFS team member in Atlas
Search for user on the Platform Team Roster
- Or search for user on the Platform Team Roster
Add 'NOT YET' label and instruct user to start the Platform orientation process
- 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
Add 'NOT YET' label and instruct user to reach out to their Product Manager
- 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
- Comment in this issue saying which roster the user is listed in.
Warning: Production access being requested or extended
- :warning: 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 :warning:
Introduction
In our previous article, we outlined the necessary steps to grant Chelsey Randolph AWS access for developing and maintaining the Lighthouse dev portal. In this article, we will address some frequently asked questions (FAQs) related to the AWS access request process.
Q: What is the purpose of the E-QIP transmittal confirmation?
A: The E-QIP transmittal confirmation is a document that confirms Chelsey Randolph's E-QIP status. This is required to ensure that she has completed the necessary security clearance process.
Q: Why is it necessary to verify the user's roster status?
A: Verifying the user's roster status is essential to ensure that Chelsey Randolph exists in a roster before granting her AWS access. This is a requirement to prevent unauthorized access to internal tools.
Q: What is the difference between a VFS team and a Platform team?
A: A VFS team refers to a team that is part of the Veterans Affairs (VA) organization, while a Platform team refers to a team that is part of the Platform team roster. Chelsey Randolph is a member of the Lighthouse Team Quokka, which is a VFS team.
Q: What is the Platform orientation process?
A: The Platform orientation process is a mandatory training program that all new team members must complete before they can access internal tools. This process ensures that team members have the necessary knowledge and skills to use the tools effectively.
Q: What is the role of the Product Manager in the AWS access request process?
A: The Product Manager is responsible for ensuring that Chelsey Randolph is added to the Platform team roster and that she has completed the necessary training programs. They also communicate with the Tier 1 Team to set reminders for the access expiration date.
Q: What is the warning about production access being requested or extended?
A: The warning is to ensure that the Tier 1 Team is aware of the access expiration date and sets a reminder to prevent unauthorized access to production systems.
Q: What are the next steps after verifying the user's roster status?
A: After verifying the user's roster status, the next step is to grant Chelsey Randolph AWS access and ensure that she has completed the necessary training programs.
Q: Who is responsible for granting AWS access to Chelsey Randolph?
A: The Vendor Onboarding Representative (Gary Trio) is responsible for granting AWS access to Chelsey Randolph.
Q: What is the access expiration date for Chelsey Randolph?
A: The access expiration date for Chelsey Randolph is 12/2028.
By addressing these FAQs, we hope to provide a better understanding of the AWS access request process and ensure that Chelsey Randolph receives the necessary access to perform her job duties efficiently.