Why

The project should integrate with GitHub Actions for code linting and wiki publishing.

Acceptance Criteria

• Publish two workflows
  • Code Linting (Using terraform fmt, tfsec)
  • Wiki

Why

Initialize the project with basic AWS modules. The project should have staging and production environments with isolated configurations.

Acceptance Criteria

• Integrated with AWS cloud service
• Separated environment variables

Do we need an Issue for the following relatively new requirement to the IC:

User and bot accounts for accessing the cloud provider are automatically provisioned. To fine-tune user access, different groups with different roles must be created.
(Setting up the IAM groups, roles, bot & user accounts.)

Also, should we move these issues into a Github Project

Why

Integrate the AWS VPC to manage and secure inbound and outbound traffic to our applications.

Acceptance Criteria

• AWS VCP service is set up for our applications
• VCP is installed with proper network configurations

Why

Integrate the Terraform cloud to help visualize the checks, deployments, and set variables.

Acceptance Criteria

• Terraform Cloud is set and goes live.
• Deployments and Plans can be managed by Terraform cloud
• 3 workspaces should be created:
  • workspace-production: triggers run from main branch and core folder
  • workspace-staging: triggers run from. develop branch and core folder
  • workspace-shared: trigger run from develop branch and shared folder

Why

Setting up AWS S3 can help the application store and retrieve data assets with high performance.

Acceptance Criteria

• AWS S3 service successfully set up
• The application can store/retrieve data

Why

An automation provision would require access from a bot account to access the AWS resources.

Acceptance Criteria

• Groups, roles, bot, and user account should be created and privileged
• The bot can have access to AWS resources

Why

The Infrastructure document helps others have a general and comprehensive knowledge of how our system structures and works.

Acceptance Criteria

• The document should contain detailed system requirements
• The document should list the necessary configuration steps

Why

Monitoring logs is an important process that helps troubleshoot and investigate the application's operation. The application should be integrated with AWS CloudWatch to analyze and identify issues.

Acceptance Criteria

• The AWS CloudWatch successfully sets up and returns the application's running logs.
• The retained logs period is set for a 14 days.

Why

• We need to provide access to a private subnet from an external network

Acceptance Criteria

• We can access one of the running EC2 instances by bastion host

Why

AWS RDS is a fully managed relational database service that supports replication across multi-AZ and guarantees our application can run with high-availability ability.

Acceptance Criteria

• The AWS RDS service is set up and connects with our application
• AWS RDS instances configured to operate in multiple AZ

Why

AWS ElastiCache helps our application improve performance by catching ability.

Acceptance Criteria

AWS ElastiCache is successfully set up and caches requests

Why

AWS ECS Fargate is a fully managed container orchestration service without the need to control every EC2 ourselves.

Acceptance Criteria

• The application is deployed to AWS ECS Fargate.
• ECS Fargate should be configured to operate in 3 ap-southeast AZ with a reasonable threshold to scale-up/scale-down and restart when the application goes down.

Why

Setting up an AWS Application Load Balancer (ALB) is necessary to distribute incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones.

Acceptance Criteria

• Configure the AWS ALB service for the application.
• Ensure that the ALB is set up to operate in multiple Availability Zones.

Why

Our applications have plenty of sensitive variables to manage hence, AWS SSM should be used for

Acceptance Criteria

• The AWS SSM should be set up to store sensitive variables for our applications
• Our application can retrieve secrets from AWS SSM

Why

Integrate the AWS ECR (Elastic Container Registry) to connect with our application to store deployment docker containers.

Acceptance Criteria

• AWS ECR service should be up and ready to connect with our application
• The application's docker images should be able to push and pull from ECR via the GitHub action workflow