Cross-Account Log Data Sharing with Subscriptions from doc’s on https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CreateDestination.html I keep getting InvalidParameterException saying An error occurred (InvalidParameterException) when calling the PutDestination operation: Could not deliver test message to specified destination. Check if the destination is valid. and this is my command aws-log aws logs put-destination --destination-name snplydst --target-arn arn:aws:kinesis:region:999999999999:stream/RecipientStream --role-arn arn:aws:iam::999999999999:role/CWLtoKinesisRole
Hey people I am trying to create an AMI from an OVA and have been running into trouble. I am using the Amazon Linux box..
I am now receiving this error after inputting this command into the cli.aws ec2 import-image --description "Vormetric DSM 6.0" --disk-containers file://containers.json
This is the error message then appears:Could not connect to the endpoint URL: "https://ec2.us.east.1.amazonaws.com/"
I did a reset the original error message was it wasn't locating the region us-east-1 in aws configure set region us-east-1
$ aws elbv2 describe-tags --resource-arns arn:aws:elasticloadbalancing:us-west-2:044443245626:targetgroup/T-1/62a3060e529c7e69
An error occurred (ValidationError) when calling the DescribeTags operation: 'arn:aws:elasticloadbalancing:us-west-2:044443245626:targetgroup/T-1/62a3060e529c7e69' must be in ARN format
hey all. can I get Secrets Manager values with a trailing slash from Parameter Store? https://docs.aws.amazon.com/systems-manager/latest/userguide/integration-ps-secretsmanager.html shows examples of a single key without a path, and these are the errors I get when trying to get the SM values with and without trailing slash (/dev/my/key is the credential in SM - also note the "null" in the first error:
$ aws ssm get-parameter --name /aws/reference/secretsmanager/dev/my/key --with-decryption
An error occurred (ParameterNotFound) when calling the GetParameter operation: An error occurred (ParameterNotFound) when referencing Secrets Manager: Secret aws/reference/secretsmanager/dev/my/keynull not found.
$ aws ssm get-parameter --name /aws/reference/secretsmanager//dev/my/key --with-decryption
An error occurred (ValidationException) when calling the GetParameter operation: Parameter name: can't be prefixed with "ssm" (case-insensitive). If formed as a path, it can consist of sub-paths divided by slash symbol; each sub-path can be formed as a mix of letters, numbers and the following 3 symbols .-_It works for an existing SM value created without trailing slash. Should I escape the trailing slash somehow?
Error parsing parameter '--parameters': Unable to retrieve https://s3-us-west-2.amazonaws.com/path/to/the/json: received non 200 status code of 403
Get-ECRLoginCommand : The security token included in the request is invalid. checked my creds all seems to be okay and when i fire the same get creds on my nix instance it seems to work
TestCPCommand.test_cp_with_error_and_warning and TestSyncCommand.test_warning_on_invalid_timestamp failing. It looks like the test utilities are trying to generate an invalid timestamp but it's not throwing the expected OverflowError on this system. Does this sound possible and/or does anyone have a working OSX setup that I could compare notes with?
aws cloudformation create-stack --stack-name my-new-stack --template-url https://s3-us-west-2.amazonaws.com/path/to/the/template --capabilities CAPABILITY_NAMED_IAM --region us-west-2 --parameters file:///path/to/json
aws s3 sync to throttle down disk I/O? My intention was to sync ~600 GB of pictures to S3, but every time I try to do that, the disk usage jumps up to 100% and makes a huge impact on the site operation. I saw in strace output that the tool walks recursively over the directory tree and collects stats, so I'd love to find a way to decrease the rate limit of those operations, if possible.
i have a docker image i want to use to "chunk" up large CSV files. what is the best feature on AWS to run and scale this on?
I want to be able to fire a payload to it from a lambda when it finds a file that is too big is detected in S3
have tried using fargate but we hit the 20 instances cap quite quickly
