I've just followed the example process as described in the predictionio docs to create a PredictionIO Cluster on AWS CloudFormation but my stack rolled back right after creation.
Did any of you successfully follow the docs?
I've looked through the error logs and found the self explaining error message:
Value (us-east-1a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-west-2b, us-west-2a, us-west-2c.
Related
i try to deploy resources for the Amazon DataSync Service with CloudFormation. The Creation of the resources worked. But i ran into an Error when starting the DataSync Task, created with CloudFormation. CloudFormation automatically tags my Task with CloudFormation Standard Tags StackName, StackID, StackLogicalId. It looks like DataSync has a Problem with these Tags. When i start the task it gives me an error:
Failed to start execution
Invalid parameter: key=aws:cloudformation:logical-id.
The Tags look like this:
Is there a possibility to deactivate this tagging? Or does anyone know how to solve this?
I'm trying to create ECS Fargate deployment using Cloudformation script, but the script fails during creation of ECS Cluster with error saying that unable to assume service role. I'm not able to figure out what I'm missing in the script, I have tried many ways none of them seem to be working.
Here is the link to cloud formation script as I'm not able to post it here due to character limitation.
ECS Cloudformation script
the error where the resource creation fails.
Resource handler returned message: "Invalid request provided: CreateCluster Invalid Request: Unable to assume the service linked role. Please verify that the ECS service linked role exists. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: e08ab312-4bd8-4c21-852f-ae5d49cc5932; Proxy: null)" (RequestToken: a686f226-e1d3-7b4c-13f1-66fa0a516c51, HandlerErrorCode: InvalidRequest
I'm able to get it working if I create an ECS cluster from aws console, as it creates a service liked role. But I want to work without creating the cluster manually from Console, enerything building up from Cloudformation. I tried looking over aws docs and did dig up Internet but couldn't get it working.Can anyone please help me out.
I am trying to setup HashiCorp Vault on AWS. There is a quickstart guide to install Vault along with Consul.
https://aws.amazon.com/quickstart/architecture/vault/
https://aws-quickstart.s3.amazonaws.com/quickstart-hashicorp-vault/doc/hashicorp-vault-on-the-aws-cloud.pdf
I followed all the steps of setting up Vault on AWS in a new VPC and in existing VPC but I was unable to complete the entire process successfully.
While trying to setup vault, the stack creation failed:
Parameters:
Events:
While trying to install Vault in existing VPC, it got installed but initialization failed as I have posted on this github issue: https://github.com/aws-quickstart/quickstart-hashicorp-vault/issues/42
I received a similar error when I was running through the same quick-start. My issue was that I didn't have an SSL certificate ARN added to the cloudformation template inputs.
this example: https://aws.amazon.com/premiumsupport/knowledge-center/stop-start-ec2-instances/
does not seem to work. I followed the example and the pipeline is always canceled. There are no logs created, i did set up logging. the only "error message" i could find is.
Error MessageUnable to create resource for #Ec2Instance_2017-06-07T09:58:49 due to: No subnets found for the default VPC 'vpc-f7dxxxx'. Please specify a subnet. (Service: AmazonEC2; Status Code: 400; Error Code: MissingInput; Request ID: ebeeae6d-9537-4627-8a56-e832999a1940)
All i am trying to do is execute a aws ec2 start-instances aws cli command as outlined in the example. the instances do exist, they are in a "stopped" state. Has anyone been successful in setting up a pipeline to start and stop existing instances? How did you do it? Thanks for the help
yes, that was it. after you finish going through the example you need to look at the pipeline and edit it. Look for the EC2Resource area. Click on it. then add a subnet. place the micro instance in the same subnet as the ec2 instances you need to start or stop. The example does not address this
I am working on EMR template with autoscaling.
While a static EMR setup with instance group works fine, I cannot attach
AWS::ApplicationAutoScaling::ScalableTarget
As a troubleshooting I've split my template into 2 separate ones. In first I am creating a normal EMR cluster (which is fine). And then in second I have a ScalableTarget definition which fails attach with error:
11:29:34 UTC+0100 CREATE_FAILED AWS::ApplicationAutoScaling::ScalableTarget AutoscalingTarget EMR instance group doesn't exist: Failed to find Cluster XXXXXXX
Funny thing is that this cluster DOES exist.
I also had a look at IAM roles but everything seems to be ok there...
Can anyone advice on that matter?
Did anyone for Autoscaling instancegroup to work via Cloudformation?
I have already tried and raised a request with AWS. This autoscaling feature is not yet available using CloudFormation. Now I am using CF for Custom EMR SecGrp creation and S3 etc and in output tab, I am adding Command line command(aws emr create-cluster...... ). After getting output querying the result to launch Cluster.
Actually, autoscaling can be enabled at the time of cluster launching by using --auto-scaling-role. If we use CF for EMR, autoscaling feature is not available because it launches cluster without "--auto-scaling-role".
I hope this can be useful...