AWS access for Ian Harrison

[it-harrison]

COR Name

Ray Wang

Vendor Onboarding Representative Name

Oddball - Amber Malcolm

Your Name

Ian Harrison

Your Email

[email protected]

Team, Role, and Company of the target individual

Design System Team, engineer, Ad Hoc

Product Manager (PM) name and email

Carol Wong / [email protected]

Product Owner (PO) name and email

Matt Dingee / [email protected]

Desired AWS Access

I need to be able to upload / remove a file to the prod-va-gov-assets S3 bucket

Access Expiration

Two weeks from when access is granted.

E-QIP Transmittal Confirmation

Additional Notes

I have a vets-website PR that generates a new file, runtime.entry.js, that must be referenced via a script tag in the head section of every page on va.gov that has a react app/widget on it. I have a content-build PR adds a script tag to the head section to download the file. The problem:

• I merge the vets-website PR which makes https://dev-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/runtime.entry.js, and https://staging-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/runtime.entry.js available
• at this point dev/staging are broken because the script tag is not in the header. I must merge the content-build PR to restore function. however, during the prod build step of content-build CI there is no https://prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/runtime.entry.js because the vets-website PR has not been deployed and therefore content-build CI fails
• I can't let the vets-website PR be deployed to prod until testing dev/staging.

If I can add runtime.entry.js to the bucket after merging the vets-website PR then I should be able to get the content-build PR to pass CI and deploy to dev/staging, after which I can test in dev/staging. Then I can deploy both PRs to prod.

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.

[it-harrison]

@patrick-black-oddball not sure if this is your ticket but wondering if there is any progress here? thanks much!

[flooose]

This request is pretty old. Since access was only requested for two weeks, I'm wondering if the underlying issue might have been resolved otherwise?

[it-harrison]

@flooose you can close this - the issue has been tackled a different way, thanks.