I'm developing a bot for Telegram and I am using Up to create a Lambda function for AWS. The problem is that when I want to create the function I get an error saying:
Error: Cannot find credentials, visit https://up.docs.apex.sh/#aws_credentials for help.
How do I create the ".aws" folder and the "credentials" file? Under what folder will this be saved? Is it in the same folder I created my bot?
This is on MAC.
After installing the AWS CLI for Mac, type aws configure to initialize the credentials file for the first time.
If you have homebrew you can install awscli like this:
brew update
brew install awscli
And then use the following to configure your aws with you access id and token:
aws configure
First, you need to install AWS CLI for OSX using the following link. Refer the documentation for Install the AWS Command Line Interface on macOS for more details.
Then you need to create AWS Programmatic Access Credentials (After creating a AWS IAM User) and download the credentials. For this you need to go to the IAM section of AWS Web Console. Refer the documentation for Understanding and Getting Your Security Credentials for more details.
Then configure the credentials using the shell commands. Refer the documentation Configuring the AWS CLI for more details.
Install AWS CLI in your mac OS from link below:
[https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux-mac.html#cliv2-linux-mac-install][1]
Verify installation. Change to aws instead of aws2 incase you are using version-1
$ aws2 --version
Configure
$ aws2 configure
You need to configure your CLI before you can use it.
From
https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
"Quick Configuration
For general use, the 'aws configure' command is the fastest way to set up your AWS CLI installation."
Related
it is possible to run the bot cli on a serverless microservice like architecture? Such as Aws Lambda and Azure Functions.
To install on my machine, first I need to have node/npm installed. Then I run this command:
npm i -g
It is possible to have a fully functional bot framework cli on a linux stateless environmen such as aws lambda? If so, there is any particular thing that I need to do to install it?
I know in advance that lambda limits the folders which I have access (i only can write at the /tmp folder, for instance).
Also, I have the option to attach a .zip containing the node modules folder if I want.
Any suggestions here?
did you try installing the bf cli package and run a command you'd like to run?
I am a newbie to both AWS and MobaXterm. I am trying to use MobaXterm to manage AWS instances because it comes with bash.
I am following the commands as per https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html.
When I run the following command $ sudo ./aws/install, I get the following error:
Unable to start 'install': There is no application associated with the
given file name extension.
I did run chmod 777 to ensure that I am able to read/write/execute. Please see attached image.
I do know that I can use Windows CLI installer in command line. However, doing SSH to EC2 is a nightmare in Windows with all certificates. With MobaXterm (because of bash), it is very easy. So, my preference is to use MobaXterm instead of Windows command prompt.
Moreover, I don't want to directly install Ubuntu. Hence, I am looking for some guidance here. I'd appreciate any help.
I am hoping that I am not missing any package. Thanks for any help.
In order for AWS cli to run on MobaXterm, you will need to run the following commands in MobaXterm:
MobApt install python2-pip
pip2 install awscli
It will take some time for MobaXterm to complete steps 1 and 2. Also, AWS cli runs super slow in MobaXterm. You are better off using cmd.
This is the site that helped me ran AWS cli on MobaXterm.
https://majornetwork.net/2017/07/installing-aws-cli-on-cygwin/
I am trying to install aws elastic beanstalk cli on my mac machine. In the prerequisites it says that Python requires following:
Xcode openssl zlib readline
But, on running the command, I get:
-bash: Xcode: command not found
How am I suppose to install this?
An alternative solution is to run the aws cli inside a docker container. It will eliminate the possible issues which may be caused by the OS/library upgrading in the future.
I am trying to use Cloud9 IDE on a server. I added the SSH key and once I try to SSH into the server the error message
Could not execute node.js on root#xxx.xxx.xxx.xxx
appears.
I have nodejs installed on the server, v0.10.25
You need to install the package "nodejs-legacy".
apt-get install nodejs-legacy
The SSH dialog allows you to set the path to the Node.js binary. That should solve your issue.
I found it is necessary to scroll down and click on the advanced tab. Then I entered /usr/bin/nodejs from my "which nodejs" output in my SSH session. This worked for me even though the documentation states AWS tries to do this by default. That left me in the AWS file work space on the server I ssh'ed into as desired.
nodejs was not installed on my EC2 instance, so I installed using the instructions from the following link, and it work perfectly. Tutorial: Setting Up Node.js on an Amazon EC2 Instance
sudo apt-get install nodejs worked for me
I am installing AWS Autoscaling tools on linux redhat, But unfortunately the as-cmd command is not working.
I am getting this error :
-bash: as-cmd: command not found
How to resolve the error ?
Any lead is appreciated
To Answer your question:
run below:
$ updatedb
$ locate as-cmd
This should provide you the path of the command like /usr/bin/as-cmd. Either you should use this complete path while running the command OR you need to update your $PATH variable to include this path. Google if you want to know how to update PATH variable.
Now, some suggestions:
You should not use as-cmd anymore. Please use AWS CLI. Here is the AWS CLI relevant autoscaling commands
The reason being, as-cmd is not maintained by Amazon anymore and all the old CLI features have been exported to AWS CLI. AWS CLI is a one stop shop for all the AWS Services unlike older CLIs where you had to install a separate CLI for individual services.
AWS CLI provides output in JSON format which is much more easier to parse.
BESIDES, You don't have to play with CLI for autoscaling. Now, you can do the same job via AWS Console.