pattonsgirl / fall2022-ceg3120 Goto Github PK

Currently uses Ubuntu 18.04 - up to 22

Do for 2350 and 2410 as well

Here is a rather heavy hint for how to take on Project 3:

1. Plan on making many stacks while you debug different pieces. I do not recommend changing everything in one go and crossing your fingers.
2. When a stack is successfully created, a set of resources will now exist, just like when you manually created them. You can go look at them, just like when you created them, and check that things like Name have the right value.
   How to tackle some of the tasks:

• You are asked to "Tag" each resource with a Key of Name and a Value of yourlastname-resource (just like when you did this manually). Do this first, test your cf template (create a stack), then go through the menus to check that resources have names.
• I give 4 sample rules in the Security Group section. They are not all good rules. Two are good models since you are also trying to create rules specific to allowing SSH access from trusted places (within subnet / VPC, WSU IPs, and your home ip). Once you think you have good rules, build another stack, look at the securitygroup it created, determine if you were correct (these are the same three rules you manually set in Project 2)
• Picking a private IP. In class, we did some CIDR exercises for midterm review. For one of them, we said what if network prefix was 10.0.0.0 and CIDR was /28, and worked through what range of IPs would be available. The one in the template is not valid was you set the subnet range to 10.0.0.0/28. If you think you got it, build a stack, check there was no error
• Changing hostname and installing software: assuming creating your stack worked (and security group rules are valid), you should have an instance you can SSH in to. If the software installed, you can check its version. If not, something is wrong in your template, and you can use journalctl to find out what happened. Same with hostname change. This is software you installed for Discord bot and a namechange command you needed to do in Project 2. Rebuild stacks until the system is "right" when you SSH in.

Require screenshot include IPs

Should be fixed by using Ubuntu 22, but new stable discord.py is 2.0.1