stealthycoin on develop
chore: Use OrderedDict in yamlh… Import from ordereddict and sim… Support parsing yaml merge tags and 2 more (compare)
@marius02 ah, that's a bit different then. if you're not getting this error in the console, then what I'm guessing is happening is that you're unable to describe instances that aren't yet initializing. if I recall there's a limit to the number of instances you can spin up at once - you might be getting that error for instances that haven't actually been provisioned yet.
You can check this by using aws ec2 describe-instances --instance-id <id> --query Reservations[].Instances[].State
. If your request to create the instance was successful (and perhaps double check that it was), the given state should let you know what's going on. Once the instance is listed as "starting" you should be able to query for its status.
Hello all!
Wondering if I can list multiple profiles on awscli
What it does:
aws configure list
# Name Value Type Location
# ---- ----- ---- --------
# profile default None None
# access_key <not set> None None
# secret_key <not set> None None
# region eu-west-1 config-file ~/.aws/config
What I want it to do:
aws configure list --all
# Name Value Type Location
# ---- ----- ---- --------
# profile default None None
# access_key <not set> None None
# secret_key <not set> None None
# region eu-west-1 config-file ~/.aws/config
# Name Value Type Location
# ---- ----- ---- --------
# profile profile1 None None
# access_key <not set> None None
# secret_key <not set> None None
# region eu-west-1 config-file ~/.aws/config
# Name Value Type Location
# ---- ----- ---- --------
# profile profile1 None None
# access_key <not set> None None
# secret_key <not set> None None
# region eu-west-1 config-file ~/.aws/config
aws ec2 describe-images --owners amazon --filters 'Name=name,Values=amzn2-ami-hvm-2.0.????????-x86_64-gp2' 'Name=state,Values=available' --query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' --output text
Hello, I have an issue with "aws cloudformation deploy"
I used it to create a stack that use a parameter named "MyInstanceType" with a string value t3.small"; when I deploy the stack, everything works fine.
When I change the param's default value with one from SSM parameter store "/MyInstanceType", deploying the stack fails with the following errors :
An error occurred (ValidationError) when calling the CreateChangeSet operation: Unable to fetch parameters ... from parameter store for this account
Any idea ?
virtualenv/bin/aws
I get 'Requirement.parse('botocore<2.0.0,>=1.12.36'), {'s3transfer'})'. If I run the aws that is in the project root (aws-cli/bin/aws) it runs without checking the requirements.
Any tips for installing on MacOSX Sierra? Python versions are as follows:
$python3 --version
Python 3.7.1
$python --version
Python 2.7.10
When I run aws configure
I get the following message:
$aws configure
Traceback (most recent call last):
File "/usr/local/bin/aws", line 4, in <module>
__import__('pkg_resources').run_script('awscli==1.18.2', 'aws')
File "/Library/Python/2.7/site-packages/pkg_resources/__init__.py", line 3018, in <module>
working_set = WorkingSet._build_master()
File "/Library/Python/2.7/site-packages/pkg_resources/__init__.py", line 612, in _build_master
ws.require(__requires__)
File "/Library/Python/2.7/site-packages/pkg_resources/__init__.py", line 918, in require
needed = self.resolve(parse_requirements(requirements))
File "/Library/Python/2.7/site-packages/pkg_resources/__init__.py", line 805, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: colorama<0.4.4,>=0.2.5
$pip3 install colorama
Requirement already satisfied: colorama in /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/colorama-0.4.3-py3.7.egg (0.4.3)
my requirement.txt has b
boto3==1.11.9
awscli==1.17.9
and Im getting this message:
awscli 1.17.9 has requirement botocore==1.14.9, but you'll have botocore 1.14.17 which is incompatible.
pendulum 1.4.4 has requirement tzlocal<2.0.0.0,>=1.5.0.0, but you'll have tzlocal 2.0.0 which is incompatible.
any idea what I need to change?
Hey there, I've got a problem that's driving me nuts.
I'm trying to set my configuration for the aws cli but it returns the error "too few arguments".
Specifically I'm talking about the following command:aws configure set aws_access_key_id $live_id --profile default
The culprit is the damn dollar sign, which leads to the aws cli ignoring everything after it.
Hallo. I am trying to create a deployment pipeline for Gitlab-CI on a react project. The build is working fine and I use artifacts to store the dist folder from my yarn build
command. This is working fine as well.
The issue is regarding my deployment with command: aws s3 sync dist/'bucket-name'
.
Expected: "Done in x seconds"
Actual:error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Running after_script
00:01
Uploading artifacts for failed job
00:01
ERROR: Job failed: exit code 1
The files seem to have been uploaded correctly to the S3 bucket, however I do not know why I get an error on the deployment job.
When I run the aws s3 sync dist/'bucket-name'
locally everything works correctly.
Hello everyone,
I am trying to fetch a secret stored on AWS SSM using aws-cli
command aws ssm get-parameter --name test-key
.
This I am trying to execute inside a ECS fargate container's entrypoint script. I am getting the following error:An error occurred (ParameterNotFound) when calling the GetParameter operation:
On the contrary, when I log into the ECS container and execute the same command on the shell command line, it works fine.
I have explicitly exported the AWS credentials and also given the necessary IAM roles for accessing SSM.
Any ideas? Any help would be really appreciated.
Thanks :)
I added an API to my react app but when I run the code I got a Network Error
when I run the below code
const apiName = "sampleApiName";
const path = "/addSomething";
const myInit = {
headers: {
'Content-Type': 'application/json',
"Authorization": `Bearer ${(await Auth.currentSession().then(data => data.idToken.jwtToken))}`
}
API.get(
apiName,
path,
myInit
).then(result => console.log(result))
.catch(err => console.log(err))
I tried running the code on my API Gateway and I am getting an error "message": "Internal server error"