GetProfileResourceAssociation
Returns information about a specified Route 53 Profile resource association.
Request Syntax
GET /profileresourceassociation/ProfileResourceAssociationId
HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- ProfileResourceAssociationId
-
The ID of the profile resource association that you want to get information about.
Length Constraints: Minimum length of 1. Maximum length of 64.
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"ProfileResourceAssociation": {
"CreationTime": number,
"Id": "string",
"ModificationTime": number,
"Name": "string",
"OwnerId": "string",
"ProfileId": "string",
"ResourceArn": "string",
"ResourceProperties": "string",
"ResourceType": "string",
"Status": "string",
"StatusMessage": "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.
- ProfileResourceAssociation
-
Information about the Profile resource association that you specified in a
GetProfileResourceAssociation
request.Type: ProfileResourceAssociation object
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
The current account doesn't have the IAM permissions required to perform the specified operation.
HTTP Status Code: 400
- InvalidParameterException
-
One or more parameters in this request are not valid.
HTTP Status Code: 400
- ResourceNotFoundException
-
The resource you are associating is not found.
HTTP Status Code: 400
- ThrottlingException
-
The request was throttled. Try again in a few minutes.
HTTP Status Code: 400
- ValidationException
-
You have provided an invalid command.
HTTP Status Code: 400
Examples
GetProfileResourceAssociation Example
This example illustrates one usage of GetProfileResourceAssociation.
Sample Request
GET /profileresourceassociation/rpr-001913120a7example HTTP/1.1
host:route53profiles.us-east-1.amazonaws.com
Accept-Encoding: identity
X-Amz-Date:20240319T231134Z
User-Agent: aws-cli/1.32.63 botocore/1.34.63 Python/3.8.18
Authorization: AWS4-HMAC-SHA256
Credential=AKIAJJ2SONIPEXAMPLE/20181101/us-east-1/route53profiles/aws4_request,
SignedHeaders=host;x-amz-date;x-amz-security-token
Signature=[calculated-signature]
{} # RequestBody is empty
Sample Response
HTTP/1.1 200 OK
Date: Tue, 19 Mar 2024 23:11:34 GMT
Content-Type: application/json
Content-Length: 517
Connection: keep-alive
x-amzn-RequestId: dcd9d91e-1a5a-481f-82b7-bafe7dexample
Access-Control-Allow-Origin: *
x-amz-apigw-id: U5eX0FdmIexample=
X-Amzn-Trace-Id: Root=1-65fa10fe-6e5a93a56a325ab8example
{
"ProfileResourceAssociation": {
"CreationTime": 1710887901.139,
"Id": "rpr-001913120a7example",
"ModificationTime": 1710887901.139,
"Name": "test-resource-association",
"OwnerId": "123456789012",
"ProfileId": "rp-4987774726example",
"ResourceArn": "arn:aws:route53resolver:us-east-1:123456789012:firewall-rule-group/rslvr-frg-cfe7f72example",
"ResourceProperties": "{\"priority\":105}",
"ResourceType": "FIREWALL_RULE_GROUP",
"Status": "COMPLETE",
"StatusMessage": "Completed creation of Profile to DNS Firewall rule group association"
}
}
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: