Learn how to update a connector through the AWS CLI
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:
Under the Stack name column, copy the stack name.
AWS Command Line Interface (AWS CLI)
AWS Permissions
Follow these steps to update a connector:
Copy the following Account level or Organization level AWS update script. Be sure to replace AWS_STACK_NAME
with your AWS stack name.
If you have not defined a default region and default profile, you must specify the region and profile in the script:
Be sure to replace AWS_PROFILE
and AWS_SERVER_REGION
with 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 StackId
.
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.
Go to the page.
enabling interaction with AWS services using your command-line shell
enabling the ability to update the stack via AWS CLI
This guide is intended for admins managing a Connector in the environment
📘 You have chosen the advanced installation method
You can also easily connect AWS in Apono following this UI guide here
Required CLI: terraform
Login to Apono and create connector in the Connector Page
Important: before you start, copy the connector Terraform params and export them in the terminal.
** if you already use your own providers, you can skip this step
Run terraform init
to validate it works
It's required that your EKS cluster OIDC provider will be added to your IAM. &#xNAN;This step is required only once, and you may have already done it.
The Connector is deployed using helm and requires an IAM Role to be able to access tagged ASM secrets in the future.