DescribeFargateProfile - Amazon Elastic Kubernetes Service

DescribeFargateProfile

Returns descriptive information about an AWS Fargate profile.

Request Syntax

GET /clusters/name/fargate-profiles/fargateProfileName HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.

name

The name of the Amazon EKS cluster associated with the Fargate profile.

Required: Yes

fargateProfileName

The name of the Fargate profile to describe.

Required: Yes

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 Content-type: application/json { "fargateProfile": { "clusterName": "string", "createdAt": number, "fargateProfileArn": "string", "fargateProfileName": "string", "podExecutionRoleArn": "string", "selectors": [ { "labels": { "string" : "string" }, "namespace": "string" } ], "status": "string", "subnets": [ "string" ], "tags": { "string" : "string" } } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

fargateProfile

The full description of your Fargate profile.

Type: FargateProfile object

Errors

For information about the errors that are common to all actions, see Common Errors.

ClientException

These errors are usually caused by a client action. Actions can include using an action or resource on behalf of a user that doesn't have permissions to use the action or resource or specifying an identifier that is not valid.

HTTP Status Code: 400

InvalidParameterException

The specified parameter is invalid. Review the available parameters for the API request.

HTTP Status Code: 400

ResourceNotFoundException

The specified resource could not be found. You can view your available clusters with ListClusters. You can view your available managed node groups with ListNodegroups. Amazon EKS clusters and node groups are Region-specific.

HTTP Status Code: 404

ServerException

These errors are usually caused by a server-side issue.

HTTP Status Code: 500

Examples

In the following example or examples, the Authorization header contents (AUTHPARAMS) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You need to learn how to sign HTTP requests only if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.

Example

The following example describes a Fargate profile called default-with-infrastructure-label in the fargate cluster.

Sample Request

GET /clusters/fargate/fargate-profiles/default-with-infrastructure-label HTTP/1.1 Host: eks.us-west-2.amazonaws.com Accept-Encoding: identity User-Agent: aws-cli/1.16.284 Python/3.7.5 Darwin/18.7.0 botocore/1.13.20 X-Amz-Date: 20191120T204303Z Authorization: AUTHPARAMS

Sample Response

HTTP/1.1 200 OK Date: Wed, 20 Nov 2019 20:43:04 GMT Content-Type: application/json Content-Length: 651 x-amzn-RequestId: e1822fa7-8aba-4342-af20-48c248337a21 x-amz-apigw-id: DebFwF0YPHcFkog= X-Amzn-Trace-Id: Root=1-5dd5a557-3ac08aa35dc4f15044c4f4d2 Connection: keep-alive { "fargateProfile": { "fargateProfileName": "default-with-infrastructure-label", "fargateProfileArn": "arn:aws:eks:us-west-2:012345678910:fargateprofile/fargate/default-with-infrastructure-label/06b7453e-ef9a-82fc-f0c3-736633e31d41", "clusterName": "fargate", "createdAt": 1574281537.866, "podExecutionRoleArn": "arn:aws:iam::012345678910:role/AmazonEKSPodExecutionRole", "subnets": [ "subnet-0420a37ee456daf3f", "subnet-09a8afb8db4f02d21" ], "selectors": [ { "namespace": "default", "labels": { "infrastructure": "fargate" } } ], "status": "ACTIVE", "tags": {} } }

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: