aws-fargate | AWS Fargate is a technology that allows you to run | Continuous Deployment library

by virtual-kubelet Go Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | aws-fargate Summary

aws-fargate is a Go library typically used in Devops, Continuous Deployment, Docker applications. aws-fargate has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

AWS Fargate is a technology that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure and scale clusters of virtual machines to run containers. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing. Fargate lets you focus on designing and building your applications instead of managing the infrastructure that runs them. Fargate makes it easy to scale your applications. You no longer have to worry about provisioning enough compute resources. You can launch tens or tens of thousands of containers in seconds. With Fargate, billing is at a per second granularity and you only pay for what you use. You pay for the amount of vCPU and memory resources your containerized application requests. vCPU and memory resources are calculated from the time your container images are pulled until they terminate, rounded up to the nearest second.

Support

Quality

Security

License

Reuse

Support

aws-fargate has a low active ecosystem.

It has 27 star(s) with 8 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

There are 10 open issues and 2 have been closed. On average issues are closed in 108 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of aws-fargate is current.

Quality

aws-fargate has no bugs reported.

Security

aws-fargate has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

aws-fargate does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

aws-fargate releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed aws-fargate and discovered the below as its top functions. This is intended to give you an instant insight into aws-fargate implemented functionality, and help decide if they suit your requirements.

runRootCommand runs the root command
loadPodState returns a map of Fargate tasks .
NewPod creates a new pod
setupHTTPServer is used to setup the HTTP server
NewCluster returns a new Fargate cluster .
SetDefaultOpts is used to set the default options
setupTracing configures the tracer with the given config .
NewFargateProvider creates a FargateProvider .
Main entry point
NodeFromProvider creates a node from a provider

Get all kandi verified functions for this library.

aws-fargate Key Features

No Key Features are available at this moment for aws-fargate.

aws-fargate Examples and Code Snippets

No Code Snippets are available at this moment for aws-fargate.

Community Discussions

Trending Discussions on aws-fargate

How to configure ephemeral storage on ECS Fargate Task via Ruby SDK?

AWS cdk deploy --all fails to create ECS service

AWS ECS Network ACL requirements

AWS - Fargate - Adding EFS to Container - From AWS Console

Permissions error trying to run Prometheus on AWS EKS (Fargate only) with EFS

Can I use EBS in EKS on fargate?

AWS Fargate cannot access application over Public DNS name

AWS Fargate cannot access dockerized spring boot application over Load balancer/ public IP

"Execution failed" when setting up API Gateway and Fargate with AWS CDK

AWS CodeDeploy for ECS Fargate Blue/Green

QUESTION

How to configure ephemeral storage on ECS Fargate Task via Ruby SDK?

Asked 2021-Jun-14 at 09:28

I'm using the Ruby SDK for AWS ECS to kick-off a task hosted in Fargate via run_task method. This all works fine with the defaults — I can kick off the task OK and can send along custom command parameters to my Docker container:

...

ANSWER

Answered 2021-Jun-14 at 09:28

