S3 Image Upload Guide for CodiMD
Note: This guide was written before the renaming. Just replace HackMD
with CodiMD
in your mind
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
thanks!
-
Go to AWS S3 console and create a new bucket.
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Click on bucket, select Properties on the side panel, and find Permission section. Click Edit bucket policy.
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Enter the following policy, replace bucket_name
with your bucket name:
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Go to IAM console and create a new IAM user. Remember your user credentials(key
/access token
)
-
Enter user page, select Permission tab, look at Inline Policies section, and click Create User Policy
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Select Custom Policy
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Enter the following policy, replace bucket_name
with your bucket name:
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
-
Edit config.json
and set following keys:
-
In additional to edit config.json
directly, you could also try environment variable.