update project readme

README.md

@@ -222,7 +222,7 @@ $ docker-compose down
 Running `docker-compose down` will properly stop and terminate the Docker Compose session.
 
 Note: None of the containers are setup by default with volumes and all data will be lost with `docker-compose down`. 
-This is specicaly important to remember regarding the postgres container. If you would like data to be persisted across 
+This is specifically important to remember regarding the postgres container. If you would like data to be persisted across 
 builds locally, update `docker-compose.yaml` to define a volume. 
 
 

internal/platform/tests/main.go

@@ -3,16 +3,17 @@ package tests
 import (
 	"context"
 	"fmt"
-	"geeks-accelerator/oss/saas-starter-kit/internal/schema"
 	"io"
 	"log"
 	"os"
 	"runtime/debug"
+	"strings"
 	"testing"
 	"time"
 
 	"geeks-accelerator/oss/saas-starter-kit/internal/platform/docker"
 	"geeks-accelerator/oss/saas-starter-kit/internal/platform/web"
+	"geeks-accelerator/oss/saas-starter-kit/internal/schema"
 	"github.com/aws/aws-sdk-go/aws/session"
 	"github.com/jmoiron/sqlx"
 )
@@ -79,7 +80,7 @@ func New() *Test {
 			// Make sure the database is ready for queries.
 			_, err = masterDB.Exec("SELECT 1")
 			if err != nil {
-				if err != io.EOF {
+				if err != io.EOF && !strings.Contains(err.Error(), "connection reset by peer") {
 					break
 				}
 				time.Sleep(time.Second)

tools/devops/cmd/cicd/service_deploy.go

@@ -499,6 +499,10 @@ func NewServiceDeployRequest(log *log.Logger, flags ServiceDeployFlags) (*servic
 						Effect: "Allow",
 						Action: []string{
 							"s3:HeadBucket",
+							"s3:ListObjects",
+							"s3:PutObject",
+							"s3:PutObjectAcl",
+							"cloudfront:ListDistributions",
 							"ec2:DescribeNetworkInterfaces",
 							"ec2:DeleteNetworkInterface",
 							"ecs:ListTasks",