Skip to content

aws

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

aws

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
src
src
 
 
.eslintrc.json
.eslintrc.json
 
 
README.md
README.md
 
 
package.json
package.json
 
 

README.md

AWS Deployment

This directory has code to deploy a containerized version of Bard to Amazon's Elastic Container Service (ECS). This solution allows for a cloud deployment of Bard that's easeier to manage, thanks to the technology offered by AWS.

Setting up the script

First, clone this repo to your local machine. Then navigate to this aws directory and install dependencies with

npm install

Next, create a .env file in the aws directory with the following variables:

AWS_ACCESS_KEY
AWS_SECRET_KEY
AWS_VPC_ID
AWS_SUBNET_ID
AWS_REGION_NAME
AWS_SECURITY_GROUP_ID

Access Keys

AWS_ACCESS_KEY and AWS_SECRET_KEY are the access key and secret key for the Amazon IAM user who will own and pay for the AWS resources the code creates. The IAM user must have the below permission policies applied in order for the script to function. See here for more information on applying permission policies to IAM users

  • AmazonECS_FullAccess
  • AmazonElasticFileSystemFullAccess

VPC and Subnet

AWS_VPC_ID and AWS_SUBNET_ID are the IDs of the Virtual Private Cloud (VPC) and subnet that the AWS resources will be created in. See here for details on creating a VPC with a single public subnet. Once the VPC and subnet have been created, you can find their IDs using the AWS VPC console.

Region name

The name of the AWS region the VPC and subnet specified above are located in. For example, us-east-1.

Security Group

AWS_SECURITY_GROUP_ID is the ID of the security group that will be associated with the AWS resources the code creates. Among other things, Security Groups control how services within the AWS Cloud are able to communicate with each other. This script will apply the same security group to all components it creates, and the script will only work if the security group allows communication for http over all ports. Note that this is NOT a secure configuration: we recommend configuring security groups according to AWS best practices once the app is running. See here for more information on creating and working with security groups.

Running the Script

Once the dependencies have been installed and the .env file is properly configured, execute the code by running

npm run start

Note that the code can take anywhere from 5 to 10 minutes to run.