"FleetId": "fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa", "PeerVpcAwsAccountId": "111122223333",
"PeerVpcId": "vpc-a12bc345"}
Peer the VPC for your Amazon Web Services fleet with a VPC on a different account
This example builds on Example 2 in CreateVpcPeeringAuthorization. If authorization succeeded, the next step is to tell Amazon Web Services to request the peering connection. As in the previous example, you want your game servers that are running on an Amazon Web Services fleet to be able to access a web service. But in this example, the web service is managed by a different account from the one that you use to manage your Amazon Web Services fleet. To request the peering, provide the following details for the two VPCs to peer: (1) the Amazon Web Services fleet ID, and (2) the account and VPC for the web service. The account ID and VPC for the web service must be the same one you used in the authorization.
The fleet's ID is fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa. Your Amazon Web Services account ID is 111122223333. The AWS account with the web service is 444455556666. The VPC ID for the web service is vpc-c67ef890.
See Also
To make this request, sign in using your credentials for AWS account 111122223333 (your Amazon Web Services account). To view resulting new connection record, call DescribeVpcPeeringConnections (p. 239) with the fleet ID.
HTTP requests are authenticated using an AWS Signature Version 4 signature in the Authorization header field.
Sample Request
POST / HTTP/1.1
Host: gamelift.us-west-2.amazonaws.com;
Accept-Encoding: identity Content-Length: 141
User-Agent: aws-cli/1.11.36 Python/2.7.9 Windows/7 botocore/1.4.93 Content-Type: application/x-amz-json-1.0
Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20170406/us-west-2/
gamelift/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target, Signature=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
X-Amz-Date: 20170406T004805Z
X-Amz-Target: GameLift.CreateVpcPeeringConnection
{ "FleetId": "fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa", "PeerVpcAwsAccountId": "444455556666",
"PeerVpcId": "vpc-c67ef890"}
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
• AWS Command Line Interface
• AWS SDK for .NET
• AWS SDK for C++
• AWS SDK for Go
• AWS SDK for Java V2
• AWS SDK for JavaScript
• AWS SDK for PHP V3
• AWS SDK for Python
• AWS SDK for Ruby V3
DeleteAlias
DeleteAlias
Deletes an alias. This operation removes all record of the alias. Game clients attempting to access a server process using the deleted alias receive an error. To delete an alias, specify the alias ID to be deleted.
Related actions
CreateAlias (p. 12) | ListAliases (p. 250) | DescribeAlias (p. 129) | UpdateAlias (p. 344) | DeleteAlias (p. 95) | ResolveAlias (p. 290) | All APIs by task
Request Syntax
{ "AliasId": "string"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters (p. 509).
The request accepts the following data in JSON format.
NoteIn the following list, the required parameters are described first.
AliasId (p. 95)
A unique identifier of the alias that you want to delete. You can use either the alias ID or ARN value.
Type: String
Pattern: ^alias-\S+|^arn:.*:alias\/alias-\S+
Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors (p. 511).
InternalServiceException
The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.
HTTP Status Code: 500 InvalidRequestException
One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.
See Also
HTTP Status Code: 400 NotFoundException
A service resource associated with the request could not be found. Clients should not retry such requests.
HTTP Status Code: 400 TaggingFailedException
The requested tagging operation did not succeed. This may be due to invalid tag format or the maximum tag limit may have been exceeded. Resolve the issue before retrying.
HTTP Status Code: 400 UnauthorizedException
The client failed authentication. Clients should not retry such requests.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
• AWS Command Line Interface
• AWS SDK for .NET
• AWS SDK for C++
• AWS SDK for Go
• AWS SDK for Java V2
• AWS SDK for JavaScript
• AWS SDK for PHP V3
• AWS SDK for Python
• AWS SDK for Ruby V3
DeleteBuild
DeleteBuild
Deletes a build. This operation permanently deletes the build resource and any uploaded build files.
Deleting a build does not affect the status of any active fleets using the build, but you can no longer create new fleets with the deleted build.
To delete a build, specify the build ID.
Learn more
Upload a Custom Server Build Related actions
CreateBuild (p. 16) | ListBuilds (p. 253) | DescribeBuild (p. 132) | UpdateBuild (p. 347) | DeleteBuild (p. 97) | All APIs by task
Request Syntax
{
"BuildId": "string"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters (p. 509).
The request accepts the following data in JSON format.
NoteIn the following list, the required parameters are described first.
BuildId (p. 97)
A unique identifier for the build to delete. You can use either the build ID or ARN value.
Type: String
Pattern: ^build-\S+|^arn:.*:build\/build-\S+
Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors (p. 511).
InternalServiceException
The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.
Examples
HTTP Status Code: 500 InvalidRequestException
One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.
HTTP Status Code: 400 NotFoundException
A service resource associated with the request could not be found. Clients should not retry such requests.
HTTP Status Code: 400 TaggingFailedException
The requested tagging operation did not succeed. This may be due to invalid tag format or the maximum tag limit may have been exceeded. Resolve the issue before retrying.
HTTP Status Code: 400 UnauthorizedException
The client failed authentication. Clients should not retry such requests.
HTTP Status Code: 400