COR Name and Vendor Onboarding Representative

Oct 13, 2025 by recoveryshake.com 28 views

Introduction

As a DevOps Engineer at Metrostar, Leigh Villarroel requires access to AWS for the Drupal CMS platform. This access is necessary for the next-build project and the transition to VAEC. In this article, we will outline the steps involved in granting AWS access to Leigh Villarroel and provide additional information to facilitate the process.

COR Name and Vendor Onboarding Representative

The COR (Contracting Officer's Representative) name is Jennifer O'Day, and the Vendor Onboarding Representative name is Paula G. Mendoza from Magnum Opus.

Target Individual Information

The target individual is Leigh Villarroel, a DevOps Engineer at Metrostar. The team, role, and company of the target individual are VACMS, DevOps Engineer, and Metrostar, respectively.

Product Manager and Product Owner Information

The Product Manager (PM) name is Grace Kretschmer, and the email address is mkretschmer@metrostar.com. The Product Owner (PO) name is Erika Washburn, and the email address is Erika.Washburn@va.gov.

Desired AWS Access

Leigh Villarroel requires access to AWS for the Drupal CMS platform. The group is vfs-cms-infrastructure, and the access is ongoing.

E-QIP Transmittal Confirmation

The E-QIP transmittal confirmation is attached as an image. Please see below:

E-QIP Transmittal Confirmation

Additional Notes

Leigh Villarroel needs this access for the next-build project and the transition to VAEC.

User Must Exist in a Roster Before AWS Access Can Be Granted

Before AWS access can be granted, the user must exist in a roster. Please see the 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.
: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:

Conclusion

In conclusion, Leigh Villarroel requires access to AWS for the Drupal CMS platform. The group is vfs-cms-infrastructure, and the access is ongoing. Before AWS access can be granted, the user must exist in a roster. Please follow the steps outlined in the AWS access documentation to facilitate the process.

AWS Access Documentation

For more information on the AWS access request process, please see the AWS access documentation:

Contact Information

If you have any questions or concerns regarding the AWS access request process, please do not hesitate to contact:

Jennifer O'Day (COR)
Paula G. Mendoza (Vendor Onboarding Representative)
Grace Kretschmer (Product Manager)
Erika Washburn (Product Owner)

Leigh Villarroel's Email

Introduction

As a DevOps Engineer at Metrostar, Leigh Villarroel requires access to AWS for the Drupal CMS platform. In this article, we will provide a Q&A section to address any questions or concerns regarding the AWS access request process.

Q: What is the purpose of the AWS access request?

A: The purpose of the AWS access request is to grant Leigh Villarroel access to AWS for the Drupal CMS platform. This access is necessary for the next-build project and the transition to VAEC.

Q: What is the desired AWS access?

A: The desired AWS access is for the Drupal CMS platform, and the group is vfs-cms-infrastructure. The access is ongoing.

Q: What is the E-QIP transmittal confirmation?

A: The E-QIP transmittal confirmation is a document that confirms the E-QIP (Electronic Questionnaire for Investigative Processing) process has been completed. It is attached as an image.

Q: What are the steps involved in granting AWS access?

A: The steps involved in granting AWS access are:

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.
: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:

Q: What is the role of the Product Manager and Product Owner?

A: The Product Manager (PM) name is Grace Kretschmer, and the email address is mkretschmer@metrostar.com. The Product Owner (PO) name is Erika Washburn, and the email address is Erika.Washburn@va.gov. They are responsible for ensuring that the user is added to the correct roster and that the access is granted.

Q: What is the contact information for the AWS access request?

A: The contact information for the AWS access request is:

Jennifer O'Day (COR)
Paula G. Mendoza (Vendor Onboarding Representative)
Grace Kretschmer (Product Manager)
Erika Washburn (Product Owner)

Q: What is the email address of Leigh Villarroel?

A: The email address of Leigh Villarroel is lvillarroel@metrostar.com.

Q: What is the purpose of the Platform orientation process?

A: The purpose of the Platform orientation process is to ensure that the user is familiar with the Platform and its tools. It is a mandatory process for all users who require access to the Platform.

Q: What is the role of the Tier 1 Team?

A: The Tier 1 Team is responsible for ensuring that the access is granted and that the user is added to the correct roster. They are also responsible for setting a reminder for the access expiration.

Conclusion

In conclusion, the AWS access request process involves several steps, including searching for the user in Atlas or the Platform Team Roster, adding the 'NOT YET' label, and instructing the user to start the Platform orientation process. The Product Manager and Product Owner play a crucial role in ensuring that the user is added to the correct roster and that the access is granted. The contact information for the AWS access request is provided above.