{"id":1278,"date":"2026-11-10T15:28:57","date_gmt":"2026-11-10T15:28:57","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/?p=1278"},"modified":"2026-11-10T15:28:58","modified_gmt":"2026-11-10T15:28:58","slug":"aws-developer-services-console-lab-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/aws-developer-services-console-lab-guide\/","title":{"rendered":"AWS Developer Services: Console Lab Guide"},"content":{"rendered":"\n
title<\/th>AWS Developer Services: Gold-Standard Console Lab Guide<\/td><\/tr>
subtitle<\/th>CodeCommit \u2022 CodeArtifact \u2022 CodeBuild \u2022 CodeDeploy \u2022 CodePipeline<\/td><\/tr>
author<\/th>Instructor Edition | Browser-Only Labs<\/td><\/tr>
date<\/th>10 November 2026<\/td><\/tr>
lang<\/th>en-US<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Course navigation<\/h2>\n\n\n\n
Lab<\/th>AWS service<\/th>Practical result<\/th><\/tr><\/thead>
1<\/td>CodeCommit<\/strong><\/td>Create a browser-authored repo, branch, PR and merge<\/td><\/tr>
2<\/td>CodeArtifact<\/strong><\/td>Configure a private npm repository and public upstream<\/td><\/tr>
3<\/td>CodeBuild<\/strong><\/td>Resolve dependencies, test, create a deployable ZIP<\/td><\/tr>
4<\/td>CodeDeploy<\/strong><\/td>Deploy the tested ZIP to AL2023 EC2 without SSH<\/td><\/tr>
5<\/td>CodePipeline<\/strong><\/td>Automate commit-triggered build and deployment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Instructor’s quick start<\/h1>\n\n\n\n

Course outcome.<\/strong> Complete five connected, independently verifiable labs that take one small web application from source control through dependency acquisition, automated build and tests, manual deployment, and change-triggered continuous delivery. All user interactions take place in web browsers and the AWS Management Console. Learners never use a terminal, AWS CLI, CloudShell, Session Manager shell, or local Git client.<\/strong> The supplied build and deployment scripts execute automatically inside managed AWS services<\/em>; they are configuration files, not manual lab commands.<\/p>\n\n\n\n

Source starting point.<\/strong> The lab adapts the idea of the official AWS GitHub repository aws-samples\/aws-codedeploy-samples<\/strong>, specifically applications\/SampleApp_Linux<\/strong>, into an Amazon Linux 2023-friendly static website with a meaningful Node.js build using an npm package from CodeArtifact. Original sample: https:\/\/github.com\/aws-samples\/aws-codedeploy-samples\/tree\/master\/applications\/SampleApp_Linux<\/a> . This manual uses a separately provided AWS_Developer_Services_Console_Lab_Source.zip<\/strong>, whose text files are created in CodeCommit through the browser. The GitHub repository is the provenance\/reference; the ZIP is the modernized educational derivative.<\/p>\n\n\n\n

Currency and verification disclosure.<\/strong> Research checked AWS’s publicly available CodeCommit, CodeArtifact, CodeBuild, CodeDeploy, Systems Manager and CodePipeline instructions on 10 November 2026<\/strong>. The source tree, JSON, YAML and shell syntax were inspected offline. AWS account-specific execution, current live console screenshots and end-to-end runtime outcomes have not been verified<\/strong>: no access to a training AWS account was provided, and package installation from npm could not be exercised in the authoring environment. AWS can change field labels, Region availability, defaults and wizard ordering. Follow the named AWS documentation links in the final section whenever a screen differs. No simulated screenshots are presented as real console evidence.<\/p>\n\n\n\n

Important service status.<\/strong> AWS announced on 24 November 2025 that CodeCommit returned to general availability for new customers<\/strong>. Do not follow older training materials claiming it is closed to new customers. Current CodePipeline documentation uses the Build custom pipeline<\/strong> creation choice and a V2<\/strong> pipeline experience. [AWS01][AWS02]<\/p>\n\n\n\n

Architecture at a glance<\/h2>\n\n\n\n
GitHub sample (reference)\n         |\n         v  Copy modernized source files through CodeCommit browser editor\nAWS CodeCommit (main)\n         |\n         +--> CodePipeline Source stage --> CodeBuild Build stage --> CodeDeploy Deploy stage\n                                             |                      |\n                    AWS CodeArtifact <-------+                      v\n                     npm upstream                           Amazon EC2 (AL2023)\n                    [lodash 4.17.21]                          Apache web server\n                                             |\n                               build release ZIP: appspec.yml,\n                               index.html, scripts\/*\n<\/code><\/pre>\n\n\n\n
The same release ZIP is first deployed manually from Amazon S3 during Lab 4<\/strong>. Later, CodePipeline passes CodeBuild’s output artifact directly to CodeDeploy in Lab 5<\/strong>; do not deploy the unbuilt CodeCommit source artifact<\/strong>, because index.html<\/code> contains build-time template placeholders.<\/p>\n\n\n\n
Time, cost and prerequisites<\/h2>\n\n\n\n
Item<\/th>Requirement or recommendation<\/th><\/tr><\/thead>
Course duration<\/td>4\u20136 hours instructor-led; 6\u20138 hours for first-time learners, excluding provisioning delays<\/td><\/tr>
AWS account<\/td>Nonproduction, disposable training account preferred; access to IAM, EC2, CodeCommit, CodeArtifact, CodeBuild, CodeDeploy, CodePipeline, Systems Manager, S3 and CloudWatch<\/td><\/tr>
User permissions<\/td>A training-admin or an approved permission set capable of creating IAM roles\/policies and passing them to AWS services; no root-user access<\/td><\/tr>
Region<\/td>Asia Pacific (Tokyo), ap-northeast-1<\/strong>, throughout; use another common Region only after adapting all Region references<\/td><\/tr>
Network<\/td>Default VPC with at least one public subnet and outbound internet, EC2 auto-assigned public IPv4, Systems Manager connectivity and HTTP\/80 access from learner’s current public IP<\/td><\/tr>
Browser<\/td>Current Chrome, Edge, Firefox or Safari with downloads and clipboard enabled<\/td><\/tr>
Downloads<\/td>AWS_Developer_Services_Console_Lab_Source.zip<\/strong> and this manual; extract ZIP locally using the operating system’s file manager (no terminal)<\/td><\/tr>
Cost<\/td>Not free by default<\/strong>. EC2 compute, EBS, public IPv4, CodeBuild, CodeArtifact, CodePipeline, S3, CloudWatch and requests may incur charges; charges vary by account\/Region\/usage. Clean up same day.<\/td><\/tr>
Security<\/td>Personal training account, least privileges where practical, S3 Block Public Access ON, EC2 TCP\/80 from My IP<\/strong> only, no SSH needed, never store credentials in Git<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Start-of-class gate.<\/strong> Open the AWS account menu, record the 12-digit account ID<\/strong>, and verify the Region Asia Pacific (Tokyo)<\/strong> is displayed in each console. If a default VPC is absent, ask the instructor to supply a VPC with a public subnet and an internet route; do not create a public EC2 target in a private subnet by mistake. All example resource names are illustrative and should be kept consistent throughout.<\/p>\n\n\n\n
Fixed naming worksheet \u2014 complete before opening Lab 1<\/h2>\n\n\n\n
Resource<\/th>Name\/value used in this guide<\/th>Record actual value<\/th><\/tr><\/thead>
Region<\/td>ap-northeast-1<\/td>__________________<\/td><\/tr>
AWS account ID<\/td>12-digit AWS account ID<\/td>__________________<\/td><\/tr>
CodeCommit repository<\/td>awsdevlab-webapp<\/code><\/td>__________________<\/td><\/tr>
CodeCommit branch<\/td>main<\/code><\/td>__________________<\/td><\/tr>
CodeArtifact domain<\/td>awsdevlab<\/code><\/td>__________________<\/td><\/tr>
CodeArtifact downstream repository<\/td>web-npm<\/code><\/td>__________________<\/td><\/tr>
CodeArtifact public upstream<\/td>npm-store<\/code><\/td>__________________<\/td><\/tr>
CodeBuild project<\/td>awsdevlab-web-build<\/code><\/td>__________________<\/td><\/tr>
S3 standalone artifact bucket<\/td>awsdevlab-artifacts-ACCOUNTID-apne1<\/code> (replace ACCOUNTID)<\/td>__________________<\/td><\/tr>
IAM EC2 instance role<\/td>awsdevlab-ec2-role<\/code><\/td>__________________<\/td><\/tr>
IAM CodeDeploy service role<\/td>awsdevlab-codedeploy-role<\/code><\/td>__________________<\/td><\/tr>
EC2 instance Name tag<\/td>awsdevlab-web-ec2<\/code><\/td>__________________<\/td><\/tr>
EC2 security group<\/td>awsdevlab-http-sg<\/code><\/td>__________________<\/td><\/tr>
CodeDeploy application<\/td>awsdevlab-web-app<\/code><\/td>__________________<\/td><\/tr>
CodeDeploy deployment group<\/td>awsdevlab-web-ec2<\/code><\/td>__________________<\/td><\/tr>
CodePipeline pipeline<\/td>awsdevlab-web-pipeline<\/code><\/td>__________________<\/td><\/tr>
CodePipeline artifact bucket<\/td>Created by pipeline wizard; record later<\/td>__________________<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Naming note.<\/strong> S3 bucket names are globally unique. If the proposed bucket name is unavailable, append a short suffix and update every reference to that bucket. Avoid changing the fixed CodeArtifact names unless you also edit buildspec.yml<\/code> through CodeCommit’s browser editor.<\/p>\n\n\n\n
\n\n\n\n
Lab 1 \u2014 AWS CodeCommit: store and review the application<\/h1>\n\n\n\n
Objective.<\/strong> Create a Git repository, populate it with the modernized GitHub-derived application, browse commit history, and complete one browser-only branch and pull request workflow.<\/p>\n\n\n\n
Before you begin.<\/strong> Sign in with the assigned training IAM Identity Center role or IAM identity; Region is ap-northeast-1<\/code>. Download and extract the provided source ZIP using the graphical file manager. Have a name and contact email available for commit metadata (not credentials).<\/p>\n\n\n\n
1.1 Create the repository<\/h2>\n\n\n\n
    \n
  1. In the AWS Console search bar, search\u00a0CodeCommit<\/strong>\u00a0and open the service (direct link:\u00a0https:\/\/console.aws.amazon.com\/codecommit\/<\/a>\u00a0).<\/li>\n\n\n\n
  2. Check the Region selector in the top bar: choose\u00a0Asia Pacific (Tokyo)<\/strong>.<\/li>\n\n\n\n
  3. In the left navigation choose\u00a0Repositories<\/strong>; select\u00a0Create repository<\/strong>.<\/li>\n\n\n\n
  4. In\u00a0Repository name<\/strong>, enter\u00a0awsdevlab-webapp<\/code>.<\/li>\n\n\n\n
  5. In\u00a0Description<\/strong>, enter\u00a0Browser-only AWS developer tools training application<\/code>.<\/li>\n\n\n\n
  6. Keep repository encryption at the AWS-managed\/default setting offered by your account. Do not configure CodeGuru or optional integrations for this lab unless your console mandates a setting.<\/li>\n\n\n\n
  7. Choose\u00a0Create<\/strong>. Wait for the new repository’s detail page to open.<\/li>\n\n\n\n
  8. Select its\u00a0Code<\/strong>\u00a0view. An empty-repository prompt is expected: there is no default branch until your first browser-created commit.<\/li>\n<\/ol>\n\n\n\n
    Checkpoint CC-1:<\/strong> Repositories lists awsdevlab-webapp<\/code>. Copy its HTTPS clone URL only as reference; do not open a terminal or clone it<\/strong>.<\/p>\n\n\n\n
    1.2 Add the application using only the CodeCommit web editor<\/h2>\n\n\n\n
      \n
    1. From the repository’s\u00a0Code<\/strong>\u00a0tab, choose\u00a0Add file \u2192 Create file<\/strong>. Open\u00a0README.md<\/code>\u00a0from the extracted source folder in a graphical text editor; copy all its contents into the CodeCommit editor; enter\u00a0File name<\/strong>\u00a0README.md<\/code>.<\/li>\n\n\n\n
    2. Fill\u00a0Author name<\/strong>,\u00a0Email address<\/strong>, and\u00a0Commit message<\/strong>\u00a0(for example,\u00a0Add lab README<\/code>). Select\u00a0Commit changes<\/strong>. The console creates the\u00a0main<\/code>\u00a0branch for the first commit in a new repository.<\/li>\n\n\n\n
    3. Return to the repository’s\u00a0Code<\/strong>\u00a0tab and confirm the branch drop-down shows\u00a0main<\/strong>. For each file below, repeat\u00a0Add file \u2192 Create file<\/strong>, paste the file’s text, enter its exact path in\u00a0File name<\/strong>, provide the same author\/email and a meaningful commit message, then choose\u00a0Commit changes<\/strong>:File name to create in CodeCommitPurposeindex.html<\/code>Site HTML template and first visible release labelpackage.json<\/code>Pinned npm dependency and build\/test scriptsbuildspec.yml<\/code>CodeBuild phases, CodeArtifact login and release-artifact selectionappspec.yml<\/code>CodeDeploy file mapping and lifecycle eventsscripts\/install_dependencies<\/code>Install Apache and curl on Amazon Linux 2023scripts\/start_server<\/code>Start and enable Apachescripts\/stop_server<\/code>Graceful stop before later deploymentsscripts\/validate_server<\/code>Local service and HTTP content verificationtests\/verify-source.cjs<\/code>Automated source checkstools\/build-release.cjs<\/code>Build release HTML and stage deployment package<\/li>\n\n\n\n
    4. For nested names,\u00a0type the entire relative path<\/strong>\u00a0such as\u00a0scripts\/start_server<\/code>\u00a0in the\u00a0Create file<\/strong>\u00a0dialog; AWS’s CodeCommit training tutorial documents this browser-only folder-creation method. Do not flatten paths to the root. [AWS03]<\/li>\n\n\n\n
    5. Verify the repository tree shows\u00a0README.md<\/code>,\u00a0index.html<\/code>,\u00a0package.json<\/code>,\u00a0buildspec.yml<\/code>,\u00a0appspec.yml<\/code>, and folders\u00a0scripts\/<\/code>,\u00a0tests\/<\/code>,\u00a0tools\/<\/code>.<\/li>\n\n\n\n
    6. Open\u00a0buildspec.yml<\/code>\u00a0in CodeCommit and verify the\u00a0domain<\/strong>\u00a0is\u00a0awsdevlab<\/code>, the\u00a0repository<\/strong>\u00a0is\u00a0web-npm<\/code>, and\u00a0artifacts.base-directory<\/code>\u00a0is\u00a0release<\/code>.<\/li>\n\n\n\n
    7. Open\u00a0appspec.yml<\/code>\u00a0and verify it is located at the\u00a0repository root<\/strong>, includes\u00a0ValidateService<\/code>, and installs\u00a0\/index.html<\/code>\u00a0to\u00a0\/var\/www\/html\/<\/code>.<\/li>\n\n\n\n
    8. Select\u00a0Commits<\/strong>\u00a0or\u00a0History<\/strong>\u00a0in the repository navigation to confirm each browser-created file produced a commit on\u00a0main<\/code>.<\/li>\n<\/ol>\n\n\n\n
      Important:<\/strong> Uploading the entire ZIP<\/strong> as one CodeCommit repository file does not<\/strong> unpack it into Git. Use the Create file<\/strong> editor separately for the listed file paths. This is deliberately slower than Git push but honors the browser-only requirement. Never paste the ZIP’s binary data into the editor.<\/p>\n\n\n\n
      1.3 Practice branching, review and merge entirely in CodeCommit<\/h2>\n\n\n\n
        \n
      1. Select\u00a0Branches<\/strong>\u00a0in the repository. Choose\u00a0Create branch<\/strong>\u00a0(the exact control may be under the\u00a0Branches<\/strong>\u00a0view).<\/li>\n\n\n\n
      2. Set\u00a0Branch name<\/strong>\u00a0feature\/lab-banner<\/code>\u00a0and\u00a0Branch from<\/strong>\u00a0main<\/code>; select\u00a0Create branch<\/strong>.<\/li>\n\n\n\n
      3. Return to\u00a0Code<\/strong>, select branch\u00a0feature\/lab-banner<\/code>, and open\u00a0index.html<\/code>.<\/li>\n\n\n\n
      4. Select\u00a0Edit<\/strong>, locate the visible sentence\u00a0Five services. One end-to-end delivery workflow.<\/code>, and replace it with\u00a0Source control review completed. Ready for CI\/CD.<\/code>\u00a0Leave\u00a0<%- releaseLabel %><\/code>\u00a0and\u00a0<%- builtAt %><\/code>\u00a0placeholders untouched.<\/li>\n\n\n\n
      5. Enter a meaningful commit message such as\u00a0Update demo banner in feature branch<\/code>; choose\u00a0Commit changes<\/strong>. Confirm that\u00a0main<\/code>\u00a0still has the original text and\u00a0feature\/lab-banner<\/code>\u00a0has the update.<\/li>\n\n\n\n
      6. Go to\u00a0Pull requests \u2192 Create pull request<\/strong>. Select\u00a0Source<\/strong>\u00a0feature\/lab-banner<\/code>\u00a0and\u00a0Destination<\/strong>\u00a0main<\/code>.<\/li>\n\n\n\n
      7. Review the diff. Enter title\u00a0Update training website banner<\/code>\u00a0and a description of the change; choose\u00a0Create pull request<\/strong>.<\/li>\n\n\n\n
      8. In the pull request, review the\u00a0Changes<\/strong>\u00a0tab, add a review comment if available, then choose\u00a0Merge<\/strong>. Select a permitted merge strategy (for a simple, conflict-free example choose\u00a0Fast forward<\/strong>\u00a0if offered), confirm the destination is\u00a0main<\/code>, and complete the merge.<\/li>\n\n\n\n
      9. Return to branch\u00a0main<\/code>\u00a0and open\u00a0index.html<\/code>. Confirm the updated sentence is present and the pull request is merged\/closed.<\/li>\n<\/ol>\n\n\n\n
        Checkpoint CC-2:<\/strong> A named feature branch, a reviewed and merged pull request, and the modified file on main<\/code> are visible in the CodeCommit console. If required by an organizational approval rule, ask another authorized learner to approve instead of bypassing governance.<\/p>\n\n\n\n
        Lab 1 evidence to capture<\/h3>\n\n\n\n