- Newest
- Most votes
- Most comments
Based on the error messages you've shared, it appears you're encountering issues with your Docker deployment on AWS Elastic Beanstalk. The main error suggests there's a problem with the Fn::Join function in your CloudFormation template, which is likely part of your Elastic Beanstalk configuration.
To resolve this issue, you should:
-
Check your .ebextensions folder and any configuration files within it. Look for any CloudFormation resources or outputs that use the Fn::Join function. Ensure that this function is correctly formatted with two parameters: a delimiter and a list of values to join.
-
Verify your Dockerrun.aws.json file. Make sure it's properly formatted and contains all necessary information for your Docker deployment.
-
If you're trying to mount an EFS volume, ensure that the configuration for this is correct. Sometimes, mounting EFS can cause issues if not configured properly.
-
Double-check your Docker image and make sure it's correctly specified in your configuration.
-
Validate your JSON files using a JSON validator to catch any syntax errors.
If these steps don't resolve the issue, you might want to try deploying a simpler version of your application first to isolate the problem. Start with a basic Docker container and gradually add complexity until you identify the specific configuration causing the error.
Remember, Elastic Beanstalk deployment issues can often be diagnosed by checking the full logs. You can access these through the AWS Management Console or by using the EB CLI tool.
If you're still stuck after trying these steps, consider providing more details about your application structure, Dockerrun.aws.json file, and any .ebextensions configurations you're using. This would help in providing more specific guidance.
Sources
eb deploy is failing with error Service:AmazonCloudFormation, Message:Template error: every Fn::Join object requires two parameters | AWS re:Post
Troubleshooting Elastic Beanstalk - Categories and FAQs - AWS Elastic Beanstalk
I would like to convey my apologies, as I'm new to AWS started like 2 months ago and yet I'm still learning about it more and more. As you said I don't have ".ebextensions" but I have created a ec2-role in the IAM and using GPT I've added all the permission that is required for Docker deployment. I'll upload the Dockerfile and Dockerrun.aws.json file screenshot. Please have a look.
Relevant content
- asked 2 years ago

Attached another query