awscli | amazon web services command line interface in ruby | AWS library

I have been able to use awscli to get start the execution but I need to be able to know when is completed or result is success before it can go to the next step in the pipeline.

aws stepfunctions start-execution --state-machine-arn arn:aws:states:us-west-2:2xx244xxxx:stateMachine:SamplePipeOrchestration-ftpiles --name SamplePipeOrchestration-ftpiles --input {} --region us-west-2 --profile sampledev

I want to bust my cloudfront cache during a CI job and then run an Algolia search crawler against the busted version:

I have an ECS task running on Fargate on which I want to run a command in boto3 and get back the output. I can do so in the awscli just fine.

I am working on a Terraform project that has an end goal of an EKS cluster with the following properties:

1. Private to the outside internet
2. Accessible via a bastion host
3. Uses worker groups
4. Resources (deployments, cron jobs, etc) configurable via the Terraform Kubernetes module

To accomplish this, I've modified the Terraform EKS example slightly (code at bottom of the question). The problems that I am encountering is that after SSH-ing into the bastion, I cannot ping the cluster and any commands like kubectl get pods timeout after about 60 seconds.

Here are the facts/things I know to be true:

1. I have (for the time being) switched the cluster to a public cluster for testing purposes. Previously when I had cluster_endpoint_public_access set to false the terraform apply command would not even complete as it could not access the /healthz endpoint on the cluster.
2. The Bastion configuration works in the sense that the user data runs successfully and installs kubectl and the kubeconfig file
3. I am able to SSH into the bastion via my static IP (that's the var.company_vpn_ips in the code)
4. It's entirely possible this is fully a networking problem and not an EKS/Terraform problem as my understanding of how the VPC and its security groups fit into this picture is not entirely mature.

Here is the VPC configuration:

I'm using the Azure Toolkit for AWS to create my lambda, and then running some powershell scripts to act on it. After creation, I get the function's ARN as an output. I don't see anywhere in the documentation where I can access the function via the ARN, everything takes the function-name as a parameter.

I have been getting the following error in my CodeBuild execution: ModuleNotFoundError: No module named 'cfn_tools'

Interesting note, the first time I ran this through CodeBuild with this module I had no issues. It only started happening after I made my next gitHub push that kicked off my pipeline that I saw this. The files that are related to this didn't change, and the modifications in that next push were to an unrelated section of the repo.

I have since tried to do:

• pip install cfn-tools & pip3 install cfn-tools which mentioned that the module was already installed. These were added to the BuildSpec section. No success - still got the error
• I've added a requirements.txt file with no success still got the error. I created this file using pip freeze also within the BuildSpec. The module shows up, but still get the error.
• Originally used runtime version 3.7 of python and then tried with 3.9 which still didn't work.

python runtime 3.9 Any assistance would be appreciated.

UPDATE: To add more information I download a .tar.gz file from S3 that contains the python scripts I need for running in this build. I extract the .tar.gz then I run the script that is having the error. Here is the output for when I install cfn-tools and do a pip freeze You will see below that cfn-tools loads and is part of the output of pip freeze but yet when I run my script it give me the above error.

The documentation has me really confused:

I am getting Partial credentials found in env error while running below command.

aws sts assume-role-with-web-identity --role-arn $AWS_ROLE_ARN --role-session-name build-session --web-identity-token $BITBUCKET_STEP_OIDC_TOKEN --duration-seconds 1000

I am using below AWS CLI and Python version-

I am using aws cloudformation package to automatically package and upload Lambda function code to an S3 bucket.

When I upload a new version of the Lambda function, previous objects remain in the S3 bucket. Is there any way to automatically remove "old" versions when uploading a new one?