When using Amazon Elastic Beanstalk with tomcat should I use S3 for all my static content -


currently deploy application war file eb , contains code generating pages plus png's needed rendering pages, happy because in 1 place.

but know can configure s3 bucket website cheaper me , faster user store images in s3bucket configured website , code full s3 path code tags.

but makes deployment more complex because part of deployment handled in tomcat.war. putting images new location 1 thing, if had static pages start affecting urls

i.e if page1 deployed tomcat , page 2 static page urls have like

you said using cloudfront, in case, static files can cached cached on cloudfront (dynamic requests way, if have same url , don't specify no caching), don't see benefit taking static files , putting them on s3. on contrary, have longer down time on upgrades, need update both java , s3 files keep service consistent, or have complex deployment mechanism versions every commit.

unless have terabytes of static images served service (which quite problem deploy anyhow), costs of keeping files on service disks vs. putting them on s3 negligible.


Comments

Popular posts from this blog

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -

ubuntu - Selenium Node Not Connecting to Hub, Not Opening Port -