Specify container port protocol for ApplicationLoadBalancedFargateService
See original GitHub issueSpecify target group protocol when creating an application load balanced service.
Use Case
To use the ECS Pattern for a LoadBalancedFargateService
when the container serves HTTPS.
Proposed Solution
Make the target protocol an option in the constructor.
This is a 🚀 Feature Request
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
class ApplicationLoadBalancedFargateService (construct)
Specifies whether the load balancer should redirect traffic on port 80 to port 443 to support HTTP->HTTPS redirects This is only valid if...
Read more >ApplicationLoadBalancedFargat...
I have an ECS service that exposes port 8080. I want to have the load balancer, target groups and target use that port...
Read more >Registering a Fargate service ELB target with correct port ...
I can't seem to find a method or set of props that lets me tell the CDK which container's port to use. Or...
Read more >@aws-cdk/aws-ecs-patterns - npm
ApplicationLoadBalancedFargateService (this, 'Service', { cluster, memoryLimitMiB: 1024, cpu: 512, taskImageOptions: { image: ecs.ContainerImage.
Read more >Lab 2: Deploy Cluster - ECS_Fargate_Workshop
ApplicationLoadBalancedFargateService (self, "FrontendFargateLBService" ... Navigate to CloudWatch console and select "Container Insights" dashboard.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
To shed some additional light on the question of “why do you need HTTPS if it’s inside your VPC” I would mention the HIPAA guidelines of “encrypt at rest, encrypt in transit”. Not to suggest that the networking inside AWS inside isn’t rock-solid already, but in general it’s easier to satisfy regulatory requirements by following them even when it’s not strictly technically necessary.
@kohidave
⚠️COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.