Posts

Site RDS Instance for Apps

  Site RDS Instance for Apps ================================================== The first step in configuring the back end is to create the database instance to hold the database objects: 1. From the AWS Management Console, select the RDS product link. 2. Click on the Create Database button in the middle of the screen. 3. On the create database page: .....a. Choose the Standard create tile for Database Creation Method. .....b. Choose Amazon Aurora for Engine Option. .....c. For Edition, choose the Amazon Aurora with MySQL compatibility radio button. .....d. Choose Serverless for Capacity Type. .....e. Choose MySQL 5.7 for Version. .....f. Enter a name such as pCluster for DB Cluster Identifier. .....g. Enter admin for Master User Name. .....h. Enter (and re-enter) a password of at least 8 characters. .....i. Accept default Capacity Settings. .....j. Under Connectivity: ..........i. Select Default VPC in the drop-down list and note it on the settings sheet. ..........ii. Select the defa

Site IAM Roles for Serverless

  Site IAM Roles for Serverless ================================================== Set up the IAM role to Access RDS from Lambda 1. From the AWS Management Console, select the IAM product link to get the IAM Management Console. 2. Select Roles from the menu on the left. 3. Click on the Create Role button. 4. Select the AWS Service tile at the top of the screen. 5. Under Use Case, click on the Lambda link and click on the Next: Permissions button. 6. Under the Filter Policies search field, enter the following policy names and then click the check box to the left of the policy found to select them: .....a. AmazonRDSDataFullAccess .....b. AmazonRDSFullAccess .....c. AmazonRDSReadOnlyAccess .....d. AmazonVPCFullAccess .....e. AWSLambdaVPCAccessExecutionRole 7. Click on the Next: Tags button. 8. Add any tags (just searchable key value pairs if you want to categorize your applications that you want) and click on the Next: Review button. 9. Enter Role Name and any description that you want (i

Create API Gateway to the Lambda Function

  Create API Gateway to the Lambda Function ================================================== To set up the API Gateway linked to Lambda function: 1. From the AWS Management Console, select the API Gateway product link to get the API Gateway Management Console. 2. Click on the Create API button. 3. Under the Rest API section, click on the Build button. 4. Click OK on the welcome popup if this is the first time. 5. Select the New API radio button. .....a. Enter an API name (i.e., pApi). .....b. Enter a Description if you like. .....c. For Endpoint Type, choose Regional (note- you have 600 available for basic accounts). .....d. Click the Create API button. 6. On the Actions drop down button in the middle, select Create Method. .....a. Choose the GET option and click the check mark next to it. .....b. Select the Lambda Function radio button for integration type. .....c. Select your region for the Lambda function. .....d. Enter/select your Lambda function name (i.e. appUserService). .....

Create Lambda Serverless Function

  Create Lambda Serverless Function ================================================== To configure the serverless function for this prototype: 1. From the AWS Management Console, select the Lambda product link to get the Lambda Management Console. 2. Select Functions on the left menu. 3. Click the Create Function button. .....a. Choose the Author From Scratch tile. .....b. Under Basic Information, enter function name (i.e., pFunction). .....c. From the Runtime drop-down list, select Python 3.8 or later. .....d. Under Permissions, choose Use Existing Role. .....e. For Existing Role, select the role created under IAM (i.e., appLambdaRole). .....f. For the function created, go to the Configuration tab: ..........1. Choose the VPC selected for the database earlier. ..........2. Choose all Subnets associated with the database created earlier. ..........3. For Security Groups, choose the security group used for the database. .....g. Click the Save button. ===================================

Create Cognito User Pool

  Create Cognito User Pool ================================================== To create an Amazon Cognito User Pool for a REST API, do the following: 1. From the AWS Management Console, select the Cognito to get the Cognito Management Console. 2. Click on the Manage User Pools button. 3. Click on the Create a User Pool button at the top of the screen. …..a. Enter a Pool Name (i.e., pPool) and click the Review Defaults button. …..b. 1st screen- username, allow emails, etc. set. Standard attributes set email, name, etc. the click Next Step button …..c. 2nd screen- password strength & complexity. Key is whether to allow users to sign up or admins only create users. Click Next Step button. .....d. One the third screen, set MFA and email verification as desired and click the Next Step button. .....e. On the remaining screens, click the Next Step buttons and finally click on the Create Pool button. 4. Note the Cognito User Pool Name setting for use configuring your application connection

Create Amplify Web Site

  Create Amplify Web Site ================================================== The AWS Amplify Management Console allows you to configure a web site (URL and options) and also upload the application web pages that people want to use. The steps to configure Amplify for this prototype are as follows: 1. Create a zip file with the web content that you wish to deploy. 2. From the AWS Management Console, select the AWS Amplify product link. .....a. Click on the New App dropdown at the top of the page and select Host Web App option. .....b. Select the Deploy Without Git Provider tile and click the Continue button. .....c. Fill out the Application Name and Environment Name (whatever makes sense such as pApp and release). .....d. Select Method drag and drop. .....e. Choose zip file for the application (proto.zip) downloaded earlier. .....f. Select the Save & Deploy button. 3. You should get a deployment completed successfully message along with the URL for the new site (called Domain on this