This was a bug of the SDK, now fixed (server-side, so doesn't require a library update).

The block of code in the question is the correct way for increasing ephemeral storage via the Ruby SDK:

Source https://stackoverflow.com/questions/67607006

QUESTION

AWS cdk deploy --all fails to create ECS service

Asked 2021-May-25 at 15:56

new to the CDK and relatively new to AWS

The Issue

I'm following this tutorial which includes creating a fargate based private API, and accessing it on the public internet through an ec2 instance which is publicly exposed.

I'm picking through, minimally correcting various issues which gets everything running. It comes time to build with:

...

ANSWER

Answered 2021-May-25 at 15:56

The timeout was due to a misnamed ECR which the bookService was attempting to access. To generalize this answer a bit, if there's a timeout it may be good to record which resources timed out and sanity check all the constituent elements.

Source https://stackoverflow.com/questions/67677763

QUESTION

AWS ECS Network ACL requirements

Asked 2021-Apr-14 at 12:09

I currently have a set up in AWS with something like the following:

Image source from task networking in aws fargate.

I am using AWS ECR to store my docker image and in my task definition, as container image, I am using the provided URI of the repository. Everything is in the same region and they are working just fine.

However I want to strengthen the security on AWS by whitelisting specific ports only. From security groups point of view, I have updated them as needed and everything is still working as expected. However for Network ACL, I am having some issues with the Fargate task. In ACL section in the public subnet, for inbound rules, I want to allow access to only HTTPS and HTTP from the internet (0.0.0.0/0). Doing so is resulting into this issue with my fargate task: ResourceInitializationError: unable to pull secrets or registry auth: pull command failed: : signal: killed. It is to be noted that the outbound rules for both subnets (private and public) allows traffic to anywhere (0.0.0.0/0).

I understand that the Fargate task needs to connect to the internet to pull the docker image in ECR and the NAT helps do that. docker pull or docker push uses HTTPS and the private subnet has allowed all traffic from all source and the same for outbound.

NACLs for public subnets

Please advice on how to amend the Network ACL to whitelist specific ports only.

P.S: The last resort would be to use AWS PrivateLink to access the ECR repository, but I don't want to do that yet.

...

ANSWER

Answered 2021-Apr-14 at 12:09

Your are only allowing ports 80 and 443 in your NACLs. This is not enough, as you need to also allow ephemeral ports.

This is because a request to ECR will come back to your container using ephemeral ports, not 80 and 443. These two ports are only used for your container to connect to ECR, not for return traffic from ECR to your container.

Source https://stackoverflow.com/questions/67090222

QUESTION

AWS - Fargate - Adding EFS to Container - From AWS Console

Asked 2020-Dec-17 at 13:53

I am trying to mount a persistent storage in a Fargate container.

I have set up an EFS file system.
I have set up an ECS Cluster.
EFS and ECS share one subnet.
When I try to create a task definition, I choose Fargate and then on Add container. I scroll down to Storage and Logging and cannot choose the EFS file system in Mount points. I cannot choose anything here, the only choice I have is:

This SO question suggests it is possible, but here it was answered using the AWS Cli Application. I wonder if I cannot just do it from the AWS Console (which is the web interface).

...

ANSWER

Answered 2020-Dec-17 at 13:53

Before you can setup Mount point in your Container definition, you have to setup Volume in your Task definition:

Source https://stackoverflow.com/questions/65341724

QUESTION

Permissions error trying to run Prometheus on AWS EKS (Fargate only) with EFS

Asked 2020-Oct-11 at 21:08

I have an EKS cluster that is Fargate only. I really don't want to have to manage instances myself. I'd like to deploy Prometheus to it - which requires a persistent volume. As of two months ago this should be possible with EFS (managed NFS share) I feel that I am almost there but I cannot figure out what the current issue is

What I have done:

Set up an EKS fargate cluster and a suitable fargate profile
Set up an EFS with an appropriate security group
Installed the CSI driver and validated the EFS as per AWS walkthough

All good so far

I set up the persistent volume claims (which I understand must be done statically) with:

...

ANSWER

Answered 2020-Oct-11 at 21:08

Working now - and writing up here for the common good. Thanks to /u/EmiiKhaos on reddit for the suggestions where to look

Problem:

EFS shares are root:root only and prometheus forbids running pods as root.

Solution:

create an EFS access point for each pod requiring a persistent volume to permit access for a specified user.
Specify these access points for the persistent volumes
apply a suitable security context to run the pods as the matching user

Method:

Create 2x EFS access points something like:

Source https://stackoverflow.com/questions/64287430

QUESTION

Can I use EBS in EKS on fargate?

Asked 2020-Sep-07 at 08:35

I want to using prometheus in EKS on AWS fargate
I follow this.
https://aws.amazon.com/jp/blogs/containers/monitoring-amazon-eks-on-aws-fargate-using-prometheus-and-grafana/
but I can't create persistent volume claims.
this is prometheus-storageclass.yaml.

...

ANSWER

Answered 2020-Sep-07 at 08:35

I forgot to create the node group.

eksctl create nodegroup --cluster=myClusterName

Source https://stackoverflow.com/questions/63763894

QUESTION

AWS Fargate cannot access application over Public DNS name

Asked 2020-Aug-21 at 11:59

This is a follow up to my previous question. I'm successfully able to access the public IP over fargate. However, after trying to attach Application load balancer, I cannot access application over public DNS. The registered target always show unhealthy status with 502 error.

Sharing my configuration settings-

VPC Route Table Public Subnet Route Table public subnet config Route Table private subnet Route Table private subnet config ACL subnet associations ACL inbound rules ACL outbound rules security inbound rules security outbound rules internet gateway nat gateway target group target group health status task details service ALB settings ALB listeners Target group with 8081 port

...

ANSWER

Answered 2020-Aug-21 at 11:59

Based on the comments.

There were two issues identified:

Incorrect port on the target group. It was 80 instead of 8081.
Healthy threshold timeout was too short (5 seconds). Increasing it seemed to solved the issue.

Source https://stackoverflow.com/questions/63502147

QUESTION

AWS Fargate cannot access dockerized spring boot application over Load balancer/ public IP

Asked 2020-Aug-12 at 05:17

I have deployed the docker image of my spring boot application over aws ECR, following creation of AWS fargate cluster. PFA screenshots of the configurations stating task, security, service and cluster definition.I can ping my public ip successfully. But I can't access my application over neither load balancer nor public ip. The urls I tried to access application were

public_ip:8081/my_rest_end_point

and

load_balancer_public_dns:8081/my_reset_end_point

I have tested running my docker image on local host using port 8081 and the same 8081 port I have configured for port mapping in my Fargate container configuration (reference: service definition). How can I access my application? I have followed almost all the articles over Medium and AWS.

Tutorials followed: https://medium.com/underscoretec/deploy-your-own-custom-docker-image-on-amazon-ecs-b1584e62484

https://medium.com/faun/aws-fargate-services-deployment-with-continuous-delivery-pipeline-b67d33407c88

...

ANSWER

Answered 2020-Aug-12 at 05:17

Based on the comments and chat discussion.

The tutorial followed creates a custom VPC with CIDR range of 10.0.0.0/16 with two subnets. There is no internet gateway (IGW); and subsequently, the Fargate tasks launched in the VPC have no internet access nor they can't be accessed from the internet.

There are two solutions to this problem:

use the default VPC which correctly provides internet access
create a custom VPC (or modify existing) that is setup with IGW and the corresponding route tables. An example of a custom VPC with internet access is in AWS docs.

Source https://stackoverflow.com/questions/63352705

QUESTION

"Execution failed" when setting up API Gateway and Fargate with AWS CDK

Asked 2020-Jun-09 at 11:39

I am trying to setup AWS API Gateway to access a fargate container in a private VPC as described here. For this I am using AWS CDK as described below. But when I curl the endpoint after successful cdk deploy I get "Internal Server Error" as a response. I can't find any additional information. For some reason API GW can't reach the container.

So when I curl the endpoint like this:

...

ANSWER

Answered 2020-Jun-09 at 11:39

After hours of trying I finally figured out that the security groups do not seem to be updated correctly when setting up the VpcLink with CDK. Broadening the allowed connection with

Source https://stackoverflow.com/questions/62214530

QUESTION

AWS CodeDeploy for ECS Fargate Blue/Green

Asked 2020-May-16 at 13:54

I am following the note:

https://aws.amazon.com/blogs/devops/use-aws-codedeploy-to-implement-blue-green-deployments-for-aws-fargate-and-amazon-ecs/

I can see new Blue/Green Deployment in ESC-Fargate Service when updating TaskDefinition and Service.

In CodeDeploy, I can see application AppECS-webapi-docker-cluster-webapi-docker-service2 and deployment ground DgpECS-webapi-docker-cluster-webapi-docker-service2

From Deployment Group, I create a Deployemnt:

What I should add in appspec?

...

ANSWER

Answered 2020-May-16 at 13:54

"The AppSpec file for an Amazon ECS deployment specifies your task definition, container name, and container port."

Please refer to this article for more information - https://docs.aws.amazon.com/codedeploy/latest/userguide/tutorial-ecs-create-appspec-file.html

Source https://stackoverflow.com/questions/61837584

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install aws-fargate

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: