You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-3Lines changed: 13 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Then, create an RDS instance, with these properties:
35
35
36
36
### Create an S3 bucket
37
37
38
-
Create an S3 bucket, name it `spring-cloud-aws-sample` and give read permissions to anonymous users. Just copy and paste this aws policy to enable anonymous read access:
38
+
Create an S3 bucket, name it `spring-cloud-aws-sample-s3` and give read permissions to anonymous users. Just copy and paste this aws policy to enable anonymous read access:
39
39
40
40
{
41
41
"Version":"2012-10-17",
@@ -45,7 +45,7 @@ Create an S3 bucket, name it `spring-cloud-aws-sample` and give read permissions
@@ -64,7 +64,7 @@ Create a new secret named as: `/secrets-app/springaws_prod`. You can insert your
64
64
65
65
### To run locally
66
66
67
-
Some configurations are required in your AWS account for this sample to work. Basically, an _S3 bucket_ (by default `spring-cloud-aws-sample` is used, but it can be changed using `cloud.aws.s3.bucket` property), and an _RDS MySQL instance_ open to the world. Additionally, we need an _IAM user_ with access key and programmatic access to AWS API so that we can access AWS resources from our development machine.
67
+
Some configurations are required in your AWS account for this sample to work. Basically, an _S3 bucket_ (by default `spring-cloud-aws-sample-s3` is used, but it can be changed using `cloud.aws.s3.bucket` property), and an _RDS MySQL instance_ open to the world. Additionally, we need an _IAM user_ with access key and programmatic access to AWS API so that we can access AWS resources from our development machine.
68
68
69
69
#### Create an IAM User
70
70
@@ -149,6 +149,16 @@ If your EC2 instance has the appropriate role (see prerequisites above), and the
149
149
150
150
As you can see is not necessary to put database credentials to run the application, it gets the necessary values from AWS Secret Manager.
151
151
152
+
### Using CloudFormation
153
+
154
+
To run with CloudFormation is not necessary to create any AWS resources, only secrets. Steps are the following
155
+
156
+
1. Insert your secret properties as explained in section [AWS Secrets Manager](#aws-secrets-manager)
157
+
2. As parameters to run your stack, you'll need to specify:
158
+
- Database password
159
+
- Key Name (for ssh)
160
+
3. Go to your application by click to the link given at the output section of the cloudformation after the stack have been created.
0 commit comments