Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: 3 Tier architecture - How to configure so that Backend Service security group's inbound rules allow Load Balanced Web Service connection #5768

Open
rickychew77 opened this issue Apr 11, 2024 · 4 comments
Labels
type/enhancement Issues that are improvements for existing features. type/feature Issues that are new feature requests. type/request Issues that are created by customers.

Comments

@rickychew77
Copy link

Describe your idea/feature/enhancement

For some project that is simple front end backend architecture, I would like to have the Backend Service's Security Group inbound rule that was created by default from Copilot to allow Load Balanced Web Service's connection. Understand that there is there is a way to import existing security_group here however this does not achieve what I described above.

Proposal

Is there a way to allow multiple copilot services to "discover" each other given the IAM permission was sorted out, so that not only security group but any other potential configuration can be seamless.

Additional Details

Maybe in either one of the services there is a field in the manifest.yml to point to each other?

@rickychew77 rickychew77 added type/enhancement Issues that are improvements for existing features. type/feature Issues that are new feature requests. type/request Issues that are created by customers. labels Apr 11, 2024
@iamhopaul123
Copy link
Contributor

Hello @rickychew77. I don't get why we need to do this through security group 🤔 Right now the backend service only allows access from all services deployed within the same environment. Do you mean you want the backend service to be only accessible from a specific LBWS, whereas all the other services deployed to the same environment can't access?

@rickychew77
Copy link
Author

yes, i am not sure if this is the best practice to do, but basically is to allowing frontend ECS connectiion to backend ECS, both are within same VPC.

@iamhopaul123
Copy link
Contributor

Yeah in that scenario using service connect or service discovery that comes with the Copilot deployment would be recommended. You can check the endpoints by doing copilot svc show!

@rickychew77
Copy link
Author

Yes, understand that using service connect (Cloud Map) that comes with Copilot deployment.

However, we still need to configure the backend ECS security group to allow access from frontend ECS (both created via copilot.) The default inbound rule only have this rule Ingress from other containers in the same security group.

Currently it's not a blocker, just that we have perform clickops in aws console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Issues that are improvements for existing features. type/feature Issues that are new feature requests. type/request Issues that are created by customers.
Projects
None yet
Development

No branches or pull requests

2 participants