Shibboleth Idp3 as docker install on AWS

[Alex Poulos]

The main benefit for any deployment, IdP included, is that you have a
single immutable artifact that contains most of your environment
(code+config instead of just code). This makes testing things in different
environments (locally, dev, qa, prod, etc.) easier. Deployments are
generally easier too: you update a parameter specifying the new container
tag and the orchestration software (docker swarm/amazon ecs/kubernetes vel
sim.) takes care of deploying the new code/config in whatever manner you
desire. Roll backs are also easier: just deploy the old container.

All of this is achievable with other means (puppet, ansible, etc...). But
containers are a particularly good way to go about it.

On Thu, May 14, 2020 at 8:56 AM Joseph Fischetti <
Joseph.Fischetti at marist.edu> wrote:

> I'm genuinely curious, because I've seen plenty of discussion about
> running the IdP in docker.
>
> What's the benefit?
>
> I understand many of the benefits of docker in general.  I don't see how
> those fit into an IdP deployment.
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200514/1532e212/attachment.htm>