-
Notifications
You must be signed in to change notification settings - Fork 3
AWS diagnostics and triage guide
How do you find production or development resources and logs? Look no further!
The steps for introspecting resources are the same in both dev and prod. When you sign into AWS you will be asked to pick a role (either development or production). You will only see resources in AWS for the environment that matches the role you picked.
- Sign into AWS and select the appropriate user role for the environment you want to inspect
- Find our bastion EC2 server
- Go to AWS EC2 -> Instances -> filter by tag
nu:application=dailp-app
-> Click instance ID
- Connect using the "Session Manager" to get a shell in the browser
- Connect -> Session Manager -> Connect
- Check if
psql
exists withwhich psql
- (optional) Install
psql
to the Bastion server if needed
sudo amazon-linux-extras install postgresql14
- Connect to the database. Password should be retrieved from Naomi or another developer
psql -h dailp-database-primary.crrytz26uak5.us-east-1.rds.amazonaws.com -p 5432 -U dailp -W
If you go to the "Monitor" tab and select "Logs" and then select a time range, you can see logging info.
- Naomi
Our website is hosted using AWS Amplify. The site is "pre-rendered" at build time and then statically hosted. All routes for the site need to use the prerender
Vite function to specify which routes exist. Currently, prerendering is used only to document which routes exist, not to fully populate the page (because our content is dynamic). You can see logs for the deployment and prerendering process by going to the Amplify console and inspecting our dailp-app
project.