<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS Well-Architected Labs</title><link>https://wellarchitectedlabs.com/</link><description>Recent content on AWS Well-Architected Labs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 31 May 2021 11:16:08 -0400</lastBuildDate><atom:link href="https://wellarchitectedlabs.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploy The Blue Car Application</title><link>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/1_deploy_blue_car_application/</link><pubDate>Mon, 31 May 2021 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/1_deploy_blue_car_application/</guid><description>&lt;p>You will start by deploying the example application which allows a customer to order medical assistance based on selecting a map location. The application consists of a public AWS API gateway which connects to a serverless application layer &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener">AWS Lambda&lt;/a>, which uses &lt;a href="https://aws.amazon.com/dynamodb/" target="_blank" rel="noopener">Amazon DynamoDB&lt;/a> .&lt;/p>
&lt;p>You will also deploy &lt;a href="https://aws.amazon.com/amplify/" target="_blank" rel="noopener">AWS Amplify&lt;/a> to host the static website with CI/CD build-in and &lt;a href="https://aws.amazon.com/cognito/" target="_blank" rel="noopener">Amazon Cognito&lt;/a> to manage users.&lt;/p>
&lt;p>Our deployed architecture should reflect the following diagram:&lt;/p>
&lt;p>&lt;img src="https://wellarchitectedlabs.com/wapartners/100_Automating_Serverless_Best_Practices_with_Dashbird/Images/section1/section1-blue-car-architecture.png" alt="Section1 Base Architecture">&lt;/p></description></item><item><title>Well-Architected Insights</title><link>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/2_well-architected_insights/</link><pubDate>Mon, 31 May 2021 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/2_well-architected_insights/</guid><description>&lt;p>Well-Architected Insights provides serverless developers with insights and recommendations to continually improve their applications and keep them secure, compliant, optimized, and efficient.&lt;/p>
&lt;p>The second section of the lab will demonstrate how to automatically create a role in your AWS account, delegating read-only access to various services in your AWS account. Follow these steps to complete the configuration:&lt;/p>
&lt;h3 id="21-account-onboarding-to-dashbird">2.1. Account Onboarding to Dashbird.&lt;/h3>
&lt;p>If you are new to Dashbird, sign up for a free account in &lt;a href="https://dashbird.io/" target="_blank" rel="noopener">Dashbird.io&lt;/a>.
If you already have an account in Dashbird, go to 2.2.&lt;/p></description></item><item><title>Modern Load Test</title><link>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/3_modern_load_test/</link><pubDate>Mon, 31 May 2021 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/3_modern_load_test/</guid><description>&lt;p>The on-demand nature of the AWS Cloud allows for a production-scale test environment to be deployed in a matter of minutes.&lt;/p>
&lt;p>While AWS serverless services allow for efficient scaling individually, it is important to consider the effect of &lt;a href="https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html" target="_blank" rel="noopener">Service Quotas&lt;/a> at both region and account level. Ignoring these maximum limits can become immediately impactful to a production workload.&lt;/p>
&lt;p>In this section we will perform load testing on our deployed Blue Car application to ensure that the architecture scales in alignment to the traffic which is being processed.&lt;/p></description></item><item><title>Tear down</title><link>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/4_teardown/</link><pubDate>Mon, 31 May 2021 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/well-architected-partners/100_labs/100_automating_serverless_best_practices_with_dashbird/4_teardown/</guid><description>&lt;p>The following steps will remove the services which are deployed in the lab.&lt;/p>
&lt;h3 id="1-delete-cloudformation-stacks">1. Delete CloudFormation stacks&lt;/h3>
&lt;ol>
&lt;li>Go to &lt;strong>aws-well-architected-labs/static/wapartners/100_Automating_Serverless_Best_Practices_with_Dashbird/Code/oncall-health-sample-app&lt;/strong> directory path and run &lt;strong>teardown_script.sh&lt;/strong>.&lt;/li>
&lt;/ol>
&lt;pre tabindex="0">&lt;code>cd aws-well-architected-labs/static/wapartners/100_Automating_Serverless_Best_Practices_with_Dashbird/Code/oncall-health-sample-app
bash teardown_script.sh
&lt;/code>&lt;/pre>&lt;p>&lt;img src="https://wellarchitectedlabs.com/wapartners/100_Automating_Serverless_Best_Practices_with_Dashbird/Images/section4/section4-teardown.png" alt="Section4 Teardown">&lt;/p>
&lt;hr>
&lt;p>&lt;strong>END OF SECTION 4&lt;/strong>&lt;/p>
&lt;hr></description></item><item><title>Create new S3 bucket and add objects to it</title><link>https://wellarchitectedlabs.com/common/documentation/createnews3bucketandaddobjects/</link><pubDate>Fri, 24 Apr 2020 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/common/documentation/createnews3bucketandaddobjects/</guid><description>&lt;h2 id="create-new-s3-bucket">Create new S3 bucket&lt;/h2>
&lt;p>These steps will guide you to create a bucket&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Go to the S3 console at &lt;a href="https://console.aws.amazon.com/s3" target="_blank" rel="noopener">https://console.aws.amazon.com/s3&lt;/a>&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>Create bucket&lt;/strong>&lt;/p>
&lt;/li>
&lt;li>
&lt;p>For &lt;strong>Bucket name&lt;/strong> supply a name. This must be unique across all buckets in AWS&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Tip&lt;/strong>: Name the bucket &lt;em>&lt;code>&amp;lt;first_name&amp;gt;&amp;lt;last_initial&amp;gt;_&amp;lt;date in yyyymmdd format&amp;gt;&lt;/code>&lt;/em> (do NOT include the angle brackets)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>Next&lt;/strong> &lt;em>three&lt;/em> times&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Review screen: click &lt;strong>Create bucket&lt;/strong>&lt;/p>
&lt;/li>
&lt;/ol>
&lt;h2 id="add-objects-to-an-s3-bucket">Add object(s) to an S3 bucket&lt;/h2>
&lt;p>Use these instructions to add one or more objects to an S3 bucket&lt;/p></description></item><item><title>example implementations for CreateNewCloudFormationStack</title><link>https://wellarchitectedlabs.com/common/examples/usecreatenewcloudformationstack/</link><pubDate>Fri, 24 Apr 2020 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/common/examples/usecreatenewcloudformationstack/</guid><description>&lt;ol>
&lt;li>&lt;a href="#case1">Case 1 - all parameters left as default &lt;/a>&lt;/li>
&lt;li>&lt;a href="#case2">Case 2 - provides directions to update or view one or more parameters&lt;/a>&lt;/li>
&lt;/ol>
&lt;h2 id="case1">Case 1 - all parameters left as default&lt;/h2>
&lt;ol>
&lt;li>
&lt;p>Go to the AWS CloudFormation console at &lt;a href="https://console.aws.amazon.com/cloudformation" target="_blank" rel="noopener">https://console.aws.amazon.com/cloudformation&lt;/a> and click &lt;strong>Create Stack&lt;/strong> &amp;gt; &lt;strong>With new resources&lt;/strong>
&lt;img src="https://wellarchitectedlabs.com/Common/images/CreateNewCloudFormationStack/CFNCreateStackButton.png" alt="Images/CFNCreateStackButton">&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Leave &lt;strong>Prepare template&lt;/strong> setting as-is&lt;/p>
&lt;ul>
&lt;li>For &lt;strong>Template source&lt;/strong> select &lt;strong>Upload a template file&lt;/strong>&lt;/li>
&lt;li>Click &lt;strong>Choose file&lt;/strong> and supply the CloudFormation template you downloaded: &lt;em>staticwebapp.yaml&lt;/em>
&lt;img src="https://wellarchitectedlabs.com/Common/images/CreateNewCloudFormationStack/CFNUploadTemplateFile.png" alt="CFNUploadTemplateFile">&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>Next&lt;/strong>&lt;/p></description></item><item><title>Setup AWS credentials and configuration</title><link>https://wellarchitectedlabs.com/common/documentation/aws_credentials/</link><pubDate>Fri, 24 Apr 2020 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/common/documentation/aws_credentials/</guid><description>&lt;ul>
&lt;li>You will supply configuration and credentials used by the AWS CLI and AWS SDK to access your AWS account.&lt;/li>
&lt;/ul>
&lt;h2 id="choose-an-option">Choose an option&lt;/h2>
&lt;p>Select the appropriate option for configuration of your AWS credentials:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="#supplied">&lt;strong>Option 1&lt;/strong>&lt;/a> - Using AWS instructor supplied accounts with Linux-style environment variables&lt;/li>
&lt;li>&lt;a href="#cli">&lt;strong>Option 2&lt;/strong>&lt;/a> - Using AWS CLI&lt;/li>
&lt;li>&lt;a href="#files">&lt;strong>Option 3&lt;/strong>&lt;/a> - Creating configuration files manually&lt;/li>
&lt;li>&lt;a href="#powershell">&lt;strong>Option 4&lt;/strong>&lt;/a> - Using PowerShell commands for Windows&lt;/li>
&lt;/ul>
&lt;h3 id="supplied">Option 1 For instructor supplied AWS accounts&lt;/h3>
&lt;p>If BOTH of the following are true then you may use &lt;strong>Option 1&lt;/strong>&lt;/p></description></item><item><title>Software Install</title><link>https://wellarchitectedlabs.com/common/documentation/software_install/</link><pubDate>Fri, 24 Apr 2020 11:16:08 -0400</pubDate><guid>https://wellarchitectedlabs.com/common/documentation/software_install/</guid><description>&lt;p>This reference will help you install software necessary to setup your workshop environment&lt;/p>
&lt;ol>
&lt;li>&lt;a href="#install-aws-cli">AWS CLI&lt;/a>&lt;/li>
&lt;li>&lt;a href="#jq">jq&lt;/a>&lt;/li>
&lt;/ol>
&lt;h2 id="install-aws-cli">Install AWS CLI&lt;/h2>
&lt;p>The AWS Command Line Interface (AWS CLI) is a unified tool that provides a consistent interface for interacting with all parts of AWS.&lt;/p>
&lt;h3 id="linux">Linux&lt;/h3>
&lt;ul>
&lt;li>
&lt;p>This includes:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>AWS CloudShell&lt;/p>
&lt;/li>
&lt;li>
&lt;p>All native Linux installs&lt;/p>
&lt;/li>
&lt;li>
&lt;p>MacOS&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Windows Subsystem for Linux (WSL)&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Run the following command&lt;/p>
&lt;pre>&lt;code>$ aws --version
aws-cli/1.16.249 Python/3.6.8...
&lt;/code>&lt;/pre>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>AWS CLI version 1.0 or higher is fine&lt;/p></description></item></channel></rss>