Exposing artifacts in S3

Exposing artifacts in S3 rely on the s3-generic bucket provided by platform team, but any custom S3 bucket can also be used.

The s3-generic bucket is a general purpose s3 bucket which we programmatically create in all AWS accounts. If your Domain is e.g. mops, you have access to 3 s3-generic buckets: s3-generic-mops-dev, s3-generic-mops-int & s3-generic-mops-prod.

Frontend applications

In order to build and deploy front-end applications, you can rely on auto-devops. To deploy a frontend, configure your project to run in dynamic (or dynamic ejected) configuration

You will also need to configure the CI operations in your package.json file

You can then configure the exposition properties using the variables EXPOSED_CDNS, EXPOSED_DOMAIN_PATH, AUTHENTICATION_TYPE

Feel free to reach us on #somebody-to-love to achieve a finer configuration.

Other artifacts

In the cases where the build of the artifacts cannot be handled by auto-devops, we recommend to use the s3-ingress flavor of our base chart. An example can be found here. The chart should be configured in the k8s folder of the project, as described in the auto-devops documentation