I'm getting the error below after running the pipepline
Unable to fetch parameters [/cdk-bootstrap/hnb659fds/version] from parameter store for this account. (Service: AmazonCloudFormation; Status Code: 400; Error Code: ValidationError; Request ID: 9bc784ac-193c-4dbe-97c0-4ecb90ce4c2d; Proxy: null)
I'm trying to setup CI/CD via code commit, code deploy, and pipeline. I added another stage in the pipleline for cloudformation but I'm getting this error when I try to run the pipeline.
Source and Build stage Succeeds but it fails on deploy stage.
Related
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.
We have a CodePipeline process set up, and all stages work except the CodeDeploy stage.
Our pipeline stage is as follows:
GenerateChangeSet for CloudFormation
ExecuteChangeSet for CloudFormation
Deploy for CodeDeploy
These stages were set up and configured by CodeStar.
Our GenerateChangeSet stage tries to access s3 to get our BuildArtifact, but fails with the following error:
Action execution failed
Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 40P7HSHQGWXSRA72; S3 Extended Request ID: I6hiCC7xx+YmnQMLfUnMzZziLDz/5b8uJWzOqWNZwSiVRCS14Q6UyVfss6q80teO5MAGuR9Xft4=; Proxy: null)
This suggests that CloudFormation cannot access s3, but I've checked and rechecked the policy that it uses and it definitely has the correct permissions for accessing s3.
I'm not quite sure why this error is happening, given that the role policy does indeed have access to s3. I even went with the nuclear option of granting this role full control over s3 (with a view to reverting once I solved the issue), but to no avail, the error still occurs.
Has anyone encountered this before? Anyone know why it might be happening?
I discovered the issue. The CloudFormation template file (template.yml and template-configuration.yml) was reading the one from the repo, but that had been removed at some point prior, so I was getting access denied errors from that resource.
I wish the error message was more explicit, it would have saved hours.
I am getting the following error on the source stage of my code pipeline:
I feel like I know this means my access token doesn't have access to s3 service, but I do I have created buckets and even ran CLI against it using my access key.
Any tips?
Action execution failed
GitHub Upload to S3 failed with the following error: The AWS Access Key Id needs a subscription for the service (Service: Amazon S3; Status Code: 400; Error Code: KMS.SubscriptionRequiredException; Request ID: NWPB863XQQJV86T2; S3 Extended Request ID: XC5qnepPTZxI0mzF6K3epFPIXpYn+iJiivZqSRjeZ4hR7yVZRAKJT0laFpGZ4twOZYOrusfaZBc=; Proxy: null) (Service: null; Status Code: 0; Error Code: null; Request ID: null; S3 Extended Request ID: null; Proxy: null)
There are a lot of steps to build a CI/CD that works. You have to make sure that you follow each step and all the config settings. The best advice is to follow theses AWS tutorials step by step. I followed these a few weeks ago and they work.
Tutorial: Create a simple pipeline (S3 bucket)
Tutorial: Create a simple pipeline (CodeCommit repository)
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.
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.