I'm trying to run the aws rds add-role-to-db-cluster
Here is what I get when I run the command:
$ aws rds add-role-to-db-cluster --db-cluster-identifier arn:aws:rds:us-east-1:<account>:cluster:<arn> --role-arn arn:aws:iam::<account>:role/<arn>
An error occurred (InvalidParameterValue) when calling the AddRoleToDBCluster operation: The feature-name parameter must be provided with the current operation for the Aurora (PostgreSQL) engine.
💥When I add the --feature-name to it, I get the following:
$ aws rds add-role-to-db-cluster --db-cluster-identifier arn:aws:rds:us-east-1:<account>:cluster:<arn> --role-arn arn:aws:iam::<account>:role/<arn> --feature-name s3Import
An error occurred (InvalidParameterValue) when calling the AddRoleToDBCluster operation: The feature name s3Import is not valid for the Aurora PostgreSQL engine.
💥$ aws --version
aws-cli/1.16.192 Python/3.7.2 Darwin/18.5.0 botocore/1.12.182
👍
$ aws configure
Credential named assume-role-with-web-identity not found.$ aws --version
aws-cli/1.16.230 Python/3.7.4 Linux/5.2.11-arch1-1-ARCH botocore/1.12.180
~/.aws/config file to make sure there's not something wrong with the default profile, or just move that out of the way to troubleshoot. It's possible the default profile you have set references a role that no longer exists in the target account
@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/configWhat 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 accountAny 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.
