I've been exploring the project and its deployment setup. After reviewing the infrastructure and considering the potential for scalability and modularity, I believe there's an opportunity to enhance the deployment process.

Proposal:
Instead of deploying the ECS cluster directly within the project setup, I suggest deploying it separately using AWS CDK. This approach would offer several benefits:

• Improved scalability and flexibility: Decoupling the ECS cluster deployment allows for independent scaling and management.
• Simplified updates: With the ECS cluster managed separately, updates to the task ARN or other configurations can be performed more seamlessly without affecting the main project deployment.
• Better resource management: Separating the ECS cluster deployment enables more granular control over resources and configurations, optimizing performance and cost-effectiveness.

Steps:

1. Utilize AWS CDK to define and deploy the ECS cluster infrastructure.
2. Integrate the deployed ECS cluster with the main project setup by updating the necessary configurations (e.g., task ARN).
3. Ensure seamless communication and interaction between the deployed ECS cluster and other project components.

This project is completely for Vite Project. But as we all know that while building React projects, instead of dist folder we get build folder. This issue has to be resolved if anyone notices.

Add custom CMDs
To install
To run
To build

Front-end or back-end code

I'm excited to build the Frontend part of this project in my unique way✨.

E:\vercel-clone\build-server>docker run -it -p 8080:5000 myvercel
exec /home/app/main.sh: no such file or directory

Please can you add support for them I want to host backend and frontend

Problem : Containers are still running even after the build process completed
Solution : Need to add publisher.disconnect(); on line 70 in /build-server/script.js
This will ensure the docker shutdown after the upload process is completed. 💯

• publisher.disconnect() will revoke the connection with redis server.

run same code but when i run task on cluster get this.

@piyushgarg-dev kindly check once

this is same docker file

Hey Can i work on the frontend of the project

output

Code

const express = require("express");
const httpProxy = require("http-proxy");

const app = express();
const PORT = 8000;

const BASE_PATH =
    "https://faucet-client-deployments.s3.amazonaws.com/__outputs";

const proxy = httpProxy.createProxy();

app.use((req, res) => {
    const hostname = req.hostname;
    const subdomain = hostname.split(".")[0];

    // Custom Domain - DB Query

    const resolvesTo = `${BASE_PATH}/${subdomain}`;

    return proxy.web(req, res, { target: resolvesTo, changeOrigin: true });
});

proxy.on("proxyReq", (proxyReq, req, res) => {
    const url = req.url;
    console.log("url", url);
    console.log("proxyReq.path", proxyReq.path);
    if (url === "/") proxyReq.path += "index.html";
});

app.listen(PORT, () => console.log(`Reverse Proxy Running..${PORT}`));

S3 Bucket policy

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject",
                "s3:GetObjectVersion"
            ],
            "Resource": "arn:aws:s3:::faucet-client-deployments/*"
        },
        {
            "Sid": "AllowWebAccess",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject",
                "s3:GetObjectVersion"
            ],
            "Resource": "arn:aws:s3:::faucet-client-deployments/*"
        }
    ]
}

I'm trying to come up with ways to support server functions, and my thought is to use a tool like this
aws-lambda-web-adapter, or maybe even SST. My idea is to deploy a static build just like it's currently doing, but deploy the project to a lambda function as well and somehow (haven't figured it out yet) get the static build to understand that API routes and serverless functions are running else where.