Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE).

Part 1 of 5: AWS Code Commit: Creating Git repositories

Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup

Part 3 of 5: AWS Code Commit: Software Developer #1

Part 4 of 5: AWS Code Commit: Software Developer #2

Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference

Here is the cleanup, evidence, and references for the prior 4 parts. After Scott saved the day, the Devops Engineer decided to clean up the environments up. The engineer also took some screenshots as evidence of the environment cleanup, because he knew the pointy-haired team lead didn't read much and enjoyed looking at pictures. Even though Mr. Pointy Hairs doesn't read, the Devops Engineer knew that the lead liked reference links, so the engineer included a link to the vendor documentation on integrating AWS Cloud9 with AWS Code Commit.

5.1: Cleanup

5.1.1: AWS Cloud 9:

5.1.2: AWS Cloud 9: Destroy the AWS Cloud 9 environments for developer #1

5.1.3: AWS Cloud 9: Destroy the AWS Cloud 9 environments for developer #1

5.2: Evidence

5.2.1: AWS Cloud9: Take a screenshot of the Cloud 9 showing just one env

5.2.2: AWS CodeCommit: Take a screenshot of the Code Commit main screen showing both repos

5.2.3: AWS CodeCommit: Take a screenshot of the Code Commit commits screen of the human-gov-application repository showing the commit activity

5.3: Reference

Integrate AWS Cloud9 with AWS CodeCommit - https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-ide-c9.html

If you want to find me, you can catch me, Lewis Lampkin, III at LinkedIn: https://www.linkedin.com/in/lewislampkin

If you want to read my blog: https://www.lewislampkin.com

Comments

Post a Comment

Popular posts from this blog

"This site uses cookies from Google to deliver its services and analyze traffic. Your IP address and user-agent are shared with Google along with performance and security metrics to ensure quality of service, generate usage statistics, and to detect and address abuse."
Read more

Orphaned No More: Adopting AWS Lambda

Image
Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture is fully automated on AWS. The architecture is not ready for go-live. All actions so far are for a proof-of-concept that is presented to the Chief Technical Officer (CTO) for review. During the weekly team meeting, Ko (User Experience Lead) reports that his team has performed thousands of tests against the infrastructure, with moves, adds, and changes, and is not finding any issues in the application user interface. Woo (Infrastructure Lead) reports that there are hundreds of 'orphaned' files in the S3 bucket. (These files are considered 'orphaned' because they do not have corresponding records in the DynamoDB table.) Kim (Tech Lead) reports that there is not a trigger to delete the file from the bucket when a user is deleted from the DynamoDB database. Brady (Lawyer) reports that not deleting t
Read more

Containing the Chaos! | A Three-Part Series Demonstrating the Usefulness of Containerization to HumanGov

Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture requires Amazon Elastic Compute Cloud (EC2) instances that are maintained by the HumanGov systems administrators. The systems administrators handle all the patching, operations, etc. Due to states wanting their data separate from each other, each state gets a separate set of EC2 instances, which means that as the application scales from one state up to 50 states, the systems administrators will have to patch 50x as many EC2 instances. The system administrators report that they have begun to schedule more and more overtime to handle the maintenance windows for updating the EC2 instances. The lead developer remarked that it was taking longer and longer for new application deployments to get rolled out as the infrastructure grew and more states came on board. By the way, the development environment does not have standa
Read more