SSL Certificate Issues when use WSO2 AWS Cloudformation stack - wso2

During Cloudformation process, I got the following error:
Certificate 'arn:aws:iam::409486064609:server-certificate/EXAMPLE' not found (Service: AmazonElasticLoadBalancingV2; Status Code: 400; Error Code: CertificateNotFound; Request ID: 24ba2810-a815-11e9-a888-8b9ad7cb576b)
I have a Certificate in place, but apparently when the process is creating or installing on load balancer, found an error and stop the process.
Any idea how to proceed?
Sirech

Related

AWS ECS Cluster Unable to assume service role, when creating with cloudformation

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.

Cloudformation not creating my stack but AWS Config will

I'm trying to deploy a conformance pack stack via cloudformation for AWS Config. I'm using https://github.com/awslabs/aws-config-rules/blob/master/aws-config-conformance-packs/Operational-Best-Practices-for-NIST-CSF.yaml for my template and I'm getting an error saying "The sourceIdentifier AWS_CONFIG_PROCESS_CHECK is invalid. Please refer to the documentation for a list of valid sourceIdentifiers that can be used when AWS is the Owner. (Service: AmazonConfig; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: cbaa077f-f932-4918-84a9-b38cecf8b1df; Proxy: null)" which is causing a rollback and deletion of resources. I deployed this same template through AWS Config and it worked just fine. I also used a NIST CSF sample pack template through AWS Config and it worked as well. My question is why it doesn't deploy via cloudformation with the script. Thank you.

Amplify Push Fail - Appsync API error - S3 The specified key does not exist

I am facing an error with cloudformation in which my nested stack got stuck in UPDATE_ROLLBACK_FAILED state causing my parent stack to failed. The reason I found out is S3 key missing for my appsync resolvers, although these files are there in S3 deployment bucket.
The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: M2X7368PMNF1G; S3 Extended Request ID: WCIc1YLjxOR9KZRxkPb1AGI4xoM6KPofiohiP9ywyps8tSfP6ehHJl8gWk7o=; Proxy: null)
I tired https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-update-rollback-failed/ https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-continueupdaterollback.html
to get my parent stack in Update_rollback_complete by skipping the failed resource. This should rollback the parent stack with update complete status and allow for further stack updates but unfortunately not. I drill down the errors and got these error.

Getting Error while launching the given cloudformation template in us-east-1 region. ( Build lambda Function receives error)

Error: The Build Lambda Function receives the following error.
AccessDeniedExceptionnull (Service: AWSLambdaInternal; Status Code: 403; Error Code: AccessDeniedException; Request ID: 7a8c9e0e-61db-403b-9448-0f5e61beddd4; Proxy: null)
I am trying to run a cloudformation template using below link. While the stack is executing it rollbacks giving above mentioned error.
What may be the probable cause for this issue??
Using this git repo:https://github.com/aws-samples/serverless-machine-learning-on-aws
using this cloudformation template link:https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=serverless-ml&templateURL=https://aws-ml-blog.s3.amazonaws.com/artifacts/serverless-machine-learning-on-aws/template.json
using this blog for creating cloudformation template:https://aws.amazon.com/blogs/machine-learning/deploying-machine-learning-models-as-serverless-apis/
The answer has something to do with the default vpc not being correctly configured in the particular region.
If you try with any other region or another aws account it will definitely work.

AWS Data Pipeline EmrClusterForLoad Error

I'm try to transfer data between s3 and dynamodb with AWSDataPipeline.
error message below...
Unable to create resource for #EmrClusterForLoad_2017-05-15T18:51:19
due to: The supplied ami version is invalid. (Service:
AmazonElasticMapReduce; Status Code: 400; Error Code:
ValidationException; Request ID: 7ebf0367-399f-11e7-b1d7-29efc4730e41)
but, i cannot solve the problem.
help me
aws datapipeline error
ami 3.9.0 is not supported in all regions.
https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-3x.html
Also make sure to select a supported EC2 instance type
https://docs.aws.amazon.com/datapipeline/latest/DeveloperGuide/dp-emr-supported-instance-types.html
Finally you need to set "Resize Cluster Before Running" as false in the Table Load activity.
I made it run after doing all these changes. Hopefully it will help you too.