|
|
|
Here I will try to put the issues I got during AWS use & the workaround or Solution I used for those.
Issue : Billing metrics is not available to create the alarm in AWS.
Solution : Check if you are pointing to region US East (N. Virginia). Billing metric data is stored in this Region and reflects
worldwide charges.
Issue : Creation of Security Groups. When you create a new Security Group & as the page having list of Security Groups is loaded then control returns back to the previously selected SecurityGroup, so keep this in mind before making any
change in your new Group, as shown in below image.
Another missing feature on Security Group page is the help for the circled clickable icons.
Solution : 1st icon minimizes the property window of security group, second is the default size & third one maximizes the
window.
Issue : Billing metrics is not available to create the alarm in AWS.
Solution : Check if you are pointing to region US East (N. Virginia). Billing metric data is stored in this Region and reflects
worldwide charges.
Issue : Creation of Security Groups. When you create a new Security Group & as the page having list of Security Groups is loaded then control returns back to the previously selected SecurityGroup, so keep this in mind before making any
change in your new Group, as shown in below image.
Another missing feature on Security Group page is the help for the circled clickable icons.
Solution : 1st icon minimizes the property window of security group, second is the default size & third one maximizes the
window.
A good article to read, though it is old one & many things would have changed by the time you read it.
https://www.percona.com/blog/2018/07/17/when-should-i-use-amazon-aurora-and-when-should-i-use-rds-mysql/
https://www.percona.com/blog/2018/07/17/when-should-i-use-amazon-aurora-and-when-should-i-use-rds-mysql/
| running-containerized-microservices-on-aws.pdf |
Issue : I am connected to my AWS on CLI using Access Key ID & Secret Access Key. But I didn't save those credentials anywhere on my machine & now I need to connect to my AWS on another CLI window simultaneously.
How can I do this?
Solution : If you are still connected to AWS in any one CLI then you get those credentials. Just Do -
> cd ~/.aws
> ls
You will credentials file there.
> cat credentials
Now you have those credentials to use.
===============================================================================================
If I connect to my AWS on different CLI to the same EC2 instance then I am able to see the commands list which I used earlier. Condition is instance should be same.
===============================================================================================
How can I do this?
Solution : If you are still connected to AWS in any one CLI then you get those credentials. Just Do -
> cd ~/.aws
> ls
You will credentials file there.
> cat credentials
Now you have those credentials to use.
===============================================================================================
If I connect to my AWS on different CLI to the same EC2 instance then I am able to see the commands list which I used earlier. Condition is instance should be same.
===============================================================================================
| practicing-continuous-integration-continuous-delivery-on-aws.pdf |
