- Newest
- Most votes
- Most comments
Looking for config file [samconfig.toml] : Found
You already have samconfig.toml. Did you download and use the working code? (URL could not be verified)
Usually, the first time you do sam deploy --guided
, you create an S3 bucket and set the created S3 information in samconfig.toml
.
If this is your first time deploying, you can delete samconfig.toml
and try it and see.
When you first run the SAM cli, it creates a CloudFormation stack called aws-sam-cli-managed-stack which creates an S3 bucket thats used to managed SAM deployments (unless you specify another S3 bucket) , and a bucket policy. It seems that this bucket has been deleted. You can verify this by looking at the outputs of the managed stack and verifying that the bucket name listed under SourceBucket
still exists. To fix this, you can delete the aws-sam-cli-managed-stack and run sam deploy --guided
again.
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks for your reply. I fixed the URL. It was not formatted properly.
Thanks, I checked the URL.
Strangely, S3 is not found, since S3 should be created automatically when this procedure is executed for the first time. I recommend deleting
samconfig.toml
and tryingsam deploy --guided
again.I will try this out shortly and let you know. Of course the SAM CLI and framework requires an S3 bucket for uploading the artifacts created. If I delete the configuration file then it will create an S3 bucket and update / create the config file with the name of the S3 bucket, once the process is completed.. That is what I have understood. Thanks once again for your answer
I tried deleting
samconfig.toml
and runningsam deploy --guided
. It doesn't work. For some reason it is looking for a managed S3 bucket calledaws-sam-cli-managed-default-samclisourcebucket-22dlzjzisaai
. I am trying to understand why this is happening