Periodically, you may need to update your AWS connector to help maintain functionality, performance, and security.
This article explains how to update a connector through the AWS CLI and redeploy the CloudFormation stack with the latest connector template.
|AWS Stack Name
|In AWS CloudFormation, name of a collection of AWS resources managed as a single unit
Use the following steps to retrieve the stack name:
|AWS Command Line Interface (AWS CLI)
|Open-source tool enabling interaction with AWS services using your command-line shell
|Permissions enabling the ability to update the stack via AWS CLI
Use the following steps to update a connector:
Copy the following AWS update script. Be sure to replace
AWS_STACK_NAMEwith your AWS stack name.
aws cloudformation update-stack --stack-name AWS_STACK_NAME --template-url https://apono-public.s3.amazonaws.com/cloudformation/aws_integration_with_connector_template.yml --parameters ParameterKey=AponoConnectorId,UsePreviousValue=true ParameterKey=AponoConnectorToken,UsePreviousValue=true ParameterKey=ExternalID,UsePreviousValue=true ParameterKey=SubnetIDs,UsePreviousValue=true ParameterKey=VpcId,UsePreviousValue=true --capabilities CAPABILITY_NAMED_IAM
If you have not defined a default region and default profile, you must specify the region and profile in the script:
--profile AWS_PROFILE --region AWS_SERVER_REGION
Be sure to replace
AWS_SERVER_REGIONwith your profile and region values.
At your AWS CLI prompt, enter the updated script from the previous step to initiate the update. The AWS CLI will return an object containing the
In CloudFormation, on the Stack Info tab, confirm that the update has completed:
- Go to the Stacks page. A list of the stacks in the account are displayed.
- Under the Stack name column, click the stack name.
- On the Stack info tab, check the Status.
This section details common errors that can occur during the updating process. If an error occurs that is not listed below, please contact your Apono representative.
An error occurred (ValidationError) when calling the UpdateStack operation: Stack [stack name] does not exist.
This occurs when the incorrect stack name has been included in the update script.
Use the following steps to correct this error:
- Locate and copy the stack name under the Stack name column of the Stacks page.
- Repeat the update process.
Updated about 2 months ago